Hide Notes 

Slide 1: Architecting with Models and UML/SysML Dr. Kenneth Kung Architecture Technology Area Director Raytheon Company June 2005 © 2005 Raytheon Company All Rights Reserved
Slide 2: Raytheon Company RAC © 2005 Raytheon Company All Rights Reserved SAS IIS NCS IDS MS RTSC Page 2
Slide 3: Four Strategic Business Areas (SBA’s) Intelligence Surveillance Reconnaissance (ISR) Precision Engagement Missile Defense Homeland Security The SBA’s Focus on Cross-Business Opportunities © 2005 Raytheon Company All Rights Reserved Page 3
Slide 4: Technology Strategy to Support Business and SBAs Strategic Business Area Missile Defense Technology Areas RF EO/Lasers Processing Arch/Syst Int Mat’l & Structure ISR Business Units MS IDS IIS NCS RAC SAS Precision Strike RF Homeland Security Correlate EO/Lasers Rationalize Strategize Processing Arch/Syst Int Mat’l/Struct • • • • Architecture Vision Reference Architectures Implementation Guidelines Repositories for Reuse • • • • Architecture Review Board (ARB) Training and Certification Framework and Standards REAP (Raytheon Enterprise Arch Process) © 2005 Raytheon Company All Rights Reserved Page 4
Slide 5: Architecture Vision – System of Elements™ Traditional System of Elements ™ © 2005 Raytheon Company All Rights Reserved Page 5
Slide 6: Reference Architecture Applicable Strategy statement “System of Elements” Governed by ARB Specific Program Requirements Customer Needs Technology, Lessons Learned, Best Practices Apply Ref Arch Businesses Mission Solution Raytheon Enterprise Architecture Process (REAP) Reference Architecture offers a single point of departure in implementing mission solutions © 2005 Raytheon Company All Rights Reserved Page 6
Slide 7: System Architecture Implementation Approach Operational, Process & Workflow Modeling Logical Architecture Modeling Capabilities Database Integration & Test Operational View System Prototype Logical View System Build Physical View © 2005 Raytheon Company All Rights Reserved Physical Modeling Page 7
Slide 8: Operational View © 2005 Raytheon Company All Rights Reserved Page 8
Slide 9: Logical View Client/Presentation Layer • • • • • • Shared Operational Picture Controls/Status Displa ys Client Applications Web Applications Applets Alerts Common Human-Machine Interface (HMI) Mission Staff/ Crew • Human Performance Design • Common Look and Feel • Style Guide External Nodes • Visualization Serv ices • Collaboration • Identity Mission Services • • • • • • • • Mission Services Netw orking Information Assurance Resource Management Workflow Management Plans Management Task/Decision Support Data Synchronizati on Mission Mgmt Sensor Management Resource Management Comm Mgmt Intel Mgmt ISR Mgmt Planning Grow th ... Integration Framework Application Services: Workflow /Orchestration Softcopy Reference Folders Information Assurance Discov ery/Inference Web Services Applications Support Serv ices Messaging/Netw orking Proxies Agents/Access Serv ices Physical Environment Services Data Services: Metadata Framew ork Operating System Ontology/Discov ery System & Support Services: System Management/Support Serv ices Repository/Resources Layer Legacy and NodeSpecific Databases Metadata Catalog (MDC) Computing Infrastructure Platform/Node Systems Radios/ Data Links Communications/Networking Services Process/Business Logic Layer Groupware Infrastructure: Demiulitarized Zone (DMZ)/Security Services Layered Architecture Patterns Browser/ Web Portal Legacy/ Specialized Clients/Viewers © 2005 Raytheon Company All Rights Reserved Page 9
Slide 10: Physical View Connection Type Node 1 :Obj n Connection Node 2 :Obj 1 <<communication>> :Obj 3 :Obj 2 :Obj 4 Hardware Block Diagram • Product Data • Standards Profile • Software Documentation • Timing/Performance Data Interface Connection Type Contained Objects Node 3 :Obj 5 Component :Obj 6 Node Design Documentation © 2005 Raytheon Company All Rights Reserved Deployment Diagram Page 10
Slide 11: Architecture Analysis Operational/Mission Analysis Scenarios/ Events Mission Outcomes Operator Roles Activity Threads Use Cases Domain Collaboration Diagram Process/Workflow Analysis Actor Inputs/ Events System Outputs Logical/Functional Analysis Messages/ Data Physical Architecture Product Data Size/Timing Estimates © 2005 Raytheon Company All Rights Reserved Action Timing Design Patterns Foundation Classes Behavioral Patterns Logical Architecture Executable Architecture Design Verification Physical Analysis Digital Product Model Page 11
Slide 12: Integrated Model Mission Profile “SysML DoDAF Operational Architecture” OVs CIM - Computation Independent Model Analyze Requirements Drive Testing Elaborated “SysML DoDAF System Architecture” SVs PIM - Platform Independent Model Unit Test, VV&A X Delivered Components Drive Architecture-Based M&S PSM - Platform Specific Model X © 2005 Raytheon Company All Rights Reserved M&S Testing Space Live Standalone Net Centric Hardware and OS Independent Common Services + HW & OS (OACE) Platform Model X Platform Profile Page 12
Slide 13: UML Profiles: Major MDA Autocode Generation Mechanism • UML profiles support the development of domain or technology specific semantics extensions to UML. mechanism for auto-code generation. be used together. • Association of code to these standard profiles is a major • Profiles can be built on other profiles, and multiple profiles can –Define a majority of the Platform Model –Key Language Mappings profiles include CORBA, DSS (publish& subscribe) and XML-SOAP. –Key facilities profiles include: ■ Scheduling, Performance, and Time (RT support) ■ Testing ■ QoS and Fault Tolerance ■ SysML is the System Engineering UML-2 Profile in process of being adopted. ■ SysML has defined interfaces to HLA, MATHLAB, AP233, SystemC, and other SysEng constructs ■ DoDAF Rights Reserved Page 13 © 2005 Raytheon Company All will become a SysML Profile. –Key domain profiles include SysML and DoDAF.
Slide 14: UML Profile for Systems Engineering (SysML) - Observations • SEDSIG RFP for UML Profile for System Engineering Very Solid • Raytheon supports and agrees with this development • SysML Partners have sGood Technical product sStrive for consensus, both users and vendors sNeed to push forward, despite schedule slips © 2005 Raytheon Company All Rights Reserved Page 14
Slide 15: UML Profile for Systems Engineering (SysML) - Expectations • A model driven language for holistic system representation – SysML is broader than UML can do – Can capture all salient aspects of complex system design • A language that is intuitive for system engineers – Supporting proven systems engineering concepts – The language must not be a barrier to traditional system engineering methods • A language that facilitates, but does not mandate OO concepts • A language that is consistent with, or transitionable to, UML used in software development • A language that is embraced by a critical mass of tool vendors © 2005 Raytheon Company All Rights Reserved Page 15
Slide 16: UML Profile for DoDAF and MoDAF (UPDM) - Observations • • • • Customers demanding DoDAF artifacts Lack of Standard expression of DoDAF views in UML Non-standard tools and techniques for modeling DoDAF RFP – very solid team – Got DoDAF 2 key people involved • Submission Development – Raytheon values this activity – Will participate in the development of this profile © 2005 Raytheon Company All Rights Reserved Page 16
Slide 17: UML Profile for DoDAF and MoDAF (UPDM) - Expectations • A set of representations that is intuitive to our customer, and to non-UML engineers • A model-based approach for developing DoDAF/MoDAF views – Consistency between views, based on underlying model • An implementable profile, based on UML 2/SysML – More consistent tools – compliance beyond basics (intermediate or complete) • Usable data exchange between tools – XMI - XML meta data interface ■ Expect tools to compliant with XMI to support interoperability – Diagram exchange interface © 2005 Raytheon Company All Rights Reserved Page 17
Slide 18: Final Thoughts • Integration of processes has blurred the distinction between software and system • Integrated tool from operational views down to executable code can ease the communication among engineers from various disciplines • OMG is building the right products – Encourage faster consensus building • Challenge: Very few of us get to design a brand new system. – How do we bring the legacy applications into the framework? – How do we decompose their functionality to be re-used in an SOA architecture? © 2005 Raytheon Company All Rights Reserved Page 18