Software Processes

1Faisal Muhammad khan

presentation : incremental process model

bs-cs 4th (b)

Fuuast Islamabad

2Title

Incremental model

3Incremental model

Method of s/w development Incremented until the product is furnished Evolution of water fall modelCombines the element of water fall with the iterative philosophy ofprototyping. scheduling and staging strategy

4Diagram

5Phases

Basically five phasesCommunicationPlanningModeling (analysis, design)Construction (code, test)Deployment (delivery, feedback)

6Communication

First or Initial phase

In the meeting different aspects of the project are suggested

Collaboration b/w two companyIdea of the customer about the project customer suggestion

7

Planning

Meeting of the project companyInstruction of the pm to the staff In this pm emphasizes on:How to work start Quickly completion of the projectGive demo version to the customer

8Modeling

Analysis and Designdevelopment team visits the customer and studies their system requirementIt also consists of personnel assignments, costs of the system, project schedule and target datesSystem Analysis and Design phase, the whole software development process, the overall software structure and its outlay are defined

9Construction

CodeTestingcode and test is performed to check the feasibility, reliability and working of the softwareAfter code generation phase the software program testing begins.

10Deploymentthe software has been delivered to the customer and gives feedback from the customerDelivery and Feedback:

Software will definitely go through change once when it is delivered to the customerThe software should be implemented to accommodate changes that could be happen during the post development period.

Example

development of word processing application the following services are provided on subsequent builds:Basic file management, editing and document production functionsAdvanced editing and document production functionsSpell and grammar checkingAdvance page layout

Applicable

Incremental software development model may be applicable to projects where:Software Requirements are well defined, but realization may be delayed.The basic software functionality are required early

Advantages

More flexible - less costly to change scope and requirements Operation product in weekEach iteration is an easily managed milestoneEasier to test and debug during a smaller iterationEasier to manage risk Easier to manage risk

Disadvantages

Each phase of an iteration is rigid and do not overlap each other.Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycleNeed an open architecture

ProblemsThere are some problems with this model. One is that each new build must be integrated with previous builds and any existing systems. The task of decomposing product into builds is not trivial either. If there are too few builds and each build degenerates this turns into Build-And-Fix model. However if there are too many builds then there is little added utility from each build.