Rational Unified Process Flashcards

1
Q

RUP

A

Rational Unified Process

  • A sample process model
  • Captures many of the best practices in modern software development
  • Designed for incremental software development
  • Widely used
  • Emphasizes the development and maintenance of (UML) models with sematically rich representations of the software system under development.
  • IBM Course
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

RUP Phases

A
  • Inception
  • Elaboration
  • Construction
  • Transition
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Inception Phase

A
  • Establish project scope and boundary conditions
  • Determine the use cases and primary scenarios that will drive the major design trade-offs
  • Demonstrate a candidate architecture against some of the primaru scenarios
  • Esimate the overall cost and schedule
  • Identify potential risks (the sources of unpredictability)
  • Prepare the supporting environment for the project.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Elaboration Phase

A
  • Define, validate and baseline the architecture as rapidly as is practical.
  • Baseline the vision
  • Refine support environment
  • Baseline a detailed plan for the construction phase
  • Demonstrate that the baseline architecture will support the vision at a reasonable cost in a reasonable period of time.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Construction Phase

A
  • Complete the software product for transition to production
  • Minimize development costs by optimizing resources and avoiding unnecessary scrap and rework.
  • Achieve adequate quality as rapidly as is practical
  • Achieve useful vesions (alpha, beta, and other test releases) as rapidly as possible.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Transision Phase

A
  • Achieve user self-supportability
  • Achieve stakeholder concurrence that deployment baselines are complete and consistent with the evaluation criteria of the vision.
  • Achieve final product baseline in a rapid and cost-effective manner.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is an iteration?

A

A distinct sequence of activities with a baseline plan and evluation criteria resulting in a release (internal or external)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is the duration of an iteration?

A
  • Begins with planning and requirements and ends with an internal or external release
  • Ideally should run from 2 - 6 weeks, depending on your project size and complexity.
  • Factors that affect duration of an iteration:
    • Size, stability, maturity of an organization
    • Familiarity with the iterative process
    • Size of the project
    • Technical simplicity of project
    • Level of automation used to manage code, distribute information, perform testing.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the rule of thumb for the number of iterations?

A

Use 6 +/- 3 iterations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is an iteration plan?

A
  • An outline of an iteration plan.
  • Contains an iteration schedule section for requirements discipline.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Concepts that drive iterative development

A
  • Early mitigation of risk
  • Early base-lining of architecture
  • Use of objective metrics
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is the definition of risk?

A

An ongoing or upcoming concern that has a significant probability of adversely affecting the success of major milestones.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are some risk types?

A
  • Technical/Architectural Risks
    • Unproven technology, uncertain scope
  • Resource Risks
    • People, skills, funding
  • Business Risks
    • Competition, ROI, supplier interfaces
  • Schedule Risks
    • Project dependencies
    • Only 24 hours in a day
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is a Risk List Artifact?

A

An identification and prioritization of risks and risk types.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is a direct risk?

A

A direct risk is when the project has a large degree of control.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is an indirect risk?

A

An indirect risk is when the project has little or no control.

17
Q

What is risk magnitude?

A

Risk magnitude is used for ranking risks. It is a combination of:

  • Probability of occurrence
  • Impact on the project (severity) e.g. project delays.
18
Q

Risk Management Strategies

A

Risk avoidance, risk transfer or risk acceptance

Mitigage accepted risks by:

  • Creating a Risk List Artifact
  • Taking some immediate, pro-active steps to reduce the probability or the impact of the risk.
  • Defining a contingency plan.
19
Q

7 Core Metrics

A
  • Work and progress - iteration planning, plan vs. actuals, management indicator
  • Budgeted cost and expenditures - financial insight, plan vs. actuals, management indicator
  • Staffind and team dynamics - Resource plan vs. actuals, hiring rate, attrition rate
  • Change traffic and stability - iteration planning, management indicator of schedule convergence
  • Breakage and modularity - Convergence, sotware scrap, quality indicator
  • Rework and adaptability - Convergence, software rework, quality indicator
  • MTFB and maturity - Test convergence/adequacy, robustness for use, quality indicator