Related Posts
Hello Users Welcome Back, We are going to explain a new topic Classical Waterfall model In Software Engineering.
What is Classical Waterfall Model , It is based on the software Development Life cycle SDLC.
it is a theoretical way of product software development.
Now a days it can’t be used in for slow development.
It is the base of all other model the different phases of classical waterfall model
Requirement Analysis And Specifications.
Design.
Coding & Unit Testing.
Integration & System Testing.
Maintenance
FEASIBILITY STUDY –
The main goal of this phase to defend the then it would be financially and tech My feasible to develop the software
It involves understanding the problem determine the various way to solve the price.
There ane many sol ane analysed and how the best solution is chosen to to overcome the drawbacks
REQUIREMENT ANALYSIS SPECIFICATION:
The main aim of this step is phase is to understand the exact requirment of the customen and dowment the properly
It has two parts
(a) Requirement Gethening and analysis :
In this step all the requirments regard ng the softwane ane gathened from the men. The the gathened nequirments and analysed and the unneccessang neque oment are omitted.
b Requinment Specification:
The analyzed docements are dowmented Sebetwane Requirement Specification (SRs) document SRS document actas a contract between development team and customers
3. DESIGN
on this phase, the sthacture of the software is design according to the Ses Document for the implementation of some programming Language
In this phase is used two different design approach
Traditional Design Approach
Object Oriented Design Approach
It is of two type
i) Architecture Design
It identifying the software component.
Decomposing the software components into modules.
ii) Detailed Design
Details of emplementation
Process of existing code and modhibice- tion of algorithan
III) Object Oriented Design Approach
Different relationship that exist among these objects are identified
It focus on time,cost, maintenance etc.
4. CODING UNIT TESTING
In this phase, the design product is translated into Source code.
Several modules is designed and coded with programming language.
Now each module is unit tested to determine whether the modrile is working or not working.
5. INTEGRATION & SYSTEM TESTING
once the coding & the unit testing is completed the mixtures and integrated then integration testing is performed. The main aim of this phase that the develop.d product meets all the requirements as the specified SRS document or not.
There are 3 types of system Testing:
Tested by the development team
Testing Tested by the resen friendly acceptance.
Testing the tested by the customer whether the software is accepted or not.
6. MAINTENANCE
It is the most important phase.
The effort spent on maintenance is 60% of the total spent to develop
It iss of 3 types software O connective maintance > souvethe error the ane not discovered during the product development O pentective maintanceEnhancethe functional ties of the systed basedon customer nequest Adaptive maintenance make the software portable for asmooth worn in new computer / new os. Advanleges – O simple and kasyto understand 1 Each stage clearly defined. haces ahe A1l the process are documented Disaolvantages At a time only one phase 28 processo
