RM-ODP Enterprise Language ISO | ITU-T 15414 | X.911 Sandy Tyndale-Biscoe (Convener ISO/JTC1/SC7/WG17) ITU-T/SG17 27 th Nov 2002.

Slides:



Advertisements
Similar presentations
Writing Good Use Cases - Instructor Notes
Advertisements

Requirements Engineering Processes – 2
Overview: Guide for applying RM-ODP with UML Profile for EDOC
ITU-T X.906 | ISO/IEC 19793: UML for ODP system specification -- Current status -- Antonio Vallecillo Universidad de Málaga Dpto. Lenguajes y Ciencias.
Chapter 13: The Systems Perspective of a DSS
Chapter 1: The Database Environment
Chapter 26 Legacy Systems.
Chapter 26 Legacy Systems.
Chapter 7 System Models.
Requirements Engineering Process
Chapter 1 The Study of Body Function Image PowerPoint
Author: Graeme C. Simsion and Graham C. Witt Chapter 8 Organizing the Data Modeling Task.
Chapter 1 Image Slides Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Service Oriented Architecture Reference Model
Global Earth Observation System of Systems
1 Aspects of IEEE P1471 Viewpoints in Unified Modeling Language (UML) Manzur Ashraf, BRAC University Humayra Binte Ali, Dhaka University Md.Mahfuz Ashraf,
Software Process Modeling with UML and SPEM
Armstrong Process Group, Inc. Copyright © , Armstrong Process Group, Inc., and others All rights reserved Armstrong Process.
Business Transaction Management Software for Application Coordination 1 Business Processes and Coordination.
ActionDescription 1Decisions about planning and managing the coast are governed by general legal instruments. 2Sectoral stakeholders meet on an ad hoc.
ITU-T/SG 27 Nov UML for ODP viewpoint specifications Bryan Wood Convenor, JTC1/SC7/WG19 ITU-T/SG 17 Geneva, 27 November.
Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
ITU-T/SG 17 Mar UML for ODP system specifications Bryan Wood Convenor, JTC1/SC7/WG19 ITU-T/SG 17 Geneva, 14 March 2004.
ITU-T/SG 17 Mar ITU-T and ISO/IEC Joint Standards for Open Distributed Processing Bryan Wood Convenor, JTC1/SC7/WG19
Module N° 7 – Introduction to SMS
Jeopardy Q 1 Q 6 Q 11 Q 16 Q 21 Q 2 Q 7 Q 12 Q 17 Q 22 Q 3 Q 8 Q 13
Jeopardy Q 1 Q 6 Q 11 Q 16 Q 21 Q 2 Q 7 Q 12 Q 17 Q 22 Q 3 Q 8 Q 13
Title Subtitle.
DIVIDING INTEGERS 1. IF THE SIGNS ARE THE SAME THE ANSWER IS POSITIVE 2. IF THE SIGNS ARE DIFFERENT THE ANSWER IS NEGATIVE.
Addition Facts
Database Design: ER Modelling (Continued)
|epcc| NeSC Workshop Open Issues in Grid Scheduling Ali Anjomshoaa EPCC, University of Edinburgh Tuesday, 21 October 2003 Overview of a Grid Scheduling.
Communicating over the Network
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design 1.
EuSEC Tool Vendors Challenge Adie Ditchburn Jon Chard 19 Sep 2006.
Week 2 The Object-Oriented Approach to Requirements
Configuration management
Software change management
EMS Checklist (ISO model)
Effectively applying ISO9001:2000 clauses 6 and 7.
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Legacy Systems Older software systems that remain vital to an organisation.
SAS 70 Third Party Report on Controls Overview and Timetable Finance / Audit Committee Meeting Austin, Texas January 14, 2003/ February 18, 2003.
Use Case Diagrams.
1 UML ++ Mohamed T IBRAHIM University of Greenwich -UK.
IONA Technologies Position Paper Constraints and Capabilities for Web Services
Software Requirements
1 UK e-Science All-Hands Meeting Nottingham, 2004 Enterprise specification of the NERC DataGrid Andrew Woolf, Ray Cramer.
Lecture plan Outline of DB design process Entity-relationship model
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Lecture 6: Software Design (Part I)
Lecture 5: Requirements Engineering
آزمایشگاه مهندسی نرم افزار
Chapter 5 Test Review Sections 5-1 through 5-4.
SIMOCODE-DP Software.
Monday, October 27, 2003 X-Change Technologies—Compliance proposal 1 Naming Proposal by X-Change Technologies.
Addition 1’s to 20.
25 seconds left…...
Chapter 2 Entity-Relationship Data Modeling: Tools and Techniques
Week 1.
We will resume in: 25 Minutes.
1Model Driven Architecture – 3. März 2008 – Siegfried Nolte 1.UML – What is it and what is it good for ? 2.MDA – What is it and what is it good for ? 3.MDA.
Representations and Models: SysML and Beyond David Long Vitech Corporation SEDC
International Telecommunication Union ITU-T Study Group 17, Moscow, 30 March – 8 April 2005 New Recommendations on ODP Arve Meisingset Rapporteur Q15.
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
DISCUSSION ABOUT REGISTRATION OF RM-ODP LIBRARY EXAMPLE BASED ON MFI Yuan Lin, Wang Jian, Wang Chong, Liang Peng, Feng Zaiwen.
Developing an IDM Information Delivery Manual Part 1. Industry Workgroup Training, Creating IDMs Alliance NA 2010 Dianne Davis, NA-IDM Coordinator Jan.
Workplan for Updating the As-built Architecture of the 2007 GEOSS Architecture Implementation Pilot Session 7B, 6 June 2007 GEOSS Architecture Implementation.
Geospatial Service Architecture Viewpoints
Presentation transcript:

RM-ODP Enterprise Language ISO | ITU-T | X.911 Sandy Tyndale-Biscoe (Convener ISO/JTC1/SC7/WG17) ITU-T/SG17 27 th Nov 2002

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

ITU-T/SG17 27 th Nov ODP Viewpoints

ITU-T/SG17 27 th Nov 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

ITU-T/SG17 27 th Nov 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!

ITU-T/SG17 27 th Nov 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

ITU-T/SG17 27 th Nov 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

ITU-T/SG17 27 th Nov 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

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

ITU-T/SG17 27 th Nov The Enterprise Language Standard (ISO | ITU-T | 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 | X.911:Purpose of | X.911: –Refine and extend the enterprise language defined in ITU-T Recommendation X.903 |ISO/IEC 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.

ITU-T/SG17 27 th Nov 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.

ITU-T/SG17 27 th Nov 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

ITU-T/SG17 27 th Nov 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 *

ITU-T/SG17 27 th Nov 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.

ITU-T/SG17 27 th Nov 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

ITU-T/SG17 27 th Nov 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 *

ITU-T/SG17 27 th Nov 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

ITU-T/SG17 27 th Nov 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

ITU-T/SG17 27 th Nov 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

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

ITU-T/SG17 27 th Nov 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.

ITU-T/SG17 27 th Nov Status IS | X.911 currently in course of publicationIS | 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

ITU-T/SG17 27 th Nov 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 – : FPDAM Ballot start – : FPDAM Ballot close – : FDAM ballot start – : FDAM available for publication

ITU-T/SG17 27 th Nov 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