Incremental Model : Software Engineering

-

  •  cost of implementing requirement change is reduced.
  • amount of analysis and documentation that has to be redone is significantly less.
  • easier to get customer feedback from software rather than judging progress from document.
  • customers are able to gain values of software earlier than that is possible from waterfall model.
  • incremental delivery means that software is used in real, operational process so user feedback is likely to be realistic.
Phases that run in cycle:
  1. Planning [Estimation, Scheduling and Risk Analysis]
  2. Modelling [Analysis, Design]
  3. Construction [Coding, Testing]
  4. Deployment [Delivery, Feedback]
  5. Communication

Limitations:
  • if developed quickly, not cost effective to produce documents that reflect every changes.
  • system degrade, messy codes accumulate as new increments are added.

Comments

Post a Comment

Popular posts from this blog

Database Normalization : 1NF, 2NF, 3NF, BCNF, 4NF

-
Image
What is normalization? Breaking down a table into functionally independent tables Follows three-step procedures {first normal form, second NF, third NF} Why normalization? Reduce data redundancy, and thus data anomalies 1NF All the key attributes are defined There are no repeating groups in the table All attributes are dependent on the primary key 2NF It is in 1NF It includes no partial dependencies Partial dependency : attributes are dependent on only a part of a composite PK Fig: Dependency Diagram 3NF It is in 2NF It includes no transitive dependencies Transitive dependency : nonkey (nonprime) attributes are dependent on another nonkey attribute BCNF A Table is in BCNF when it is in 3NF and contains no non-key attribute that determines a key attribute. – Convert to BCNF by exchanging the determinate with the key attribute and then resolving the partial dependency with a new table. 4NF A Table is in 4NF when it is in 3NF table with no multi-valued dependencies :  – Convert to 4NF
Read more