Rational Unified Process Flashcards
1
Q
Phases - Inception
A
- Define the scope and develop business case
- Milestone 1: Objectives
2
Q
Phases - Elaboration
A
- Plan the project, understand the domain and the architecture
- Milestone 2: Architecture
3
Q
Phases - Construction
A
- Build the product
- Milestone 3: Initial operational capability
4
Q
Phases - Transition
A
- Deploy the system in its operating environment
- Milestone 4: Product release
5
Q
Should we start (continue) the project?
Inception - Tasks
A
- Identify all major use cases
- work out the details of the most important ones - Perform a risk analysis
- Define
- success criteria for the project (important deliverables)
- needed resources
- important milestones (customer point of view)
6
Q
Should we start (continue) the project?
Inception - Results and Deliverables
A
- Project scope definition
- Most important requirements
- initial use case model - Initial project plan
- most important milestones
- coarse cost estimation
- project deliverables - Initial model of the application domain (domain model)
- Glossary
7
Q
Elaboration
A
- Do we know what to deliver?
- Do we have an appropriate architecture?
- Can we control the risks?
8
Q
Elaboration - Tasks
A
- Work out use cases in detail
- Identify and formulate non-functional requirements
- Design the top-level architecture
- Create first prototype
- Detail the project plan
9
Q
Elaboration - Results and deliverables
A
- Extended use case model
- Use cases (80% written and reviewed by end of phase)
- Use case Model (80% done)
- Non-functional requirements - Top-level architecture
- Prototypes
- Revised project plan
- Chosen development technology
10
Q
Can we develop the system?
Construction - Tasks
A
- Select use cases to be implemented
- Work out in detail the use cases (if necessary)
- Revise the architecture (if necessary)
- Implement the use cases
- Test the resulting system
11
Q
Can we develop the system?
Construction - Results and deliverables
A
- Tested system release
- User documentation
- System documentation of the developed release
12
Q
Transition
A
- Are all requirements implemented?
- Do we have to perform a further development cycle?
13
Q
Transition - Tasks & Result
A
Tasks:
1. Transfer the system to the user
- includes, shipping, installation, training, technical support, and maintenance
2. Integration with existing systems
- legacy, existing versions, etc.
3. Development team begins to shrink
Result: Final system
14
Q
Process Customization
A
- A generic process model has to be customized
- Complexity and size of the project
- Culture of the development organization - Aspects to be customized
- Artifacts: Only those artifacts valuable for the project should be created
- Workflows: Not needed activities can be removed, others can be combined
- Roles: Can be combined
15
Q
Five Best Practices
A
- Develop the system in an iterative way - driven by risks
- Manage the requirements with use cases
- Focus on the architecture. Build the system with well delimited components
- Continuously review and test the system
- Manage changes in a controlled way
