Chapter 5

Question 1

Development process usually consists of:

Answer 1

Specification
Development
Implementation
Validation
Refinement

Question 2

Waterfall model

Answer 2

Requirements, Analysis and specification
High level design
Detailed design
Coding 
Unit testing 
Integration testing 
System & Acceptance testing

Question 3

Evolutionary model

Answer 3

evolves an implementation through user feedback until a final version that can satisfy the user requirements is produced.

Question 4

Evolutionary model advantages

Answer 4

More likely to meet requirements
Regular testing more likely to identify problems
Applicable to smaller projects

Question 5

Evolutionary model disadvantages

Answer 5

Difficult to understand
Deliverables aren’t well defined
Need to constrain iterations due to costs

Question 6

Incremental model advantages

Answer 6

Prioritises the requirements of the system
Produces prototypes to meet basic requirements
At each increment the requirements are allowed to evolve

Question 7

Incremental model disadvantages

Answer 7

Often difficult to map requirements into smaller increments
Some types of projects don’t suit requirement prioritisation
Integration testing often not possible with early increments

Question 8

Spiral model - each iteration passes through 4 quadrants…

Answer 8

Determine objectives
Identify and resolve risks
Development and test
Plan next iteration

Question 9

5 of Agile developments 12 principles

Answer 9

Deliver early and often to satisfy customer
Welcome changing requirements
Face to face communication is best
Measure progress against working software
Simplicity is essential

Question 10

3 Agile methods

Answer 10

Scrum
Extreme programming
Crystal
Feature-Driven development
Lean development
Adaptive software development
Dynamics Systems development method

Question 11

3 scrum weaknesses

Answer 11

Lack of scalability
Integration done after all increments built
Lack of formalism

Question 12

3 XP weaknesses

Answer 12

Difficulty coordinating large teams
Tendency to not document thoroughly
Can result in never ending project if not managed correctly

Question 13

Disadvantages of waterfall model

Answer 13

Specification often fixed early as to progress with project
Cannot adapt to changing specification
Testing at the end of development

Question 14

Exploratory development

Answer 14

Starting point established from requirements
First generation of complete system is created
This version is evaluated and second gen system is produced
Repeats until requirements including any new requirements are met
Customer/end user feedback

Question 15

Throwaway prototyping

Answer 15

Used to explore factors critical to system success
Involves implementing parts of a system to be evaluated
Aim to define requirement/specification
An example would be a user interface with no functionality

Question 16

Waterfall model advantages

Answer 16

Outputs method of measuring progress
Intuitive model, imposes planning before action
Implies a top-down approach to design.