1 International Enterprise Architecture Standards, Organizations & Activities 17 January 2007 L. Mark Walker.

Slides:



Advertisements
Similar presentations
A Comparative Survey of Enterprise Architecture Frameworks
Advertisements

Configuration management
1 INCOSE Chesapeake Chapter Enterprise SE Panel Discussion L. Mark Walker/LMC 21 March 2007.
Advanced Manufacturing Laboratory Department of Industrial Engineering Sharif University of Technology Session # 11.
Applying the Human Views for MODAF to the conception of energy-saving work solutions Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf.
Human Views for MODAF Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf of the Human Factors Integration Defence Technology Centre.
Chapter 3 Process Models
Ch 3 System Development Environment
Enhancing Data Quality of Distributive Trade Statistics Workshop for African countries on the Implementation of International Recommendations for Distributive.
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.
Overview of OASIS SOA Reference Architecture Foundation (SOA-RAF)
Harmonisation of Standards for Enterprise Integration – an urgent need
Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.
Reference Architecture for Enterprise Integration CIMOSA GRAI/GIM PERA Dima Nazzal.
Environmental Terminology System and Services (ETSS) June 2007.
Software Engineering General Project Management Software Requirements
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Lecture Nine Database Planning, Design, and Administration
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Course Instructor: Aisha Azeem
Extended Enterprise Architecture Framework (E2AF)
Chapter 1 The Systems Development Environment
Enterprise Architecture
TDT4252 Modelling of Information Systems Advanced Course
What is Business Analysis Planning & Monitoring?
Effective Methods for Software and Systems Integration
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Reuse Standards Dr. Carma McClure Extended Intelligence, Inc. Copyright (c) 1998 by Extended Intelligence, Inc.
Chapter 2 The process Process, Methods, and Tools
TDT4252/DT8802 Exam 2013 Guidelines to answers
Geoff Payne ARROW Project Manager 1 April Genesis Monash University information management perspective Desire to integrate initiatives such as electronic.
Work breakdown structure
EDISON INTERNATIONAL® SM SCE Project Story CIM User Group 10/12/2010 Jim Horstman Southern California Edison.
Architecture Business Cycle
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Page 1 ISO/IEC JTC 1/SC 7/WG 7 N Summary of the Alignment of System and Software Life Cycle Process Standards The material in this briefing.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e UPDM Review Session Col. Jack Jibilian Enterprise Architecting & Warfighting Decision Support SAF/XCPA.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Lecture Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Illustrations and Answers for TDT4252 exam, June
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
EI2N2008 © O. Noran, P. Bernus 2008 Service Oriented Architecture vs. Enterprise Architecture: Competition or Synergy? Ovidiu Noran, Peter Bernus EI2N.
1 ISO TC184/SC4 Industrial Data ISO JTC1/SC32 Meeting Berlin, Germany Gerald Radack Concurrent Technologies Corp.
Common Information Model - enabling data exchanges and interoperability in the electric utility industry P&E Magazine, May 2015 Power & Energy Magazine.
Joint Meeting Report on Standards 8 July Recent Accomplishments Systems Modeling Language (SysML) specification accepted for adoption by OMG AP233.
Systems Analysis and Design in a Changing World, Fourth Edition
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Achieving Semantic Interoperability at the World Bank Designing the Information Architecture and Programmatically Processing Information Denise Bedford.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
International Workshop 28 Jan – 2 Feb 2011 Phoenix, AZ, USA Modeling Standards Activity Team Model-based Systems Engineering (MBSE) Initiative Roger Burkhart.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Integrating MBSE into a Multi-Disciplinary Engineering Environment A Software Engineering Perspective Mark Hoffman 20 June 2011 Copyright © 2011 by Lockheed.
ISO/IEC JTC 1/SC 7 Working Group 42 - Architecture Johan Bendz
Object-Oriented Software Engineering Using UML, Patterns, and Java,
The Systems Engineering Context
The Open Group Architecture Framework (TOGAF)
Quality management standards
Systems Engineering Tool for Intelligent Transportation
Software Engineering I
System architecture, Def.
Presentation transcript:

1 International Enterprise Architecture Standards, Organizations & Activities 17 January 2007 L. Mark Walker

LMWalker2 Agenda Background Background The Multitude of Architecture Standards Activities The Multitude of Architecture Standards Activities 1- ISO: –TC184/SC5/WG1 (Four Enterprise Architecture Standards) –JTC1/SC7/WG42 (based on IEEE 1471, ISO 15288, 12207, etc.) 2- Governments: –US: DODAF, FEAF, CADM, etc. –Europe: MODAF, etc. 3- Others: OMG (SysML, UML, ArchSC), TOGAF, etc. Status and Challenges for INCOSE, ISO, etc. Status and Challenges for INCOSE, ISO, etc. –INCOSE Chesapeake Chapter Involvement?

LMWalker3 Overall Multitude Intl Architect Standards, etc (2D) Model Language (3D) ETC (SW) (SE) (IEEE 1471, etc.) 10303: AP233, etc. OMG: SysML, UML, ETC IEEE, TOGAF, ETC Europe: MODAF, ETC US/DoD: FEAF, DODAF, CADM, ETC ISO Liaisons ? Vocabulary & Definitions ISO The Others ETC ISO Liaisons Others: Japan, China, etc. ? INCOSE Liaisons ? Bottom Line: People are in Multiple Intl Efforts ISO TC184/SC5 ISO JTC1/SC7

LMWalker4 ISOs Key Architecture Working Groups 1. ISO/TC184/SC5/WG1 is the lead for development of Four ISO Enterprise Architecture Standards based on manufacturing industry needs –TC184/SC5/WG1 initiated the upgrade planning for their ISO this summer 2. ISO/JTC1/SC7/WG42 is developing an architecture standard by fast tracking IEEE 1471 –JTC1/SC7/WG42 formed in June ISO/JWG8 is developing the Data Standards including 10303, 100s of standards including AP ISO SC5/SG1 & SC7: identifying vocabulary overlaps/conflicts and recommending commonality/Harmonization

LMWalker5 1- ISO Enterprise Architecture Standards- TC184 Chair:Emanuel dela Hostria (USA) Contact:ISO/TC 184/SC 5 Secretariat: ISO/TC 184 Industrial Automation Systems & Integration SC 4 Industrial Data Advisory Group SC 2 Robots for Manufacturing Environments SC 1 Physical Device Control PT1 Revision of ISO QC - Quality Committee WG2 Part Library WG3 Product Modeling JWG8** Industrial manufacturing management data JWG9 Electrical & electronic applications WG11 Express language, implementation methods WG12 Common resources PPC Policy & planning committee WG8 Distributed installation in industrial applications WG4 NC Programming Languages WG7 Data modeling for integration of physical devices WG1-Richard Martin Lead Modeling & Architecture MT1 Communications & Interconnections WG4 Manufacturing Software & Environment WG5 Application Integration Frameworks WG6 Application Service Interface JWG15 Enterprise-Control System Integration WG7 Diagnostics/Maintenance/Cont rol Integration SG1 Vocabulary and terminology JWG8** Industrial manufacturing management data SC 5 Architecture, Communications & Integration Frameworks Note: Other WGs may also be of interest. Key Current Architecture WGs of Interest

LMWalker6 The 4 ISO/TC184/SC5/WG1 EA Standards StanrdTitle Key Focus Status Industrial automation systems Requirements for enterprise-reference architectures and methodologies Enterprise-reference architectures; provides means of organizing engineering projects. Includes requirements. Based on GERAM WG1 initiated systematic review summer 06, leading to a revision project that commenced late Enterprise integration Framework for enterprise modelling Ent Arch Models & Modeling Phases (planning), views & genericity. Published May FDIS Enterprise integration Constructs for enterprise modelling Computer modeling language and key elements. Completed and in for balloting. May be final by early Industrial automation systems Concepts and rules for enterprise models Provides enterprise level architecture modeling basis. Business, operational and metamodel will replace when new version is approved

7 ISO Industrial automation systems Requirements for enterprise- reference architectures and methodologies

LMWalker Scope Covers topics deemed necessary to carry out all types of enterprise projects required for the life of the enterprise, including: Covers topics deemed necessary to carry out all types of enterprise projects required for the life of the enterprise, including: –Enterprise creation, –Major enterprise restructuring efforts –Incremental changes, –Parts of the enterprise-life cycle.

LMWalker9 ISO Basis: GERAM (Generalized Ent. Reference Arch Methodology) Generalized Enterprise Reference Architecture identifies concepts of enterprise integration Enterprise MOdels provide implementable modules of human professions, operational processes, technologies Enterprise Engineering Tools support enterprise engineering Enterprise Operational Systems support the operation of the particular enterprise Partial Enterprise Models provide reusable reference models and designs of human roles, processes and technologies Generic Enterprise Modeling Concepts (Theories and Definitions) define the meaning of enterprise modeling constructs Enterprise Models enterprise designs, and models to support analysis and operation Enterprise Modeling Languages provide modeling constructs for modeling of human role, processes and technologies employs utilize Implemented in support used to build used to implement Enterprise Engineering Methodology describe process of enterprise engineering (Adapted from ISO 15704) Richard Martin

LMWalker Key integration principles Applicability to any enterprise Applicability to any enterprise –total customer service solution involves information, culture & mission Enterprise identification and mission definition Enterprise identification and mission definition –must produce products or services desired by customers Separation of mission-fulfillment functions from mission- control functions Separation of mission-fulfillment functions from mission- control functions –fulfilling the mission, i.e. operating processes that produce product or service –achieve the desired economic or other gains that assure viability or continued successful existence of enterprise. Two distinct transformation classes Two distinct transformation classes –1-Information, 2-material & energy

LMWalker Key enterprise integration principles (cont) Identification of process contents, three classes of implemented tasks or business processes: Identification of process contents, three classes of implemented tasks or business processes: –information and control activities –mission activities –human activities, Recognition of enterprise life-cycle phases Recognition of enterprise life-cycle phases Evolutionary approach to enterprise integration Evolutionary approach to enterprise integration –projects can be carried out individually or collectively Modularity Modularity –activities & interfaces defined in modular fashion

12 ISO/FDIS Enterprise integration Framework for enterprise modelling

LMWalker13 ISO/FDIS Dimensions requirements definition concept definition implementation description design specification domain operation decommission definition domain identification genericity enterprise modelling view enterprise model phase organization view resource view information view function view partial level particular level generic level Reference Catalog Particular level not defined at the domain operation phase Systems Integration: Framework for Enterprise Modelling Richard Martin

LMWalker14 GERA Framework (Basis for 19439) { Hardware Software Instantiation Management Customer service Human Machine Life-cycle phases Views } } } Generic Partial Particular { } Design Preliminary design Detailed design Identification Concept Implementation Operation Decommission Requirements Resource Organisation Information Function } Reference Architecture Particular Architecture according Subdivision to genericity according to Subdivision purpose of activity according to physical manifestation Subdivision according to Subdivision model content to means of Subdivision according implementation and control { Source: ISO 15704:2000 Annex A and Figure 10, The GERA modelling Framework of GERAM [GERAM V ](used with permission) Focus of ISO Richard Martin

LMWalker15 Recursion with Do C R D I O Dc Enterprise A (operational) (new) Enterprise B (new) Enterprise C reference catalog R Do C R D I O Dc Do C R D I O Dc Enterprise operations can model new enterprises either from its own particular models or using reference constructs and partial models. Do C R D I Dc Do C R D I Dc Do A Do B Do R Do A Do C Richard Martin

LMWalker16 ISO (2006/07) Focus on: Modeling Language for Modelers (those who develop architecture & modeling tools, e.g. tool vendors) Focus on: Modeling Language for Modelers (those who develop architecture & modeling tools, e.g. tool vendors) Use of UML being attempted Use of UML being attempted –Evaluating SysML as alternative due to UML Limitations Significant detail on modeling language constructs Significant detail on modeling language constructs

LMWalker Figure B.4 Functional aspects

LMWalker18 ISO Published 1998 Focus is on: Concepts & Rules Focus is on: Concepts & Rules Based on System Theory Based on System Theory Introduces 2D perspective Introduces 2D perspective –Plan/Build, Use and Operate, Dispose –What, How and Do Activities Addresses: Addresses: –Hierarchy, Structure, Behavior, Real World, Reqts for model interoperability will be incorporated into upgraded version will be incorporated into upgraded version

LMWalker19 ISO and IEEE 1471 Meta Models TBD

LMWalker20 Overall Multitude Intl Architect Standards, etc (2D) Model Language (3D) ETC (SW) (SE) (IEEE 1471, etc.) 10303: AP233, etc. OMG: SysML, UML, ETC IEEE, TOGAF, ETC Europe: MODAF, ETC US/DoD: FEAF, DODAF, CADM, ETC ISO Liaisons ? Vocabulary & Definitions ISO The Others ETC ISO Liaisons ISO TC184/SC5 ISO JTC1/SC7 Others: Japan, China, etc. ? INCOSE Liaisons ? Bottom Line: People are in Multiple Intl Efforts

LMWalker21 2- JTC1/SC7/WG42 WG42 established June 06- identifying members WG42 established June 06- identifying members ISO/IEC 25961: Fast Tracking IEEE ISO/IEC 25961: Fast Tracking IEEE Includes systematic review of TC184/SC5/WG1s 15704:2000 (Liaison Activity) Includes systematic review of TC184/SC5/WG1s 15704:2000 (Liaison Activity) Harmonize with ISO & (ISO Systems and Software Engineering Standards) Harmonize with ISO & (ISO Systems and Software Engineering Standards) –FYI; now in revision also Includes Vocabulary Reconciliation Includes Vocabulary Reconciliation –Includes architecture views and viewpoints among other SE terms and ISO/IEC Includes 1 yr Milestone: Includes 1 yr Milestone: –Possible Reassignment & Re-staffing INCOSE STC also supporting this effort INCOSE STC also supporting this effort

LMWalker22 3- ISO/JWG8: Data Standards (ISO 10303, Includes 100+ standards Industrial Manufacturing Management Data Industrial Manufacturing Management Data Extensive set of standards, over 100 Extensive set of standards, over 100 –AP233 one of the more well known standards under this umbrella INCOSE also involved in this effort INCOSE also involved in this effort

LMWalker23 4- ISO SC5/SG1 Identifying vocabulary overlaps/conflicts and recommending commonality in SC5 Standards Identifying vocabulary overlaps/conflicts and recommending commonality in SC5 Standards –Currently reviewing over 500 terms/words and definitions, many overlaps and inconsistencies –Similar effort to SC7 –Similar challenges with use of terms/words and definitions These efforts need to be further coordinated across themselves (an ISO Liaison task). These efforts need to be further coordinated across themselves (an ISO Liaison task). Then what about the other international architecture and SE activities? Then what about the other international architecture and SE activities?

LMWalker24 Current ISO SC5/WG1 & INCOSE Activities ISO TC184/SC5/WG1 ISO TC184/SC5/WG1 –Developing Plan for revision –Evaluating 15704/GERAM & IEEE1471 –Involved with INCOSE, OMG (SysML & UML), etc. –Considering DODAF 2.0 Efforts/Evolution –Reviewing 15704/GERAM Comments & Recommendations from Manufacturing Industry –Terminology Issues INCOSE INCOSE –Standards Tech Committee: Committed to Supporting SC5/WG1, SC7/WG7, etc. Among Higher STC Priorities Among Higher STC Priorities –INCOSE TC184/SC5 Liaison (Mark Walker Lead) –INCOSE Connect Webpage Established –INCOSE INSIGHT Articles (Jan & April 07) –ISO EA Standards Tutorial- Symposium 07

LMWalker25 Overall Assessment Many Semi-Independent International Architecture Standards & Activities Many Semi-Independent International Architecture Standards & Activities –Harmonization is Critical, Too Many Conflicting Terms, Many Perspectives, Varied Applications Other Issues: Other Issues: –US/DoD Architecture Perspectives (DODAF, CADM, FEAF) – DODAF 2.0 Coming in 07 –INCOSE Architecture related WGs biased towards DoD/US Govt perspectives/needs ISO TC184/SC5 EA Standards biased to Intl & Manufacturing Industry Architecture Perspectives ISO TC184/SC5 EA Standards biased to Intl & Manufacturing Industry Architecture Perspectives Harmonizing these diverse International EA viewpoints together is a major challenge Harmonizing these diverse International EA viewpoints together is a major challenge Being involved provides Opportunity to Learn future direction of Architecture & Influence Resulting Standards, Applications, etc.

LMWalker26 Challenge to Chesapeake Chapter Should we start an Interest Group? Should we start an Interest Group? –Understand the ISO EA Standards, –Application to our companies and customers –Involvement with INCOSE Liaison Efforts –Learn Potential Architecture Principles, Methods, Terminology, Perspectives, Applications, etc. Who is Interested? Who is Interested?

27 Backups

LMWalker Contents: Requirements Applicability and coverage of enterprise-entity types – –Generality – –Enterprise design – –Enterprise operation Concepts – –Human oriented – –Process oriented – –Technology oriented – –Mission-fulfillment oriented – –Mission-control oriented – –Framework for enterprise modeling – –Life cycle, Life history – –Modelling views – –Genericity

LMWalker Contents: Requirements & Annexes Components of enterprise-reference architectures – –Engineering methodologies – –Modelling languages – –Generic Elements – –Partial models – –Particular models – –Tools – –Modules – –Enterprise-operational systems Annexes: – –Representation – –Glossary – –Completeness and compliance

LMWalker Benefits The enterprise-reference architecture and methodology requirements The enterprise-reference architecture and methodology requirements –checklist for completeness with respect to current and future purpose. Relevant to any group charged with improving an enterprise infrastructure or its processes. Relevant to any group charged with improving an enterprise infrastructure or its processes. –Select or create a reference architecture of its own –Terminology that pertains specifically to the company, industry, and culture involved.

LMWalker – Aim & Benefits for enterprise- reference architectures & methodologies An enterprise-reference architecture with associated methodologies & enterprise-engineering An enterprise-reference architecture with associated methodologies & enterprise-engineering Technologies that fulfill requirements enable integration & planning Technologies that fulfill requirements enable integration & planning Teaming to determine and develop course of action that is complete, accurate, properly oriented to future Teaming to determine and develop course of action that is complete, accurate, properly oriented to future Business developments to: Business developments to: –describe tasks required; –define necessary quantity of information; –specify relationships among humans, processes, and equipment in integration considered; –address management concerns; –address relevant economic, cultural, and technological; –computer-support required; –support process modelling for enterprise history

LMWalker32 INCOSE Activities INCOSE Standards Tech Committee INCOSE Standards Tech Committee –Standards TC working with other WGs –Developing Overall INCOSE Approach and Plan –Coordinate INCOSE WG involvement, tasks, etc. –Liaison for ISO Standards efforts –Developing Standards Architecture Tutorial(s) for 07 Symposium and Jan 07 Intl Workshop Other INCOSE WGs Other INCOSE WGs –Mark Sampson- Consolidating Arch Info. –Identify ISO WG(s)/standard(s) of interest –Identify WG Lead and others who will support –Contact STC with WGs intentions, focus and objectives for involvement Special EA Jan 07 IW Special EA Jan 07 IW

LMWalker33 INCOSE Involvement 1. Level of INCOSE Involvement At INCOSE Symposium, July 06At INCOSE Symposium, July 06 Strong Additional WG, etc. interest established Strong Additional WG, etc. interest established Mark Sampson to capture scope of architecture activities Mark Sampson to capture scope of architecture activities Established ISO TC 184/SC5 website, etc. Established ISO TC 184/SC5 website, etc. Initiated INCOSE awareness and recommended INCOSE Steering Committee Initiated INCOSE awareness and recommended INCOSE Steering Committee INCOSE Liaison for ISO SC7/WG42 (IEEE 1471) Fast Track effortINCOSE Liaison for ISO SC7/WG42 (IEEE 1471) Fast Track effort 2. Involvement of other INCOSE WGs: Strong interest –Architecture, Model Driven System Design –Tools Database, Tools Integration and Interoperability –Information Systems –Requirements & OOSEM & SysML