The Waterfall Process Model

1226 Words5 Pages
2) Waterfall Process Model Waterfall Process Model or The Classical Life Cycle o was the oldest process model to present a linear framework, describing main phases that are compulsory for a successful software development model. It formed the basis for most software development standards and contains the following stages: Requirements elicitation, Designing, Implementation and Testing. In this model, to begin next stage current stage must be completed. To apply waterfall process model, requirements should not change since there is no turn to back. Main advantage of waterfall process model is simple to understand it and easy to arrange tasks. 3) Incremental Model In incremental development process, software features divided into parts and…show more content…
Milestones & Deliverables Project Charter 28.10.2015 It will provide a picture of where we are going, why we are going there, who will be impacted. It will determine the roles and responsibilities in the system. It also includes the constraints and the important dates concerning the development of the product. This information should be complete and accurate. Requirements Phase 28.10.2015-16.12.2015 Detailed Requirements Specification 21.11.2015 Comprehensive description of intended purpose will be included. It will fully describe what the software will do and how it will be expected to perform. It will define how an application will interact with the system hardware, other programs and human users in a wide variety of real-world situations. Parameters like portability, response time, and security will be evaluated. Business System Requirements 29.11.2015 It will describe what must be delivered to meet business needs to provide value by meeting business objectives. Business requirements exist within the business environment and must be discovered. Also constraints in terms of economics, social, ethical will be elaborated. Software Project Management Plan…show more content…
Interfaces of the system will be defined and individual modules will be identified. Packages of the system will be described. Additionally, relation among the classes and class diagrams will be clarified. Software Development Phase 15.02.2016-10.04.2016 In software development phase, general structure of project will be translated into an executable program and all software features will be implemented part by part. Also unit testing will be done at that phase. System Testing Phase 10.04.2016- 04.05.2016 System Integration Testing 25.04.2016 The whole system will be tested to verify data integrity and to ensure that all subcomponents are integrated successfully to provide expected results. Testing of emergent properties is particularly important. User Acceptance Testing 03.05.2016 In user acceptance testing stage, actual software users will test the software to make sure it can handle required tasks in real-world scenarios, according to specifications. Release of Alpha Version 04.05.2016 In alpha version of CatFm, developers will observe the problems, bugs, crashes. It helps to improve the quality of the product. Release of Beta Version
Open Document