Semantic Enterprise Architecture
15 likes•8,664 views
The document discusses semantic enterprise architecture and defines it as the terminology and composition of enterprise components, their relationships with the external environment, and the guiding principles for analyzing, designing, and evolving an enterprise. It notes that enterprise architecture is primarily about people communicating with each other to build systems and services that can also communicate with each other. The document provides examples of different techniques that can be used for enterprise architecture like UML, BPMN, IDEF, and many others.
Semantic Enterprise Architecture
- 1. Semantic Enterprise Architecture Michael zur Muehlen, Ph.D. Stevens Institute of Technology Howe School of Technology Management Center for Business Process Innovation Hoboken, New Jersey [email protected] 1
- 2. “Vision without execution is hallucination” Thomas Alva Edison 2
- 3. A Story in 3 Parts 3
- 4. “If it doesn’t make three people angry, it is not a process” Beyond Reengineering (Michael Hammer, 1996) 4
- 5. Business as a System Enterprise Management System Management Planning and Mgt. Information Information Control System System Custo- Directive Suppliers Reporting mers Operational System Operational Information System Goods and Services Money 5
- 6. “All models are wrong, some are useful”George P.E. Box 6
- 7. Why Model? predict guide explain constrain past present future 7
- 8. What are Good Models? Correct Relevant Economical Model Quality Systematically Clear Comparable Designed 8 Source: Becker, Rosemann, von Uthmann
- 10. Understanding Process Modeling BPMN is a standard notation for business processes, but it is complex (50+ symbols) Questions: How expressive is BPMN in theory? Which parts of BPMN are used in practice? Which parts of BPMN should be used in practice?
- 11. Which BPMN Modeling subset do people Practice use? Δ = untapped potential Δ = skill deficit OR unnecessary features How should you What can BPMN use BPMN? express? BPMN BPMN Best Features Practice Δ = standard design flaws 11
- 12. Normal Flow Task End Event Start Event / Event Pool Data-Based XOR Start Message Text Annotation Message Flow Parallel Fork/Join Lanes Gateway Sub-Process (Collapsed) Association Data Object Intermediate Timer Intermediate Message End Terminate Sub-Process (Expanded) End Link Default Flow Inclusive Decision/Merge Activity Looping Exception Task Start Link End Message End Exception Complex Decision/Merge Event-Based XOR Multiple Instance Group Transaction Intermediate Event End Cancel Compensation Intermediate Compensation Conditional Flow Exception Flow Intermediate Link Start Timer Off-page connector Start Rule Intermediate Rule Intermediate Multiple End Compensation Start Multiple Intermediate Exception source: zur Muehlen, Recker (2007) Intermediate Cancel End Multiple Compensation Association 12
- 13. How to Improve a Standard Engage Issue BPMN Analyze Define BPMN BPMN 2.0 w/ BPMN Use Subset Standards Conformance Body Classes 2007 2008 2009 2010 Add BPMN Develop Issue Policy Develop 2.0 to BPMN 2.0 Memo Skilled Enterprise training mandating Workforce Standards program BPMN 2.0 Use Registry While keeping the vendor community continually informed... 13
- 14. enterprise architecture |ˈentəәrˌprīz ˈärkiˌtekCHəәr| Terminology and composition of enterprise components, their relationships with the external environment, and the guiding principles for the analysis, design, and evolution of an enterprise. Source: Wikipedia 14
- 15. Why Enterprise Architecture? To Understand Analyze what already exist Assess what will be Main purpose: People Integration/Conversation To Build Design what will be within today’s constraints Set objectives and constraints for detailed speci cations Main purpose: Instruction/Guideline To Verify Provide a framework for others Evaluate current practice against existing guidelines Main purpose: Compliance/Control 15
- 16. Enterprise Architecture is primarily about People talking to each other... 16
- 17. ...so we can build Systems and Services that talk to each other 17
- 18. Business as a System Enterprise Management System Management Planning and Mgt. Information Information Control System System Custo- Directive Suppliers Reporting mers Operational System Operational Information System Goods and Services Money 18
- 19. 19
- 20. 20
- 21. Business as a System Enterprise Management System 2 Management Planning and Problem: Mgt. Information Information Control SystemInformation Overload System 3 1 Custo- Directive Suppliers Problem: Problem: Reporting mers Decision Quality Information Quality Operational System Operational Information System Goods and Services Money 21
- 22. 22 others... UML, IDEF, BPMN, RAD, EPC, PowerPoint and many, many Many Techniques Multiple Views <<TupleType>> <<type>> C apability::CapabilityP erformerManifestation C apability::Capability place1Type place1Type <<pow ertype>> A ctivities::Condition <<TupleType>> place1Type Goals::E ffectP artOfCapabi lity place1Type <<Tupl eType>> A ctivities::A ctivityR esultsInE ffect place2Type place2Type pl ace2Type <<TupleType>> <<TupleType>> <<TupleType>> <<Indi vidual Type>> A ctivities::A ctivityC ondi tionOverlap A ctivities::A ctivityP artOC apability <<TupleType>> <<pow ertype>> place3Type place2Type place1Type Goal s::V isi onsR ealizedB yD esiredE ff Goals::V ision Goals::D esiredE ffectD irectsA ctivity Goals::D esi redE ffect ect place2Type pl ace1Type place2Type 0..1 place1Type <<pow ertype>> A ctivities::A cti vity place3Type place1Type place2Type place1Type place1Type <<IndividualType>> Goals::Goal <<TupleType>> A ctiviti es::A cti vityP erformerOverl ap place1Type <<pow erType>> <<pow erType>> <<TupleType>> A ctiviti es::S erviceFunction A ctiviti es::E vent A ctivi ties::A ctivi tyC hangesE ffectObject 1..* <<pow ertype>> P roject::P lan <<TupleType>> <<Tupl eType>> <<TupleType>> <<TupleType>> A ctivities::P erformerS upportingA ctivity A ctivities::A ctivityP erformedB yP erformer A ctivities::A ctivityW holeC onsumingP artOfA ctivity A ctivities::A ctivityW holeP roduci ngP artOfA ctivi ty <<Indi vidual Type>> <<TupleType>> P roject::P roject P roject::GoalsR ealizedB yP roj ect pl ace1Type pl ace2Type place2Type place2Type <<TupleType>> <<pow ertype>> <<pow ertype>> R ules::R uleGuidanceOfA ctivityV al idUnitorC ondition A ctivities::ConsumingP artOfA ctivi ty A ctivities::P roducingP artOfA ctivity <<individualType>> R ules::Guidance pl ace2Type <<TupleType>> R ules::R uleConstrainsA ctivi ty pl ace1Type <<individualType>> place1Type <<i ndivi dualType>> pl ace3Type <<TupleType>> place2Type 0..* R ules::S ecurityA ttributes <<pow ertype>> R ules::R ule A ctivities::A ctivityR esourceOverlap pl ace2Type Group Measures::Measure Type 1 0..* <<IndividualType>> <<TupleType>> Measures::Measure A ctivi ties::P erformerRuleC onstrainsA ctivityOverlap place4Type <<individual Type>> <<individualType>> <<individualType>> <<type>> <<type>> <<type>> <<type>> <<type>> <<type>> <<type>> R ules::S tandard R ules::A greement R ules::C onstraint Measures::P hysi cal Me Measures::E ffectsMea Measures::P erformanc Measures::NeedsS atisfacti on Measures::Maintainability Measures::A daptability Measures::Organizational asure sure eMeasure Measure Measure Measure Measure <<individualType>> <<pow erType>> <<pow erType>> R ules::Functi onalS tandard R ules::TechnicalS tandard R ul es::S erviceP oli cy <<type>> <<type>> <<type>> <<type>> <<type>> <<type>> Measures::S patialMea Measures::A ccuracyP r Measures::RateThroug Measures::Capacity Measures::Interoperabi Measures::Cost sure eci si on hput lity <<type>> <<type>> <<type>> Measures::Timeliness Measures::Dependabil i Measures::S ervi ceLev ty el <<type>> R esourceFl ow s::E ffectObject place2Type <<type>> <<type>> <<type>> place1Type Measures::Trustw orthi Measures::Rel iability Measures::S ecurity ness place2Type <<type>> R esourceFl ow s::R esource pl ace2Type 0..* place2Type <<type>> Locations::IntentionallyC onstructedInd ividual <<IndividualType>> <<type>> <<pow ertype>> <<type>> R esourceFl ow s::Individual R esou R esourceFlow s::P erformer R esourceFlow s::R esourceType R esourceFlow s::Means rce place1Type <<IndividualType>> place1Type place2Type Locations::Location <<TupleType>> <<Tupl eType>> place2Type R esourceFlow s::P erformerLocationOverlap S ervi ces::P ortP artOfP erformer <<type>> InformationA ndD ata::Thing place1Type <<IndividualType>> <<Indivi dualType>> <<IndividualType>> <<IndividualType>> <<Indi vidual Type>> tupl eP lace1 <<IndividualType>> <<IndividualType>> <<type>> <<pow ertype>> Locations::GeoFeature Locations::S oli dV olum Locations::S urface Locati ons::Line Locations::P oint <<pow ertype>> <<pow ertype>> <<pow ertype>> associateOne R esourceFlow s::IndividualP erfo S ervi ces::P ort place2Type <<TupleType>> <<TupleType>> e Locations::GeoP oliti calE xtent place2Type R esourceFlow s::P erformerType R esourceFlow s::Materi el R esourceFlow s::Information R esourceFlow s::D ata pointOnLine rmer InformationA ndD ata::D ataA ss InformationA ndD ata::tuple place1Type associateTwo ociation 2 place2Type place1Type place2Type place3Type relationship tupl eP lace2 w holeInformation dataP art place2Type <<TupleType>> R esourceFlow s::D ataP artOfInformation <<TupleType>> <<TupleType>> <<TupleType>> pl ace1Type <<IndividualType>> <<Indivi dualType>> <<Indi vidual Type>> <<IndividualType>> <<IndividualType>> InformationA ndD ata::D escribedB y S ervices::S erviceE nablesA ccessTo R esourceFlow s::MaterielP artOfS ystem description Locations::P l anerS urface Locati ons::RealP ropert Locations::Instal lati on Locations::Country R esourceFlow s::Organizatio thingD escribed y n place1Type pl ace2Type place1Type pl ace1Type <<Tupl eType>> InformationA ndD ata::namedB y <<type>> <<pow ertype>> <<pow ertype>> <<pow ertype>> <<pow ertype>> <<pow ertype>> <<pow ertype>> <<pow ertype>> <<NameType>> place1Type <<Indivi dualType>> <<Indi vidual Type>> <<TupleType>> S ervices::S ervi ceP ort R esourceFlow s::S ervice R esourceFl ow s::Organ R esourceFlow s::S ystem R esourceFlow s::P ersonnelTyp R esourceFlow s::S erviceD escription R esourceFlow s::D omainInformation R esourceFlow s::A rchitectureOverview A ndP urpose R esourceFlow s::N ame <<IndividualType>> Locations::Facility Locations::S i te Locati ons::S iteP artOfIn Locations::RegionOfCo izationType e nameType stallation untry thingB ei ngDescribed pl ace2Type place2Type <<TupleType>> R esourceFlow s::nameTypeInstance nameInstance place1Type pl ace2Type nameType place2Type place1Type <<NameType>> R esourceFl ow s::A ddress place1Type <<Tupl eType>> <<TupleType>> Locations::Facil ityP artOfS ite <<pow ertype>> R esourceFlow s::P ersonnelTypeP artOfS ystem R esourceFlow s::N ameType place1Type <<TupleType>> S ervices::InterfaceType place1Type <<Tupl eType>> R esourceFlow s::S ki llP artOfP ersonnelType <<pow erType>> S ervi ces::S erviceC hannel place2Type <<pow ertype>> TrainingS killE ducation::S kill pl ace1Type Different Framworks Enterprise Architecture Issues
- 23. Dependencies (DoDAF 2.0 Spec) NOTE 1: Developed iteratively as the Architecture Description is developed. NOTE 2: The AV-2 presents all the metadata used in an architecture. An AV-2 shows elements from the DoDAF Meta-model that have been described in the Architectural Description and new elements (i.e., not in the DM2) that have been introduced by the Architectural Description. parallel relationship SvcV- 10c completion order SV- Viewpoint may/may not be 10c required SvcV- NOT a JCIDS Requirement 10b DIV- SV- 3 10b SvcV- 6 SV- 6 SvcV- CV- 9 x SvcV- 4 DIV- 1 SV- 9 PV- OV- 1 4 StdV- DIV- 2 2 OV- 6c SV- SvcV- 4 8 OV- 3 SV- 8 AV- 2 OV- SvcV- 2 2 NOTE 2 SV- SV- StdV- 5a 2 1 OV- OV- OV- 5b 5a 1 SvcV- 1 CV- AV- OV- 6 SV- 1 6a SV- 3 5b SV- NOTE 1 OV- 1 6b 23
- 24. Example: Capability Meta Model 24
- 25. Core Description realized performed through Activity/ by Resource Capability Process/ (Person/ Function System) input/output Resource (Data) 25
- 26. Relationships De ne De ne De ne De ne Capabilities Activities Resources Performers realized Activity Capability through Performs Performer (Process) Decomposed Sub-Activity In/Out Resource (Activity) 26
- 27. Vocabulary-driven Architecture Which What is the Which data/ processes/ Who/What architecture resources will activities will will be supposed to be consumed provide the involved? achieve? or produced? capabilities? C A R P De ne Capabilities De ne Activities De ne Resources De ne Performers Items: Items: • Objectives Items: Items: • Roles • Features • Verbs •Nouns • Systems • Services • Actors
- 28. CARP Baseline 28
- 29. Milestones (Process) 29
- 30. Use Case (Capabilities) From CARP 30
- 31. Class Diagram (Data) From CARP 31
- 32. Modeling & Simulation Simulate Model Shared Concepts Implement 32
- 33. semantics |səәˈmantiks| the meaning of a word, phrase, sentence, or text: such quibbling over semantics may seem petty stuff. Source: Merriam-Webster 33
- 34. Enterprise Architecture Architecture described by Model Model Model Model 34
- 35. Separate Content and Representation Defined by Architecture Modeling Language described by Model captures Structure Model Model Model Model Domain captures Content Organized by Domain Ontology 35
- 36. Storing Content and Representation Defined by Architecture Modeling Language described by Model captures Model Data Structure saved as Model Model Model Model Domain captures Vocabulary Content saved as Organized by Domain Ontology 36
- 37. Example This part describes the layout of the process (tool-speci c rendering the This part describes information)the process content of (the business logic)
- 38. Focus Consistent Rendering from Requirements Capture to Implementation Architecture Target Audience: Engineer/Implementer described by Model captures Model Data Structure saved as Model Model Model Model Domain captures Vocabulary Content saved as Target Audience: Domain Expert Fit-for-Purpose Rendering based on Stakeholder Needs 38
- 39. Organizing Domain Content Defined by Architecture Modeling Language described by Model captures Structure Model Model Constraints Model Model contains Domain apply to captures Content Terms & Organized by contains Concepts Domain Ontology 39
- 40. Semantic Example Source: Moran (2011) 40
- 41. Design Process BPMN Semantics Time Semantics (e.g., (e.g., objects + activity labels) connectors) Payload Semantics (e.g., data objects + messages) Metadata (e.g. author, Layout (placement version, validity) of objects) Payload Instance Processing Behavior Semantics (e.g., (e.g., audit trail) Run case data + Time messages) 2
- 42. 42
- 43. SO WHAT? 43
- 44. So what? Semantic approach leverages ontologies to describe domains and content Need upper ontology to provide primitives For elementary concepts (capability, activity, resource, performer, event, ...) For elementary properties (metric, objective, condition, ...) Need domain ontologies to provide context Domain-speci c context (key data elements, processes, actors, ...) Domain ontologies map to concepts in the upper ontology Need system ontologies to provide architecture details System-speci c content Map to domain ontology or directly to upper ontology Integration via mapping of shared concepts, not rede nition 44
- 45. Semantics.... 45
- 46. Thank You - Questions? Ph.D. ovation hlen, el zu r Mue Process Inn gement Micha r Business ology Mana fo n Center hool of Tech hnology Sc ec Howe Institute of T dson s u Steven int on the H Po Castle , NJ 07030 -8293 Ho boken 1 (201) 216 385 Phone : + 216-5 ns.edu +1 (201) @steve /bpm Fax: uehlen du : mzurm w.stevens.e urmuehlen E-mail ww http:// eshare.net/ mz Web: www.s lid slides: 46