RT24: Integration of M&S and DoDAF for Software/IT Systems 2012 RT-24 Post… · Explore ways to...

1
“Dandelion om4s1” DNA Signatures of SysMLbased OPNET Models Equation Graphs AutoGenerated from SysML Parametrics Structure Group1 scenarios (in G1 rollup model) Group2 scenario Group3 scenario “Dandelion om3s5” “Dandelion Pinwheel” OPNETSysML Interfacing Test Case HTTP Traffic Results for ACME News Network Design SysML model with requirements context for OPNET model OPNET model with baseline design & two alternatives HTTP traffic reqt. margin result (via above SysML model) OPNET results SERC Sponsor Research Review, November 13, 2012 RT24: Integration of M&S and DoDAF for Software/IT Systems Russell Peak, Selcuk Cimtalay, Miyako Wilson, et al. Objectives Testbed Results (continued) Approach Contact Summary & Impact ACME News Testbed GIT Aspects Exploiting DoDAF Support in UPDM/SysML Explore ways to make DoDAF more useful during development & usage of softwareintensive IT systems Overcome current approach: Burdensome afterthefact documentation generation Developed new concepts and prototypes as needed (e.g., OPNET interface) and new models for ACME News testbed Leveraged examples by vendors/others where feasible; adapted, extended, and improved them for RT24 purposes — Provided high value to illustrate RT24 concepts in a wider variety of sponsorrelevant contexts — Ex. Compare below original vs. RT24enhanced models for OV4 organizational structure/FTEs Successfully demonstrated UPDM/SysMLenabled M&S for IT/network/software domain — Diverse examples in RT24 ACME News Testbed — OPNET, GSM, FTE calculator, deadline timer, ..., with requirements margins in a UPDM/SysMLbased system model context — M&Sintensive examples from related work Provides strong evidence that this approach can likely fulfill sponsor needs per RT24 objectives Impact: Sponsor took SysML training in 2012 & is planning a pilot project Greatly enhanced integration of M&S and DoDAF for software/ITintensive systems Russell S. Peak, PhD Senior Researcher MBSE Branch Chief Aerospace Systems Design Lab www.asdl.gatech.edu Georgia Institute of Technology 270 Ferst Drive NW, Weber 123 Atlanta, Georgia 303320150 office +14048947572 [email protected] Recognize that UPDM enables “modelbased DoDAF” Recognize that UPDM Level 1 (L1) includes SysML Leverage SysMLenabled modeling & simulation (M&S) Apply capabilities to representative softwareintensive information systems problem (as proxy for sponsor) Interface to representative M&S tools (e.g., OPNET) Rapid evolution in recent years (esp. during 2010-2011) UPDM Profile: Top Level Structure UPDM with SysMLbased Parametrics Extended & Improved OV4 Model for RT24 (prepared by GIT) Model Structure (schema) Instances: Nested Views Instances: DNA Signature View Model structure statistics: 24 blocks (including generalized org. unit) Instance statistics: 4 org. unit levels = 1 corporation (ACME) with 1 HQ and 2 offices (16 org units & 51 people) ACME News Corp. - 17 org units - 51 people Atlanta HQ - 5 org units - 22 people LA Office - 5 org units - 16 people London Office - 6 org units - 13 people - 17 equations - 68 variables

Transcript of RT24: Integration of M&S and DoDAF for Software/IT Systems 2012 RT-24 Post… · Explore ways to...

“Dandelion om4s1”

DNA Signatures of SysML‐based OPNET ModelsEquation Graphs Auto‐Generated from SysML Parametrics Structure

Group1 scenarios(in G1 rollup model)

Group2 scenario

Group3 scenario

“Dandelion om3s5”

“Dandelion Pinwheel”

OPNET‐SysML Interfacing Test CaseHTTP Traffic Results for ACME News Network Design

SysML model with requirements context for OPNET model OPNET model with baseline design & two alternatives

HTTP traffic reqt. margin result (via above SysML model)

OPNET results

SERC Sponsor Research Review, November 13, 2012

RT24: Integration of M&S and 

DoDAF for Software/IT Systems Russell Peak, Selcuk Cimtalay, Miyako Wilson, et al.

Objectives Testbed Results

(continued)

Approach

Contact

Summary & Impact

ACME News Testbed

GIT Aspects Exploiting DoDAF Support in UPDM/SysML

Explore ways to make DoDAF more useful during development & 

usage of software‐intensive IT systems

Overcome current approach: 

Burdensome after‐the‐fact documentation generation

Developed new concepts and prototypes as needed (e.g., OPNET 

interface) and new models for ACME News testbed

Leveraged examples by vendors/others where feasible; adapted, 

extended, and improved them for RT24 purposes

— Provided high value to illustrate RT24 concepts 

in a wider variety of sponsor‐relevant contexts

— Ex. Compare below original vs. RT24‐enhanced models for 

OV‐4 organizational structure/FTEs

Successfully demonstrated UPDM/SysML‐enabled M&S for 

IT/network/software domain

— Diverse examples in RT24 ACME News Testbed

—OPNET, GSM, FTE calculator, deadline timer, ..., with requirements 

margins in a UPDM/SysML‐based system model context

—M&S‐intensive examples from related work

Provides strong evidence that this approach can likely fulfill 

sponsor needs per RT24 objectives

Impact:

Sponsor took SysML training in 2012 & is planning a pilot project

Greatly enhanced integration of M&S and DoDAF

for software/IT‐intensive systems

Russell S. Peak, PhD

Senior Researcher   

MBSE Branch Chief

Aerospace Systems Design Lab

www.asdl.gatech.edu

Georgia Institute of Technology 

270 Ferst Drive NW, Weber 123

Atlanta, Georgia 30332‐0150 

office +1‐404‐894‐7572 

[email protected]

Recognize that UPDM enables “model‐based DoDAF”

Recognize that UPDM Level 1 (L1) includes SysML

Leverage SysML‐enabled modeling & simulation (M&S)

Apply capabilities to representative software‐intensive information 

systems problem (as proxy for sponsor)

Interface to representative M&S tools (e.g., OPNET)

Rapid evolution in recent years (esp. during 2010-2011)

UPDM Profile: Top Level Structure

UPDM with SysML‐based ParametricsExtended & Improved OV‐4 Model for RT24 (prepared by GIT)

Model Structure (schema)

Instances: Nested Views

Instances: DNA Signature View

Model structure statistics:  24 blocks (including generalized org. unit)Instance statistics:  4 org. unit levels = 1 corporation (ACME)

with 1 HQ and 2 offices (16 org units & 51 people)

ACME News Corp.- 17 org units- 51 people

Atlanta HQ- 5 org units- 22 people

LA Office- 5 org units- 16 people

London Office- 6 org units- 13 people

- 17 equations- 68 variables