Вы находитесь на странице: 1из 12

| 

||
 |

BY:
ANSHUMAN MAHAPATRA.
SWAPNIL CHANDRA.
RITESH KAUL.
ABHISHEK KOTECHA.
—   —  | 
 
 

j Software is basic set of instructions with desired features.

j Includes tools, methods, process and quality focus

j Software development involves a series of steps.

j This development process is like glue which holds all the components of
software engineering together.

j Any successful software totally depends on the process of development.


— 
  
 

j Software process models help in tailoring the development process.

j They are part of generic framework activities that define a software¶s development.

j Software development process models can be largely categorized as:


± Prescriptive models.
± Incremental process models.
± Evolutionary process models.
± Specialized process models.
± Formal methods process models.

j This a general categorization of all models but there are many specialized models
under it.

j This seminar envisages at providing us an insight into software process models.


   

j Can be represented or graphically modelled as a cascade.

j Advantages:
± simple, easy to execute, requirement already defined..

j Disadvantages:
± blocking states, no change, no customer feedback, inconsistent.

j Suitable for:
-simple hardware products.

j Not suitable for:


± software products because of the complexity issue.
—   

j Combines elements of
   applied in an     .

j Advantages ±
± not require complete instructions, feedback

j Disadvantages ±
± less defined objective, problems to future.

j Suitable for-
± risky to develop whole project at once

j Not suitable for -


|    
 

j These process models are designed specifically to deal with unique


issues.

j Has a narrowly defined engineering.

j Involves two main process models :

- OOP ( Object Oriented Programming)


- CMMI ( Capability maturity Model )



j Involves development of applications in slices rather than layers.


j Advantages :
± Reduced complexity
± Increased reusability
j Disadvantages :
± Limited to only oop oriented languages.
j Suitable for :
± OOP programming language based applications.
j Not suitable :
± Applications with more integrated components.

—


j Involves continuous process   .


j Advantages:
- helps a process grow and makes it flexible.
- reduces the chances of system errors.
j Disadvantages:
- takes a lot of time.
- lasting changes need continuous efforts.
j Suitable for:
- Projects with long time in hand for completion.
j Not suitable for:
± Projects that have strict specifications.
   

j These models are developed after a gradual developmental process.

j Development takes place in stages.

j Involves two main process models:

± Rapid prototyping model.


± Spiral model
 

j Involves building a working replica of the entire system.

j Advantages:
± Requires short time period generally {60-90 days}.

j Disadvantages:
± Sufficient work power needed and must work with equal speed.
± Building components problematic if not modularised properly.

j Suitable for:
± Large projects with tight time frame.

j Not suitable for:


± applications with high technical risks.
| 

j Combination of waterfall and iterative prototyping models, more rapid in nature.

j Advantages:
± Most realistic, controls cost risks, early functionality.

j Disadvantages:
± Less defined, uncomfortable for management, incompatibility with audit process.

j Suitable for:
± Across all applications, one with many computations, one in which risks are too
high.

j Not suitable for:


± Not for small business applications as success rate is not guaranteed.
|    

j If a manager has a general project to arrange past records and build efficient
database that can increase the speed and optimality.

j The team he is working with must work in a manner that this aim is achieved.

j Fashion would be initially the pace is fast and then gradually declines as the
members become exhausted.

j The manager would use a model to understand the productivity loss over time.

j There can be two methods of solving:


± System dynamic approach.
± Process model approach.

Вам также может понравиться