1. 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

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

3. ITU-T/SG17 27 th Nov 2002 3 ODP Viewpoints

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

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

6. ITU-T/SG17 27 th Nov 2002 6 5 Viewpoints on a WP package Technology - Package name, system requirementsTechnology - Package name, system requirements Computational - functionality as a set software componentsComputational - functionality as a set software components Engineering - inter-component and external communications, display servicesEngineering - inter-component and external communications, display services Information - things it understands – text, graphic, multi- media objects, fonts etcInformation - things it understands – text, graphic, multi- media objects, fonts etc Enterprise - organisational rules for how the package fits into the businessEnterprise - organisational rules for how the package fits into the business

7. ITU-T/SG17 27 th Nov 2002 7 ODP Viewpoints What the system is for What the system is about How it works How to put it together Computational Enterprise Technology Engineering Open System Information

8. ITU-T/SG17 27 th Nov 2002 8 Viewpoints and the Real World - the Enterprise Language is different! Real world systems and software Real world actors and things Enterprise specification Modelled as Isomorphisms Technology specification Modelled as Information specification Computationa l specification Engineering specification Modelled as

9. ITU-T/SG17 27 th Nov 2002 9 An ODP based specification process Technology Specification Information Specification Computational Specification Engineering specification Enterprise Specification

10. ITU-T/SG17 27 th Nov 2002 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)An enterprise specification defines the purpose, scope and policies of an ODP system. (Part 3, Clause 5) Purpose of 15414 | X.911: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. ITU-T/SG17 27 th Nov 2002 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):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. ITU-T/SG17 27 th Nov 2002 12 The Standard is silent about … Any form of development methodAny form of development method Any form of modelling methodAny form of modelling method Any form of notationAny form of notation but it is consistent with commonly used techniques such as UP and UML

13. ITU-T/SG17 27 th Nov 2002 13 Enterprise Language Concepts Community sub-objective 1 * Objective has 1 objective of * configuration of member of * * Enterprise Object 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. Contract defines 1 defined in *

14. ITU-T/SG17 27 th Nov 2002 14 Enterprise Language Concepts RoleActionBehaviour 1..* of * fulfils defined by * * defines 0..1 identified by 1 identifies part of collection of * 1 Community sub-objective 1 * Objective has 1 objective of * configuration of member of * * Enterprise Object Contract defines 1 defined in * 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. ITU-T/SG17 27 th Nov 2002 15 Enterprise Language Concepts Process Step 1has of * to meet1 * leads to 1..* graph ofpart of 1..* RoleActionBehaviour 1..* of * fulfils defined by * * defines 0..1 identified by 1 identifies part of collection of * 1 Community sub-objective 1 * Objective has 1 objective of * configuration of member of * * Enterprise Object Contract defines 1 defined in * Process: A collection of steps taking place in a prescribed manner and leading to an objective

16. ITU-T/SG17 27 th Nov 2002 16 Enterprise Language Concepts Process Step 1has of * to meet1 * leads to 1..* graph ofpart of 1..* RoleActionBehaviour 1..* of * fulfils defined by * * defines 0..1 identified by 1 identifies part of collection of * 1 Community sub-objective 1 * Objective has 1 objective of * configuration of member of * * Enterprise Object Contract defines 1 defined in * The concepts Resource, Artefact and Actor represent the parts played by Enterprise Objects in the behaviour being described Actor Artefact Resource requires * * essential to 1..* performed by participates in 1..* concerns referenced in *

17. ITU-T/SG17 27 th Nov 2002 17 Enterprise Language Concepts The concept Community Object, is used to refine an EO and its behaviour at a greater level of detail Process Step 1has of * to meet1 * leads to 1..* graph ofpart of 1..* RoleActionBehaviour 1..* of * fulfils defined by * * defines 0..1 identified by 1 identifies part of collection of * 1 Community sub-objective 1 * Objective has 1 objective of * configuration of member of * * Enterprise Object Contract defines 1 defined in * Actor Artefact Resource requires * * essential to 1..* performed by participates in 1..* concerns referenced in * Community Object represents0..1 refines1

18. ITU-T/SG17 27 th Nov 2002 18 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 Process Step 1has of * to meet1 * leads to 1..* graph ofpart of 1..* RoleActionBehaviour 1..* of * fulfils defined by * * defines 0..1 identified by 1 identifies part of collection of * 1 Community sub-objective 1 * Objective has 1 objective of * configuration of member of * * Enterprise Object Contract defines 1 defined in * Actor Artefact Resource requires * * essential to 1..* performed by participates in 1..* concerns referenced in * Community Object represents0..1 refines1 agreed to 1..* Contracting Party Party

19. ITU-T/SG17 27 th Nov 2002 19 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 Policy of *1..* has * part of set of 1..* Process Step 1has of * to meet1 * leads to 1..* graph ofpart of 1..* RoleActionBehaviour 1..* of * fulfils defined by * * defines 0..1 identified by 1 identifies part of collection of * 1 Community sub-objective 1 * Objective has 1 objective of * configuration of member of * * Enterprise Object Contract defines 1 defined in * Actor Artefact Resource requires * * essential to 1..* performed by participates in 1..* concerns referenced in * Community Object represents0..1 refines1 agreed to 1..* Contracting Party Party

20. ITU-T/SG17 27 th Nov 2002 20 Enterprise Language Concepts – Responsibility concepts An enterprise specification identifies those actions that involve accountability of a party. Action CommitmentDeclarationDelegationEvaluationPrescription

21. ITU-T/SG17 27 th Nov 2002 21 Enterprise Language Concepts – Core concepts Model Element CommunityEnterprise ObjectRoleAction Type Template has of * 1..* has for * * Policy governsgoverned by ** 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. ITU-T/SG17 27 th Nov 2002 22 Status IS 15414 | X.911 currently in course of publicationIS 15414 | X.911 currently in course of publication Concentrates on less contentious aspects:Concentrates on less contentious aspects: –behavioural concepts –organisational concepts (structuring communities) –policy concepts –responsibility concepts

23. ITU-T/SG17 27 th Nov 2002 23 Work in Progress PDAM in course of developmentPDAM 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 yearsShould 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

24. ITU-T/SG17 27 th Nov 2002 24 Benefits of using RM-ODP Coherent framework for diverse modelsCoherent framework for diverse models Separation of concerns to match stakeholders interestsSeparation of concerns to match stakeholders interests 2-way traceability from Business requirements to implementation2-way traceability from Business requirements to implementation Better control of development iterationsBetter control of development iterations Better business control of IT implementations and hence more business satisfactionBetter business control of IT implementations and hence more business satisfaction