- SDLC is a process of developing various information system
- Phases of SDLS
- Requirement Capturing
- Analysis
- Design
- Coding
- Testing
- Implementation
- Support / Maintenance
Software Development Life Cycle in Details
Request for Proposal (RFP)
- Nokia will prepare and distribute the RFP to selected vendors (Software Companies)
- Software company’s sales and marketing team respond the RFP with PROPOSALS (About the company, Technical solution, Delivery schedule, Budget, Timeline, and Deliverables etc.)
- If Nokia likes proposal from any vender then they will sign Statement Of Work (SOW) with that Vender (Work Order)
- Conduct project Kick-Off meeting (It’s a high level meeting between the senior Managers, CTO and Project Managers)
- Identify Project Manager
- Project Manager will prepare Project Management Plan (PMP)
- After high level meeting with customer, Business Team / Technical Team will release Business Requirement Specification (BRS)
- BRS is a high level document containing project requirements from customer
- Person should be a Domain expert / Functional expert. He / She is eligible to convert the BRS into SRS (Software Requirement Specification)
QA and Testing:
- Identify standards, guidelines, procedure, checklist and template require to develop the project
- Review and approval of SRS (Mapping SRS with BRS)
- Once SRS is approved, create baseline of SRS (SRS_1.0v)
Development:
- Based on approved SRS, Software Architect will design Model of the project (Blue print or Prototype)
- Model contains:
- Architectural Design (Modules, Sub-System and etc)
- Database design
- User Interface Design
- UML Diagrams
- Use Case
- Classes
- Objects
- Sequence etc.
- Review and approval of Design Documents Mapping Design document with SRS
QA and Testing:
- Test Manager / Test Lead will prepare Test Plan for project
- Review and approval of Test Plan
- Test Engineer will Identify the Test Scenarios for project ( What is to be tested)
- Review and approval of Test Scenarios
- Test Engineer will prepare Test Cases (How what is to be tested) for all approved Test Scenarios
- Review and approval of Test Cases
Development:
- Based on approved design documents, Developers are going to convert the logic specified in the design documents into coding as per chosen programming language and they will release code
- Perform Code Reviews
- Once Code is approved, Perform UNIT LEVEL TESTING
- Once UNIT LEVEL TESTING is approved, Developers will integrates the UNITS and release the build for testing.
QA and Testing:
- Test Case Execution (Perform Integration Level Testing)
- Test results with Pass and Fail
- Defect reporting of Failed Test Cases
- Defect status tracking and retesting of fixed defects
- Perform Regression Testing
- Once Integration Level Testing is approved, perform System Level Testing
- Again perform Retest and Regression Testing
Development:
- Developers are going to fix the defects which are reported by Testing Team
QA and Testing:
- Once System Level Testing is approved, release the Application for User Acceptance Testing (UAT)
- Perform UAT testing
- Once UAT is approved, release the application for production Department to create executable file
- Once executable file is ready, perform Installation Testing
- Once Installation Testing is approved, implement the developed software into Customer environment and provides user training
- Provide support to the Customer for any defects / Issue / Queries and future enhancements.
Project Teams:
- Client and CEO
- Sales and Marketing Team
- VP Delivery Manager
- Project Manager (Project Execution)
- Project Lead
- Business Team
- Technical Architects (Design HLD and LLD)
- Development Lead
- Developers (Coding)
- Test Manager (Test Management)
- Test Lead
- Test Engineer (Validation)
- SCM team (Project Repository)
- SQA - Software Quality Assurance Team (Process and Audits)
- CCB - Change Control Board (Change Management)
- Technical Writers (Project Documentation –Help Guide)