| |
MPS
believes and understands that customer satisfaction is the biggest
recognition for the success of any product or service. Our focus
is on rendering best service and delivering quality, eco-friendly,
on-the-dot solutions that invariably meet the most stringent benchmarks
set in an ever-increasing world of globalization and fierce competition.
Quality Management is implemented in every project that we undertake,
right from the conception through various stages of execution. Our
process and methodologies are constantly monitored, updated to keep
pace with the new innovations in technology and customer's needs.
Our entire development process is broadly divided into following
modules:
|
|
| |
|
|
| |
Project Commencement
Phase Description
Project commencement is first Phase of the Project. It creates
the framework for Project execution. The Operational Process
for the Project is defined and the Plan for managing the Project
is established.
Entry Criteria
4 Contract for project has been received
from the client.
4 Tasks
Initiate Project
4 Analyze
request for proposal and Prepare Estimates
4 Establish
/ Review Capability Baseline
4 Prepare
Software Project Plan
4 Review
and Update Project Plan
4 Setup
Environment
4 Induct
Project Team
4 Review
Project
4 Metric
Definition, Capture and Reporting
4 Review
Phase Deliverables, Approve and Release
4 Causal
Analysis
Validation And Verification
8
Review Contract
=
Review Software Project Plan
Exit Criteria
8
Software Project Plan has been approved and released
=
Planned Project Metrics is available
Phase Deliverables
8
Software Project Plan
=
Planned metric
|
|
|
| |
|
Requirement
Analysis & High Level Design
Phase Description
The purpose of this phase is to arrive at a proposed solution
to meet the user requirements in terms of software characteristics
and to design the overall functioning of the proposed system
and to establish the functional and physical rules and guidelines
governing the system as a whole.
The user requirements are arrived at based on a study of the
existing system in place and discussion with users. These
are analyzed to define the scope, purpose and key issues of
the proposed system. This is the phase where input and output
formats are also finalized. The functional standards of the
system should be presented in the documentation in a manner
which could be easily understood by the users as well as by
the project teams. The users must be able to approve the design
presented in the document. The project team must be able to
perform the subsequent phases based on this documentation.
Additional document delivered to the client in this phase
is the system design document, which contains Functional Data
Model and Functional Process Model. Functional Specification
document is finalized and sign-off obtained before proceeding
with the Low Level Design phase. No Approval on prototype
is taken from the client.
Entry Criteria
8 Software Project Plan is available
Tasks
4 Plan
and Prepare for Phase Execution
4 Conduct
Task kick-off meeting
4 Study
Existing System and Define User Requirement
4 Prepare
Conceptual Data and Process Model
4 Prepare
Functional Data and Process Model
4 Review
and Update Models
4 Prepare
Functional Specifications
4 Review
and Update Functional Specifications
4 Develop
Prototype
4 Setup
Environment
4 Review
Project
4 Review
and Update Project Plan
4 Metric
Definition, Capture and Reporting
4 Review
Phase Deliverables, Approve and Release
4 Perform
Final Inspection and Delivery
4 Causal
Analysis
Validation And Verification
8 Review
Conceptual Data Model
= Review
Conceptual Process Model
= Review
Functional Data Model
= Review
Functional Process Model
= Review
Functional Specifications
= Review
Prototype
= Review
Updated Software Project Plan
Exit Criteria
8 Approved
Functional Specification Document is available
= Approved
System Design Document (Functional Data Model and Functional
Process Model) is available.
= Updated
Software Project Plan is available
= Updated
Metrics are available
Phase Deliverables
8 Functional
Specifications Document
= System
Design Document (Functional Data Model and Functional Process
Model)
= Prototype
(Internal Project Team only)
= Updated
Software Project Plan
= Updated
Metric
|
|
|
| |
Low Level Design
Phase Description
The purpose of the Low Level Design Phase is to produce a detailed
design of the software components based on the High Level Design.
The Specifications for various software components of the system
are written during the Phase.
Entry Criteria
8 Software Project Plan is available
= Approved
Functional Specification Document is available
= Reviewed
System Design Document is available
Tasks
4 Plan and
prepare for Phase Execution
4 Conduct
Task Kick off Meeting
4 Prepare
Physical Data Model
4 Review
& Update Models
4 Prepare
Program Specifications
4 Review
and Update Program Specifications
4 Prepare
Unit Test Cases, Test Data
4 Review
and Update Unit Test Cases
4 Prepare
Integration Test Cases and Test Data
4 Review
and Update Integration Test Cases and Test Data
4 Prepare
Functional Test Cases, Test Data
4
Review and Update Functional Test Cases, Test Data 13. Setup
Environment
4 Review Project
4 Review and Update Project Plan
4 Metric Definition, Capture and Reporting
4 Review Phase Deliverables, Approve and Release
4 Perform Final Inspection and Delivery
4 Causal Analysis
Validation
And Verification
4
Review Program Specification
4 Review Physical Data Model
4 Review Unit Test Cases, test data
4 Review Integration Test Cases, test data
4 Review Functional Test Cases, test data
4 Review Updated Software Project Plan Exit Criteria
4 Program Specifications are released
4 Unit Test Cases and data are released
4 Integration Test Cases and data are released
4 Functional Test Cases and data are released
4 Updated Software Project Plan is released
4 Updated Metrics are available
4 Updated Functional Specification Document
4 Updated System Design Document
Phase Deliverables
8
Program Specifications
=
Physical Data Model
= Unit Test Cases & Test Data
= Integration Test Cases & Test Data
= Functional Test Cases & Test Data
= Updated Software Project Plan
= Updated
Metrics |
|
|
| |
|
Construction
Phase
Description
The purpose of the system Construction Phase
is to produce the software components. It uses the outputs of
the Low Level Design to produce Unit Tested software items.
Entry Criteria
8 Software Project Plan is available
= Functional
Specification and Low Level Design documents are available
= Unit Test
Cases and data are available
Tasks
4 Plan and
prepare for Phase Execution
4 Conduct
Task Kick off Meeting
4 Prepare
Program Code
4 Review
and Update Program Code
4 Conduct
Unit Testing
4 Setup Environment
4 Review Project
4 Review and Update Project Plan
4 Metric Definition, Capture and Reporting
4 Review Phase Deliverables, Approve and Release
4 Causal Analysis
Validation
And Verification
8
Review Program Code
=
Review Unit Test Results
= Review Updated Software Project Plan Exit Criteria
= Reviewed and Unit Tested Program Code is available
= Updated Unit Test Cases are available
= Updated Software Project Plan is available
= Updated Metrics is available Phase Deliverables
= Unit Tested Program Code
= Updated Unit Test Cases and data
= Updated Software Project Plan
= Updated Metrics |
|
|
| |
|
Testing
Phase Description
Purpose of this Phase is to test the software component for
integrated functionality of different modules. This Phase
is recursive and is to be repeated as many times as there
are levels of testing.
Entry Criteria
4
Software Project Plan is available
4
Successfully
Unit Tested Code is available
4
High Level
Design and Low Level Design documents are available
4
Integration
and Functional test cases and test data are available
Tasks
4 Plan
and prepare for Phase execution
4 Conduct
Task Kick off Meeting
4 Conduct
Integration Testing 4
Conduct Functional Testing
4 Prepare
User Documents
4 Review
and Update User Documents
4 Setup
environment
4 Review
Project
4 Review
and Update Project Plan
4 Metric
Definition, Capture and Reporting
4 Review
Phase Deliverables, Approve and Release
4 Perform
Final Inspection and Delivery
4 Causal
Analysis
Validation And Verification
8 Review
Integration Test Results
= Review
Functional Test results
= Review
Updated Software Project Plan
= Review
User Documentation Exit Criteria
= Tested
System is released
= Updated
Integration Test Cases and Test data are available
= Updated
Functional Test Cases and Test data are available
= User
Documentation is available
= Updated
Software Project Plan is available
= Updated
Metrics are available as Phase Deliverables
= Test
results
= User
Documentation
= Updated
Software Project Plan
= Updated
Metrics
|
|
|
| |
|
Acceptance
Phase Description
Based on the pre-defined Acceptance criteria, the Client conducts
the Acceptance Test during this Phase. Support is provided by
the Project Team if required by the Contract.
Entry Criteria
4
Successfully Functional Tested software is available
4 Software Project Plan is available
4 Acceptance Test Plan is available
4 User documents are available
Tasks
4
Plan and Prepare for Phase Execution
4 Conduct Task kick-off Meeting
4 Organize and Conduct User Training
4 Review and update User Documents
4 Provide Support for Acceptance
4 Review and Update Program Specifications
4 Review Project
4 Review and Update Project Plan
4 Metric Definition, Capture and Reporting
4 Causal Analysis
4 Obtain Project Sign-off
Validation And Verification
8
Review updated Software Project Plan
=
Review Updated User Documents
4 Review User Training Material
4 Review Program Specifications Exit Criteria
4 Accepted System is available
4 Acceptance letter is obtained from the Client
4 Updated User Documentation is available
4 Updated Program Specification are available
4 Updated Project Documents are available
4 Updated Metrics are available Phase Deliverables
4 Acceptance Letter
4 Updated Program Specifications
4 Updated Project
documents
4 Updated Software Project Plan
4 Updated Metrics
|
|
|
| ALLIANCES
| DOMESTIC
CLIENTELE | INTERNATIONAL
CLIENTELE |
