1. 3106 Use of UML 2.0 Diagrams for Systems Architecture Modeling Gundars Osvalds Systems of Systems Architect The Boeing Company

2. 2 Contents Architecture Definition Architecture Frameworks Zachman Framework Architecture Model Definitions UML 2 for System Engineering Features Enterprise Architecture Process and Models Example Architecture Demonstrating the use of UML 2 Diagrams

3. 3 What Is an Architecture? Architecture –“The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.” IEEE 1471 Architect –Models the Stakeholders vision Stakeholder –The customer of the Architecture

4. 4 Purpose of an Enterprise Architecture A building plan for a system or set of systems Set of high-level design decisions made by senior architects –Addresses important system-wide issues –Documents decisions that affect the subsequent elaboration of a system –Provides a guideline to the system designer and developer Some decisions may not be popular with the developers but are made for the good of the Enterprise

5. 5 Architecture Design Process The purpose is to synthesize a solution that satisfies system requirements –Partition the system functions identified in the system requirements –Investigate COTS solutions –Evaluate existing solutions, model and perform comparisons –The design solution is established and documented using models ISO 15288

6. 6 Sponsor –Defines the capabilities Customer –User of System System Engineer –Model the enterprise and system specifications Enterprise Architect –Perform architectural design of the system Designer/Developer –Design and develop the software and hardware to implement the system Enterprise Architecture Define Needs Enterprise Architect Designer Developer Sponsor System Engineer Uses Specs Model Needs Design System Arch Customer Stakeholders Enterprise Architectural Stakeholders Activities in developing a project architectural design INCOSE 2004

7. 7 What Is an Architecture Framework? –A guidance to the architect defining views and models that represent the thing (object) that is to be modeled How does this relate to an information system implementation? –The architecture model guides the implementation –The enterprise constraints provides guidance to implementers

8. 8 Architecture Definition Conceptual Model Ref 1,6 IEEE 1471-2000 definition was enhanced to include Architecture Framework and Artifacts INCOSE 2001

9. 9 Chesapeake Chapter INCOSE OOSEM WG OOSEM RUPBridged ZF Object Oriented Structured Analysis (Functional) Functional Object Oriented Diagrams Modeling Methods FE AFZachman FW Architecture Framework C4ISR/DoD AF Architecture Frameworks Architecture Framework Relationships e.g., IDEF0 e.g., OMG UML SD SAOther Standards

10. 10 Why Select Zachman Framework as the Benchmark? Performed industry survey on frameworks –Determined that the Zachman Framework describes basic architecture elements unencumbered by politics, committees or commercial pressures –Can be used describe any other framework using elements –Since being developed 17 years ago it has consistently proven itself, become a de facto standards and has been used in whole or part by: Federal Architecture Framework C4ISR Architecture Framework (in “All Views”) Tool Vendors (Ptech, Popkin) Spewak’s Enterprise Architecture Planning

11. 11 Architecture Modeling Based on the Zachman Framework The Zachman Framework is a total set of descriptive representations to fully describe a complex object a framework of “elements” a helpful thinking tool a classification schema Therefore the Zachman Framework views and elements are used as the basis for definition of the Architecture models Ref 2

12. 12 MOTIVATION (Why) TIME (When) PEOPLE (Who) NETWORK (Where) FUNCTION (How) DATA (What) Abstractions Designer Builder Perspectives Objective/ Scope (Contextual) Enterprise Model (Conceptual) System Model (Logical) Technology Model (Physical) Detailed Model (Out of Context) Subcontractor Conceptual Description of The Zachman Framework Functioning Enterprise Owner Planner Popkin

13. 13 ZIFA 2004

14. 14 Work Product Generation Principles The Zachman Framework defines primitive elements –Each cell then presents an example of a single- variable model –The columns present more detail –The relationship of the rows is not defined Composite models are defined by row primitives –The composite model create the work products –Used them to define the view bridged models The defined models are independent of the diagrams –Diagrams can be updated when the modeling language is enhanced (UML 2, SysML TM )

15. 15 Primitives to Work Products Described as Single Variable Products The Cells Contain Primitives Node = Business Location Link = Business Linkage e.g., Logistics Network The Artifacts Contain the View Elements Artifacts Contain the View Elements NETWORK Artifact (Where) NETWORK Artifact (Where) Logical View LOGICAL ARTIFACTS DATA Artifact FUNCTION Artifact NETWORK Artifact PEOPLE Artifact TIME Artifact MOTIVATION Artifact (How) (What) (Where) (Who) (When) (Why) Composite Models are the Work Products Logical Classes Logical Packages Logical Interactions Logical Scenarios Logical States ZIFA 2001

16. 16 Bridged Zachman Framework Models Physical View Models Logical View Models Business View Models Enterprise View BTEC7 2004

17. 17 MOTIVATION (Why) TIME (When) PEOPLE (Who) NETWORK (Where) FUNCTION (How) DATA (What) Abstractions Logical View Physical View Perspectives Scope Business Model System Model Technology Model Detailed Representations Specification Functioning Enterprise Business View Enterprise View Conceptual Description of the Bridged Zachman Framework

18. 18 Architectural Framework Model

19. 19 UML 2 Support for Systems Engineering Allows for more flexible System, Subsystems and Component representations Structural decomposition –e.g., Classes, Components, Subsystems System and component interconnections –via Parts, Ports, Connectors Behavior decomposition –e.g., Sequences, Activities, State Machines Enhancements to Activity diagrams –e.g., data and control flow constructs, activity partitions/swim lanes Ref 7

20. 20 UML 2 Support for Systems Engineering (cont.) Enhancements: –alternative sequences –reference sequences –interaction overview –timing diagrams Support for information flows between components Improved Profile and extension mechanisms Compliance points and levels for tool compliance Ref 7

21. 21 UML 2.0 Diagram Taxonomy Ref 7 New Updated New All diagrams refined some updated while others are new OMG 2003

22. 22 Speedpass TM Enterprise Architecture Example Presents the model of the Enterprise Architecture of Speedpass TM to show an example of the the bridged Object Oriented models and diagrams –Speedpass TM was developed by Mobile, and now is also used by Exxon –The primary purpose of Speedpass TM is to speedup transactions at gas pump and other merchants –The secondary purpose of Speedpass TM is to provide a tool to collect customer information that can be used for direct marketing

23. 23 Speedpass TM Example The Speedpass Enterprise consists of purchase payment capabilities provided by the entities –Enterprise is from point of view of customer

24. 24 Enterprise Architecture View Process UML Activity Diagram (Updated)

25. 25 Capability Model UML Use Case Diagram

26. 26 Resource Model UML Component Diagram

27. 27 Organization Model UML Component Diagram From the Tag point of view

28. 28 Information Model UML Class Diagram

29. 29 Conceptual Model UML Class Diagram

30. 30 Interaction Model Obtain Tag Capability UML Sequence Diagram (Updated)

31. 31 Interaction Model Make Purchase Capability UML Sequence Diagram (Updated)

32. 32 Business Architecture View Process UML Activity Diagram (Updated)

33. 33 Process Overview Model UML Interaction Overview Diagram (New)

34. 34 Process Model Obtain Tag Capability UML Activity Diagram (Updated)

35. 35 Process Model Make Purchase Capability UML Activity Diagram (Updated)

36. 36 Component Model Obtain Tag Capability UML Class Diagram

37. 37 Component Model Make Purchase Capability UML Class Diagram

38. 38 Dynamic Interaction Model Obtain Tag Capability UML Communication Diagram (Updated)

39. 39 Dynamic Interaction Model Make Purchase Capability UML Communication Diagram (Updated)

40. 40 Process State Model Obtain Tag Capability UML State Machine Diagram

41. 41 Process State Model Make Purchase Capability UML State Machine Diagram

42. 42 Timeline Model Obtain Tag Capability UML Timing Diagram (New)

43. 43 Timeline Model Make Purchase Capability UML Timing Diagram (New)

44. 44 Logical Architecture View Process UML Activity Diagram (Updated)

45. 45 Logical Activity Model Obtain Tag Capability UML Use Case Diagram

46. 46 Logical Capability Model Make Purchase Capability UML Use Case Diagram

47. 47 Static Element Model Obtain Tag Capability UML Class Diagram

48. 48 Static Element Model Make Purchase Capability UML Class Diagram

49. 49 Logical Package Model Obtain Tag Capability UML Package Diagram

50. 50 Logical Package Model Make Purchase Capability UML Package Diagram

51. 51 Message Interaction Model Obtain Tag Capability UML Sequence Diagram (Updated)

52. 52 Message Interaction Model Make Purchase Capability UML Sequence Diagram (Updated)

53. 53 Physical View Architecture Process UML Activity Diagram (Updated)

54. 54 Component Model UML Component Diagram

55. 55 Interaction Model UML Sequence Diagram (Updated)

56. 56 Component Relationship and Technology Model UML Composite Structure Diagram (New)

57. 57 Deployment Model UML Deployment Diagram

58. 58 Wrap-up Architecture diagrams need to be defined by models (independent of diagrams) Models need an prospective: a view UML 2 diagrams provide additional capabilities for modeling architecture Use of Object-Oriented methodology models provide output to developers that is consistent with the software design and development tools

59. 59 References UML 2.0 Superstructure Specification –http://www.omg.org/cgi-bin/doc?ptc/2003-08-02http://www.omg.org/cgi-bin/doc?ptc/2003-08-02 –Update in progress, finalization scheduled for November “UML 2 Toolkit” –Hans-Erik Eriksson, Magnus Penker, Brian Lyons, David Fado –www.wiley.com/compbookswww.wiley.com/compbooks Zachman Framework –www.zifa.comwww.zifa.com International Council on Systems Engineering (INCOSE) –www.incose.orgwww.incose.org International Organization Standardization (ISO) –www.iso.orgwww.iso.org Institute of Electrical Engineers (IEEE) –www.ieee.orgwww.ieee.org

60. Questions? Architecture Framework Models UML 2 Diagrams 60

61. 61 Thank You 3106 Use of UML 2.0 Diagrams for System Architecture Modeling Please fill out the speaker evaluation You can contact me further at … gundars.osvalds@boeing.com