don't insert so many links idiot

Archive for the ‘Specification’ Category.

Review Cycle for UMM 2.0 Public Draft has been extended

The UMM 2.0 Specifications (both, foundation and base) are currently in ODP Step 5, which means they are currently a public draft. The review cycle for the draft has been extended to 31st October – that’s one week before the forum meeting in Senegal. We kindly encourage our stakeholders to go through the draft and file comments if needed.

The UMM 2.0 Public Draft (and always the version of the UMM 2.0 spec) is located at

http://www.untmg.org/umm/spec/foundation/2_0

UMM 2.0 – Internal Draft Specification available

The UMM 2.0 specification has finished step 3 of the Open Development Process (Internal Draft) and has now entered phase 4 (Internal Review). Feel free to read through the specification and learn more about the great enhancements the UMM 2.0 standard has in comparision to the UMM 1.0.

The UMM 2.0 internal draft specification can be found on the internal UN/CEFACT collaborative website under the following link:

UMM 2.0 Internal Draft specification

Next UN/CEFACT forum meeting in Mexico City

The next UN/CEFACT forum meeting will be held in Mexico City from April 7 – 11. The entire UMM-Dev team will attend the meeting and the release of the first draft of the UMM 2.0 standard is planned for the end of the forum meeting.

See you there!

Pre-draft REA Profile for Enterprise Architect available

Yellow FolderFor those interested we have uploaded a first version of the UML Profile for REA for Enterprise Architect together with a (still incomplete) test model. We will continue our collaborative work with Prof. McCarthy in order to allow for a seamless integration of REA into the UMM.

REA will become a specialization module of UMM

Bill McCarthy from Michigan State university is currently in Vienna and we are working together on a UMM specialization module for REA (Resources-Events-Agents). The REA Enterprise Information Architecture covers the value chain and supply chain of an enterprise system. A first version of the specialization is scheduled for the UMM Forum meeting taking place in Mexiko City from the 7th – 11th April 2008.

More information on REA can be found on Prof. McCarthy’s website.

New package structure in UMM 2.0

UMM 2.0 will have an enhanced package structure which greatly facilitates modeling.

Changes in the package structure:

  • The BusinessDomainView has moved into the BusinessRequirementsView
  • There is now a dedicated BusinessPartnerView in the BusinessRequirementsView
  • The BusinessProcessView does not exist any more. Instead the BusinessProcessActivityGraph is located directly under the corresponding BusinessProcess
  • The former BusinessTransactionView is now called BusinessChoregraphyView
  • BusinessInteractionView and TransactionRequirementsView are now merged into the new BusinessTransactionView which is located underneath the BusinessChoreographyView
  • The BusinessTransaction is now located directly under the corresponding BusinessTransactionUseCase
  • CollaborationRequirementsView and BusinessCollaborationView are now merged into the new BusinessCollaborationView
  • The BusinessCollaborationProtocol is now located directly under the corresponding BusinessCollaborationUseCase
  • CollaborationRealizationView remains unchanged
  • The BusinessInformationView is now a dedicated view

UMM 2.0 new package structure

View an animated Powerpoint slide illustrating the transition from the UMM 1.0 package structure to the UMM 2.0 package structure: UMM 2.0 Re-Packaging

TMG F2F Meeting in Zurich: UMM 2.0 First Draft is approaching

UN/CEFACT TMG is currently meeting in Zurich at SAP Regensdorf. The major work item within the Business Process Working Group (BPWG) for this week is the 1st Draft of the UMM 2.0 specification. The major benefits of UMM 2.0 will be:

  • UMM 2.0 will be defined as a UML 2.0 profile
  • Re-packaging (flattening) of the UMM meta model
  • Eliminating the complex “maps to” relationships
  • A business transaction may now comprise up to two responding business documents in order to represent different business intentions (e.g., a positive and a negative response to a purchase order)
  • Shortened names of stereotypes
  • In general, the UMM meta model will be less strict – especially during the requirements elicitation phase – as well as less complex

We hope to publish first results at the end of this week. Stay tuned…