1 / 61

3106 Use of UML 2.0 Diagrams for Systems Architecture Modeling

3106 Use of UML 2.0 Diagrams for Systems Architecture Modeling. Gundars Osvalds Systems of Systems Architect The Boeing Company. Contents. Architecture Definition Architecture Frameworks Zachman Framework Architecture Model Definitions UML 2 for System Engineering Features

kyleigh
Télécharger la présentation

3106 Use of UML 2.0 Diagrams for Systems Architecture Modeling

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  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. 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. 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. 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. 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 System Engineer Enterprise Architect Sponsor Customer Designer Developer Enterprise Architectural Stakeholders • Activities in developing a project architectural design Stakeholders Enterprise Architecture Model Needs Define Needs Design System Arch Uses Specs INCOSE 2004

  7. What Is an Architecture Framework? • 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. Enterprise 1 defines Architecture Framework Stakeholder 1..* Mission 1..* 1..* scopes represents holds fulfills 1..* 1..* 1..* Architecture guides Requirement Information System implements 1..* documents documents System Description Architecture Description guides 1..* 1 1 1 specifies contains 1..* View 1..* describes 1..* 1..* comprise Artifacts Model 1..* 1..* Architecture DefinitionConceptual Model IEEE 1471-2000 definition was enhanced to include Architecture Framework and Artifacts INCOSE 2001 Ref 1,6

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

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

  13. ZIFA 2004

  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, SysMLTM)

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

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

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

  18. Architectural Framework Model

  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. UML 2 Support forSystems 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. Updated New New Updated New Updated Ref 7 UML 2.0 Diagram Taxonomy • All diagrams refined some updated while others are new OMG 2003

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

  23. SpeedpassTMExample • The Speedpass Enterprise consists of purchase payment capabilities provided by the entities • Enterprise is from point of view of customer

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

  25. Capability Model UML Use Case Diagram

  26. Resource Model UML Component Diagram

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

  28. Information Model UML Class Diagram

  29. Conceptual Model UML Class Diagram

  30. Interaction ModelObtain Tag Capability UML Sequence Diagram (Updated)

  31. Interaction ModelMake Purchase Capability UML Sequence Diagram (Updated)

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

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

  34. Process ModelObtain Tag Capability UML Activity Diagram (Updated)

  35. Process ModelMake Purchase Capability UML Activity Diagram (Updated)

  36. Component ModelObtain Tag Capability UML Class Diagram

  37. Component ModelMake Purchase Capability UML Class Diagram

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

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

  40. Process State ModelObtain Tag Capability UML State Machine Diagram

  41. Process State ModelMake Purchase Capability UML State Machine Diagram

  42. Timeline ModelObtain Tag Capability UML Timing Diagram (New)

  43. Timeline ModelMake Purchase Capability UML Timing Diagram (New)

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

  45. Logical Activity ModelObtain Tag Capability UML Use Case Diagram

  46. Logical Capability ModelMake Purchase Capability UML Use Case Diagram

  47. Static Element ModelObtain Tag Capability UML Class Diagram

  48. Static Element ModelMake Purchase Capability UML Class Diagram

  49. Logical Package ModelObtain Tag Capability UML Package Diagram

  50. Logical Package ModelMake Purchase Capability UML Package Diagram

More Related