Jump to content

Oracle unified method

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Kamranshafiei (talk | contribs) at 19:44, 12 June 2007 (Created page with ' oracle_corporation has developed the Oracle Unified Method (OUM) to achieve the vision of supporting the successful implementation of every...'). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

oracle_corporation has developed the Oracle Unified Method (OUM) to achieve the vision of supporting the successful implementation of every Oracle product – applications, middleware, and database. The current release, OUM 4.3, supports the complete range of technology projects including deep support for Service Oriented Architecture (SOA), Enterprise Integration, Custom Software, Identity Management (IdM), and Governance, Risk and Compliance (GRC). Upcoming releases of OUM will add integration of a complete set of Envision material, support for Oracle's Analytic and Business Intelligence products and technologies, and support for Oracle's full complement of Enterprise Application suites.



OUM is standards based. OUM leverages the de facto industry standard, Unified Process (UP)2 approach to developing and implementing software systems. Project managers use UP’s four-phase approach (inception, elaboration, construction, and transition) to make sure they and their stakeholders have a shared understanding of what is needed, choose a correct architecture, and transfer the ownership of the end-product to the stakeholders. OUM tailors and extends the Unified Process by incorporating addtional standards, field experience, and intellectual capital contributed by Oracle practitioners.

OUM is iterative and incremental. OUM recognizes the proven advantages of an iterative and incremental approach to development and deployment of information systems. Iterations allow the project team to get things right sooner, improve quality, and reduce rework. Tasks or groups of tasks within OUM may be iterated. OUM suggests certain "iteration groups," but these choices are up to the practitioners. Whether or not to iterate, as well as the number of iterations, varies. Tasks may be iterated to increase the quality of the work products to a desired level, to add sufficient level of detail, or to refine and expand the work products on the basis of user feedback. It is important that project managers strike a balance between iterations and scope control.