Iterative Development Summarises some aspects of the iterative development notes as an aid to study. Not a substitute for the full notes. - PowerPoint PPT Presentation

About This Presentation
Title:

Iterative Development Summarises some aspects of the iterative development notes as an aid to study. Not a substitute for the full notes.

Description:

Iterative Development. Summarises some aspects of the iterative development notes ... Each iteration consists of Analysis, Design, Coding & Testing ... – PowerPoint PPT presentation

Number of Views:17
Avg rating:3.0/5.0
Slides: 10
Provided by: homepag91
Category:

less

Transcript and Presenter's Notes

Title: Iterative Development Summarises some aspects of the iterative development notes as an aid to study. Not a substitute for the full notes.


1
Iterative DevelopmentSummarises some aspects of
the iterative development notesas an aid to
study. Not a substitute for the full notes.
  • Requirements Engineering Bsc Applied Computing
    Year 2

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

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

4
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

5
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

6
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

7
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

8
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.

9
Authorship
  • Prepared by Dave Martin with modifications by
    Ian Downey
Write a Comment
User Comments (0)
About PowerShow.com