|
|
| |
| Our technical capabilities : |
|
|
|
|
 |
Methodology : |
|
| We have been following below Methodology : |
|
|
AIM |
|
PRINCE2 |
|
RUP |
|
If any Client Methodology |
|
| |
|
|
|
|
AIM : |
|
AIM has seven stages.
The objectives of each of the seven stages may be summarized as follows: |
 |
|
Strategy |
|
Determine the strategic objectives, high level functions and key data required |
|
|
|
|
|
|
|
Analysis |
|
Conduct detailed analysis of elementary functions and data elements |
|
|
|
|
|
|
|
Design |
|
Develop a design blueprint for the system modules and tables |
|
|
|
|
|
|
|
Documentation |
|
Prepare system and end-user documentation for the application |
|
|
|
|
|
|
|
Build |
|
Build the modules and tables of the application |
|
|
|
|
|
|
|
Transition |
|
Transition to the new system |
|
|
|
|
|
|
|
Production |
|
Support the WIP system in production |
|
|
 |
|
|
The following are the highlights of key activities of each stage : |
|
Strategy Stage |
|
|
Identify key management objectives, priorities and constraints |
 |
Document business needs, goals and direction |
|
Formulate a development plan that provides a framework for database |
|
Development throughout the enterprise |
|
Obtain management consensus and commitment |
|
Agree on the business terminology |
|
Identify and analyze significant entities |
|
Determine significant entities, relationships and attributes |
|
Create a high-level entity-relationship model |
|
Create a high-level function hierarchy model |
|
|
|
|
Develop detail function model |
|
Determine initial volumes of data and frequencies of functions |
|
Develop fully defined entity-relationship model |
|
Formalize preliminary transition needs like testing, conversion & training |
|
Cross check models for accuracy and completeness |
|
Determine distribution requirements |
|
Review models with end users |
|
Determine known system constraints |
|
|
|
|
Define system architecture |
|
Determine detailed database sizing |
|
Construct logical and physical database schemas |
|
Document performance and optimization issues |
|
Determine initial program/ module structures |
|
Plan for training and documentation |
|
|
|
|
Finalize the development environment |
|
Build program modules |
|
Perform unit testing |
|
Design manual proceeds |
|
Perform System Testing |
|
|
|
|
|
Develop systems documentation |
|
Develop end user training |
|
Develop end user documentation-user guides and reference manuals |
|
|
|
|
|
|
Perform data take-on and conversion |
|
Conduct pre-production user review |
|
Conduct acceptance testing |
|
Deliver user training and education |
|
Execute a trial transition |
|
Perform a trial run |
| |
|
|
Obtain system acceptance |
|
|
|
Conduct system monitoring |
|
Provide support procedures |
|
Perform spot & integrity checks |
|
Conduct post production reviews and necessary reworking |
|
|
|
|
Perform data take-on and conversion |
|
Conduct pre-production user review |
|
Conduct acceptance testing |
|
Deliver user training and education |
|
Execute a trial transition |
|
Perform a trial run |
| |
|
|
Obtain system acceptance |
|
|
|
|
|
PRINCE 2 : |
|
PRINCE2 is a structured method providing organizations with a standard approach to the management of projects. The method embodies proven and established best practice in project management. It is widely recognized and understood, and so provides a common language for all participants in the project.
|
PRINCE2 provides benefits to the organization, as well as the managers and directors of the project, through the controllable use of resources and the ability to manage business and project risk more effectively. PRINCE2 enables projects to have :
|
|
|
|
A controlled and organized start, middle and end |
|
Flexible decision points |
|
The involvement of management and stakeholders at the right time and place during the project |
|
Regular reviews of progress against plan and against the Business Case |
|
Automatic management control of any deviations from the plan |
|
Good communication channels between the project, Project Management, and the rest of the organization |
|
 |
|
|
|
|
|
|
Rational Unified Process (RUP) |
|
Project has four phases |
|
Inception - Capture requirements and establish the project boundaries |
|
Elaboration - Baseline the data, process, rules and architecture of the system |
|
Construction - Build the system incrementally; develop and test rules |
|
Transition - Ensure the software is available for its end users |
|
Each phase has specific tasks to accomplish : |
|
Data track - Produce the data model, and possibly the database |
|
Process track - Determine the interactions between the solution and its users |
|
Business rule track - Capture, analysis, automation and change of business rules |
|
Technology track - Select, customize and support the technology used |
|
 |
|
