Friday, February 15, 2008
Principles of The RUP
Attack major risks early
Deliver value
Focus on executable software
Allow change
Establish an architecture
Componentize
Work as a team
Quality
Rup is irerative as opposed to waterfall.
static structure of rup:
activites, roles, disciplines, artifacts
dynamic structure of rup
time/phases: inception, elaboration, construction, transition
Subsequent Milestones
Lifecycle objective milestone
Lifecycle architecture milestone
Initial operation capability milestone
Product milestone
Objectives of the Inception Phase
Understand what to build
Identify key system functionality
Determine at least one possible solution
Understand the cost schedule and risks
Decide what process to follow and what tools to use.
Lifecycle Object Milestone Criteria
Stakeholder agreement on scope and initial cost schedule estimate
Agreement that the right requirements hve been captured
Agreement that the cost/schedule estimate, priorities, risks, and developement process are appropriate
Have identified risks and a mitigation strategy has been defined
Objectives of the Elaboration Phase
get a more detailed understanding of the requirements
design, implement, validate, and baseline the architecture
Mitigate essential risks, and produce more accurate schedule and cost estimates
refine the developement case and put the developement environment in place
Lifecycle Architecture Milestone Criteria
vision and requirements are stable
architecture is stable
approaches to testing and evaluation are proven
executable prototype shows the major risks have been addressed and resolved
construction plans are sufficient
iteration plans for construction phase have credible estimates
stakeholders agree the vision can be met by current architecture
actual resources are acceptable in terms of planned resources
Objectives of the Construction Phase
Minimize developement costs and achieve some degree of parallelism
Scale up the project
Build and assess several internal releases
Iteratively develop a complete product that is ready to transition to its user community
Initial Operation Capability Milestone Criteria
product release is stable and mature enough to be released in the user community
stakeholders are ready for transition into the user community
actual resources are still acceptable in terms of planned resources
Objectives of the Transition Phase
Beta test to validate user expectations are met.
Train users and maintainers to achieve user self-reliability
Prepare deployment site and convert databases
prepare for launch packaging, production and market rollout; release to sales force; personnel training
Achieve stakeholder agreement that deployment baselines are complete and consistent with vision
Improve project performance through lessons learned
Product Release Milestone Criteria
The user is satisfied
actual resources are acceptable in terms of planned resources and if not what can aid this in the future
Key modeling elements of the RUP
roles - how the individual should do the work
activity - a unit of work that one in role is to perform usually effecting an artifact
artifact - a piece of info that is produced modified or used by a process
workflow - adds meaning to sequence of activities that produce value and show interaction between roles.
disciplines - are high level workflows and containers for roles, activities and artifacts
workflow details - workflows within a discipline
usecase- a section in the future user manual for the system under developement
low ceremony - low documentation and formalism in the procedure
high ceremony - comprehensive documentation and traceability maintained between artifacts, change control boards, etc.
Agile - low ceremony
disciplined - high ceremony
discipline - partition of activities by type
baseline - A specification or product that has been formally reviewed and agreed upon, that serves as the basis for further development, and that can be changed only through formal change control procedures.
Development Cycle - one pass through the four RUP phases
Development Case - a brief description of how your project should use your RUP Configuration
RUP Process Component - a module of process knowledge
RUP Library - a collection of process components out of which a set of RUP Process Configuration may be compiled
RUP Base - a collection of process components meant to be extended by applying plugins to generate RUP process configurations. It resides in a RUP library
RUP Plugin - a unit for one or several process components that can extend a RUP base
The RUP Phases
Inception
Objectives of the inception phase
Understand what to build - determine vision, scope, and boundaries
Identify key system functionality - determine which ways of using the system are critical
determine at least one possible solution - decide on a candidate structure
Undertand Costs, Schedules, and risks
Decide on what process to follow and what tools to use.
Introducing The RUP to a project
Assess
Plan
Configure and customize
Execute
Evaluate
Attack major risks early
Deliver value
Focus on executable software
Allow change
Establish an architecture
Componentize
Work as a team
Quality
Rup is irerative as opposed to waterfall.
static structure of rup:
activites, roles, disciplines, artifacts
dynamic structure of rup
time/phases: inception, elaboration, construction, transition
Subsequent Milestones
Lifecycle objective milestone
Lifecycle architecture milestone
Initial operation capability milestone
Product milestone
Objectives of the Inception Phase
Understand what to build
Identify key system functionality
Determine at least one possible solution
Understand the cost schedule and risks
Decide what process to follow and what tools to use.
Lifecycle Object Milestone Criteria
Stakeholder agreement on scope and initial cost schedule estimate
Agreement that the right requirements hve been captured
Agreement that the cost/schedule estimate, priorities, risks, and developement process are appropriate
Have identified risks and a mitigation strategy has been defined
Objectives of the Elaboration Phase
get a more detailed understanding of the requirements
design, implement, validate, and baseline the architecture
Mitigate essential risks, and produce more accurate schedule and cost estimates
refine the developement case and put the developement environment in place
Lifecycle Architecture Milestone Criteria
vision and requirements are stable
architecture is stable
approaches to testing and evaluation are proven
executable prototype shows the major risks have been addressed and resolved
construction plans are sufficient
iteration plans for construction phase have credible estimates
stakeholders agree the vision can be met by current architecture
actual resources are acceptable in terms of planned resources
Objectives of the Construction Phase
Minimize developement costs and achieve some degree of parallelism
Scale up the project
Build and assess several internal releases
Iteratively develop a complete product that is ready to transition to its user community
Initial Operation Capability Milestone Criteria
product release is stable and mature enough to be released in the user community
stakeholders are ready for transition into the user community
actual resources are still acceptable in terms of planned resources
Objectives of the Transition Phase
Beta test to validate user expectations are met.
Train users and maintainers to achieve user self-reliability
Prepare deployment site and convert databases
prepare for launch packaging, production and market rollout; release to sales force; personnel training
Achieve stakeholder agreement that deployment baselines are complete and consistent with vision
Improve project performance through lessons learned
Product Release Milestone Criteria
The user is satisfied
actual resources are acceptable in terms of planned resources and if not what can aid this in the future
Key modeling elements of the RUP
roles - how the individual should do the work
activity - a unit of work that one in role is to perform usually effecting an artifact
artifact - a piece of info that is produced modified or used by a process
workflow - adds meaning to sequence of activities that produce value and show interaction between roles.
disciplines - are high level workflows and containers for roles, activities and artifacts
workflow details - workflows within a discipline
usecase- a section in the future user manual for the system under developement
low ceremony - low documentation and formalism in the procedure
high ceremony - comprehensive documentation and traceability maintained between artifacts, change control boards, etc.
Agile - low ceremony
disciplined - high ceremony
discipline - partition of activities by type
baseline - A specification or product that has been formally reviewed and agreed upon, that serves as the basis for further development, and that can be changed only through formal change control procedures.
Development Cycle - one pass through the four RUP phases
Development Case - a brief description of how your project should use your RUP Configuration
RUP Process Component - a module of process knowledge
RUP Library - a collection of process components out of which a set of RUP Process Configuration may be compiled
RUP Base - a collection of process components meant to be extended by applying plugins to generate RUP process configurations. It resides in a RUP library
RUP Plugin - a unit for one or several process components that can extend a RUP base
The RUP Phases
Inception
Objectives of the inception phase
Understand what to build - determine vision, scope, and boundaries
Identify key system functionality - determine which ways of using the system are critical
determine at least one possible solution - decide on a candidate structure
Undertand Costs, Schedules, and risks
Decide on what process to follow and what tools to use.
Introducing The RUP to a project
Assess
Plan
Configure and customize
Execute
Evaluate
posted by Joe at
11:03 AM
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home