Saturday, March 25, 2017

OAGi Development Methodology for 2016

We are pleased to announce that we have released an updated version of the OAGi Development Methodology.

Our OAGi Development Methodology has been updated every year since the year 2000.  It has brought us through early XML (DTD's), XML Schema, ebXML, Web Services, UN/CEFACT Core Components release 2.01, UN/CEFACT Core Components 3.0 and now JSON.

The Methodology lays out how to form a Working Group, How to run a Working Group, and four phases of development for building OAGIS content. The purpose of the OAGi Development Methodology is to provide a documented, step-by-step, repeatable, and open process for building OAGi open standards.

The OAGi standards development methodology includes four major phases each consisting of multiple activities and deliverables. This is an executive summary of those activities and deliverables. Please refer to the full documentation on the OAGi website Full Document.

The methodology is based on a commitment to timely delivery, quality and incorporation of all the available best practices and is subject to change and adjustments as newer and more relevant methods and process become available.

The four major phases of the Methodology consist of:

  • Definition – establish and approve a Working Group

  • Construction – creation of the deliverables

  • Review and Approval – internal approvals and incorporation of public input

  • Publication – packaging, deliver general available release and announce

OAGi Development Methodology Phases
Minimize

The Definition Phase consists of several goals and associated deliverables:

  • Define the boundaries and scope of a proposed Working Group
    - PowerPoint Project Definition completed (What, Why, Who and Impact

  • Select a Leader/Chair and establish a team of willing participants
    - Completed presentation ready for approval including expected workflow

  • Obtain approval to establish the Working Group from the Policy Board
    - Majority approval of the Policy Board and also of the Council if sponsored by a Council

  • Obtain IP signatures for all participants
    - All participants provide company signatures via last page of presentation prior to attending any session or obtaining access to a Group or Site Work area

  • Establish a Group (Yahoo or Google) for the Working Group to manage their tasks and deliverables

  • Full coordination with the Architecture Working Group

The Construction Phase consists of several goals and associated deliverables:

  • Refine the Working Group existing standard and domain impact as well as process deliverables
    - Agreed to Process maps (Scenarios) that includes impacted messages and flow that will be needed or that will need to be changed – including exception handling
    - Agreed to schedules and delivery dates – including which OAGIS release it will be included in.

  • Define the messages (BODs) and their detailed contents including Nouns, Components, Elements and Fields using the existing OAGIS frameworks and library and then defining and justifying new if needed – this includes the UML Class diagrams, schema files and instance examples

  • Coordinate with the Architecture and Quality Working Groups

  • Documentation that outlines the business value and reasons for message and process selection

  • Documentation of all coordination and collaboration with other industry organizations to ensure the appropriate “due diligence” was invested in standards reuse and incorporation

  • Documentation of all expected values, processes, XSD components, instance expectations, scenarios, diagrams, use cases and version differences are developed and delivered in this phase

The Review and Approval Phase includes these goals and deliverables:

  • Provide final versions of all previous deliverables

  • Affirmative vote by the Working Group concerning all previous work

  • Affirmative vote from the Policy Board and OAGi staff to move to Public Review

  • Completed 30 or 60 day Public Review

  • Review and dispensation of all requests from all OAGi groups and the Public Review

  • Approval of by the Architecture and Quality Working Groups

  • Affirmative vote by the OAGi Policy Board for release

The Publication Phase incorporates these goals and deliverables:

  • Incorporation of all previous deliverables into a release

  • Resolution of any final defects

  • Creation of a deliverable package that is made available for public consumption

  • Publication of the deliverable packages on the appropriate OAGi site for downloading

  • Creation and delivery or supporting marketing and publication deliverables as appropriate

  • Collection and packaging of all Working Group materials for archival

  • Recognition of all involved

Privacy Statement  |  Terms Of Use
Copyright 2017 Open Applications Group, Inc. All Rights Reserved