Methodologies
Development Methodology
The project will be implemented offshore model using OOAD methodology.
The following activities will be carried out as part of the execution strategy.
2) Requirements Document and use case Development.
3) Preparation of Low Level design documentation.
4) Preparation of High level design documentation.
5) Preparation of Unit Test Plan and Test Cases.
6) Preparation of User Interface mock ups.
7) Coding and Unit Testing.
8) Deployment and System Integration Testing the application on staging server.
9) User Acceptance Testing.
10) Bug Fixing, Build and Release Management Documentation.
Project Management
1) Approach & Methodology
In the development of a web interface, aesthetics assume a great importance. To converge the right appearance of the site requires a few iterations. Therefore, INSTA would use a “Prototyping” methodology for development of this project. The following activities comprise the development activities.
Requirements Analysis
Preparation of Design Document
Build Prototype and obtain approval of the same from the client
Buildtheapplication
Testing the application
Acceptance Testing
Delivery
2) Design and Prototype
The Design phase focuses on transforming the requirements gathered during analysis into a concrete design for this implementation. In the Design phase, we work together to develop a systems design for the application. The Design Phase includes content collection and co-ordination, high and low level software design specifications, authoring framework definition, graphic element design, template design, look and feel specifications (and style guides as appropriate); application test environment definition and test plan creation.
The Design Phase consists of a Creative/Cognitive Design and a Technical Design. All the necessary functionality mapped on the package(s) used is the fundamental aspect of the Design (along with the architecture).
This effort consists of a User Requirement Specification and a Technical Specification. Information gathered in the specification document form the basis for the design phase. The design phase leverages this information.
A Design Specification document is delivered on the completion of this phase.
INSTA employs a design philosophy that divides every application into three conceptual layers: a Presentation layer, a Functionality layer, and a Data Management layer. The Presentation layer is responsible for interacting with the user; receiving mouse commands, keyboard input, displaying the application's information to the user. The Functionality layer enforces security and controls the functionality of the application. The Data Management layer stores and sources the information of the application.
These layers are logical constructs and do not necessarily dictate the physical implementation of the application. Once a system is designed in this manner, implementation decisions are made to satisfy the performance and security goals of the application.
4) Change Management
At INSTA, we believe in strict adherence to the change management procedures as defined in INSTA’s Quality Management System process for the success of any project. All the onsite/offshore activities will strictly follow these procedures, which will be well defined at the beginning of the project. We can also adopt any of CLIENT’s procedures, after ensuring that the procedures cover all the required aspects of change management.
The main aspect of Change Management relates to change in scope of the original contract in terms of expansion and contraction based on CLIENT’s requirements.
“Change” is defined as the deviation in the scope of the requirement that is signed off. For instance, if a new requirement is requested in the implementation stage and the same has not been identified in the Design stage, which has been signed off, then the same is considered as a “Change”.
When such requirements arise, our Project Manager will:
Assess the impact of the change on the contract
Negotiate with CLIENT’s Project Manager to finalize the adjustments within certain timeframe and proceed with the incorporation of the change only after obtaining an approval from the CLIENT’s Project Manager.
Configuration Management involves activities like:
Identifying configurable items like:
Process related documentation (e.g. plans)
Software requirements documents
Software design documents
Coding standards
Source code units
Software test procedures
Software system build for the software test activity
Software system build for delivery to the customer or end users
Baseline Configurable Items
Controlling versions of the baseline items
Creating final deliverables using appropriate baselines
Recording/ Documenting configuration management activities
Auditing the entire configuration management process
The configuration management processes at INSTA ensure the following:
Delivered software conforms to requirements
Software has undergone all reviews and tests
Right version of any work product is used at any point of time
All components of the delivered software are consistent with each other
Right version of the software components is shipped to the customer site.