The Unified Process Flashcards

1
Q

What is the Unified process?

A

The unified process is an agile software development process that can be rigorous and document-led, but also iterative and evolutionary.

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

Can UP accommodate Scrum?

A

Yes

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

When does development start in UP

A

Development starts before the exact software requirements have been specified.

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

In UP what is used to clarify,correct and improve the evolving specifications?

A

Feedback

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

What is an iteration in UP

A

An iteration is a time-boxed mini-project during which an increment of software is developed.

It is also called a sprint.

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

What happens during each iteration in UP

A

Each iteration contains an analyzed, designed, coded, and tested chunk of future software.

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

How often does each phase happen in UP

A

Almost daily

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

In which iteration should an executable be created in UP?

A

Every iteration in UP must include coding and produce an executable that is potentially shippable. (Even the first)

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

Why is change important in UP?

A

Change is encouraged in agile as agile processes seek feedback from potential user or clients. This can help prevent the software from being redundant as change that is constantly improving the software will lead to a more successful product.

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

How to know when to change?

A

The best way to obtain valuable change is via feedback.

It is very risky to embark on a software project if genuine feedback cannot be obtained.

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

How long should an iteration be?

A

Each iteration should be time boxes between 2 to 6 weeks, don’t go over 6 weeks as adaptation and rapid feedback are lost.

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

What is a de-scope?

A

When an iteration deadline can’t be met an agile response is to de-scope: schedule tasks and requirements for future iterations

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

Why the UP structure?

A

The UP is relatively well structured compare to other agile processes.

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

What are the four phases of UP

A

Inception phase, Elaboration phase, construction phase and transition phase.

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

What is the inception phase?

A

First weeks which the original idea is fleshed out.

Key constraints on the future software are identified.

Try to come up with estimates

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

What is the elaboration phase?

A

During this phase coding takes place, requirements are analysed and part of the software is designed.

Validating for the Unique Selling Point.

Feedback is sought out at the end of each iteration on running software.

17
Q

What is the construction phase?

A

Usually the longest phase.

During this phase the software settles, changes will still occur but should be more minor.

Each iteration build upon the previous, adding new functional and non functional requirements.

18
Q

What is the Transition phase?

A

Last few weeks left for beta testing and deployment to the distribution platform.