ACE Working Group 2007 Tools, Techniques, & Practices for Analyzing Architectures For Software-Intensive Systems
Architecture from the Systems Engineering Perspective Architectural Design from the Systems Engineering Perspective
Hans-Peter Hoffmann, Ph.D Chief Systems Methodologist
Modeling Solutions Product Division peter.hoffmann@telelogic.com Model-Driven Development of Embedded Systems Integrated Systems / Software Development Process Harmony
System Changes
Systems Engineering Harmony-SE
• Requirements Models RequirementsRequirements Test Scenarios SystemSystem • Use Case Models AnalysisAnalysis AcceptanceAcceptance
Executable
• Use Case Models / SystemsSystem (Sub-)System(Sub-)System Functional System Model AnalysisAnalysis & & Design Design IntegrationIntegration & & Test Test • Architectural System Model
System Architecture SW Module Baseline SW AnalysisAnalysis & & Design Design Integration & Test Software Model / Requirements Repository * Repository Model / Requirements Software Implementation Model Engineering Harmony-SWE SWSW Implementation && Unit Unit Test Test * Configuration Controlled Knowledge of the System Under Development: - Requirements Documentation - Requirements Traceability - Design Documentation - Test Definitions
2 © Telelogic AB SysML-Based Systems Engineering (Harmony-SE )
SysML Artifacts Requirements Analysis Requirements Requirements Capture ● Requirements Diagram(s) (optionally) ● Use Case Diagram(s) Definition of System Use Cases System Use Cases Per Use Case: System Use Cases ● Activity Diagram (Black-Box) ● Sequence Diagrams (Black-Box) System Functional Analysis ● Use Case Structure Diagram (BDD, IBD) Use Case Models, (Use Case-Based) System-Level Operations with Ports and Interfaces ● Statechart Diagram System-Level Operations
Architectural Design ● UC Activity Diagrams (White-Box) ● UC Sequence Diagrams (White-Box) System Architectural Design System Architecture Model with ● System Structure Diagram (BDD,IBD)
Model / Requirements/ Requirements Repository Repository Model Model allocated Operations with Ports and Interfaces Subsystem Architectural Design ● Subsystem(s)/Subsystem Component(s) Physical Subsystem Models with Statechart Diagram HW/SW allocated Operations
Logical ICDs HW/SW Req Specs incl. Test Scenarios Links providing traceability to original requirements HW/SW Design
3 © Telelogic AB Harmony-SE: System Functional Analysis Derivation of Use Case Scenarios from a UC Black-Box Activity Diagram
4 © Telelogic AB Harmony-SE: System Architectural Design Allocation of Operations to Subsystems
Use Case Black-Box Activity Diagram
Use Case White-Box Activity Diagram
5 © Telelogic AB Enterprise Architecture (DoDAF) Extending the Scope: From Enterprise Architecture O l p a e c r to System Architecture i a n t h io c n e a T l Systems
System Changes
Systems Engineering Harmony-SE
RequirementsRequirements Test Scenarios SystemSystem AnalysisAnalysis AcceptanceAcceptance
SystemsSystem (Sub-)System(Sub-)System AnalysisAnalysis & & Design Design IntegrationIntegration & & Test Test
System Architecture SW Module Baseline SW AnalysisAnalysis & & Design Design Integration & Test Software Model / Requirements Repository * Repository / Requirements Model Engineering Harmony-SWE SWSW Implementation && Unit Unit Test Test
6 © Telelogic AB Department of Defense Architecture Framework (DoDAF)
7 © Telelogic AB Telelogic MDD Tools
War Fighting Business Operations Operations
System Architect Enterprise Architecture
Systems Rhapsody Tau C C++ C++ Software Ada, C# J2ME J2EE
8 © Telelogic AB