Help shape GoConqr. What should we add next?

Slides

The Unified Process

César Eugenio Jiménez García Spanish 7 slides

Slides in this set (7)

  1. Unified Process

    • Is an iterative and incremental software development framework from which a customized process can be definied. The most popular variations include the Rational Unified Process and the Open Unified Process.
  2. Key Characteristics and Practices

    • -It is an iterative and incremental development framework.
    • -It is risk-focused and emphasizes that highest-risk factors be addressed in the earliest deliverables possible.
    • -It is use-case and UML model driven with nearly al requirements being documented in one of those forms.
    • 1.-Develop Software Iterativaly
    • 2.-Manage Requirements
    • 3.- Use component-based Architectures
    • 4.- Visually Model Software
    • 5.- Verify Software Quality
    • 6.-Control Changes to Software
  3. Components of the UP:

    • -Cycles
    • -Phases
    • -iterations
    • -Disciplines (also known as Workflows)
    • -Activities
    • -Artifacts
    • -Workers
  4. THE DISCIPLINES

    • Business Modeling: Focuses on efforts to understand the organization, its process and the problem domain.
    • The factors for the Business Modeling are:
    • -Enterprise business rules
    • -Enterprise business process model
    • -Enterprise domain model
    • -Enterprise mission statement
    • -Enterprise vision
    • -Organization model
  5. Slide 5

    • Requirements: Is like the requirements discipline in pretty much every other software process.
    • The main difference is that RUP requirements are highly focused in the form of UML models and Use Cases.
    • The Analysis and Design dlsclpline would be better named the Solution Analysis and Design discipline In my opinion. This Is because the requirements are analyzed from a solution design perspective, rather than a requirements analysis perspective.
  6. Slide 6

    • Implementation consists of coding, unit testing, and integration of the software.
    • Testing is focused on quality assurance of the software being released in that cycle oriteration.
    • The Deployment discipline is focused on planning the deployment of, and actually deploying, the software that is being completed that cycle, phase or iteration.
    • The Configuration and Change Management discipline is focused on managing change to the project’s work products.
    • The Project Management discipline is focused on standard project management activities.
    • The Environment discipline is focused on supporting the overall project and development efforts through managing environmental factors.
  7. The Phases

    • The Inception Phase Is the part of the framework when the "why" of the development effort ls deflned.
    • The Elaboration Phase Is the part of the framework when more detailed analysis and planning are undertaken to better understand the problem domain, develop a more concrete project plan, identify and eliminate the high-risk elements of the effort, and to establish a solid architectural foundation for the software to be developed.
    • The Construction Phase is the part of the framework where software development, integration, and testing takes place. Because of the emphasis on component-based architectures and the significant attention paid to the architectural plan in the Inception and Elaboration phases.
    • The Transition Phase of the framework is where the software is deployed to end users and is essentially a broad "beta" test of the application. Users begin to use the new software, issues are identified and potentially corrected, and any features that were delayed are finished and deployed.

Information

Description
Slide Set on The Unified Process, created by César Eugenio Jiménez García on 26/07/2017.
Views
12
Rating

More on Software Development Life Cycle Models

Feedback

What is it about?

What should we add next?