Scribd
Upload
71 views

Software Engineering 2

The document describes the waterfall model of software development. It has five sequential phases: requirements analysis, design, implementation, integration and testing, and operation and maintenance. Each phase must be completed before moving to the next. Requirements are analyzed first to document customer needs, then the design is created based on requirements, implementation follows, then integration and testing, and finally the software is deployed for operation and maintenance.

Uploaded by

Ahmed Suliman
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
71 views

Software Engineering 2

The document describes the waterfall model of software development. It has five sequential phases: requirements analysis, design, implementation, integration and testing, and operation and maintenance. Each phase must be completed before moving to the next. Requirements are analyzed first to document customer needs, then the design is created based on requirements, implementation follows, then integration and testing, and finally the software is deployed for operation and maintenance.

Uploaded by

Ahmed Suliman
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Waterfall Model This Model have five phases.

Requirements analysis and specification design, implementation and unit testing integration and system testing and operation and maintenance. The phases always occur in this order and don't overlap. The developer must complete each phase before the next phase begins.

Requirement analysis specification spec Design

Implementation unit testing

Integration and system testing

Operation and Maintenance

Water fall Model Requirement analysis and specification phase :The goal of this phase is to understand the exact requirement of customer and document them properly. This activity is usually executed together with customer, also to document all function performance and interfacing requirement for the software. The requirement describe the (what) of system not the (how). This phase produce a large document written at natural language, contains a description of what the system will do without describing how it will be done. The resultant document is known as Software requirement (SRS) document. The (SRS) document may acts as contract between the developer and customer. If developer fails to implement full set of requirement it may amount to failure to implemented the contracted system.

Design Phase
(SRS) document produced in previous phase which contain the exact requirement of customer. In This phase, transform requirement specification into structure that to implemented into programming language this work is documented and known as software design description (SDD) document.

Implementation and Unit Testing phase


During this design is implemented if the (SDD) is completed. The implementation and coding process smoothly because all the information needed by software developer is contained in the (SDD). During testing major activities are constructed around the examination and modification of the code. Initially small modules tested in isolation from software !!!! Here Is Problem.

Integration and System Testing Phase


Important phase --- software product more satisfied use lower maintenance costs more accurate and reliable results. It is very expensive activity and consumer half of the cost. The purpose of unit is to determine that each independent modules is correctly implemented. This give little chance to determine the interface between modules is also correct, for this integration is performance.

Operation and Maintenance


When software delivered to customer installed and operational. The time spent to keep the software operational after release is very good. That is very important and challenging tasks. Software maintenance includes error correction enhancement of capabilities.

Problem of waterfall model


It is difficult to define all requirement at the beginning of the project. Is not suitable for changing, it doesn't scull up well to large project. Real project are not sequential application of waterfall model should be limited situation. Here the requirements and their implementation are well understood for example organization has experience in developing accounting system, them building a new accounting systems based on existing design could be easily managed with the waterfall model.

Proto type Model


A disadvantage of waterfall model the working software is not available until late in the process thus, delaying the discovery of error the major idea of this model to making a working proto type of the software instead of developing the actual software, the working proto type is developed as per current available requirements. It has Limited functional capabilities, low reliability, low performance. The developer should develop (Proto type) as early as possible to speed up the software development process. After the finalization of software requirements and specification (SRS) document. The Proto type is discarded and actual system is then developed using waterfall approach.

Interface Enhancement Model


Same phases of waterfall model but phased conducted in several cycle. A product is realized at the end of the each cycle. With each release providing additional functionality.

Requirement Planning Phase


Required are captured --- User Description :Teams of developers and users to prepare, understand and review the requirements. The team may use automated tools to capture information from the Other users.

Construction Phase :Here detailed design, coding and testing phase. Release the product to customer. Cut Over Phase :Acceptance phase testing by the user installation of the system and user training. In this model quick lutial views about the product are possible .

Selection of Life Cycle Model


Requirements, Development team, Users, Project Type and associated risk.

Software Engineering Analysis and Specification


When we receive a request for a new Software Project from the customer. First --- want to understand the project. New project may replace the existing system such preparation of students semester results. Electronically rather than manually or new project is an enhancement of a current automated system.

Requirement Engineering
Requirement describe ( what ) of the system not the ( How ). Requirement Engineering produces the one large document written in an natural language, contains description of what the system will do without describing how it will do requirement Engineering is a problem Statement by the Customer. Step of Requirement Engineering The quality of software product is only as good as the process that create it. This process consist of four steps as in figure

Requirement Engineering

Requirement Elicitation

Requirement Analysis

SRS

Requirement Documentation

Requirement

Process of Requirement Engineering

Review

You might also like