The Core Components Working Group (CCWG) provides techniques and methodologies for the development and reuse of business information.
Part 1 of Core Component Technical Specification (CCTS)
The Core Components Technical Specification (CCTS) describes and specifies a new approach to the well-understood problem of the lack of information interoperability between applications in the e-business arena. Traditionally, standards for the exchange of business data have been focused on static message definitions that have not enabled a sufficient degree of interoperability or flexibility. The CCTS presents a methodology for developing a common set of semantic building blocks that represent the general types of business data in use today and provides for the creation of new business vocabularies and restructuring of existing business vocabularies. Further information can be found in the project area.
The main goal of the UML Profile for Core Components 3.0 (UPCC) is to evolve the current UPCC 1.0 specification in order to meet the requirements of the Core Components Technical Specification 3.0.
The goals of the UML Profile for Core Components (UPCC) project are:
- To define a UML profile for the Core Components Technical Specification that allows UML tool vendors to customize their tools to be CCTS compliant. Better UML 2.1.1. tool support will lead to a growing CCTS user base.
- Make CCTS compliant information modeling accessible to a broad user base through standard UML tool support.
- Notwithstanding known problems with XMI interchange between UML tools, the UML profile will help to improve interchange between tools of different vendors
- The XMI representations of core component models based on the UPCC can be used for storage of core component definitions in business registries (e.g. ICG registry)
- Support the validation of structure and semantics of information models against the CCTS through specific validation rules.
- Clarify the basic concepts that a UPCC-compliant business document model is based on.
- Provide an unambiguous definition for UPCC business information models that allows an unambiguous mapping to deployment artifacts for IT systems. Note, that the mapping itself is not part of UPCC.
- To provide increased rigor and formality to the CCTS specification
These goals are achieved through the development of a formal UML profile for CCTS that includes stereotypes, tagged values, and OCL constraints.
The purpose of the UN/CEFACT Context Methodology (UCM) Project is to develop a context methodology and technical specification for organizing, expressing, assigning, and apllying context through the use of context values for a number of UN/CEFACT standard artefacts, such as Business Data Type, Business Information Entity, Business Message, Business Area, Business Process Models etc. The UCM will also be applicable further than the UN/CEFACT specifications. This project will start from the current context mechanism described in the Core Components Technical Specification (CCTS).
The project will provide a specific methodology for design time assembly of business documents in a semantic and reusable order. A key objective will be to maximize interoperability and reusability of business documents by providing support for families of business documents.
|Project Title||Project Name||Project Chair||Project Initiator||Supporters||Extra Budgetary Resources||Start Date||End Date||ODP 1||ODP 2||ODP 3||ODP 4||ODP 5||ODP 6||ODP 7||ODP 8||Aim of 2010|
|CCTS||Core Component Technical Specification V3.0 – Part 1 of CCTS||Jim Wilson||08.12.2004||31.12.2008||ODP 7|
|UPCC||UML Profile for Core Components V3.0 – Part 2 of CCTS||Philipp Liegl||01.10.2008||01.03.2011||ODP 6|
|UCM||UN/CEFACT Context Methodology V1.0||Scott Hinkelman||01.03.2005||30.06.2009||ODP 5|
|[CCBDA]||Core Component Business Document Assembly||Sue Probert||||||||ODP 1|