Faisal Incremental Model


Published on

Incremental Model

Published in: Sports, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Faisal Incremental Model

  1. 1. 1<br />Faisal Muhammad khanpresentation :incremental process modelbs-cs 4th(b)Fuuast Islamabad <br />
  2. 2. 2<br />Title<br />Incremental model<br />
  3. 3. 3<br />Incremental model<br />Method of s/w development <br />Incremented until the product is furnished <br />Evolution of water fall model<br />Combines the element of water fallwith theiterative philosophy of prototyping. <br />scheduling and staging strategy<br />
  4. 4. 4<br />Diagram<br />
  5. 5. 5<br />Phases<br />Basically five phases<br />Communication<br />Planning<br />Modeling (analysis, design)<br />Construction (code, test)<br />Deployment (delivery, feedback)<br />
  6. 6. 6<br />Communication<br />First or Initial phase<br />In the meeting different aspects of the project are suggested<br />Collaboration b/w two company<br />Idea of the customer about the project<br /> customer suggestion<br />
  7. 7. 7<br />Planning<br />Meeting of the project company<br />Instruction of the pm to the staff<br /> In this pm emphasizes on:<br />How to work start <br />Quickly completion of the project<br />Give demo version to the customer<br />
  8. 8. 8<br />Modeling<br />Analysis and Design<br />development team visits the customer and studies their system requirement<br />It also consists of personnel assignments, costs of the system, project schedule and target dates<br />System Analysis and Design phase, the whole software development process, the overall software structure and its outlay are defined<br />
  9. 9. 9<br />Construction<br />Code<br />Testing<br />code and test is performed to check the feasibility, reliability and working of the software<br />After code generation phase the software program testing begins.<br />
  10. 10. 10<br />Deployment<br />the software has been delivered to the customer and gives feedback from the customer<br />Delivery and Feedback: <br />Software will definitely go through change once when it is delivered to the customer<br />The software should be implemented to accommodate changes that could be happen during the post development period.<br />
  11. 11. Example<br />development of word processing application<br />the following services are provided on subsequent builds:<br />Basic file management, editing and document production functions<br />Advanced editing and document production functions<br />Spell and grammar checking<br />Advance page layout<br />
  12. 12. Applicable<br />Incremental software development model may be applicable to projects where:<br />Software Requirements are well defined, but realization may be delayed.<br />The basic software functionality are required early<br />
  13. 13. Advantages<br />More flexible - less costly to change scope and requirements <br />Operation product in week<br />Each iteration is an easily managed milestone<br />Easier to test and debug during a smaller iteration<br />Easier to manage risk <br />Easier to manage risk<br />
  14. 14. Disadvantages<br />Each phase of an iteration is rigid and do not overlap each other.<br />Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle<br />Need an open architecture<br />
  15. 15. Problems<br />There are some problems with this model. <br />One is that each new build must be integrated with previous builds and any existing systems. <br />The task of decomposing product into builds is not trivial either.<br /> If there are too few builds and each build degenerates this turns into Build-And-Fix model. <br />However if there are too many builds then there is little added utility from each build.<br />