Chapter 4 Flashcards

1
Q

List

Characteristics of Agile Process

A

Not suuitable for large, high-risk, or mission-critical projects
Minimal rules and documentation
Continuous involvment of testers
Easy to accomodate product changes
Depends heavily on stakeholder interaction
Easy to manage
Early delivery of partial solutions
Informal risk management
Built in continuous process improvement

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

List

Characteristics of Spiral process

A

Not suitable for small, low-risk projects
Several steps required, along with documents done up front
Early involvement of testers (might be outside of main team)
Hard to accomodate product changes until prototype completed
Continuous stakeholder involvement in planning and risk assessment
Requires formal project management and coordination
Project end not always obvious
Good risk management
Process improvment handled

q

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

List

First prototype guidlines

A
  1. Transition from paper prototype to software design
  2. Prototype a user interface
  3. Create a virtual prototype
  4. Add input and output to prototype
  5. Engineer algorithms
  6. Test prototype
  7. Prototype with deployment in mind
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

List

Prototype evaluation

A
  1. Provide scaffolding when asking for product feedback: “I like, I wish, what if?”
  2. Test on right people
  3. Ask the right questions
  4. Be neutral when presenting alternatives to users
  5. Adapt while testing
  6. Allow the user to contribute ideas
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

List

Recommended Process Steps

A
  1. Requirements engineering
  2. Preliminary architecture design
  3. Estimate required project resources
  4. Construct first prototype
  5. Evaluate prototype
  6. Go, no-go decision
  7. Evolve system
  8. Release prototype
  9. Maintain software (DOCUMENT)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Define

Regression testing

A

Make sure that software that was previously working still does after changes are made

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

Define

Corrective maintanence

A

Reactive modification of software to repair problems discovered after software is delivered

firefighting

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

Define

Adaptive maintanence

A

Reactive modification of software after delivered to keep software usable in changing environment

firefighting

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

Define

Perfective maintanence

A

Proactive modification of software after delivery to provide new user features, better program code structure, or improved documentation

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

Define

Preventative maintanence

A

Proactive modification of software after delivery to correct product faults before discovery by users

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