Architecting the Problem Space Model-Based User Needs Analysis

Transcription

1 AEROSPACE CONCEPTS Architecting the Problem Space Model-Based User Needs Analysis David Harvey and Tommie Liddy Aerospace Concepts Format Lecture and tutorial exercise mix Classic Model-Based Systems Engineering introduction What is a system, which system and what is Systems Engineering Systems Engineering and Model-Based Systems Engineering Applying MBSE to user needs analysis and beyond Capability and capability system requirements (key to the problem space) Classic MBSE to support capability focus Stakeholders, views and architectures Case study Part 1 Operational scenario analysis Case study Part 2 High-level solution and system requirements Conclusion Tutorial Outline Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

2 Administrative Details Facilities and safety Schedule: 10:00 17:00 Lunch: 12:10 13:30 Afternoon break: 14:55 15:30 Additional breaks if needed Questions as they occur may be deferred (but not forgotten!) Introductions Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Who Are We? Aerospace Concepts Pty Ltd Systems engineering in aerospace, defence & related domains, specialising in: Model Based Systems Engineering (MBSE) and capability development Flight Safety Analysis (aerospace modelling and simulation) Engineering Management System development Main team of 20 plus ecosystem of specialists on contract Guidance Space vehicle design Human factors Communications eng. Failure analysis Military operations Aerospace Research Driving force in the Antarctic Broadband program Quantum computing Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

3 Now for you! Name Organization / Role What you hope to get from the tutorial Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS AEROSPACE CONCEPTS Classic Model-Based Systems Engineering Module 1 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS 2014

4 SYSTEMS ENGINEERING INTRODUCTION Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS A System is a thing, which contains smaller interconnected things, and exists in a larger thing, where it interacts with other things, to do something. is: a collection of components connected by links to form a purposeful entity within a larger context (aka system environment) form components and links = structure does: performs functions to process items, transforming inputs to outputs while responding to controls, consuming or producing resources & (usually) creating by-products and/or waste function time sequence of functions and items = behaviour behaviour is observed at external interfaces seen in the system context fit interfaces are comprised of links that transfer external items driven by external stimulus and response functions performed by external components joined by the interfaces a system is, and a system does will be, will do was, did What is a System? Current: as is Future: to be Past: as was and a system evolves 8

5 Which System..? Context System defines the problem Deployed System modifies the Context System Martin, James N., The Seven Samurai of Systems Engineering: Dealing with the Complexity of 7 Interrelated Systems, Fourteenth Annual International Symposium of the International Council On Systems Engineering (INCOSE), June 2004 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS What is Systems Engineering? (1) Systems Engineering is an engineering discipline whose responsibility is creating and executing an interdisciplinary process to ensure that customer and stakeholder needs are satisfied in a high quality, trustworthy, cost efficient and schedule compliant manner throughout a system's entire life cycle. INCOSE INCOSE SE Handbook 2012 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

6 What is Systems Engineering? (2) Based on systems thinking Discussing, examining and modelling the real world Cross-discipline Bridging the gap between fields of knowledge Interconnectivity Knowing how separate systems fit together in a larger context Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS History of Systems Engineering Formal origin in the 1930s with British multi-disciplinary team to analyse air defence system Developed since then initially in aerospace and defence now more widespread Driving factors Complexity Precision Rapid development INCOSE SE Handbook 2012 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

7 Systems Engineering Activity Areas Requirements Domain Behavior Domain Test & Evaluation Domain Architecture Domain Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Systems Engineering Process Stated Need Requirements Analysis: Defined Problem Systems Analysis & Process Control Requirements Loop Functional Analysis: Logical Solution Constraint Analysis: Design Limitations Logical model what the system does Verification Feedback derived from MIL-STD-499B (Draft) Design Loop Architecture Synthesis: Design Solution Solution Specification Physical model - how the system is structured Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

8 Managing Complexity with Hierarchies Decomposition and Aggregation to manage complexity From universe down to individual component Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Decomposition, Iteration & Recursion SYSTEM Iterative repeat process at a level derivation and allocation SUBSYSTEM Recursive same process at successive levels ELEMENT feedback Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

9 MODEL-BASED SYSTEMS ENGINEERING Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Documents and Specifications Capabilities and Requirements Product or Process Architecture Standards Trade Studies MOEs COIs Courtesy Vitech Corp. Verification Performance Constraints Traceability Reviews Validation Interfaces Decisions Architecture Risks Change Management Complexity in relationships often hidden Inconsistencies result in problems Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

10 Model-Based Approach Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Systems Engineering in Transition Traditional Specifications Future ATC Pilot Airplane Interface requirements Authorize Request to proceed Initiate power-up System design Direct taxiway Report Status Power-up Initiate Taxi Analysis & Trade-off Executed cmds Test plans Moving from document-centric to model-centric Reprinted from INCOSE Model-Based Systems Engineering Workshop, February 2010 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

11 Essential Components of MBSE A declared metamodel Structure and semantics Textual and graphical Explicit, context-free language for communication Problem, solution, and management dimensions Defined mappings / projections Fit for purpose views Documentation and design artefacts Other work products A process or methodology Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS What Makes an MBSE Model? Metamodel Language clear and unambiguous Structure behavior expressed in relationships Presentation Ways to express content, direct from the model Content Information built within the structure using the language Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

12 MBSE Concepts The model is essential, it is: the single source of truth The model encompasses the system design and specification The model is provided to subsequent teams throughout the product lifecycle Required system specifications are generated from the model, complete and consistent Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Evolution of MBSE Good Systems Engineering is inherently model based (holistic approach) Two major factors led to need for tool support 1. Increasing complexity of projects vs understanding capacity Metcalfe s Law (Metcalfe 1973) vs Miller s Magical Number (Miller 1955) Outsourcing (Sparrow & Wegner 2011) 2. Teams of Systems Engineers Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

13 Tool Support Evolution MBSE tools can be used to support SE that is either focused on the documents required or the system model Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS SE Centricity and Basis Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

14 Document-Centric SE The engineer s focus is on production of documents not the definition of the problem and appropriate system solution No reference to a central model Lack of enforced consistency and information reuse Documents still useful for communication (see Logan & Harvey 2011) Suggested by Estafan 2008 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Model-Centric SE Derived from Estafan 2008 Model development is the systems engineer s major focus Model of and about a system contained within a model of the context Key artefact becomes the model, but documents can be used to: Capture information As fit-for-purpose outputs from the model for review and approval Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

15 One Integrated Model Source Requirements Domain Originating requirements trace to behavior Behavior Domain Data verified by V&V Domain Data Behavior is allocated to physical components Architecture Domain Data verified by verified by Originating requirements trace to physical components Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Top-down system analysis & design process (example) Identify governing Standards, driving Requirements and responsible Organizations if given Identify top level Component (the System) which performs top level Function within the System Context Decompose Functions, capturing behavior through use of Resources, control flows, triggering and Exit logic and identifying input and output Items and performance Requirements (MOP) Develop system breakdown structure, with Components connected by Links that comprise Interfaces and transfer Items Allocate atomic Functions to atomic Components Produce component Specifications and other report Documents System Schema Segment Exit Resource comprised of transfers Perf Char Organization responsible for Selected Classes exits by Interface Link Item exhibits includes joins connected to decomposed by inputs / outputs / triggered by captures / consumes / produces Component refined by performs decomposed by System Architecture Domain built from Document (Standard) documents Selected Classes Requirement refined by specifies basis of specifies Function Color Code Physical Element Functional Element Selected Classes Interface Element Requirement Element Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

16 MBSE Concurrent Activities Process Inputs Middle out Functional/ Behavior Analysis System Behavior Models Data Inputs/Outputs Control/Sequencing Performance Rqmts. Top down Source Requirements Analysis Originating Rqmts. Issues and Decisions Risks CORE Repository Architecture/ Synthesis System Architecture Components Interfaces Constraints Allocated Rqmts Bottom up Design Validation and Verification Analysis Verification Methods Test Plans Process Outputs Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS A Model-Based Approach Supporting Fit for Purpose Views Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

17 The Automatic Generation of Representations and Work Products Customers Collectors Request Link Collector Product Link Return Link Command Link Geospatial Library System Views are projections of the model. Choose the views that serve the purpose and drive them from a single, integrated model. Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Model-Based, Model-Centric Focus on the information of and about the system Traceability Links established and maintained as part of the approach Consistency Single source of truth Internal consistency Adaptability Any number of views or documents can be produced as snapshots of slices of the model Robustness & information sharing System information made explicitly clear Domain specialist views are possible without neglecting the interconnected nature of domains Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

18 Rubbish in, rubbish out MBSE is Not a Silver Bullet Complete automation is not possible, nor desirable, input and review needed It is not easy MBSE doesn t make your life easier. MBSE done badly = bad SE = poor outcomes However, it makes projects more successful in the long-run less chance of schedule and cost overruns greater chance of delivering the right capability greater management of interfaces Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS AEROSPACE CONCEPTS Applying MBSE to user needs analysis and beyond Module 2 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS 2014

19 Directed Action CAPABILITY Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Stakeholder Needs and Operational Concepts 0. Define Need & System Concept ISO/IEC 15288* Stakeholder Requirements Definition Shared vision of stakeholders Mission requirement(s) Collection of scenarios involving external systems *ISO/IEC (2008) 15288:2008, Systems and Software Engineering System Life Cycle Processes. Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

20 Capability System Capability [Requirement] the Need the capacity or ability to achieve a particular effect may be described in terms of the nature of the effect and how, when, where and duration it is produced. Capability System the Solution a useful combination of elements required to deliver capability, Doctrine, Organization, Training, Materiel System, Leadership, Personnel, Facilities and Policy DOTmLPF-P cf: UK DLOD TEPID OIL + I, and AUS Fundamental Inputs to Capability (FICs) Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS DOTmLPF-P DOTmLPF-P is defined in the Joint Capabilities Integration Development System (JCIDS) process The DOTmLPF-P model represents categories of solutions required to create an operational capability DOTmLPF-P is a key authoritative intellectual tool in DoD s efforts to improve efficiency and effectiveness Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

21 Capability The ability to achieve a desired effect under specified standards and conditions through combinations of means and ways to perform a set of tasks. It is defined by an operational user and expressed in broad operational terms in the format of a joint or initial capabilities document or a joint doctrine, organization, training, materiel, leadership and education, personnel, and facilities (DOTMLPF) change recommendation. DoDAF v1.5 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Where Does Capability Fit? DoDAF v2.0 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

22 Capability System Requirements Capture end-user and other stakeholders views of the capability what they achieve and what they do Derive their needs of the enabling capability system in which some of them are a constituent element! Develop a solution-class concept for the Capability System that addresses those needs Derive the capability requirements for the capability system elements; and for which solutions are to developed and tested for all of the DOTmLPF-P elements, not just the major (materiel) systems! Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Traditional System Acquisition and Systems Engineering CUSTOMER Stakeholder requirements definition Program engineering Installation & validation Operational system Single project at the systems level SUPPLIERS System Requirements definition Proposed characteristics Architectural design Product engineering Reporting, metrics & management control Integration & verification Integrated system Multiple projects Allocated requirements Proposed characteristics Reporting, metrics & management control Delivered sub-systems Local user & organizational requirements Multiple projects Local user & organizational requirements System requirements definition Allocated requirements System requirements definition Component developments Allocated requirements Architectural design Component requirements Architectural design Proposed characteristics Product engineering Proposed characteristics Product engineering Component design Reporting, metrics & management control Integration & verification Integration & verification Reporting, metrics & management control Component build & test Integrated configuration items Delivered sub-systems Integrated configuration items Delivered components Components Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

23 A System Maritime missile defence capability enabled by an integrated detection, control and engagement system Classical systems engineering focuses on designing a best solution (system) for a bounded, controlled problem: i.e. system-centric analysis, design and integration Single Performer (aka Operational Node), many activities; single system, many functions. Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS System of Systems Increasing complexity of the system requires a new approach to capability development and employment. DETECT Networked detection, control and engagement capability: collaborating systems The Network CONTROL ENGAGE Network Centric Warfare; Network Enabled Capability Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

24 System of Systems Acquisition CUSTOMER Multiple projects at Multiple the SoS projects level Local user & organizational requirements Multiple projects Local user & organizational requirements Statement of of Need Need Allocated requirements Operational System Concept requirements concept definition Allocated requirements System requirements definition Component developments Proposed Proposed characteristics characteristics Architectural Architectural design design Allocated requirements Component requirements Architectural design Program Engineering Proposed characteristics Reporting, Reporting, metrics metrics & & management management control control Capability Product Engineering engineering Proposed characteristics Product engineering Component design Reporting, metrics & management control Installation & validation Reporting, metrics & management control Integration Installation & validation & verification Integration & verification Component build & test Operational Capability System Delivered systems Integrated Integrated systems SoS Delivered sub-systems Integrated configuration items Delivered components Components Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Stated Needs and Constraints Systems Engineering Process Requirements Analysis: Defined Problem Systems Analysis & Process Control Requirements Loop Functional Analysis: Logical Solution Constraint Analysis: Design Limitations Logical model: system behavior Verification Design Loop Solution Synthesis: Physical Solution Physical model: system structure System Requirements Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

25 3.1.1 Accept Requests 3.1 General Requirements Retain Inventory Control Multiple Sensors 1 s1.make Collection Request C.2 Customers AND External System 2 s1.accept & Format Request 3 C.1 s1.check Product Inventory Universe External System C.3 Collectors External System S.1.1 Analysts Human AND SYS.1 4 Collection Management... S.1.2 System Command Center Subsystem s1.get Product From Inventory S Work Stations Subsystem s1.provide Product to User Architecting the Problem Space - Model-Based User Needs Analysis Tuesday, 01 July 2014 Strategic Goals and Limitations Capability Definition Process Mission Analysis: Objectives and Tasks Operational Analysis & Process Control Validation Needs Loop Activity Analysis: Capability Concept Architecture Loop Constraint Analysis: Capability Limitations Capability Design: Capability [System] Solution Logical model: operational behavior Physical model: operational structure Capability [System] Requirements Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Model-Based System Definition Concurrent Activities Process Inputs: Source Rqmts. Change Requests Functional/ Behavior Analysis System Behavior Models Data Inputs/Outputs Control/Sequencing Performance Rqmts. Source Requirements Analysis Originating Rqmts. Issues and Decisions Risks CORE System Design Repository Architecture/ Synthesis System Architecture Components Interfaces Constraints Allocated Requirements Automated Document Generation Design Validation and Verification Analysis Verification Methods Test Plans Process Outputs: System Requirements Documents System Design Model Exports to Other Tools Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

26 3.1.1 Accept Requests General Requirements Retain Inventory Control Multiple Sensors 1 s1.make Collection Request C.2 Customers External System AND 2 3 s1.accept & Format Request C.1 s1.check Product Inventory Universe External System C.3 Collectors External System S.1.1 Analysts Human SYS.1 AND Collection Management... S.1.2 System Command Center Subsystem 4 s1.get Product From Inventory S.1.3 Work Stations Subsystem 5 s1.provide Product to User Architecting the Problem Space - Model-Based User Needs Analysis Tuesday, 01 July 2014 Model-Based Capability Definition Concurrent Activities Process Inputs: Guidance CONOPS Activity Analysis Operational Behavior Models Information Inputs/Outputs Control/Sequencing Effectiveness Measures Source Data Analysis User Needs Policies and Regulations Issues and Decisions Risks CORE Capability Design Repository Operational Validation Analysis Validation Methods Test Concepts Capability Design Operational Architecture Orgs, Roles, Nodes Interaction Needlines Allocated Needs Automated Document Generation Process Outputs: Operational Requirements Documents Operational Architecture Views Exports to Other Tools Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Operational & System Definition Recursion Mission Mission Analysis: Defined Goals Activity Analysis: Capability Concept Constraint Analysis: Capability Limitations Operational Design Capability Solution Systems Analysis & Process Control validation Capability System Requirements operational architecture measures of effectiveness validation system architecture System Requirements Requirements Analysis: Defined Problem Functional Analysis: Logical Solution Constraint Analysis: Design Limitations Systems Analysis & Process Control verification measures of performance Solution Synthesis: Physical Solution System Solution 52

27 Capability System Engineering Mission Analysis: Defined Goals Systems Analysis & Process Control Activity Analysis: Capability Concept Constraint Analysis: Capability Limitations Operational Design Capability Solution Capability System: The combination of the DOTMLPF elements Doctrine, Organization, Training, Materiel system, Leadership and education, Personnel, Facilities and Policy. Requirements Analysis: Defined Problem Systems Analysis & Process Control Requirements Analysis: Defined Problem Systems Analysis & Process Control Requirements Analysis: Defined Problem Systems Analysis & Process Control Requirements Analysis: Defined Problem Systems Analysis & Process Control Constraint Analysis: Design Limitations Constraint Analysis: Design Limitations Constraint Analysis: Design Limitations Constraint Analysis: Design Limitations Functional Analysis: Logical Solution Functional Analysis: Logical Solution Functional Analysis: Logical Solution Functional Analysis: Logical Solution Solution Synthesis: Physical Solution Doctrine Solution Solution Synthesis: Physical Solution Organization Solution Solution Synthesis: Physical Solution Training Solution Solution Synthesis: Physical Solution Leadership Solution Requirements Analysis: Defined Problem Systems Analysis & Process Control Requirements Analysis: Defined Problem Systems Analysis & Process Control Requirements Analysis: Defined Problem Systems Analysis & Process Control Requirements Analysis: Defined Problem Systems Analysis & Process Control Constraint Analysis: Design Limitations Functional Analysis: Logical Solution Constraint Analysis: Design Limitations Functional Analysis: Logical Solution Constraint Analysis: Design Limitations Functional Analysis: Logical Solution Constraint Analysis: Design Limitations Functional Analysis: Logical Solution Solution Synthesis: Physical Solution Personnel Solution Solution Synthesis: Physical Solution Facilities Solution Solution Synthesis: Physical Solution Policy Solution Solution Synthesis: Physical Solution Materiel System Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Definition and Description ARCHITECTURE Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

28 What is an Architecture? Architecture: the fundamental organization of a system embodied in its components, their relationships to each other and to the environment and the principles guiding its design and evolution, where: fundamental organization means essential, unifying concepts and principles system includes application, system, platform, system of-systems, enterprise, product line,... environment is developmental, operational, programmatic, context of the system ISO/IEC/IEEE 42010:2011, Systems and software engineering Architecture description Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS What is an Architecture Description? Mission ISO/IEC/IEEE 42010:2011 fulfills inhabits Environment influences System has has an Architecture described by has Stakeholder identifies addresses selects Architectural Description organized by provides Rationale aggregates covers conforms to Concern Viewpoint View Aerospace Concepts Pty Ltd 2014 has source Library Viewpoint methods for consists of Model Architecting the Problem Space INCOSE IS

29 Views and Viewpoints Multiple views; How many viewpoints? Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS What is an Architecture Framework? An architecture framework establishes a common practice for creating, interpreting, analyzing and using architecture descriptions within a particular domain of application or stakeholder community. ISO/IEC/IEEE 42010:2011 Architecture is often equated with structure. This might even be true, given a sufficiently general notion of structure. This issue goes to the heart of the Standard, which rests on two principles: (I) The fundamental concepts of systems are increasingly nonphysical and increasingly removed from what has been traditionally called "structure". In this tradition, "structure" usually refers to the components and organization of physically identifiable things, such as hardware entities or software objects such as modules. (II) All architecture views of the system are of equal importance. The Standard does not assume that a physical-structural view is primary or that it can be used to derive other views or properties of the system. Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

30 US DOD Architecture Framework C4ISR May 2009 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS DoDAF 2 Viewpoints From DoDAF 2.0 Volume 1: Introduction, Overview, and Concepts Manager Guide, May 28, 2009 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

31 DoDAF Meta-model Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS DoDAF Viewpoint Definitions (1) All Viewpoint -overarching aspects of architecture context Capability Viewpoint - capability requirements, delivery timing, and deployed capability what, when and who has it/will get it Operational Viewpoint - operational scenarios, activities, and requirements that support capabilities mission, tasks, who, op roles and activities, when, where, how Project Viewpoint - relationships between operational and capability requirements and the various projects being implemented capability development plan Services Viewpoint - design for solutions articulating the Performers, Activities, Services, and their Exchanges, providing for or supporting operational and capability functions logical support for operations Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

32 DoDAF Viewpoint Definitions (2) Systems Viewpoint - design for solutions articulating the systems, their composition, interconnectivity, and context providing for or supporting operational and capability functions physical support for operations Data and Information Viewpoint - data relationships and alignment structures satisfying capability and operational requirements, system engineering processes, and systems and services Standards Viewpoint - applicable operational, business, technical, and industry policies, standards, guidance, constraints, and forecasts Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS One Model Many Views Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

33 Operational scenario analysis CASE STUDY PART 1 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Case Study Generate a set of views that describe the architecture of the Emergency Medical Services Coordination Capability Use a mix of view models i.e. templates Text, table, and / or graphic Traditional views and SysML diagrams Handouts progressively provide an example of model-based capability analysis and system definition Document-Based, Model-Centric Systems Engineering Could move to Model-Based by using Systems Engineering tool support Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

34 Emergency Medical Services Coordination Emergency Medical Services Coordination?? System Center Capability????? Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Capability Definition Questions Why does it do it? goal and objectives => mission Who uses it? Who is impacted by it? organization elements and relationships Where is it used? locations, logical and / or physical When is it used? time, sequence, major events, cycles How is it used? processes and procedures, behavior What is in it & what does it do? How is this achieved? Operational Analysis Black Box context analysis Solution Concept Solution Design Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

35 Needline Information Exchange Information Exchange Performance Sim User OV2 Ref Source Activity Destination Category Content Services Size Freq Qty Air to Air Refuel ADF Generic ADF Conduct of Coord Info Electronic Very small 1-3 On demand Refueller aircraft in Aircraft Operations Data (3-6 per day) 1 needline AAR - Generic ADF Aircraft 1 needline AAR - Generic ADF Aircraft (V1) Air to Air Refueller (V1) 2 needline AEW&C - MROC Mobile Remote Operations Centre (V1) flight Refuel ADF aircraft in flight Conduct mobile regional operations Command (V1) Generic ADF Aircraft Command (V1) AEW&C (V1) Conduct of Operations Conduct of Operations Coord Info Fighter control rebro 2 needline AEW&C - MROC tbd tbd ROC MROC ISR/BM AEW&C Radar Plot 2 needline AEW&C - MROC AEW&C (V1) Distribute AEW&C 3 needline AOC - WOC Air Operations 4 needline Generic Missile Controller - FOSOW Command (V1) Generic FOSOW Controller (V1) track data Plan and manage air operations Control and update FOSOW flight path post launch Data ROC MROC ISR/BM AEW&C Track Data Generic Wing Operations Centre (V1) Generic Wing Operations Centre (V1) FOSOW (V1) FOSOW (V1) Command and Control System Telemetry refer to generic TG- TU C2 missile control data, target updates Low Quality Voice Low Quality Voice Electronic Data Electronic data refer to generic TG- TU C2 Electronic Data 30 min radio circuit 30 min radio circuit 1-3 On demand (3-6 per day) Exchange Latency Security Criticality Interop Type Near RT Duplex - S S Essential Joint, Coalition voice Half duplex S Essential Joint, Coalition 1-10 On demand voice Half duplex S Essential Joint, Coalition large 1-3 Continuous Near RT Simplex S Essential Joint medium 1-3 On demand (3-6 per day) refer to generic TG- TU C2 refer to generic TG- TU C2 refer to generic TG- TU C2 small 1-3 On mission demand, 1-10 per day Near RT Simplex S Essential Joint refer to generic TG- TU C2 Duplex - S refer to generic TG- TU C2 Essential refer to generic TG- TU C2 Key radios (relay It is assumed tha is equivalent in m between the Gen link. This IER referenc of this document. RT Duplex - S S Essential Joint Data transmissio Architecting the Problem Space - Model-Based User Needs Analysis Tuesday, 01 July 2014 Operational Architecture Domain built from decomposed by performs Guidance includes guides Selected Classes Capability basis of includes refined by Operational Task Performer (Op Node) Operational Activity achieves decomposed by Operational Schema Segment composed of connected to / thru NeedLine (Op I face) transfers Operational Item inputs / outputs / triggered by exits by captures / consumes/ produces achieves Mission includes Architecture achieves Exit Resource assigned to Organization responsible for Selected Classes Operational Viewpoint: model captures operational elements, the tasks and activities, and resource flow exchanges users need to achieve their goals and tasks - the mission views visualize the captured data Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Operational Analysis Methodology and Outputs An operational concept provides a mission overview that involves the users of a system of interest users who have formal (command) relationships and operational roles that constitute the performers which, to achieve missionnecessary operational tasks, exchange operational information which is produced or consumed by the operational activities that achieve the operational tasks performed by performers and the information exchange has various attributes and meets certain performance criteria. OV1 High-Level Operational Concept Graphic OV4 OV2 OV5b OV3 Organization Relationships Chart Operational Resource Flow (Needlines) Operational Activity Model Operational Resource Flow Operational Architecture represented by Operational Views Operational activity (hierarchy): OV5a Operational rules, transitions and timelines: OV6 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

36 Operational Scenario Analysis Matthew collapses at work. His colleague, John contacts the Emergency Medical Services (EMS). Alan, an EMS specialist call-center operator, takes the call Formal Organization acts as Performer performs Operational Activities results in Operational Need connected by exchange Needline transferred by Operational Items Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Organizational Relationships Organization Type: < > Role: <.> controls coordinates Organization Organization Theatre Company includes a Person with Role: Actor who becomes a Character in a Stage Play. The Person (organization) as Actor (role) performs as the Character (performer) in the Stage Play (operational scenario). Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

37 Operational Interaction Organization Type: < > Role: <.> responsible for Static View formal organization Performer connected to Needline aka Operational Interface Dynamic View working organization, scenario dependent Needed Interactions transfers Operational Item Resource Flows Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Scenario EMSCC Scenario Analysis: Who? Major medical emergency all services required Organization Elements and Performers Person Organization / Description [has] Role(s) Alan Emergency medical services call-center operator Emergency medical service coordinator [acts as] Performers(s) Call Taker / Operator Turn over and draw an EMSCC Organization Diagram Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

38 Organization as Hierarchy includes/ included in) coordinates with/ coordinated by) Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Organization as Spider Diagram Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

39 Organization traced to Performer The Organization is responsible for The Performer(s) Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Operational Connectivity Resource Flows Mission achieve Operational Tasks Performer performs achieve Operational Activity connected to inputs, outputs Needline transfers Operational Item Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

40 Scenario Interaction, Activities and Flows: Where, When and How? Major medical emergency all services required Operational Connectivity Needline Description Performers Caller - Operator Telephone link between the caller and the Emergency Medical Services Caller /Operator Info Transferred between Performers Patient Symptoms, Request for further details, etc Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Performer Hierarchy Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

41 Operational Connectivity Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Interaction, Activities and Flows: Where, When and How? Scenario Major medical emergency all services required Operational Activities and Information Flow Activity Description Performer Report medical emergency Contact Emergency Medical Services (EMS) Caller Receive Call Takes the EMS call Operator Input Item (Resource) Patient Symptoms Output Item (Resource) Patient Symptoms Request for further details, Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

42 Behavior Diagrams EFFBD* *Enhanced Functional Flow Block Diagram Time-sequenced Activity = Behavior Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS SysML Activity Diagram Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

43 Timeline Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS DoDAF OV-3 Operational Resource Flow Blank attributes missing information? Data can be readily reviewed in this view and format Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

44 Operational Data Metamodel OV1 assigned to Mission Organizations <role(s)> OV4 augmented by achieved by External File Operational Tasks Guidance (Policy & Doctrine) guides OV6a Business Limitations & Constraints responsible for achieved by results in Operational Needs & Constraints OV-2 Operational Nodes connected to performs OV-5a,b OV-6b,c Operational Activities inputs/ outputs generates Critical Operational Issues Operational Interfaces transfers Operational Items OV-3 Views generated from data model: OV-1: High-Level Operational Concept OV-2: Operational Resource Flow Description OV-3: Operational Resource Flow Matrix OV-4: Organizational Relationships Chart OV-5a: Operational Activity Decomposition Tree OV-5b: Operational Activity Model OV-6a: Operational Rules Model OV-6b: State Transition Description 87 OV-6c: Event-Trace Description Operational (User) Needs Derivation Organization <role(s)> assigned to Mission/ Op Task requires Capability connected to Performer [Op Node] Needline responsible for performs IT transfers achieves Operational Activity Operational Item inputs/ outputs/ triggered by results in refines (User) Requirement <Origin: operational> <Type: functional/ performance/ constraint> exhibits Measure of Effectiveness An organization element acting in it s operational role [i.e. as a performer] performs operational activity(s) and interacts with other performers to achieve a mission and / or operational tasks. Effective performance of that activity needs particular capability characteristics. Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

45 Scenario Operational / User Needs Derivation: What? Major medical emergency all services required Operational Needs (User Requirements) Performer Activity Need(s) Effectiveness Operator Receives Call Operator needs notification of Percentage of calls answered incoming emergency call. when an operator is available. Operator needs to accept Call Within time specified. Call wait time less than 30 secs for 99% of calls Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS User Needs SysML Reqts Diagram Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

46 Functions, requirements and system synthesis CASE STUDY PART 2 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS IEEE1220 Systems Engineering Plan Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

47 IEEE1220 Requirements Analysis User needs and other stakeholder requirements analysis Aerospace Concepts Pty Ltd 2014 System Requirements Analysis 93 IEEE1220 Functional Context Analysis Functional Requirements Analysis To: Requirements analysis Functional Design Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

48 System Requirements Model Business Limitations & Constraints refined by Performance Characteristic (MOP) SV-7 System Constraints Views generated from data model: SV-1 Systems Interface Description SV-2 Systems Resource Flow Description SV-4 Systems Functionality Description SV-6 Systems Resource Flow Matrix SV-7 Systems Measures Matrix SV-10a Systems Rules Model SV-10b Systems State Transition Description SV-10c Systems Event-Trace Description exhibits SV-4/SV-10 specifies SV-1/SV-2 Operational Needs & Constraints basis of Functions performed by System joined to [External] Interfaces System Requirements specified by inputs/ outputs connected to comprise joins verified by Verification Requirements Items transferred by Links connects External System(s) SV-6 Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Top-down system analysis & design process (example) Identify governing Standards, driving Requirements and responsible Organizations if given Identify top level Component (the System) which performs top level Function within the System Context Decompose Functions, capturing behavior through use of Resources, control flows, triggering and Exit logic and identifying input and output Items and performance Requirements (MOP) Develop system breakdown structure, with Components connected by Links that comprise Interfaces and transfer Items Allocate atomic Functions to atomic Components Produce component Specifications and other report Documents System Schema Segment Exit Resource comprised of transfers Perf Char Organization responsible for Selected Classes Interface exits by Link Item joins connected to decomposed by inputs / outputs / triggered by exhibits includes captures / consumes / produces Component performs decomposed by refined by System Architecture Domain built from Document (Standard) Selected Classes Requirement specifies refined by specifies basis of Function Color Code Physical Element Functional Element Selected Classes Interface Element MB CD Requirement 8 Element - 96 documents Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

49 Functions and Requirements: How this is achieved Scenario: Major medical emergency all services required Function and Performance Requirements (System Requirements) User Need Function(s) Performance Requirement Operator needs notification of incoming emergency call. Provide aural alarm Audio level above xxdba The EMS operator station shall provide an aural alarm at an initial level for xx dba escalating to yy dba over 10 sec period. Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS From Operational to System Space Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

50 End-to-end Analysis Thread The Operational Activities result in User Needs which form the basis of system Functions specified by Requirements Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS IEEE1220 System Functional Design Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

51 IEEE1220 System Synthesis Analysis of Alternatives Much analysis in design Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS * IEEE1220 System Design Much analysis before Final Design Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

52 Enterprise Other S holders Requirements Analysis and System Design User needs and other stakeholder requirements User Org Mission Limitations Op Tasks System requirements analysis Op Nodes Op Activities Op Needs Op Interfaces Op Items Constraints Functional Analysis and System Synthesis *Functions/Perf Items *System Links Interfaces External Systems *Functions/Perf *System Sub-functions Components Requirements Document Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Operational Architecture Domain documents built from Document (Guidance) refined by Selected Classes refined by Capability basis of decomposed by Operational Task includes Operational Capability Performer performs Op Activity decomposed by achieves achieves Aerospace Concepts Pty Ltd 2014 composed of connected to transfers NeedLine inputs / outputs / triggered by exits by captures / consumes / produces includes Op Item Mission enables Architecture achieves Exit Resource Organization responsible for Selected Classes The Model Framework Mode Interface comprised of State implemented by Link Transition Event implemented by implemented by Operational Needs implemented by implemented by exits by composed of Item includes joins transfers decomposed by inputs / outputs / triggered by captures / consumes / produces System of Interest connected to Component Function refined by performs basis of decomposed by Physical Element Functional Element System Architecture Domain built from Document (Standard) Selected Classes refined by Color Code documents Requirement Selected Classes Interface Element specifies Requirement Element 104

53 AEROSPACE CONCEPTS Summary Conclusions and beyond Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS CONCLUSION Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

54 Tutorial Summary Introduced classic systems engineering process and a modelbased systems engineering method Discussed architecture definition frameworks and their application to the problem space analysis Applied MBSE methods to the problem space (exploratory research and conceptual design) from goal identification through to needs definition to solution concept Gained practical experience in developing an information model and derivation of user needs and other stakeholder requirements Emergency Medical Services Capability Appreciation of the opportunities and challenges in adopting an MBSE method as a structured and explicitly defined approach for user and other stakeholder requirements analysis. Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Closing thoughts All good systems engineering is and always was model-based Documents are still an important part of MBSE With the rise in complexity of projects and teams, MBSE tool support is required Always ask Why, Who, Where, When, How & What Symmetry between the system and operations schema segments, the process and techniques are (almost) the same! Using the best available tool helps do the best possible job Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

55 Model Based Systems Engineering If you doubt the power of model based system descriptions, without using your hands, or simile or metaphor, describe a spiral staircase (to someone who has never seen one) Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Upcoming 2-Day MBCD Course Model-Based Conceptual Design A Practical Approach Date: Wednesday 9 to Thursday 10 July 2014 Location: Washington DC Fees: $995 USD per person For more details go to: and search conceptual design Enter the promotional code matesrates for 25% off 110

56 MODEL-BASED MODEL-CENTRIC APPROACH Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS Tool Support for Model-Based Approach Today we have focused on documentbased model-centric approach Here is an example of a model-based model-centric approach to the same problem Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS

57 QUESTIONS? Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS For additional information contact: Thank You! David Harvey Aerospace Concepts PO Box 3005 Port Adelaide SA 5015 AUSTRALIA Aerospace Concepts Pty Ltd 2014 Architecting the Problem Space INCOSE IS