Beruflich Dokumente
Kultur Dokumente
Outline
What is UP? UP History UP Axioms UP Core Workflows UP Structure Details on UP Phases
1/32
What is UP?
A software development process (SDP) or software engineering process (SEP) defines the who, what, when, and how of developing software The Unified Software Development Process (USDP) or, in short, the Unified Process (UP) is an industry standard process created by the authors of UML
2/32
UP History
UP evolution,
3/32
UP Founders
Grady Booch
Video: why engineering? Video: the promise, the limits, the beauty of software Video: smarter products for a smarter planet
4/32
UP Axioms
Use case and risk driven Architecture centric Iterative and incremental
Each iteration contains all the elements of a regular software development project: planning, analysis, design, construction, integration, testing, internal or external release
5/32
UP Core Workflows.
Requirements: Determining what the system should do Analysis: Refining and structuring the requirements Design: Defining system architecture to satisfy requirements Implementation: Building the software Testing: Verifying that the implementation is correct
A baseline is the result of an iteration, a partially complete version of the final system. An iteration is the difference between two consecutive baselines.
6/32
7/32
UP Structure.
8/32
UP Structure
9/32
Details of the above for Inception are given next. The remaining three phases are described in Subsection 2.9 of the textbook
10/32
Inception
amount of work in each core workflow
Requirements establish business case and scope. Capture core requirements
Inception Elaboration Construction Transition
12
Inception - milestone
Life Cycle Objectives - conditions of satisfaction:
System scope has been defined Key requirements for the system have been captured. These have been defined and agreed with the stakeholders An architectural vision exists. This is just a sketch at this stage A Risk Assessment A Business Case Project feasibility is confirmed The stakeholders agree on the objectives of the project
13
Elaboration
Requirements refine system scope and requirements Analysis establish what to build
Inception Elaboration
R A D
Construction
Transition
Focus Goals
14
Elaboration - milestone
Lifecycle Architecture - conditions of satisfaction:
A resilient, robust executable architectural baseline has been created The Risk Assessment has been updated A project plan has been created to enable a realistic bid to be formulated The business case has been verified against the plan The stakeholders agree to continue 15
Construction
R A
Requirements uncover any requirements that had been missed Analysis finish the analysis model
Inception Elaboration Construction
Transition
Focus Goals
16
Construction - milestone
Initial Operational Capability - conditions of satisfaction:
The product is ready for beta testing in the user environment
17
Transition
D
Requirements not applicable Analysis not applicable
Inception Elaboration Construction
Transition
Focus Goals
18
Transition milestone
Product Release - conditions of satisfaction:
Beta testing, acceptance testing and defect repair are finished The product is released into the user community
19