Menu Content/Inhalt
Standards PDF Print E-mail

Below you can find the standards in which MODELPLEX project is working around. We have detailed the relevance of these standards to achieve MODELPLEX´s objetives.

If you want to get further details or collaborate in the promotion of these standardisation proposals please contact at: jason dot mansell at esi dot es

 

OMG – Object Management Group

 

Name Software Process Engineering Model version 2 (SPEM2) RFP
Description This specification presents the Software Process Engineering Metamodel (SPEM). This metamodel is used to describe a concrete software development process or a family of related software development processes. Process enactment is outside the scope of SPEM, although some examples of enactment are included for explanatory purposes.
Modelplex participants and role Adaptive (submitter), ESI (submitter), SOFTEAM (submitter), TRT (submitter), LIP6 (supporter)
Relevance to MODELPLEX Provide input from the results of WP2 (Framework building) related with the process enactment so that the MODELPLEX process enactment issues are considered for future SPEM 2.0.
Related Word Package WP2 - Framework building

 

Name UML 2.2 RTF
Description A specification defining a graphical language for visualizing, specifying, constructing, and documenting the artifacts of distributed object systems.
Modelplex participants and role SOFTEAM participates in the UML2.1 RTF. This consolidation work will lead to the UML2.2 standard.

ADAPTIVE is co-chair.

Relevance to MODELPLEX UML is used as the main modelling language within MODELPLEX. Its metamodel is the starting point of many MDA implementations within MODELWARE.
Related Word Package WP2 - Framework building

 

Name UML Profile for DoDAF and MODAF
Description An RFP was issued in September 2005, seeking an UML Profile for the Department of Defence Architecture Framework (DoDAF) and the Ministry of Defence Architecture Framework (MODAF). At stake is the standardization of an unambiguous domain model and representations for DoDAF and MODAF, with interchange support across tools.
Modelplex participants and role ADAPTIVE: submitter

TRT: supporter

Relevance to MODELPLEX Foreseen general impact of the standard is large:

•DoDAF/MODAF modelling tool interoperability. First implementations probably Q2-Q3 2007.

•De facto acceptance in the defence domain.

•Also, may constitute the basis for a de facto enterprise architecture standard.

Architecture Frameworks are a key component of model-driven solutions for complex systems, as developed by MODELPLEX. DoDAF and MODAF are de-facto standards in the community, where they are used more and more outside of the defence domain. Due to their acceptance and scope, they are key elements of the MODELPLEX baseline.

The UML Profile for DoDAF and MODAF moreover opens the way for broader support to Architecture Frameworks in OMG. In particular, viewpoint formalisation requires MOF-level standards that the current initiative could help support.

Related Word Package WP5 - System management

 

Name UML Profile and Metamodel for Services
Description OMG’s position in SOA world

The OMG is currently defining its position with respect to SOA. OMG’s place in SOA is to enable the architect span the business and technical perspectives using MDA. The OMG is thus aiming at complementing the work of other organisations such as OASIS, W3C or the Open Group, covering existing gaps in the SOA community where a large number of technology-specific programming standards are elaborated, through providing technology-independent modelling solutions for the architects.

UML Profile for SOA RFP

An initial RFP is being drafted to address a foundational technology-independent service model.

SOA RFP goal – current status:

• A common vocabulary and metamodel to unify the diverse definitions that exist in industry.

• Clarify UML semantics concerned with service modelling and establish modelling best practices. UML as main target; SySML may be considered, but not a goal (could be addressed by a submitter).

• Support a service contract describing the requirements for the collaboration between providers and requestors, separating requirements specification, service specification from service realisation.

• Integrate with and complement relevant standards at OASIS, W3C, Open Group.

• Enable abstract service model, raise level of abstraction, MDA dimension. Decouple service design from technologies.

Modelplex participants and role IBM and Adaptive: Submitters

ESI: CoSubmitter

TRT and Softeam: Supporters

Relevance to MODELPLEX SOA is a key paradigm for complex systems engineering and integration. At least the Thales industrial case in MODELPLEX is using this architectural style. The MODELPLEX MDE solutions will incorporate service description models and service-oriented architecture models.
Related Word Package WP2 - Framework building, WP4 - Verification and validation and WP5 - System management

 

Name Diagram Definition
Description This new OMG standard will define a MOF-based metamodel for defining diagram types for metamodels and thus form the basis for defining viewpoints.
Modelplex participants and role ADAPTIVE (Authoring the RFP)
Relevance to MODELPLEX Diagram definition is relevant to MODELPLEX for the complex system’s architecture modelling and for the language engineering.
Related Word Package WP2 - Framework building and WP3 - Model engineering

 

Eclipse Foundation

 

Name Traceability in the Eclipse Modelling project
Description There is a need to standardise the concept of traceability links so that different tool vendors can populate a standardised traceability repository. There is currently no initiative to this end in Eclipse, but the Eclipse Modelling project is a suitable place where this is highly relevant. We will pursue to include traceability in this project.
Modelplex participants and role SINTEF, initiator
Relevance to MODELPLEX Direct results from WP3 (Model engineering), task 3.2 (Composition & Refinement)on traceability.
Related Word Package WP3 - Model engineering

 

ETSI – European Telecommunications Standards Institute

 

Name Testing and Test Control Notation Version 3 (TTCN-3)
Description Maintenance of TTCN-3 Language, standardization on next version of TTCN-3
Modelplex participants and role FHG - Special Task Force members, standardization members
Relevance to MODELPLEX TTCN-3 is the test suite language used for test execution and evaluation. Mapping rules between TTCN-3 and U2TP exist to support existing test infrastructure.
Related Word Package WP3 - Model engineering

 

ISO – International Standardization Organisation

 

Name ISO/IEC 15909-2 Software and Systems Engineering - High-level Petri Nets
Description Define a modelling language and its transfer format, known as High-level Petri Nets.
Modelplex participants and role LIP6 (Committer)
Relevance to MODELPLEX Important for WP4 (Verification and validation), task 4.3 (Model based Verification) - it is important to use a standardized language and metamodel to activate verification tools.
Related Word Package WP2 - Framework building and WP3 - Model engineering

 

If you want to get further details or collaborate in the promotion of these standardisation proposals please contact at: jason dot mansell at esi dot es

 

 
[ Back ]

Events

August 2010 September 2010 October 2010
Mo Tu We Th Fr Sa Su
Week 35 1 2 3 4 5
Week 36 6 7 8 9 10 11 12
Week 37 13 14 15 16 17 18 19
Week 38 20 21 22 23 24 25 26
Week 39 27 28 29 30

Search

MODELPLEX mailing list



Receive HTML?