WISS Development Methodology for Software Engineering Process
WISS follows the Spiral Model of Software Engineering Process that forms the foundation, to provide rational and timely development of software solutions to our clients. It provides the framework to establish a comprehensive plan for software development. It is suitably applied based on the nature of the project and application, the methods and tools to be used and the controls and deliverables that are required.
The WISS Development Methodology uses the Spiral Method of Software Engineering Process to:
|
 |
Combine the iterative nature of prototyping with the controlled and systematic aspects of Waterfall Model.
|
|
Rapidly develop software in a series of incremental releases
(During early iterations the incremental releases may be a paper model or prototype)
. |
|
Produce increasingly complete versions of the software in later iterations. |
|
Steps followed in the development process, i.e. moving clockwise in a spiral beginning from the core.
|
|
Product Specifications are developed with the first (or more) circuits of the planning regions of the spiral. |
|
The Prototype and sophisticated versions of the software are developed progressively by repeatedly following all the steps enunciated in the planning regions. |
|
Project Plans are adjusted with each spiral of the planning regions. |
|
Cost and Schedules are adjusted based on the feedback from the Client Evaluation. |
The Spiral model is adapted to apply throughout the life of the software. Whenever a change is initiated the process starts at the appropriate entry point (e.g. Product enhancements).
|
WISS Software Development Life-Cycle
|
Cycle 1: Initial Analysis
|
|
Consultation with Functional Heads
The WISS Project Team will consult with the functional heads of the client and understand the objectives, suggest alternatives and identify all constraints that envisage the project.
|
|
Business Process Mapping
The Team will study the entire business process of the client
conceptually and try to map the same with the software.
|
|
Prototype Model
Once the mapping is done prototype for the same with some live data of the user will be taken and demonstrated to the client.
|
|
Identification of Risks
All risks in terms of using the product, business processes, technology, infrastructure etc will be identified at this stage and possible solutions will be provided.
|
|
Recommendations
The team will also educate the client with alternative solutions or good business practices followed by similar industries from their earlier experiences and will adapt whatever is feasible in consultation with the client.
|
|
Project Plan
The entire Project Plan will be prepared, documented and agreed upon in consultation with the client in terms of: Efforts, Costs, Manpower Allocations, Phases, Deliverables, Schedules etc.
|
Cycle 2: Final Analysis
|
|
Definition of User Requirements
The WISS Project Team will have detailed discussion with all functional heads and other coordinators to understand and define the User Requirements clearly.
|
|
Documentation of System Requirement Specifications
All User Requirements will be documented and the System Requirement Specification (SRS) document will be prepared.
|
|
Review of SRS
The SRS document will be thoroughly studied and reviewed by the users and signed off.
|
|
Implementation and Customization Plan
The development plan for any customizations and the implementation plan will also be prepared at the end of this phase.This document is the key for any further developments.
|
Cycle 3 - Design
|
|
During this phase the entire software in terms of Customizations, Additional Requirements, enhancements etc will be done. Also Test Plans and Acceptability Criteria for the same will be obtained from the client.
The system design document, test plan, test cases, integration plan and acceptability criteria will be prepared.
|
