The methodology used by the proponents is the classical waterfall model. The waterfall model is the classical model of software engineering. This model is one of the oldest models and is widely used in government projects and in many major companies. As this model emphasizes planning in early stages, it ensures design flaws before they develop. In addition, its intensive document and planning make it work well for projects in which quality control is a major concern. The pure waterfall lifecycle consists of several non overlapping stages, as shown in the following figure. The model begins with establishing system requirements and software requirements and continues with architectural design, detailed design, coding, testing, and maintenance. The waterfall model serves as a baseline for many other lifecycle models. System Requirement
Figure 3.1 The Classical Waterfall Model
The following list details the steps for using the waterfall 1. System requirements
In this phase, the proponents establish the components for building the system, including the hardware requirements, software tools, and other necessary components. Examples include decisions on hardware, such as plug-in boards (number of channels, acquisition speed, and so on), and decisions on external pieces of software, such as databases or libraries. 2. Software requirements
In this stage, the expectations for software functionality and system requirements were established and identified by the proponents. Requirements analysis includes determining interaction needed with other applications and databases, performance requirements, user interface requirements, and so on. 3. Architectural design
The proponents determine the software framework of a system...
Please join StudyMode to read the full document