MPS has objective to deliver the highest possible quality projects and solutions that meet or exceed customer expectations. Quality, to MPS, is not a mere business generating strategy but a standard to be practiced by everyone in the organizational hierarchy. MPS’s Quality Management Systems are based on the best of industry standards. Moreover the quality management concept evolves from practical on-the-job lessons and the organization's strategy. Its implementation is effectively managed through a comprehensive, practical and well-designed process. Constant review and audit of this system ensures its applicability and use throughout the organization.

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:

 

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
Contract for project has been received from the client.
Tasks Initiate Project
Analyze request for proposal and Prepare Estimates
Establish / Review Capability Baseline
Prepare Software Project Plan
Review and Update Project Plan
Setup Environment
Induct Project Team
Review Project
Metric Definition, Capture and Reporting
Review Phase Deliverables, Approve and Release
Causal Analysis
Validation And Verification
Review Contract
Review Software Project Plan
Exit Criteria
Software Project Plan has been approved and released
Planned Project Metrics is available
Phase Deliverables
Software Project Plan
Planned metric  

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
Software Project Plan is available
Tasks
Plan and Prepare for Phase Execution
Conduct Task kick-off meeting
Study Existing System and Define User Requirement
Prepare Conceptual Data and Process Model
Review and Update Models
Prepare Functional Specifications
Review and Update Functional Specifications
Develop Prototype
Setup Environment
Review Project
Review and Update Project Plan
Metric Definition, Capture and Reporting
Review Phase Deliverables, Approve and Release
Perform Final Inspection and Delivery
Causal Analysis
Validation And Verification
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
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
Functional Specifications Document
System Design Document (Functional Data Model and Functional Process Model)
Prototype (Internal Project Team only)
Updated Software Project Plan
Updated Metric


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
Software Project Plan is available
Approved Functional Specification Document is available
Reviewed System Design Document is available
Tasks
Plan and prepare for Phase Execution
Conduct Task Kick off Meeting
Prepare Physical Data Model
Review & Update Models
Prepare Program Specifications
Review and Update Program Specifications
Prepare Integration Test Cases and Test Data
Review and Update Integration Test Cases and Test Data
Prepare Functional Test Cases, Test Data
Review and Update Functional Test Cases, Test Data 13. Setup Environment
Review Project
Review and Update Project Plan
Metric Definition, Capture and Reporting
Review Phase Deliverables, Approve and Release
Perform Final Inspection and Delivery
Causal Analysis
Validation And Verification
Review Program Specification
Review Physical Data Model
Review Unit Test Cases, test data
Review Integration Test Cases, test data
Review Functional Test Cases, test data
Review Updated Software Project Plan Exit Criteria
Program Specifications are released
Unit Test Cases and data are released
Integration Test Cases and data are released
Functional Test Cases and data are released
Updated Software Project Plan is released
Updated Metrics are available
Updated Functional Specification Document
Updated System Design Document
Phase Deliverables
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


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
Software Project Plan is available
Functional Specification and Low Level Design documents are available
Unit Test Cases and data are available
Tasks
Plan and prepare for Phase Execution
Conduct Task Kick off Meeting
Prepare Program Code
Review and Update Program Code
Conduct Unit Testing
Setup Environment
Review Project
Review and Update Project Plan
Metric Definition, Capture and Reporting
Review Phase Deliverables, Approve and Release
Causal Analysis
Validation And Verification
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


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
Software Project Plan is available
Successfully Unit Tested Code is available
High Level Design and Low Level Design documents are available
Integration and Functional test cases and test data are available
Tasks
Plan and prepare for Phase execution
Conduct Task Kick off Meeting
Conduct Integration Testing
Conduct Functional Testing
Prepare User Documents
Review and Update User Documents
Setup environment
Review Project
Review and Update Project Plan
Metric Definition, Capture and Reporting
Review Phase Deliverables, Approve and Release
Perform Final Inspection and Delivery
Causal Analysis
Validation And Verification
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


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
Successfully Functional Tested software is available
Software Project Plan is available
Acceptance Test Plan is available
User documents are available
Tasks
Plan and Prepare for Phase Execution
Conduct Task kick-off Meeting
Organize and Conduct User Training
Review and update User Documents
Provide Support for Acceptance
Review and Update Program Specifications
Review Project
Review and Update Project Plan
Metric Definition, Capture and Reporting
Causal Analysis
Obtain Project Sign-off
Validation And Verification
Review updated Software Project Plan
Review Updated User Documents
Review User Training Material
Review Program Specifications Exit Criteria
Accepted System is available
Acceptance letter is obtained from the Client
Updated User Documentation is available
Updated Program Specification are available
Updated Project Documents are available
Updated Metrics are available Phase Deliverables
Acceptance Letter
Updated Program Specifications
Updated Project documents
Updated Software Project Plan
Updated Metrics


OmniTracker CTS

Case Management
Solution

OmniTracker CRM

Client Relationship Mgmt. Solution

OmniTracker HRS

Job Recruitment Mgmt. Solution

OmniTracker TRMS

Talent Retention Mgmt. Solution

OmniTracker ESMS

Executive Schedule Mgmt. Solution

Help is on the way. Share your story
or specific requirement. We will
contact you within hours.