Life Cycle Delivery Model

Life Cycle Delivery Model

Business Service Model

The methodology we follow at Shakti Solutions during the development life cycle ensures active client involvement at every step of the process.

The following stages make up in our methodology:

  • Business Modeling
  • Requirements
  • Analysis & Design
  • Implementation
  • Test
  • Deployment

The six core process workflows for development, delivery and support are as follows:

Business Modeling:

Document business processes using business use cases. The business use cases are analyzed to understand how the business should support the business processes. This is documented in a business object model. This step is optional for some projects.


Describe what the system should do and allow the developers and the client to agree on that description. To achieve this we elicit, organize and document the required functionality and constraints. A vision document is created and stakeholder needs are elicited. Use cases are identified to represent the behavior of the system. The use cases function as a unifying thread throughout the system development cycle. The same use case model is used during requirements capture, analysis, & design and testing, The deliverable at the end of this phase is the Functional Requirements Specifications document.

Analysis & Design:

Determine how the system will be realized in the implementation phase. Analysis & Design results in a design model. The design model serves as an abstraction of the source code. The design model consists of design classes and design subsystems with well defined interfaces, representing what will become components in the implementation. The deliverable at the end of this phase is the System Requirements Specification document.

Implementation - the system is realized through the implementation of components.

The purpose of this workflow is:

  • To define the organization of code, in terms of implementation subsystems
  • To implement objects and classes in terms of subsystems
  • To test the developed components as units
  • To integrate the results produced by individual implementers (or teams) into an executable system


The purpose of this workflow is:

  • To verify the integration between components
  • To verify the proper integration of all components
  • To verify that all requirements have been correctly implemented
  • To identify and ensure defects are addressed prior to the deployment of the software

Testing is an iterative process, which means that testing is performed throughout the projects. Tests are carried out along four quality dimensions - reliability, functionality, application performance and system performance. The deliverable at the end of this phase is testing documentation for the test procedures implemented.

Deployment - successfully deliver the project to the end user.

Main activities include:

  • Installation
  • Support
  • Planning and conducting beta tests
  • Formal acceptance

Typically, the deliverables at the end of the deployment include prototype, application source code, user manuals and support documentations.