Reviewing RUP

1
Reviewing RUP
2
What is RUP

• It is a software engineering process, aimed at
  guiding software development
• It has a well defined and regular structure,
  using a object-oriented approach for its
  description
• It is designed and documented using the Unified
  Modelling Language (UML)

3
Process Structure

• Two dimensions.
• Horizontal axis represents time and shows the
  lifecycle aspects of the process as it unfolds.
• Dynamic aspect of the process -gt cycles, phases,
  iterations and milestones
• Vertical axis represents core process workflows,
  which group activities logically by nature.
• Static aspect of the process -gt activities,
  disciplines, artifacts and roles

4
2 Dimensions of RUP
5
Phases

• Inception
• Elaboration
• Construction
• Transition

6
Inception Objectives

• Establish software scope and boundary conditions.
• Discriminate critical Use Cases of the system.
• primary scenarios of behaviour.
• Exhibit at least one candidate architecture.
• Estimate overall cost.
• Estimate risks.

7
Inception Activities

• Formulate scope of project
• Plan and prepare a business case and evaluate
  alternatives for risk management, staffing,
  project plan
• Synthesise a candidate architecture.

8
Outcome of Inception

• A vision document, i.e., a general vision of
  the core projects requirements, key features and
  main constraints.
• A Use-Case model survey all Use Cases and
  Actors that can be identified so far.
• An initial project glossary.
• An initial business case including business
  context, success criteria and financial forecast.
• Initial risk assessment.
• Project plan, with phases and iterations.

9
Other Artifacts Produced

• Initial Use Case model (10-20 complete)
• A domain model static picture of scope.
• A business model (if necessary) workflow.
• A preliminary development case description to
  specify the process used.
• One or several prototypes.
• Behavioral, Structural, Exploratory or
  Evolutionary.

10
Evaluation Criteria at End

• Agreement on scope definition and cost and
  schedule estimates
• Requirements understanding as shown by the
  correctness of the primary Use Cases.
• Credibility of the cost and schedule estimates,
  priorities, risks and development process.
• Depth and breadth of any architectural prototype
  that was developed.
• Actual expenditure v planned expenditure.
• If the project fails to pass this milestone, it
  may be cancelled / rethought.

11
Our work so far .

• Requirements elicitation
• Requirements specification
• Use case model
• Activity diagram
• Initial class diagram
• Initial sequence diagram
• Acceptance criteria
• Post-conditions for each use-case should be
  tested to see if they match user expectations.
• Project planning
• Financial planning is outside the scope of these
  modules.

Software Architecture
12
Inception complete

• Once the Inception phase is complete,
• There is an overall, coarse-grained plan.
• There is a fine-grained plan for the first
  iteration.
• Each iteration must go through
• Elaboration
• Construction
• Transition.