# Presentation: 693931

## Extending UML from Software to Systems

***OMG SE DSIG Chair***
***Lockheed Martin Corporation***
***(703) 293-5557***
***sanford.friedenthal@lmco.com***

**Extending UML from Software to Systems**

***Aerospace Product Data Exchange Workshop***
***April 8, 2003***

## Topics

***Background and Motivation***
***Establishing Requirements for UML for SE***
***Challenges and Summary***

## Background and Motivation

## Background

***Increasing system complexity and software content***
***Process standards evolving to enhance systems maturity and integration with software***
***Need standards for ***_***modeling***_*** complex systems, which bridges with software and hardware modeling***
***Initiatives underway to address this need***
***ISO 10303 (AP-233) standards effort for SE data interchange and tool interoperability***
***INCOSE / OMG effort to extend UML to systems***

## SE Process Standards

***CMMI-SE/SW Guidance***
***Integrated Capability Maturity Model (CMMI) for Systems and Software***
***ISO/IEC 15288 Standard***
***System Life Cycle Processes***
***ANSI/EIA 632 Standard***
***Processes for Engineering a System***
***IEEE 1220-1998***
***Standard for Application and Management of the Systems Engineering Process***

## Current Practice for Describing Systems

***Specifications***
***Interface requirements***
***System design description***
***Trade studies***
***Test plans***

- Current SE Practices are Document Centric

## Why Model Based Approach ?

***Improved communications***
***Reduced ambiguity***
***Reduced errors***
***More complete representation***
***Enhanced knowledge capture***

## SE Modeling Techniques

***Many proven modeling techniques***
***Behavior diagrams***
***Data and control flow***
***Functional flow diagrams***
***IDEF***
***N2 charts***
***Schematic block diagrams***
***Signal flow diagrams (control loop)***
***State charts***
***Unstructured (e.g. power-point)***
***Limitations***
***No broadly accepted standard***
***Scalability to address complexity***
***Do not integrate well with software***
***Lack of extensibility mechanisms***

## Why UML for Systems Engineering ?

***De-facto standard within the software community***
***Robust and extensible language to adapt to SE needs***
***OMG Infrastructure***
***Broad international and industry representation***
***Defined adoption process to evolve UML***
***Availability of tool vendor and training support***

## Modeling Language

***UML***
***Is a visual modeling language***
***Is not a methodology***
***Visual Modeling Language = Notation + Semantics***
***Semantics = meaning***
***Notation = representation of meaning***
***Layered meta-model with extension capability***
***Status***
***Current Version – 1.5***
***UML V2.0 expected for adoption in 2003***

## Class diagram
Object diagram
Use Cases
Sequence diagram
Collaboration diagram
Activity diagram/Swim Lane
State chart
Component diagram
Deployment diagram

***Class diagram***
***Object diagram***
***Use Cases***
***Sequence diagram***
***Collaboration diagram***
***Activity diagram/Swim Lane***
***State chart***
***Component diagram***
***Deployment diagram***

## Establishing Requirements for UML for Systems Engineering

## OMG Systems Engineering Domain Special Interest Group (SE DSIG)

***Joint INCOSE / OMG Initiative to extend UML to SE***
***Chartered SE DSIG in July ‘01***
***SE DSIG kickoff in Sept ‘01***
***Aligned with ISO AP-233 Systems Engineering data interchange standard to support tool interoperability***

## Requirements Analysis for UML for SE

**Requirements Analysis for UML for SE**

***SE ***
***Concept ***
***Model***

***SE UML***
***Proto. &***
***Eval.***

***SE Req’ts***
***Analysis***

***AP-233, OMG***
*** ******& INCOSE***
***Inputs***

***Issues &***
***Approaches***

***SE UML***
***RFI ***

***UML Meta-Model***
***& Profiles***

***Industry***
***Responses***

***UML ***
***V2.0***
***Input***

***Other sources***

***SE UML***
***Profile***
***RFP prep***

***SE DSIG /***
***UML 2.0 ***
***Collaborations***

***UML for***
***SE RFP***

## RFI Response Summary

***Increased use of UML for SE across broad range of industry (automotive, aerospace, telecom)***
***Still  represents a small percentage of SE efforts***
***Positive indicators and results from the use of UML for SE (e.g., improved communications, precision, ..)***
***UML needs to address a broader set of SE concerns to provide a more robust SE modeling language***
***Broad interest from tool vendors to provide SE modeling capability***

## System UML Modeling (Notional)

**System UML Modeling (Notional)**

***Safety Model***

***Performance Model***

***Structure Models***

***Behavior Models***

## Summary of Perceived UML 1.x Limitations (Partial List) 

***Continuous time behavior***
***Decision tree (e.g. support for trade studies)***
***Hierarchical modeling of scenarios and behavior***
***Input/output flow (including data and mass/energy flow)***
***Integration with other specialty engineering models***
***Integration with geometric and spatial models ***
***Parametric relationships (e.g. performance models)***
***Performance and physical characteristics (incl probabilities)***
***Physical interfaces and connections***
***Problem definition and causal analysis***
***Requirements constructs***
***System, subsystem, element & component representations***
***Terminology harmonization***
***Verification and validation results***

## SE Conceptual Model

***SE Conceptual model defines fundamental SE concepts, and represents a primary input to the requirements for UML for SE***
***Expressed as a UML meta-model***
***Supporting Semantic Dictionary of definitions***
***Jointly developed and used by the ISO AP-233 SE data interchange standard , INCOSE, and the SE DSIG***
***Current baseline is Draft 12, which will continue to be refined through the reviews and issue resolution process***

## Top Level Conceptual Model – Draft 11

**Domain**
**of Interest**

**Element**

**System**

**Property**

**Structure**

**Physical**
**Property**

**Environment**

**System**
**Requirement**

- statement of

- Interacts with

- exhibits

- allocated to

**Stakeholder**
**    ****Need**

**Stakeholder**

- satisfied by

- represented by

- has

- allocated to

- budgeted to

**System**
**View**

- has view

- (1)

- (3)

- (5)

- (4)

- (6)

- (7)

- (8)

- derived from

- (9)

- (10)

**Behavior**

- (12)

- (14)

- (13)

**Reference**
**Document**

- (11)

- reference for

**Category**

- categorizes

- (2)

- reference for

- verifies

## UML for SE RFP

***Specifies requirements for UML for SE***
***Joint requirements reviews by OMG/INCOSE/AP-233 ***
***Issued by OMG on March 28, 2003***
***OMG Doc # ******ad/03-03-41****** ***
***http://syseng.omg.org/UML_for_SE_RFP.htm***
***Schedule***
***Initial Submissions - October 2003***
***Revised Submissions – March 2004***

## Challenges and Summary

## Challenges to Adopting UML for SE

***Developing a robust modeling language that addresses the broad system modeling requirements****** ***
***The evolution of model based methodologies***
***Acceptance of the model based approach by the SE community, implementers, and customers****** ***
***Ability to integrate the SE models with other discipline-specific models  (i.e. software, hardware, simulation and analysis, etc)****** ***
***Ensuring adequate infrastructure to support the use of models, including tools and training****** ***
***Continued adaptation and evolution of the modeling language***

## Summary

***Need system modeling language to address system complexity and bridge systems & software gap***
***Extending UML offers a potential solution to provide robust system modeling capability***
***INCOSE/OMG established SE DSIG with broad participation to extend UML from software to systems***
***UML for SE RFP issued March ‘ 2003 ***
***Expected adoption of standard systems modeling language in 2004***

## OMG SE DSIG Website

**http//syseng.omg.org**