Iterative Development Summarises some aspects of the iterative

Iterative Development Summarises some aspects of the iterative development notes as an aid to study. Not a substitute for the full notes. Requirements Engineering Bsc Applied Computing Year 2

Iterative Development > The Unified Process uses iterative development > 4 phases of development > Inception > Elaboration > Construction > Transition

Iterative Development > Construction phase is divided into Iterations > Each iteration consists of Analysis, Design, Coding & Testing > Majority of coding done during Construction Phase

Inception Phase > Determining if the project is worth doing > Identifying the boundaries in regard to what the system will include > Identifying some requirements > Getting a Go/No Go from client

Elaboration Phase > Identifying risk factors e. g. requirements, skills & technological risks > Collecting further requirements and establishing a baseline architecture by using such things as: > Use Case Models > Class Diagrams > Sequence Diagrams > Preparing a plan of construction

Construction Phase > Divided into iterations with strict deadlines > Each iteration implements a few scenarios or even a whole use case > If time is running out, scenarios moved to a later iteration > Refactoring of previous code occurs in each iteration > Production quality code after each iteration

Construction Phase > Order in which use cases are built depends on (i) importance and (ii) risk > Domain people divide Use Cases from most to least important > Developers divide use cases from most to least risky > Most important and most risky done first

Transition Phase > Takes up between 10% and 35% of total project time > Training the main users of the system > Beta testing to perfect the system > Performance tuning to ensure that the system meets speed and memory requirements etc.

Authorship: Prepared by Dave Martin with modifications by Ian Downey