EE493'05 Rational Unified Process

1
EE493.05Rational Unified Process
Royal Military College of Canada Electrical and
Computer Engineering

• Professor Greg Phillips
• Greg.Phillips_at_rmc.ca
• 1-613-541-6000 ext. 6656

Major JW Paul Jeff.Paul_at_rmc.ca 1-613-541-6000
ext. 6091
2
Monday Meanderings
3
Review

• What are the key features of the Spiral Model
• risk reduction process
• iterative reuse
• off-ramps
• Five Steps
• set objective
• prototype soln
• build soln
• evaluate soln
• plan next phase

4
Todays Class

• RUP

5
RUP - Definition

• Rational Unified Process (RUP) is an
  object-oriented and web-enabled program
  development methodology... According to Rational
  (developers of Rational Rose and the Unified
  Modeling Language), RUP is like an online mentor
  that provides guidelines, templates, and examples
  for all aspects and stages of program
  development. RUP and similar products -- such as
  Object-Oriented Software Process (OOSP), and the
  OPEN Process -- are comprehensive software
  engineering tools that combine the procedural
  aspects of development (such as defined stages,
  techniques, and practices) with other components
  of development (such as documents, models,
  manuals, code, and so on) within a unifying
  framework.
• http//whatis.techtarget.com/

6
Core Concepts

• Best Practices
• Match process to project
• Integrate support tools
• Artifacts are output of process
• Project Management Approach

7
6 best practices

• Develop software iteratively
• Manage requirements
• Use component-based architectures
• Visually model software UML
• Verify software quality
• Control changes to software

8
Unified Process - Phases
Engineering Stage
Production Stage
Inception
Elaboration
Construction
Transition
idea
architecture
beta releases
products
functionality
quality
9
Unified Process - Phases
Engineering Stage
Production Stage
Inception

• achieve concurrence among stakeholders on
  objectives
• identify critical use cases and the primary
  scenarios likely to drive design
• demonstrate at least one candidate architecture
• estimate the cost and schedule for entire project
• estimate potential risks

idea
10
Unified Process - Phases
Engineering Stage
Production Stage
Elaboration

• baseline the architecture
• baseline the vision
• baseline a high fidelity plan for construction
• demonstrate that the architecture supports the
  vision at a reasonable cost in a reasonable time

architecture
11
Unified Process - Phases
Engineering Stage
Production Stage
Construction

• minimize development costs by optimizing
  resources and avoiding scrap/rework
• achieve adequate quality as rapidly as possible
• achieve useful versions as rapidly as possible
• assess product releases against vision

beta releases
12
Unified Process - Phases
Engineering Stage
Production Stage
Transition

• beta test to validate user expectations
• beta test / parallel operations relative to
  legacy system (if applicable)
• conversion of data / databases
• training of users and maintainers
• achieve final product baseline
• achieve stakeholder concurrence that deployed
  product meets vision

products
13
Artifacts process work products

• Five sets
• Management Set
• Requirements Set
• Design Set
• Implementation set
• Deployment Set
• Artifacts of a modern process should be natural
  direct outputs of the process
• as opposed to the conventional low-value tree
  killers

14
Management Set

• Planning Artifacts
• work breakdown structure
• business case
• release specifications
• software development plan

• Operational Artifacts
• release descriptions
• status assessments
• software change order database
• deployment documents

15
Engineering Set

• Requirements Set
• vision document
• operational concept
• change risks
• requirements model(s)
• use cases
• scenarios
• collaborations, etc.

• Design Set
• design model
• class diagrams
• collaborations
• state charts, etc.
• test model
• software architecture description

16
Production Set

• Implemenation Set
• source code baseline
• compile-time files
• component executables

• Deployment Set
• integrated product executable baselines
• run-time files
• user manual

17
Workflows of the Process
Management
Environment
Requirements
Design
Implementation
Assessment
Deployment
18
Tailoring the Process

• a process framework is not a paint-by-numbers
  procedure for success
• judgement and tailoring is essential
• no one recipe fits all organizations, projects
  and domains
• considerations
• scale or size of software application
• stakeholder cohesion or contention
• process flexibility
• process maturity
• architectural risk
• domain experience

19
Tailoring the Process
High Technical Complexity

• more domain expertise
• longer inception/elaboration phases
• more iterations for risk management
• less predictable costs/schedules

• embedded, real-time, distributed
• fault-tolerant, portable
• unprecedented

• High Management Complexity
• large scale, contractual
• many stakeholders
• projects

• Low Management Complexity
• smaller scale
• informal, few stakeholders
• products

• less emphasis on risk management
• emphasis on individual skills
• longer production/transition phases

• emphasize risk management
• emphasize teamwork
• more process formality
• longer inception/elaboration

Low Technical Complexity

• straightforward automation
• single platform
• many precedents

• emphasize existing assets
• shorter inception/elaboration phases
• fewer iterations, more predictable costs

20
Developing Methodology
21
Summary
from www.rational.com
22
Review

• What are the core concepts?
• Best Practices
• Match process to project
• Integrate support tools
• Artifacts are output of process
• Project Management Approach

23
Review

• What are artifacts?
• Management Set
• Requirements Set
• Design Set
• Implementation set
• Deployment Set
• Should all exist at all phases (to varying
  degrees)

24
Conclusion - RUP is a framework

• Iterations of the workflows microprocess
• management/requirements/design/code/assess/deploy
• Across
• Engineering Construction macroprocess
• inception / elaboration / construction /
  transition
• emphasize pragmatic, value-added artifacts
• on-line reviews, self-defining, self-documenting
• tailored framework
• depends on complexity technical management

25
Questions?
26
Next Class

• Project Planning and Control

27
Workflows of the Process
Management

• planning the project
• controlling the project
• organization
• ensuring win conditions for all stakeholders

28
Workflows of the Process
Environment

• automating the project
• evolving the maintenance environment
• evolving the change order database

29
Workflows of the Process
Requirements

• analyzing the problem space
• evolving the requirements artifacts

30
Workflows of the Process
Design

• modeling the solution
• evolving the architecture
• evolving the design artifacts
• (includes test artifacts)

31
Workflows of the Process
Implementation

• programming / acquiring / modifying the
  components
• integrating and testing all new and modified
  components
• evolving the implementation artifacts
• evolving the deployment artifacts

32
Workflows of the Process
Assessment

• assessing the trends in process
• assessing the product quality
• assessing the product against the vision
• identifying rework and scrap

33
Workflows of the Process
Deployment

• transitioning the product to the end user /
  maintainer
• conducting a post-mortem