We have a robust and efficient development and reengineering methodology, covering all phases of a project's lifecycle from strategic planning through construction to product launch and maintenance. Our methodology comprises following phases.

Vision and Strategy

The Vision and Strategy phase establishes the future direction and priorities for Business Systems Modernization. This phase translates the fundamental customer business strategy into a transformation strategy for business processes, information technology, and organizational change. It considers customer needs, best practices, and external drivers. By the end of this phase, the customer will have defined a set of business areas for change and determined when they are to be addressed.

Architecture

The Architecture phase establishes the concept/vision, requirements, and design for a particular business area or a target system. The process results in identifying the components of the target business system, their interrelationship, and the associated requirements and defining the releases to be used as the basis for the time phasing of development, integration, and deployment.

Development

The Development phase addresses the requirements, design, construction, modification, and testing of system components. It is performed separately for each defined work package within the release. (Dividing the release into work packages happens during the release development planning activity of Architectural Engineering / Development Coordination.) Each work package contains one or more configuration items. The different work packages comprising the release are integrated, piloted, and tested in combination during the subsequent Integration phase.

Integration

The Integration phase tests a release through a complete business cycle in the test environment, using test transactions, and�possibly�at the pilot site, using real business transactions at realistic volumes. A release that performs successfully in the test environment is accepted for piloting or, if no piloting is performed, for distribution to deployment sites. If the release is piloted and performs successfully, it is accepted for distribution to the deployment sites.

Deployment

The Deployment phase follows the Integration phase. When Integration concludes, the integration and deployment teams bring the following output together for deployment:

• An integrated, tested, and deployment-certified release
• A release that has been appropriately packaged for easy distribution to deployment sites
• Model views and test plans that have been updated to reflect any changes made during Intergation phase.
• The Template Site Deployment Plan, which will serve as the basis for the individual Site Deployment Plans that control implementation of the release at each deployment site.

The Deployment phase rolls out a release to deployment sites by:

• Developing detailed Site Deployment Plans
• Preparing each site in all specialty areas, for both constructive and deconstructive activities
• Implementing the release at each deployment site
• Obtaining acceptance of the release at each site
• Supporting initial operation at each site.

Operations and Support

Whereas the other parts of the life cycle focus on discrete projects, this part of the life cycle focuses on continuous service delivery. Providing continuous services means running or managing an existing system to the degree specified in established service level agreements. The existing system may be a newly released, recently modified, or legacy system.