1 / 25

RM-ODP Enterprise Language ISO | ITU-T 15414 | X.911

RM-ODP Enterprise Language ISO | ITU-T 15414 | X.911. Sandy Tyndale-Biscoe (Convener ISO/JTC1/SC7/WG17) Sandy@Open-IT.co.uk. ITU-T/SG17 27 th Nov 2002. Outline. RM-ODP Viewpoints How the Enterprise Language fits into the overall ODP picture Motivation for the Enterprise Language

bambi
Download Presentation

RM-ODP Enterprise Language ISO | ITU-T 15414 | X.911

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RM-ODP Enterprise LanguageISO | ITU-T 15414 | X.911 Sandy Tyndale-Biscoe(Convener ISO/JTC1/SC7/WG17) Sandy@Open-IT.co.uk ITU-T/SG17 27th Nov 2002

  2. Outline • RM-ODP Viewpoints • How the Enterprise Language fits into the overall ODP picture • Motivation for the Enterprise Language • Enterprise Language Concepts • Current Status and Work in Progress

  3. ODP Viewpoints

  4. Enterprise Computational Information Open System Technology Engineering ODP Viewpoints The purpose, scope and policies for the organisation that will own the information system Information handled by the system and constraints on the use and interpretation of that information Functional decomposition of the system into objects suitable for distribution System hardware & software elements Infrastructure required to support distribution

  5. Enterprise Computational Information Open System Technology Engineering ODP Viewpoints The purpose, scope and policies for the organisation that will own the information system Information handled by the system and constraints on the use and interpretation of that information THESE ARE NOT LAYERS! ODP Viewpoints Functional decomposition of the system into objects suitable for distribution System hardware & software elements Infrastructure required to support distribution

  6. 5 Viewpoints on a WP package • Technology - Package name, system requirements • Computational - functionality as a set software components • Engineering - inter-component and external communications, display services • Information - things it understands – text, graphic, multi-media objects, fonts etc • Enterprise- organisational rules for how the package fits into the business

  7. What the system is for Enterprise What the system is about Computational Information Open System How it works Technology Engineering How to put it together ODP Viewpoints

  8. Real world actors and things Enterprise specification Modelled as Information specification Isomorphisms Modelled as Real world systems and software Computational specification Modelled as Modelled as Modelled as Engineering specification Technology specification Viewpoints and the Real World - the Enterprise Language is different!

  9. An ODP based specification process Technology Specification Enterprise Specification Engineering specification Information Specification Computational Specification

  10. The Enterprise Language Standard(ISO | ITU-T 15414 | X.911) - Motivation • An enterprise specification defines the purpose, scope and policies of an ODP system. (Part 3, Clause 5) • Purpose of 15414 | X.911: • Refine and extend the enterprise language defined in ITU-T Recommendation X.903 |ISO/IEC 10746-3 to enable full enterprise viewpoint specification of an ODP system; • Provide the terms and structuring rules to specify the purpose, scope and policies for an ODP system in a manner that is meaningful for the stakeholders for that system, including the owners, the users, the developers and the maintainers.

  11. Motivation • The RM-ODP Enterprise Language provides a common modelling language (set of terms and structuring rules for their use) so that stakeholders can discuss and agree about a system (or component): • how it fits into the business environment it supports, • its roles and responsibilities, • associated human roles and responsibilities, • what damage it can do to the business when it fails.

  12. The Standard is silent about … • Any form of development method • Any form of modelling method • Any form of notation but it is consistent with commonly used techniques such as UP and UML

  13. sub-objective * 1 defines defined in Contract Objective 1 * objective of 1 has * Community configuration of * member of * Enterprise Object Enterprise Language Concepts Community: A configuration of objects formed to meet an objective. The objective is expressed as a contract which specifies how the objective can be met.

  14. sub-objective * 1 defines defined in Contract Objective 1 * objective of 1 has * Community * defined by configuration of * * member of defines * Role Behaviour Action of fulfils 1 * identifies collection of Enterprise Object * 1..* identified by 1 0..1 part of Enterprise Language Concepts Role: Identifier for a behaviour, which may appear as a parameter in a template for a composite object, and which is associated with one of the component objects of the composite object.

  15. sub-objective * 1 defines defined in graph of part of * Step Contract Objective Process 1 * 1..* 1..* 1 to meet leads to objective of 1 of * has * 1 has Community * defined by configuration of * * member of defines * Role Behaviour Action of fulfils 1 * identifies collection of Enterprise Object * 1..* identified by 1 0..1 part of Enterprise Language Concepts Process: A collection of steps taking place in a prescribed manner and leading to an objective

  16. sub-objective * 1 defines defined in graph of part of * Step Contract Objective Process 1 * 1..* 1..* 1 to meet leads to objective of 1 of * has * 1 has Community * defined by configuration of * * member of defines * Role Behaviour Action of fulfils 1 * identifies collection of Enterprise Object * 1..* identified by 1 0..1 part of performedby * 1..* requires concerns 1..* * Resource essential to * Artefact referenced in Actor 1..* participates in Enterprise Language Concepts The concepts Resource, Artefact and Actor represent the parts played by Enterprise Objects in the behaviour being described

  17. sub-objective * 1 defines defined in graph of part of * Step Contract Objective Process 1 * 1..* 1..* 1 to meet leads to objective of 1 of * has * 1 has Community * defined by refines 1 configuration of * * member of defines * represents 0..1 Role Behaviour Action of fulfils 1 * identifies collection of Community Object Enterprise Object * 1..* identified by 1 0..1 part of performedby * 1..* requires concerns 1..* * Resource essential to * Artefact referenced in Actor 1..* participates in Enterprise Language Concepts The concept Community Object, is used to refine an EO and its behaviour at a greater level of detail

  18. sub-objective agreed to 1..* * 1 defines defined in graph of part of * Step Contract Objective Process 1 * 1..* 1..* 1 to meet leads to objective of 1 of * has * 1 has Community * defined by refines 1 configuration of * * member of defines * represents 0..1 Role Behaviour Action of fulfils 1 * identifies collection of Community Object Enterprise Object * 1..* identified by 1 0..1 part of performedby * Party 1..* requires 1..* concerns 1..* Contracting Party * Resource essential to * Artefact referenced in Actor 1..* participates in Enterprise Language Concepts Party: An enterprise object modelling a natural person or any other entity considered to have some of the rights, powers and duties of a natural person

  19. sub-objective agreed to 1..* * 1 defines defined in graph of part of * Step Contract Objective Process 1 * 1..* 1..* 1 to meet leads to 1..* set of objective of 1 of * has * * part of Policy * 1..* 1 has of has Community * defined by refines 1 configuration of * * member of defines * represents 0..1 Role Behaviour Action of fulfils 1 * identifies collection of Community Object Enterprise Object * 1..* identified by 1 0..1 part of performedby * Party 1..* requires 1..* concerns 1..* Contracting Party * Resource essential to * Artefact referenced in Actor 1..* participates in Enterprise Language Concepts Policy: A set of rules related to a particular purpose. A rule can be expressed as an obligation, an authorization, a permission or a prohibition

  20. Action Commitment Declaration Delegation Evaluation Prescription Enterprise Language Concepts – Responsibility concepts An enterprise specification identifies those actions that involve accountability of a party.

  21. Type of * has 1..* governs governed by Policy Model Element for * * has * Template * Community Enterprise Object Role Action Enterprise Language Concepts – Core concepts This diagram is still wrong!Diagrammatic representation of these concepts is still on-going work (as part of PDAM), but it will show (when correct) how the basic (Part 2) concepts of Type and Template may be applied to many enterprise language concepts, and how Policy may be applied to instances of almost all EL concepts, including policies themselves.

  22. Status • IS 15414 | X.911 currently in course of publication • Concentrates on less contentious aspects: • behavioural concepts • organisational concepts (structuring communities) • policy concepts • responsibility concepts

  23. PDAM in course of development Some (minor) refinement of concepts that were contentious when IS15414 went to press Inclusion of a comprehensive explanatory annex Inclusion of a “metamodel” – non-normative but useful for tool builders and for WG19 NWI. Should be complete and issued in about 2 years 2003-07: FPDAM Ballot start 2003-11: FPDAM Ballot close 2004-02: FDAM ballot start 2004-08: FDAM available for publication Work in Progress

  24. Benefits of using RM-ODP • Coherent framework for diverse models • Separation of concerns to match stakeholders interests • 2-way traceability from Business requirements to implementation • Better control of development iterations • Better business control of IT implementations and hence more business satisfaction

More Related