47
10/27/2014 1 D. Kaslow L. Anderson [email protected] [email protected] 610-405-6685

Louise Anderson - INCOSE CubeSat Challenge Team (SSWG): Developing a Model Based Systems Engineering Reference Model

Embed Size (px)

Citation preview

Agenda Team Composition

INCOSE MBSE Initiative – SSWG & Challenge Team

What is Model Based Systems Engineering (MBSE) & Systems Modeling Language (SysML)

MBSE Roadmap for INCOSE

SSWG Challenge Project History (Phases 1 – 3)

Phase 1: CubeSat Reference Model & Application to Radio Aurora Explorer Mission (RAX) 3U CubeSat

Phase 2: Expanded RAX CubeSat Model including modeling behaviors and interface with Commercial Off the Shelf Simulation tools

Phase 3: CubeSat Enterprise Model Expansion (cost & product lifecycle) & design & operational characteristics of RAX

Developing a CubeSat Reference Model (Phase 4)

Next Steps

How to Participate

10/27/2014 2

JPL

NoMagic, MagicDraw

Developers/Engineers

CubeSat Challenge Team

Composition

JPL & NASA

Engineers

10/27/2014 3

University Professors & Students

Engineers and Developers from

Commercial Modeling & Simulation

Tool Providers

Modeling Experts from across the

world

Space System Working Group Lead

– David Kaslow

[email protected]

CubeSat Challenge Team Lead –

Louise Anderson

[email protected]

INCOSE MBSE Initiative - Genesis, Flow,

Interaction

4

International Council on

Systems Engineering (INCOSE)

INCOSE SE Vision 2020 [1]

2007

MBSE & SysML

MBSE Initiative &

Roadmap [2], ]3]

MBSE Challenge Teams

Space System Modeling

Object Modeling

Group (OMG)

1989

Unified

Modeling

Language

(UML)

1995

Systems

Modeling

Language

(SysML) [4]

2006

INCOSE

Working

Groups

Space

Systems

Working

Group

2000

SSWG

Challenge

Project

10/27/2014

CubeSat Focus

2011

MBSE and SysML

5

INCOSE Systems Engineering Vision 2020 [1]

MBSE: Formalized application of modeling to support system

requirements, design, analysis, verification, and validation activities

Object Management Group [4]

SysML: A graphical modeling language

for modeling complex systems including

hardware, software, information,

personnel, procedures, and facilities

Survey of Model Based Systems Engineering Methodologies [5], [6]

e.g. INCOSE OOSEM, IBM Telelogic Harmony SE, Vitech MBSE

MBSE: A collection of related processes, methods, and tools

Object Oriented Systems

Engineering Method

OOSEM

Top down, scenario

driven process that uses

SysML

10/27/2014

SysML

6

Model

Elements

Blocks

Actors

Flow

Specifications

Constraint Blocks

Interfaces

Signals

Ports

Diagrams are views of the

underlying system model

Behavior

Diagrams

Use Case

Activity

Sequence

State Machine

Structure

Diagrams

Block Definition

Internal Block

Block Properties

Parts

References

Values

Constraints

Operations

Receptions

A Block is the basic

unit of structure

Parametric

Diagram

Package

Diagram

Requirements

Diagram

SysML is a language

It is not a methodology

It is not a tool

10/27/2014

CubeSats? NanoSatellite (1-10kg)

Used for Space Research, Technology Demonstrations

1U = 10 cm^3, 2U, and 3U

Ultra Low Cost Missions

University/Company Training

COTS Hardware

First CubeSat Launched in 2003

Over 75+ CubeSats in Operation

10/27/2014 7

ISIS. "CubeSat Concept - Satellite Missions." CubeSat Concept - Satellite

Missions. N.p., n.d. Web. 13 Jan. 2013.

<https://directory.eoportal.org/web/eoportal/satellite-missions/c-

missions/CubeSat-concept>

MBSE RoadMap

10/27/2014 8

2010 2020 2025

Matu

rity

MBSE Capability

Ad Hoc MBSE Document Centric

2010

Well Defined MBSE

Institutionalized MBSE across Academia/Industry

Reduced cycle times Design optimization across broad trade space Cross domain effects based analysis

System of systems interoperability

Extending Maturity and Capability

Distributed & secure model repositories crossing multiple domains

Defined MBSE theory, ontology, and formalisms

Emerging MBSE standards

Matured MBSE methods and metrics, Integrated System/HW/SW models

Architecture model integrated with Simulation, Analysis, and Visualization

•Planning & Support

•Research

•Standards Development

•Processes, Practices, & Methods

•Tools & Technology Enhancements

•Outreach, Training & Education

Refer to activities in

the following areas:

[3]

SSWG Challenge Project History

9

INCOSE MBSE

Challenge Project

Initiated in 2007

INCOSE SSWG

2007-2010

Phase 0

Modeled a Space System

in SysML

Hypothetical FireSat –

Space Mission Analysis

and Design

Enterprise Modeling

for CubeSats

All lifecycle phases

RAX CubeSat Model

Trade Studies

MBSE CubeSat Project

2011 to Present

Phase 1

CubeSat Framework

Preliminary RAX Model

Phase 2

RAX Behavior Modeling

Power, Comm, State

(Phase 3)

(Phase 1-2)

Early

10/27/2014

Model Examples

10/27/2014 10

Tools

11

No Magic - MagicDraw

Graphical modeling tool

No Magic - Cameo Simulation Toolkit

Enables the time-step execution of behavior models within Magic Draw

InterCAX - Paramagic

Plug-in modudle for MagicDraw

Enables the execution of parametric models and system trades

Wraps external models such as MATLAB/Simulink, Mathematica , or

Excel

10/27/2014

Tools

12

Analytical Graphics - Systems Tool Kit

Simulation and visualization of spacecraft behavior

• Phoenix Integration - ModelCenter

– Graphical environment for creating simulation workflows by integrating

various types of simulation models, including Excel spreadsheets, STK

scenarios, and MATLAB scripts.

– Once a simulation workflow is created, PHX ModelCenter executes the

workflow, automatically transferring data between the simulators

• Phoenix Integration - MBSE Analyzer

– Enables the execution of parametric diagrams via ModelCenter

10/27/2014

Phase 0 - FireSat MIT/GaTech

Collaboration

Build an integrated model of FireSat

SubSystems in Matlab, STK, Excel

Integrated with Phoenix Model Center

Student Teams Mentored by Industry Experts from INCOSE SSWG

Successes

executable trade model for FireSat

Challenges

Difficult to build

SubSystem models were difficult to integrate

No architecture of the model integration or key parameters

Difficult to Audit for completeness correctness

Phase 1/2 – CubeSat

Framework and Method

Build a Modeling Framework and Method for CubeSats

CubeSat Domain-Specific Terms

SE Framework for Modeling CubeSat Missions, Spacecraft, and Ground Systems

Example Application using RAX Mission

Successes

First version of Framework

Early version of multiple executable demos

Challenges

Resources

Executability

Integration

15

MBSE CubeSat Project

Phase 3

Integrated Model-Based Systems Engineering (MBSE)

Applied to the Simulation of a CubeSat Mission

10/27/2014

RAX Mission Simulation

16

State Diagrams

Orbit

Solar

Experiment

Download

Models behavior in

response to internal

and external events

Parametric Diagrams

Get States

Power Collection

Update Energy

Update Data

Update Download

Mapped to analytical and

simulation models that

estimate RAX performance

Activity Diagrams

Run Operation

‒ Steps through time

Update States

Send Signals

‒ Controls update

of state values

Update State Values

Defines actions in the

activity along with the flow

of input, output, and control

Time step through a scenario and model:

Energy collection and usage

Data collection, storage, and downlink

10/27/2014

17

MBSE CubeSat Project

Phase 4

Developing a CubeSat

Model Based System Engineering (MBSE)

Reference Model

10/27/2014

CubeSat Reference and Project

Models

18

CubeSat System

Reference Model

SysML elements for

specifying requirements,

design, development, and

operations

Starting point for

mission specific

CubeSat model

CubeSat Project Model

Processes and methods for

developing and operating

Includes SysML activity and

sequence diagrams

Cal Poly CubeSat Design Specification [7]

Mechanical, Electrical, Communication Licenses, Imaging Licenses,

Debris Mitigation, Verification Reporting and Signoff

10/27/2014

CubeSat Reference Model - Scope

19

CubeSat Reference Model

A model that can be used as a

starting point for a mission

specific CubeSat model

Phases of

Operations

Launch

Early ops

Normal ops

Degraded

Sustainment

Foundations

INCOSE Systems Engineering Handbook [8]

NASA System Engineering Handbook [9]

Applied Space Systems Engineering [10]

Space Mission Engineering -The New SMAD [11]

CubeSat Mission Design Based on Systems

Engineering Approach [12]

Lifecycles

Conception through

retirement

Mission

Stakeholders

Needs

Objectives

Measures of

Effectiveness

Constraints

10/27/2014

CubeSat Reference Model – Goal

20

CubeSat

Reference Model

SysML Diagrams

Package Diagrams

Block Def Diagrams

Internal Block Diagram

Requirements

Parametrics

Behaviors Mission Specific

CubeSat

Interface with COTS

Modeling and

Simulation Tools

Space and Ground –

System Components

Library of components to

swap in and out of model

No Magic’s

Magic Draw

Graphical SysML

Modeling Tool

10/27/2014

CubeSat System

Reference Model

21 10/27/2014

CubeSat Domains

22 10/27/2014

CubeSat Stakeholders

23 10/27/2014

CubeSat Mission Needs, Objectives, Requirements

24 10/27/2014

CubeSat Operational Domain

25 10/27/2014

CubeSat External Environment

and External Contraints

26 10/27/2014

CubeSat Mission Enterprise

27 10/27/2014

CubeSat Logical Space System

28 10/27/2014

CubeSat Logical Ground

System

29 10/27/2014

Next Steps

NDIA Sys Eng Conf - 29 Oct

2014 INCOSE SSWG MBSE CubeSat Project 30

CubeSat Project Model

Physical Model

Library of Components, Requirements, Processes, etc.

Development Domain

Production Domain

Sustainment Domain

Retirement Domain

How to Participate

Email [email protected] & [email protected]

Added to the [email protected]

Weekly Teleconferences

Friday at 11:00 AM MT

Next one 11/07/14

View Past Meetings Notes

https://drive.google.com/?tab=mo&authuser=0#folders/0BwZ

IJenWp5PXSUc5YmowUUUwcEU

Talk to me Today!

10/27/2014 31

References

[1] Systems Engineering Vision 2020, INCOSE –TP_2004-004-02, ver. 2/03,September 2007. [Online]. Available: http://www.incose.org/ProductsPubs/pdf/SEVision2020_20071003_v2_03.pdf

[2] International Council on Systems Engineering (INCOSE), “MBSE Initiative,” January 2007. [Online] Available: https://connect.incose.org/tb/MnT/mbseworkshop/

[3] MBSE Roadmap. MBSE Wiki, INCOSE MBSE IW 2012. MBSE Wiki. [Online} Available: http://www.omgwiki.org/MBSE

http://www.omgwiki.org/MBSE/lib/exe/fetch.php?media=mbse:mbse_iw_2012-introduction-2012-01-21-friedenthal-c.pptx

[4] Object Management Group (OMG), OMG Website. [Online]. Available: http://www.omgsysml.org/

[5] Survey of Model-Based Systems Engineering (MBSE) Methodologies. INCOSE-TD-2007-003-01, Ver B. 10 June 2008. [Online]. Available https://www.incose.org/ProductsPubs/pdf/techdata/MTTC/MBSE_Methodology_Survey_2008-0610_RevB-JAE2.pdf.

NDIA Sys Eng Conf - 29 Oct

2014 INCOSE SSWG MBSE CubeSat Project 32

QUESTIONS?

10/27/2014 33

Backup

10/27/2014 34

Radio Aurora Explorer (RAX) Michigan Exploration Lab and SRI International

CubeSat mission

Space Weather Missions

Study plasma irregularities in the ionosphere

Disturbs Ground-Space Communication and Navigation

Science Experiment

Bistatic Radar Configuration

Radar signal transmitted by Incoherent Scatter Radar Site

Poker Flats, Alaska

Science Data

Processed on-board and compressed

Download to a globally distributed network

Commanded by control center in Ann Arbon, Michigan

10/27/2014 35

Challenge: Communication and Consistency

• Challenges

• Communicating the system in a world of models

• How do you extract all the rich detail from these simulations into

System Specification?

• DOORS? Documents/Slides/Spreadsheets?

• How do you assert mutual consistency between models?

• Meetings? Emails?

• Need an equally rich mechanism for expressing the system

design

– Human readable

– Machine readable

36 10/27/2014

Role of Languages in MBSE Enterprise

37 10/27/2014

From multiple points of view

Capture and express information about the system

Provide analyzable representations of the system

Authoritative source of information about the system

Power Scenario Demo Overview

Motivation

• “Bringing the model to life”, executing model

• Replaces “hacked” integrated software (e.g. manual/ complex code)

Integrating multiple software tools

• MagicDraw (SysML), Systems Tool Kit (STK), Matlab

• Phoenix ModelCenter (PHX) acts as “glue”

What does this enable?

• “Batch” execution of scenarios (i.e. full time history at once)

• Evaluation if requirements are satisfied/objective

• Test/compare scheduling algorithms (heuristic, optimized, etc.)

• Automatically re-run different scenarios (e.g. vary orbit, network)

• Parametric studies: Sensitivity to vehicle/ network parameters

Power Scenario: Lessons Learned

Useful things we “figured out” (with vendor support):

• Extracting time-dependent parameters (e.g. position in STK)

• Passing vectors between simulators was equally useful in PHX

Things to keep in mind for future modeling:

• Ensure you have required licenses! (may require vendor support)

• Parametric diagrams must inherit inputs/ outputs of PHX models

• Exploit existing code/ scenarios as much as possible

• Maintain modularity so can re-configure code for different

applications

Document Generation

10/27/2014 40

Models are great, still need to support reviews and

presentations

Generate document artifacts from the model

Leverage ISO 42010 (with some extensions)

Domain Specific Experts and Reviewers should NOT have to

go back to the model to do their job

Need a way to present the model-based document artifacts to

others without requiring others to understand the model.

Challenge Team History

2007 – First Challenge Team was Founded

2007-2010

SysML Model of FireSat (SMAD Textbook)

SysML Suitability for modeling space missions

2011 – CubeSat Initiative Began

CubeSat Modeling Framework

Foundation to model/design many current and future CubeSat missions

2012

Applying SysML Framework to Operational Mission

10/27/2014 41

Timeline of Activity

Y1: MIT/GaTech Student FireSat Example

Y2-4: SysML model of FireSat

Space Analysis Library using SMAD (Space Mission Analysis

and Design textbook, Wertz and Larson)

Basic Model of FireSat

Solar Panel Trade

Satellite Toolkit Integration

Y5->: CubeSat: An Architecture Framework and Method for

Space Systems MBSE

FireSat SysML Model

Build SysML model of FireSat

Learn SysML

Describe FireSat using SysML

Compare Model Description against typical document representation

Successes

Models of descriptions from book

Model views corresponding to documents

Challenges

Technique of modeling and applying the methodology

Table representations

Model Analysis

Document Production

SysML Space Analysis Library

Build SysML Space Analysis Library

Build Library of analysis from SMAD

Build approach to VnV for Library

Successes

Libraries for many analysis types

Useful testing approach

Challenges

Deep subject – much could not be captured

Executability (significantly improved since)

Units and Dimensions (significantly improved since)

Presentation of equations

FireSat Solar Panel Trade

Use Library to replicate Solar Panel Sizing Trade

FireSat Model and Library-> executable trade

Successes

Successfully built executable trade

Hard-linked to requirements

Powerful view of driving systems properties

Challenges

Executability (improving since)

Debugging

Scaling

FireSat Integrated Modeling

Integrate FireSat SysML Model with Satellite ToolKit

Exchange Orbit Scenario properties

Successes

Basic Exchange of Parameters

Direct comparison of MBSE in SysML and STK

Explicit link between models and requirements

Challenges

Integration

Complicated

Difficult to Scale

Consensus of Team

Modeling with SysML

Everything was hard at first

Methodology is critical to a model that hangs together

SysML simplified construction of basic things like functions and properties

SysML tastes like early CAD apps

Libraries of model analysis were effective in making solar panel trade

Integration with STK

Document Comparison

Model unified properties between views

Simplified understanding of the System

The common SysML language improved communication between teams and simplified collaboration

Automated reports allowed for more time to focus on engineering