Professional Documents
Culture Documents
AIM - Methodlogy Pksss001
AIM - Methodlogy Pksss001
AIM is a framework of related elements. It involves phases, processes, tasks and dependencies:
A task is a unit of work, which results in a single deliverable. That deliverable may take many different forms like reports,
schedules, code, or test results for example.
A process is a closely related group of dependent tasks, which meets a major objective. A process is usually based on a common
discipline.
A phase is a chronological grouping of tasks. It enables a flexible way to organize tasks, schedule major deliverables, and deliver
projects.
Phases
An AIM project is conducted in phases that provide quality and control checkpoints to co-ordinate project activities that have a
common goal. During a project phase, your project team will be executing tasks from several processes. A brief description of the AIM
processes are given below:
1. Definition: This consist of review the organization's business objectives, evaluate the feasibility of meeting those objectives under time,
resource, and budget constraints. Moreover this can be best consider as SOW(statement of work) preparation phase.
2. Operations Analysis:During Operations Analysis, the project team develops Business Requirements Scenarios based on deliverables from
Definition that are used to assess the level of fit between the business requirements and standard application functionality. Gaps are identified
and corresponding solutions developed. The analysis results in a proposal for conducting business operations under the envisioned application
technical architecture. Solutions for gaps evolve into detailed designs during Solution Design.
3. Solution Design:The purpose of Solution Design is to develop the detailed designs for the optimal solutions to meet the future business
requirements. During this phase, project team members create detailed narratives of process solutions developed during Operations Analysis.
Supporting business requirements may require building application extensions to standard features; several alternative solutions may have
been defined during Operations Analysis. The project team carefully scrutinizes these solutions and chooses the most cost effective
alternatives.
4. Build:The coding and testing of all customizations and other custom software including enhancements, data conversions, and interfaces is
done during Build. Policy and procedure changes relating to business process modifications are developed. Business system testing is
performed to validate that the developed solutions meet business requirements. If customizations, extensions, or conversions are not
required, Build is still important because it includes the business system test, which is commonly conducted as a formal conference room
pilot. The business system test validates the solutions and is performed in an environment that closely resembles production.
5. Transition: During Transition, the project team deploys the finished solution into the organization. All the elements of the implementation
must come together to transition successfully to actual production. The project team trains the end users while the technical team configures
the production environment and converts data. Transition ends with the cutover to production, when end users start performing their job
duties using the new system.
6.Production: Production begins immediately with the production cutover. It marks the last phase of the implementation, and the beginning
of the system support cycle. Included in this final phase is a series of refinements and performance measurement steps. The inhoues MIS/IT
Department personnel work quickly to stabilize the system and begin regular maintenance. They will provide the ongoing support to the
organization for the remaining life of the system. During Production, you compare actual results to project objectives.