This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• RM-ODP ViewpointsRM-ODP Viewpoints– How the Enterprise Language fits into the overall How the Enterprise Language fits into the overall
ODP pictureODP picture
• Motivation for the Enterprise LanguageMotivation for the Enterprise Language• Enterprise Language ConceptsEnterprise Language Concepts• Current Status and Current Status and Work in ProgressWork in Progress
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
OpenSystem
InformationInformation
THESE ARE N
OT LAYERS!
THESE ARE N
OT LAYERS!
6ITU-T/SG17 27th Nov 2002
5 Viewpoints on a WP package5 Viewpoints on a WP package
• TechnologyTechnology - - Package name, system requirementsPackage name, system requirements
• ComputationalComputational - - functionality as a set software componentsfunctionality as a set software components
• EngineeringEngineering - - inter-component and external communications, inter-component and external communications, display servicesdisplay services
• InformationInformation - - things it understands – text, graphic, multi-things it understands – text, graphic, multi-media objects, fonts etcmedia objects, fonts etc
• EnterpriseEnterprise - organisational rules for how the package fits into - organisational rules for how the package fits into the businessthe business
7ITU-T/SG17 27th Nov 2002
ODP ViewpointsODP Viewpoints
What the system is for
What the system is about
How it works
How to put it together
ComputationalComputationalEnterpriseEnterprise
TechnologyTechnology EngineeringEngineering
OpenSystem
InformationInformation
8ITU-T/SG17 27th Nov 2002
Viewpoints and the Real World - the Viewpoints and the Real World - the Enterprise Language is different!Enterprise Language is different!
Real world systems and software
Real world actors and thingsEnterprise
specificationModelled as
Isomorphisms
Technology specification
Modelled as
Information specification
Computational
specification
Engineering specification
Modelled as
Modelled as
Modelled as
9ITU-T/SG17 27th Nov 2002
An ODP based specification processAn ODP based specification process
Technology Technology SpecificationSpecification
Information Information SpecificationSpecification
The Enterprise Language StandardThe Enterprise Language Standard((ISO | ITU-T 15414 | X.911) - ISO | ITU-T 15414 | X.911) -
MotivationMotivation
• An enterprise specification defines the purpose, An enterprise specification defines the purpose, scope and policies of an ODP system. (Part 3, scope and policies of an ODP system. (Part 3, Clause 5)Clause 5)
• Purpose of 15414 | X.911:Purpose of 15414 | X.911:– Refine and extend the enterprise language defined in ITU-T Refine and extend the enterprise language defined in ITU-T
Recommendation X.903 |ISO/IEC 10746-3 to enable full Recommendation X.903 |ISO/IEC 10746-3 to enable full enterprise viewpoint specification of an ODP system;enterprise viewpoint specification of an ODP system;
– Provide the terms and structuring rules to specify the Provide the terms and structuring rules to specify the purpose, scope and policies for an ODP system in a manner purpose, scope and policies for an ODP system in a manner that is meaningful for the stakeholders for that system, that is meaningful for the stakeholders for that system, including the owners, the users, the developers and the including the owners, the users, the developers and the maintainers.maintainers.
11ITU-T/SG17 27th Nov 2002
MotivationMotivation
• The RM-ODP Enterprise Language provides a The RM-ODP Enterprise Language provides a common modelling language (set of terms and common modelling language (set of terms and structuring rules for their use) so that stakeholders structuring rules for their use) so that stakeholders can discuss and agree about a system (or can discuss and agree about a system (or component):component):– how it fits into the business environment it supports,how it fits into the business environment it supports,– its roles and responsibilities,its roles and responsibilities,– associated human roles and responsibilities,associated human roles and responsibilities,– what damage it can do to the business when it fails.what damage it can do to the business when it fails.
12ITU-T/SG17 27th Nov 2002
The Standard is silent about …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 but it is consistent with commonly used techniques such as UP and UMLtechniques such as UP and UML
13ITU-T/SG17 27th Nov 2002
Enterprise Language Concepts Enterprise Language Concepts
Community
sub-objective
1*
Objective
has1objective 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
*
14ITU-T/SG17 27th Nov 2002
Enterprise Language ConceptsEnterprise Language Concepts
Role ActionBehaviour1..*
of
*
fulfils
defined by
*
*defines
0..1 identified by1identifies
part of
collection of *
1
Community
sub-objective
1*
Objective
has1objective 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.
15ITU-T/SG17 27th Nov 2002
Enterprise Language ConceptsEnterprise Language Concepts
Process Step
1 has
of *
to meet1
*
leads to 1..*
graph of part of
1..*
Role ActionBehaviour1..*
of
*
fulfils
defined by
*
*defines
0..1 identified by1identifies
part of
collection of *
1
Community
sub-objective
1*
Objective
has1objective 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
16ITU-T/SG17 27th Nov 2002
Enterprise Language ConceptsEnterprise Language Concepts
Process Step
1 has
of *
to meet1
*
leads to 1..*
graph of part of
1..*
Role ActionBehaviour1..*
of
*
fulfils
defined by
*
*defines
0..1 identified by1identifies
part of
collection of *
1
Community
sub-objective
1*
Objective
has1objective 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..*
performedby
participates in1..*
1..*
concerns
referenced in*
17ITU-T/SG17 27th Nov 2002
Enterprise Language ConceptsEnterprise Language Concepts
The concept Community Object, is used to refine an EO and its behaviour at a greater level of detail
Process Step
1 has
of *
to meet1
*
leads to 1..*
graph of part of
1..*
Role ActionBehaviour1..*
of
*
fulfils
defined by
*
*defines
0..1 identified by1identifies
part of
collection of *
1
Community
sub-objective
1*
Objective
has1objective of
*
configuration of
member of
*
*
Enterprise Object
Contract defines
1
defined in
*
Actor
Artefact
Resource
requires*
*
essential to
1..*
performedby
participates in1..*
1..*
concerns
referenced in*
Community Object
represents 0..1
refines 1
18ITU-T/SG17 27th Nov 2002
Enterprise Language ConceptsEnterprise 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
1 has
of *
to meet1
*
leads to 1..*
graph of part of
1..*
Role ActionBehaviour1..*
of
*
fulfils
defined by
*
*defines
0..1 identified by1identifies
part of
collection of *
1
Community
sub-objective
1*
Objective
has1objective of
*
configuration of
member of
*
*
Enterprise Object
Contract defines
1
defined in
*
Actor
Artefact
Resource
requires*
*
essential to
1..*
performedby
participates in1..*
1..*
concerns
referenced in*
Community Object
represents 0..1
refines 1
agreed to1..*
1..*
Contracting PartyParty
19ITU-T/SG17 27th Nov 2002
Enterprise Language ConceptsEnterprise 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
1 has
of *
to meet1
*
leads to 1..*
graph of part of
1..*
Role ActionBehaviour1..*
of
*
fulfils
defined by
*
*defines
0..1 identified by1identifies
part of
collection of *
1
Community
sub-objective
1*
Objective
has1objective of
*
configuration of
member of
*
*
Enterprise Object
Contract defines
1
defined in
*
Actor
Artefact
Resource
requires*
*
essential to
1..*
performedby
participates in1..*
1..*
concerns
referenced in*
Community Object
represents 0..1
refines 1
agreed to1..*
1..*
Contracting PartyParty
ITU-T/SG17 27th Nov 2002 20
Enterprise Language Concepts – Enterprise Language Concepts – Responsibility conceptsResponsibility concepts
An enterprise specification identifies those actions that involve accountability of a party.
Enterprise Language Concepts – Enterprise Language Concepts – Core conceptsCore concepts
Model Element
Community Enterprise Object Role Action
Type
Template
has
of
*
1..*
hasfor
*
*
Policygoverns governed 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.
22ITU-T/SG17 27th Nov 2002
StatusStatus
• IS 15414 | X.911 currently in course of IS 15414 | X.911 currently in course of publicationpublication
• Concentrates on less contentious aspects:Concentrates on less contentious aspects:– behavioural conceptsbehavioural concepts– organisational concepts (structuring communities)organisational concepts (structuring communities)– policy conceptspolicy concepts– responsibility conceptsresponsibility concepts
23ITU-T/SG17 27th Nov 2002
Work in ProgressWork in Progress
• PDAM in course of developmentPDAM in course of development– Some (minor) refinement of concepts that were contentious Some (minor) refinement of concepts that were contentious
when IS15414 went to presswhen IS15414 went to press– Inclusion of a comprehensive explanatory annexInclusion of a comprehensive explanatory annex– Inclusion of a “metamodel” – non-normative but useful for Inclusion of a “metamodel” – non-normative but useful for
tool builders and for WG19 NWI.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 start2003-07: FPDAM Ballot start– 2003-11: FPDAM Ballot close2003-11: FPDAM Ballot close– 2004-02: FDAM ballot start2004-02: FDAM ballot start– 2004-08: FDAM available for publication2004-08: FDAM available for publication
24ITU-T/SG17 27th Nov 2002
Benefits of using RM-ODPBenefits of using RM-ODP
• Coherent framework for diverse modelsCoherent framework for diverse models• Separation of concerns to match stakeholders Separation of concerns to match stakeholders
interestsinterests• 2-way traceability from Business 2-way traceability from Business
requirements to implementationrequirements to implementation• Better control of development iterationsBetter control of development iterations• Better business control of IT implementations Better business control of IT implementations
and hence more business satisfactionand hence more business satisfaction