Define (That is project setup, project plan) Analyze (That is understand functional requirement, functional specification document) Design (Database, UI, documents) Coding & Unit testing (Man at work) Verification and Validation (Integration and system testing)Each phase has envolved some documentation to work on.1. Define: Project is available to us. We check if statement of work is available to us. So,Statement of Work (SOW)document would be the first document received from client. Once project in, we may "initiate" and do an official kick off of the project. So, we may createProject Initiation Notedocument. That may be created by Business Manager as well as the attendants of this meeting. Team would start on Project Plan(by Project Manager) document,Quality Plan&Test Plan(by QA Manager) document. We also identify quantifiable risk which are involved in project at this level and create Project Risk Management Plan (by Project Manager) document.2. Analyze: The most important documents at this stage are;Requirement SpecificationDocument (SRS); that is a joint effort by client and team and second is theMinutes of Meeting(MOM) document created on each discussion/interaction/communication. This phase also may includeUse Casedocument based on SRS document (joint effort of client, programmers and QA) as well asRequirement Tracebility Matrixdocument (by progammers). Parallelly QA may work on revisedTest Plandocument which may have change based on analysis.3. Design: Important document is;Design document(joint effort of Team head, solution architect) that specifies use of design pattern, code or design guidelines, UI guidelines and standard to maintain may also consider to add screen prototypes. If reports are involved then we may also createReport Designdocument. At this stage Solution architect or Team may review these documents and prepare a revised Requirement Traceability Matrixdocument which may change based on design. QA may updateTest Plandocument. I mean to say, each document which are created earlier may tend to change and get updated in incremented way.4. Coding: Important documents are; Code itself. Well, of course only if you consider it as a document as well. This is the part most awaited by developers, we maintain code guideline in this phase. A parellel code review might be going on the way, which producesCode Reviewdocument. At the same time QA may be working onTest case Specification(by QA head) document. Developers may createUnit Test plan/detaileddocument if require. QA executes their Test case specification on actual functions and prepateTest Resultdocument. At this stage as well, theRequirement Tracebility Matrixdocument will be having most updation. Because, we may face this situation where actual problem/issue/challenges we face only at this stage which we may not have anticipated.5. Verify:Its a testing stage; where we give importance toTest Case, Test Resultdocuments. We, developers; receiveDelivery notes(by QA head) after a test cycle or Test case execution on modules and integrated modules to deliever as a milestone.This may be less or more based on the organization structure, project requirement or methodology you adhere.

SDLC Roles and Responsibilities Glossary and Acronyms Templates Alternate Methodologies FAQsTemplates1. Initiation Phase Concept Proposal ProjectCharter2. Concept Development Phase Project Scope Statement3. PlanningPhase Project Management Plan Risk Management Plan Change Management Plan Communication Management Plan Staffing Management Plan Stakeholder Management Plan4. Requirements AnalysisPhase Functional Requirements Document Test Master Plan5. DesignPhase System Design Document Conversion Plan Implementation Plan Operations Manual System Administration Manual Maintenance Manual Training Plan User Manual6. DevelopmentPhase Software Development Document Integration Document Test Analysis Report7.TestPhase Test Analysis Approval Determination TestProblem Report8.ImplementationPhase Version Description Document Post-Implementation Review Report9.Operations and MaintenancePhase Disposition Plan