SDLC

A typical project follows the life cycle depicted in the picture. Each phase has distinct activities and clear criteria that mark the completion of the phase. The Software Process Database (SPDB) is not only a repository where knowledge assets generated by the project are stored but also a knowledge bank that can be exploited for smarter planning.

ANALYSIS




Analysis phase is where the software requirements are detailed out and the Functional Specifications Document (FSD) is prepared. This is reviewed and verified against the requirements established in the Proposal document. The System Test Criteria (STC) is also prepared at this stage, which becomes an input for the testing phase.



The following Procedures & Guidelines are referred to in this phase:

Requirement Analysis Procedure

Peer Review Procedure

Requirement Analysis Guideline

Functional Specification Document (FSD) Template

Gap Analysis Document (GAD) Template

System Test Criteria (STC) Template

Peer Review Report Template



DESIGN



The Design phase follows where the software solution is designed and the Architectural Design Document (ADD) and the Detailed Design Document (DDD) are prepared, reviewed and verified against the FSD.



The following Procedures & Guidelines apply to this phase:

Design Procedure

Peer Review Procedure

Design Guidelines

Architectural Design Document (ADD) Template

Detailed Design Document (DDD) Template

Combined Design Document (CDD) Template

Template for Traceability Matrix

Peer Review Report Template



CONSTRUCTION



Once the design is frozen, the Construction phase is started which involves development of code as per the program specifications drawn up and approved. At Nucleus we typically write the program specifications in this phase though it is traditionally a design activity.



The following Procedures & Guidelines are referred to in this phase:

Development Procedure

Coding Guidelines

Finness Development Standard

Java Coding Standard

NSEL Coding Standard

Oracle Coding Standard

Powerbuilder Coding Standard

Finness Coding Checklist

Program Specifications (for EJB) Template

Program Specifications Template

Program Submission Form

Unit Test Plan Template

Unit Checklist

Peer Review Procedure

SRS Template



SYSTEM INTEGRATED TESTING



The System Integrated Testing phase involves the complete testing of the developed software from installation to operations as per a developed Software Test Plan (STP). The software may go through iterative test cycles until it is bug free.



The Procedures & Guidelines to be referred to are:

Testing Procedure

Peer Review Procedure

Testing Guidelines

System Test Plan Template

Template for Traceability Matrix

SRS Form



QUALITY CONTROL TESTING



The recently added Quality Control Test is aimed at improving the overall quality of Nucleus deliveries as well as help in identifying defect injection and defect capture effectiveness.

The QCT Team will involve itself in the project from an early stage and subject it to an independent test in a controlled environment.



At the moment there are no special procedures defined for this phase and it follows the same processes as the System Integrated Testing phase.



USER ACCEPTANCE TESTING



Client user representatives typically hold the User Acceptance Testing (UAT) at the customer’s site. Our involvement is in terms of installation of the software, its setup, hand-holding the user group in using the software and correcting any defects/changes detected in the UAT.



IMPLEMENTATION



The implementation phase commences once the software is accepted by the customer (post-UAT). The phase involves installation of the software for live use, setup of the application, user training, conversion of data (in case necessary), support users on its use.



Daily tracking of its usage is a key activity in the initial stages of the software's going live. Review of transactions being executed on the system and processing being done is advised.



The conversion of data is a complex activity that needs special focus. Apart from drawing up a strategy for transition of data, we must outline a reconciliation strategy and a test strategy for the converted data.



Requirements: Functional Specification Document

Gap Analysis Document.

Design: Architectural Design Document

Combined Design Document

Detailed Design Document

Impact Analysis Document

Program Specifications

Coding/Development: Program Submission

Code Header

Testing/QCT: QCT Acceptance

Project Analysis Report

QCT Weekly Progress Report

Quality Control Test Plan

System Test Plan

Unit Test Plan

Senior Management Review (QCT)

Release: Configuration Item Release

Customer Release Note

Maintenance Annual Technical Support

Maintenance Plan

Progress Report

Project Board Review (Support)

Project Schedule (Support Projects)

Documentation: User Manuals



Various lifecycle models descriptions

o Waterfall

o Spiral

o Prototyping (Evolutionary Prototyping)

o Incremental