1.0 Software Development Methodology

Software Development Methodology adopted by Fusion Technologies is based on strong process foundation aligned inline with the requirements of ISO 9001:2000 and SEI – CMMI. Following are significant phases:

  • Requirements Management Phase (Requirements Definition, Elicitation, Requirements Management and Requirements change control)
  • Technical Solution Phase: Detail Design Phase
  • Code Construction
  • Testing Phase
  • Installation and Acceptance Phase
  • Maintenance & Support Phase

1.1 Requirements Management Phase

1.1.1 Phase Overview

Proposal and Contracting is the first step before entering into Requirements Management Phase. Requirements Management starts with collecting the requirements from the customer. This would provide enough bases for scoping the project. Size and Effort estimates are prepared an exit criterion of this phase.

1.1.2 Associated Tasks

  • Customer contract with Fusion Technologies or Fusion’s contract with the customer
  • RFI (Request For Information) from the customer
  • RFP (Request For Proposal) from the customer
  • Rough effort estimation and cost estimation
  • Drafting of Proposal
  • Review & Approval of Proposal by customer
  • Discussions with the customer on Proposal
  • Demonstration of the prototype
  • Getting Letter of Intent from the customer
  • Effort Estimation
  • Eliciting the Requirements
  • Holding discussions on the various requirements to make sure that the requirements required by the customer are the same in all regards, as the requirements perceived by Fusion Technologies
  • Analysing various alternative solutions to arrive at the optimum solution
  • Preparation of the Software Requirements Specification
  • Review & Approval of Software Requirements Specification
  • Sign off for the Software Requirements Specification by the customer
  • User Acceptance Criteria (part of SRS)

2.2 Technical Solutions Phase

2.2.1 Phase Overview

This phase covers the modularisation of the Software, preparation, review, verification, validation and approval of High Level Design Document (HLDD), preparation, review and updation of STP (Software Test Plan).

2.2.2 Associated Tasks

  • Modularisation of the application
  • Preparation of High Level Design Document (HLDD)
  • Preparation of Module Specifications
  • Review, verification, validation and approval of HLDD
  • Updation of Software Test Plan (STP)
  • Review and approval of Software Test Plan (STP)
    Preparation of the Detail Design Specifications, User interfaces, Reorganization of table structure, its review and approval
  • Preparation of Coding Specifications, their review and approval
  • Updation of Software Test Plans, their review and approval

2.3 Code Construction

2.3.1 Phase Overview

Coding phase covers the coding of the application as per the standards till it is defect free and also code walkthroughs / reviews as per unit testing.

2.3.2 Associated Tasks

  • Coding of the screens, menus etc as per the Coding Specifications till these are found error-free
  • Self-testing of the code by the programmer / coder
  • Code walkthroughs / Code review
  • Defining / Adherence to Coding Standards
  • Unit Testing
  • Rectification of code based on Unit Test results
  • Self-testing and Unit Testing of rectified code till code is error-free

2.4 Testing Phase

2.4.1 Phase Overview

The Software Product uses a systematic approach by means of integration of the unit-tested modules. The phases in the Integration of the modules are: Integration Planning, Integration and Integration Testing.

2.4.2 Associated Tasks

  • Unit Testing
  • Rectification of code based on Unit Test results
  • Self-testing and Unit Testing of rectified code till code is error-free
  • Integration Test(s)
  • Rectification of code based on the result of Software Integrated Test(s) followed by Self test
  • Unit Test, Integration Test till the code is error-free

2.5 Installation and Acceptance Phase

2.5.1 Phase Overview

Installation phase covers the installation of the software at the user site for actual usage (production usage) and acceptance of the software by the user. User acceptance phase covers the installation of software for conducting User Acceptance Test, conducting of User Training, rectification of errors/bugs based on User Acceptance Test results.

2.5.2 Associated Tasks

  • Installation of the software at user site
  • Acceptance of the software by the user
  • Install software at the site agreed for User Acceptance Test
  • Impart User Training till they are satisfied
  • Help the user in conducting the User Acceptance Test
  • Get the User Acceptance Test results
  • Modify the code if required
  • Carry out the tests on modified code
  • The above steps will continue till the user is satisfied

2.6 Maintenance & Support Phase

2.6.1 Phase Overview

Maintenance & support phase covers the associated Tasks from the emanation of problems or change requests from the customer as per Warranty/Maintenance Contract and the modification of the code to solve the problems and/or provide the changes requested.

2.6.2 Associated Tasks

  • Entering into Maintenance Contract in case not under warranty
  • Preparation & sign-off of Maintenance Plan (in case of Maintenance Contract)
  • Problem Logging, Change Requests logging
  • Carrying out of Impact Analysis
  • Updation, Review & Approval of SRS, DDD, STP (if any)
  • Effecting modifications/enhancements
  • Undertaking rigorous tests on the modified software (regression testing)
  • Updation of User/Technical manual (if any)
  • Delivery of new release/version to the customer
  • Version Control/Change Management.

 

 
  Copyright © 2003 Fusion Technologies