Software Development Life Cycle (SDLC)
SDLC is a systematic procedure of developing any application or software
from beginning to end. It is a process which is used by different organizations
to check whether the development process of an application is going on in a
proper manner or not. It is a combination of different phases. These phases
are as following:
1.
Requirement
2.
Feasibility Study
3.
Design
4.
Coding
5.
Testing
6.
Implementation
7.
Maintenance
1. Requirement: It is a phase where Client tell their requirement about the
application. It is a detailed formal reference document about Clients
business requirement.
CRS: Customer Requirement Specification.
2. Feasibility Study: The best possible way to do work. It is a joint work
done by group of people. Here they discuss about the Software and
Hardware which supports the application with their platforms.
This is a detailed formal reference document about Software Requirement.
This document converts the client/user language into Technical Language.
BRS: Business Requirement Specification.
3. Designing: It is a phase where requirement gets converted into flow
chart or different modules. Designing is divided into 2 parts.
1. High Level Design (HLD): It describes the Architecture of an
applications module look and how each and every module communicated
with each other. It describes each module into brief. Exactly like what
backend and frontend to be used. What language is used for both front &
backend.
It is developed by Tech. Architect, Professional Architect or Tech. Managers
who have 10+ years of experience.
2. Low Level Design (LLD): This is more emphasized on format and
appearance. It describes each module in details. It is done by Senior
Developers, Senior Software Engineer who has min. of 4+ years of
experience.
NOTE: HLD is a Macro Level Design where LLD is Micro Level Design.
4. Coding: Based on the requirement, developers generate Pseudo Code
against LLD in machine readable form.
5. Testing: To ensure that the application is working as per client/user
requirement specifications. Testing team checks whatever the Pseudo Code,
is accessible or not and also to ensure that the application developed by
developers is working correctly or not.
If testing team finds the BUG, they communicate with the development team
and then developer modifies the code as per the requirement. Again testing
team has to verify the application and repeat the same process until it
matches the requirement.
6. Implementation: Software/ Application installed at clients premises,
after development gets over.
7. Maintenance: Services provided to client/user after the delivery of
software/application.