Scribd
Upload
50 views4 pages

SDLC Introduction To SDLC

The document provides an overview of the Software Development Life Cycle (SDLC) which includes common phases like requirements gathering, analysis, design, coding, testing, and maintenance. It then describes each phase in more detail including activities like developing requirements and design specifications, writing code, testing at the unit, integration, and system levels, and deploying the final product. The full SDLC process from initial request for proposal through user acceptance testing and production release is outlined.

Uploaded by

Abhishek Vangala
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
50 views4 pages

SDLC Introduction To SDLC

The document provides an overview of the Software Development Life Cycle (SDLC) which includes common phases like requirements gathering, analysis, design, coding, testing, and maintenance. It then describes each phase in more detail including activities like developing requirements and design specifications, writing code, testing at the unit, integration, and system levels, and deploying the final product. The full SDLC process from initial request for proposal through user acceptance testing and production release is outlined.

Uploaded by

Abhishek Vangala
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

SDLC Introduction to SDLC

SDLC (Software Development Life Cycle).It is a process of developing various information systems.

Phases of SDLC
Requirement gathering
Analysis Design Coding Testing Implementation Maintenance or Support

SDLC Workflow Request for Proposal [RFP]: Client will distribute the RFP to vendors (Software companies) Companies will respond to RFP with their proposals.

Proposal:
Proposal contains Technical Solutions, Cost, Delivery, Schedule, Timeline, Deliverables
etc]

SOW:
If Client likes the proposals from any vendor, then they will sign Statement of Work with vendor.

Kick-Off Meeting:
Client will conduct the kick of meeting with the vendor and explains the expectations.

PMP:
Once the Project Manager got identified then he/she will prepare the Project Management Plan.

BRS: Business Requirement Documents


After high level meeting with the customer they will release business requirements specification. BRS is a high level document containing project requirements from customer.

SRS (Software Requirement Specification):


Person should be a domain expert or functional expert he will be eligible to convert the BRS into SRS Identify standards ,Guidelines ,checklist and templates required for the project

Review SRS for Consistency---functional Specifications.

Correctness---If there are any problems identify beginning of the project.


Completeness---see the completeness of document Testability---entire system eligible for testing or not. Once SRS is approved to prepare the baseline of SRS (SRS 1.0)

Development:
Based on approved SRS software Architect or Technical Lead will design the model of the project (prototype or blue print) Model contains architectural design

Data base design (modules, subsystems etc) UI (User Interface) design all UML diagrams a) Use case b) Class c) Object d) Sequence e) Collaborations

Review and approval of the design documents.

QA & Testing:

Test manager or Test lead (assigned by TM) shall study the approved SRS and prepares
the Test Plan for the Project.

Review and approval of the Test plan. Based on approved SRS and design documents test engineers are going to identify the
required Test Scenarios for the test project. Review and approval of the test scenarios.

Test engineers are going to prepare the Test Cases for all approval scenarios.
Review and approval of the test cases.

Development:
Developers are going to converts the logics specified in design documents programs as per chosen programming language and they will release code. Perform code review.

Once particular unit of code as reviewed, and approved perform unit testing.
Once unit testing is approved developers will integrate the units and release the build for testing

QA & Testing:
Perform integration testing Once integration testing is approved perform system testing. . Perform retesting and regression testing.

Development:
Developers are going to fix the defects reported by testing teams.

QA &Testing:
Once system testing is approved then the application will be released for UAT

Perform UAT (User Acceptance Testing) Once UAT is approved release the application for production. Once product is ready perform the installation testing. Once installation testing is approved, implement the developed software into customer environment and provide user training. Provide support to the customer for any problems/issues or for any future enhancements

You might also like