Scribd
Upload
11 views1 page

Requirements Gathering in SDLC

The SDLC (Software Development Life Cycle) involves 7 phases: requirements gathering, analysis, design, coding, testing, implementation, and maintenance. In requirements gathering, requirements are collected from the client. Analysis involves creating documentation like the high level design document. Design uses the low level design document and UML diagrams to further specify the system. Coding develops the modules, integration, and deployment are done in implementation after passing testing. Maintenance provides fixes and support after deployment.

Uploaded by

Sandesh Ahir
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
11 views1 page

Requirements Gathering in SDLC

The SDLC (Software Development Life Cycle) involves 7 phases: requirements gathering, analysis, design, coding, testing, implementation, and maintenance. In requirements gathering, requirements are collected from the client. Analysis involves creating documentation like the high level design document. Design uses the low level design document and UML diagrams to further specify the system. Coding develops the modules, integration, and deployment are done in implementation after passing testing. Maintenance provides fixes and support after deployment.

Uploaded by

Sandesh Ahir
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

SDLC

To develop any s/w project we have to follow the following SDLC phases……….

1. Requirements Gathering:
In this phase we gather all the requirements from the client, i.e. what are the
client expected input, output……
2. Analysis:
In this phase based upon the client requirements we prepare one
documentation is called “High Level Design Document”. It contains Abstract,
Functional Requirements, Non Functional Requirements, Existing System,
Proposed System, SRS,………
3. Design:
It is difficult to understand the High Level Design Document for all the members,
so to understand easily we use “Low Level Design Document”. To design this
document we use UML (Unified Modeling Language). In this we have Use case,
Sequence, Collaboration……..diagrams
4. Coding:
In this phase we develop the coding module by module. After developing all the
modules we integrate them.
5. Testing:
After developing we have to check weather client requirements are satisfied or
not. If not, we are again going to develop.
6. Implementation:
In testing phase if client requirements are satisfied, we go for implementation.
i.e. we need to deploy the application in some server.
7. Maintenance:
After deployment, if at all any problems come from the client side; we are
providing maintenance for that application.

You might also like