Featured post

Functionality of Segment Value Inheritance ESS Process

  The Segment Value Inheritance process simplifies the maintenance of the chart of accounts. When the characteristics of values in the value...

Sunday 11 October 2015

R12 Methodology - OUM

R12 Methodology - OUM

http://atawaynt.ar.ataway.com/OUM/METHOD/OM40/OUM_E_6.3/OUM/OUM_HOME.HTM

OUM (Oracle Unified Method is new methodology to implement Oracle projects)
No more AIM Methodology.

OUM:  Oracle Unified Method
It has 5 phases.
Inception à Requirement Gathering and risk analysis
The overriding goal of the Inception phase is to have concurrence among all stakeholders on the
lifecycle objectives for the project. Therefore, the Inception phase is critical for all projects because
the scope of the effort, high-level requirements, and significant risks must be understood before the
project can proceed.

Eloboration à Design
The overriding goal of the Inception phase is to have concurrence among all stakeholders on the
lifecycle objectives for the project. Therefore, the Inception phase is critical for all projects because
the scope of the effort, high-level requirements, and significant risks must be understood before the
project can proceed.

Construction à Build
The goal of the Construction phase is to take the solution from detailed requirements models, through
configuration of standard packaged software functionality, development and testing of custom
components, and integration to a system that is ready for a first release that goes into production, often
a limited release and often called a beta release. In short, complete the development of the application
system, validate that all components fit together, and prepare the system for the acceptance test and
deployment.

Transition à Moving solution to production
The goal of the Transition phase is to take the completed solution from installation onto the
production system through the acceptance test to launch of the live application, open, and ready for
business. Validate that the system is tested systematically and is available for end users. During this
phase, the new system is accepted by the client organization, the organization is made ready for the
new system, and the system is put into production and, if the new system replaces an old one, a
smooth cutover to the new application is provided.

Production  à Opearating Production system
The goal of the Production phase is to operate the newly developed system, assess the success of the
system, and monitor and address system issues. This includes monitoring the system and acting
appropriately to maintain continued operation; measuring system performance; operating and
maintaining supporting systems; responding to help requests, error reports and feature requests by
users; and managing the applicable change control process so that defects and new features may be
prioritized and assigned to future releases and put into a plan for future enhancements.
Documents:
AN100 (AN à Analysis) à Functional Specification Document (MD050 Replacement)
DS140 (DS à Design Specification) è Technical Design Document (MD070 Replacement)
T020 (Unit Test Plan Document)
Refer below screen shot for details.

No comments:

Post a Comment

Please review my topic and update your comments

Note: only a member of this blog may post a comment.