The Waterfall Process Model

-
•Main characteristics:
–Also called classic software life cycle or sequential model
–Process activities (phases/stages) are clearly separated

•Advantages
–Organized approach, provides robust separation of phases.
–Reflects common engineering practice.

•Disadvantages:
– Doesn't cope well with changes required by the client.
–Development teams might wait for each other.
–A working version of the product is available only late.

•Applicability:
–When requirements are well known and few changes are likely to be needed.
–Can be used also for parts of larger software systems.

You can also view:
1. Boehms Spiral Process Model
2. Rational Unified Process Model
3. Rapid Application Development-RAD
4. Prototyping Process Model
5. Incremental Process Model
6. Component Based Software Engineering
7. Evolutionary Process Development Model
8. Waterfall Process Model
9. Software Process Framework Activity

Comments

Post a Comment

i am running my new blog at Knowledge Sharing (https://ksharing.info). please subscribe my new blog

Popular posts from this blog

Component Based Software Engineering

-
Image
•Main characteristics –Makes intensive use of existing reusable components. –The focus is on integrating the components rather than on creating them from the scratch. •Advantages –Reduces considerably the software to be developed “in-house”. –Allows faster delivery. –In principle, more reliable systems, due to using previously tested components. •Disadvantages –agreement in requirements are needed. –Less control over the system’s evolution •Applicability: –When there is a pool of existing components that could satisfy the requirements of the new product. –Emerging trend: integration of web services from a range of suppliers. You can also view: 1. Boehms Spiral Process Model 2. Rational Unified Process Model 3. Rapid Application Development-RAD 4. Prototyping Process Model 5. Incremental Process Model 6. Component Based Software Engineering 7. Evolutionary Process Development Model 8. Waterfall Process Model 9. Software Process Framework Activity
Read more

Use Case Diagrams

-
Image
Use Case Diagrams: A use case in software engineering and systems engineering is a description of a system’s behavior. In other words, a use case describes "who" can do "what" with the system in question. The use case technique is used to capture a system's behavioral requirements by detailing scenario-driven threads through the functional requirements.  Actor: An actor represents a set of roles that users of use case play when interacting with these use cases. Actors can be human or automated systems. Actors are entities which require help from the system to perform their task or are needed to execute the system’s functions. Use Case Diagram for School Management Fig: Use Case Diagram for School Management Use Case Diagram for Point of Sale Fig: Use Case Diagram for Point of Sale
Read more

What is software engineering

-
1.What is software? Ans:Computer programs and associated documentation. Software products may be developed for a particular customer or may be developed for a general market. 2.What is software engineering? Ans:Software engineering is an engineering discipline that is concerned with all aspects of software production. 3.What is the difference between software engineering and system engineering? Ans:System engineering is concerned with all aspects of computer-based systems development including hardware, software and process engineering. Software engineering is part of this more general process 4.What are the key challenges facing software engineering? Ans:Coping with increasing diversity, demands for reduced delivery times and developing trustworthy software. 5.What are the costs of software engineering? Ans:Roughly 60% of software costs are development costs, 40% are testing costs. For custom software, evolution costs often exceed development costs. 6.What are the best software engine...
Read more