Unified Process Flashcards

1
Q

What is iterative development

A

series of short mini projects - iterations

each iteration gives a tested, integrated and executable system

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

Steps in iteration development

A
requirements
analysis
design
implementations
integration and system test
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the output of an iteration

A

not experimental prototype but a production subset of the final system
each iteration tackles new requirements and extends the system

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

key ideas of central unified process ideas?

A
iterative development is number one
tackle high risk items early
continuous engagement of uses
core architecture in early iterations
test
apply use cases continuously
model with UML
carefully manage requirements
control changes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

name and explain the unified process phases

A

Inception - define project scope
elaboration - plan, specify features, baseline architecture
construction - build it
Transition - transfer to user community

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

what are artefacts

A

docs, diagrams, code that track progress
everything is optional
best kept electronically on website

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

which artefacts can be started/created at inception phase

A
use case model
vision
supp specification
glossary
SW dev plan
development case
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

waterfall vs agile

A

waterfall - well documented, traceability, change control, few risks, sequential, late integration and testing
Iterative - little documentation, light process, risk driven, continuous integration and testing

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

prototyping framework

A

build system to clarify requirements

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

Rapid application development framework

A

well defined 60-90 day projects

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

incremental framework

A

deliver increasing functionality at each iteration

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

spiral (boehm) framework

A

similar set of tasks applied for each turn of the spiral

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

component based framework

A

aimed at producing and reusing OO components

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

Agile framework

A

embrace change and adapt to it and keep things simple

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

Process model

A

framework of tasks applied during software engineering

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

How do iterative methods attempt to reduce risk

A

bringing out versions early

17
Q

Benefits of iterative development

A
early reduction of risk
early visible progress
early feedback
managed complexity
get robust architecture
handle evolving requirements
allow for changes
learn and apply lessons withing dev process
18
Q

What does prototyping help to investigate

A
technical issues
work flow and task design
screen layouts, UI, information display
difficult, controversial, critical areas
match between engineering and customer specification
19
Q

benefits of prototyping

A

helps to investigate different things within the project
demonstrate proof of concept
more concrete than a narrative

20
Q

Why should we prototype

A
enable evaluation and feedback
improves communication between a team
testing ideas out - encourages reflection
answer questions
explore alternatives
21
Q

Horizontal prototype

A

wide range of functions, little detail

e.g. test UI before backend is developed

22
Q

vertical prototype

A

provide a lot of detail for a few features/functions

23
Q

Throw away prototypes

A

address high risk issues - uncertainty in requirements, UI design, alternative implementation strategies, tech platform
Only enough effort to help address specific issues
great for trying alternative ideas

24
Q

Evolutionary prototypes

A
early version of the actual software
will evolve into the final product
quality is important
can be put to limited use
implementing and validating well understood requirements
25
Q

How to make sure that the system works on demo day

A
no last minute code changes
demo a stable version
rehearse entire demo
resist temptation to change the demo
test any peripherals that are needed
26
Q

how to prepare for a demo

A

list and test tasks that will be demoed
plan what to say
plan what to say during each test
ensure that each team member participates
rehearse and time the demo
think of questions and prep answers for them