1

Extending UML From Software Extending UML From Software to Systemsto Systems

INCOSE ChapterINCOSE ChapterCrossroads of AmericaCrossroads of America

September 12, 2002September 12, 2002

Sanford FriedenthalSanford FriedenthalINCOSE Liaison/SE DSIG ChairINCOSE Liaison/SE DSIG ChairLockheed Martin CorporationLockheed Martin Corporation(703) 293(703) 293--55575557sanford.friedenthal@lmco.comsanford.friedenthal@lmco.com

2

BackgroundBackground•• Increasing system complexity and software contentIncreasing system complexity and software content

•• Process standards evolving to enhance systems Process standards evolving to enhance systems maturity and integration with softwarematurity and integration with software

•• Need approach to model complex systems, which Need approach to model complex systems, which bridges with software and hardware modelingbridges with software and hardware modeling

•• Initiatives underway to address this needInitiatives underway to address this need–– ISO APISO AP--233 standards effort for SE data 233 standards effort for SE data

interchange and tool interoperabilityinterchange and tool interoperability–– INCOSE / OMG effort to extend UML to systemsINCOSE / OMG effort to extend UML to systems

3

Current Practice for Describing Current Practice for Describing SystemsSystems

•• SpecificationsSpecifications

•• Interface requirementsInterface requirements

•• System design descriptionSystem design description

•• Trade studiesTrade studies

•• Test plansTest plans

4

Communications Challenge for SECommunications Challenge for SE

Translating Customer Requirements toTranslating Customer Requirements toHW, SW, Specialty, and Test requirementsHW, SW, Specialty, and Test requirements

SESE

SWSW

TesterTester

HWHW

RelRel, Mfg, HFE..., Mfg, HFE...

Marketing /Marketing /ProjProj Mgmt

CustomerCustomerMgmt

5

Why Model Based Approach ?Why Model Based Approach ?

•• Improved communicationsImproved communications

•• Reduced ambiguityReduced ambiguity

•• Reduced errorsReduced errors

•• More complete representationMore complete representation

•• Enhanced knowledge captureEnhanced knowledge capture

6

SE Modeling TechniquesSE Modeling Techniques•• Many proven modeling techniquesMany proven modeling techniques

–– Behavior diagramsBehavior diagrams–– Data and control flowData and control flow–– Functional flow diagramsFunctional flow diagrams–– IDEFIDEF–– N2 chartsN2 charts–– Schematic block diagramsSchematic block diagrams–– Signal flow diagrams (control loop)Signal flow diagrams (control loop)–– State chartsState charts–– Unstructured (e.g. powerUnstructured (e.g. power--point)point)

•• LimitationsLimitations–– No broadly accepted standardNo broadly accepted standard–– Scalability to address complexityScalability to address complexity–– Do not integrate well with softwareDo not integrate well with software–– Extensibility mechanisms to adapt to specific applicationsExtensibility mechanisms to adapt to specific applications

7

Why UML for Describing Systems ?Why UML for Describing Systems ?

•• DeDe--facto standard within the software communityfacto standard within the software community

•• Robust and extensible language to meet SE needsRobust and extensible language to meet SE needs

•• OMG InfrastructureOMG Infrastructure–– Broad international and industry representationBroad international and industry representation–– Defined adoption process to evolve UMLDefined adoption process to evolve UML

•• Tool vendor and training supportTool vendor and training support

8

Modeling LanguageModeling Language

•• UMLUML–– Is a modeling languageIs a modeling language–– Is not a methodologyIs not a methodology

•• Modeling Language = Syntax + SemanticsModeling Language = Syntax + Semantics–– Semantics = meaningSemantics = meaning–– Syntax = representation of meaningSyntax = representation of meaning

•• UML ApproachUML Approach–– Layered metaLayered meta--model with extension capabilitymodel with extension capability

9

UML Models (V1.4)UML Models (V1.4)

•• Class diagramClass diagram

•• Object diagramObject diagram

•• Use CasesUse Cases

•• Sequence diagramSequence diagram

•• Collaboration diagramCollaboration diagram

•• Activity diagram/Swim LaneActivity diagram/Swim Lane

•• State chartState chart

•• Component diagramComponent diagram

•• Deployment diagramDeployment diagram

10

System UML Modeling (Notional)System UML Modeling (Notional)

Safety ModelSafety Model Performance ModelPerformance Model

Structure ModelsStructure Models

Behavior ModelsBehavior Models

Gain Compensation 1/S 1/S

Dy namics

+-

X(t) Y(t)

11

OMG Systems Engineering Domain OMG Systems Engineering Domain Special Interest Group (SE DSIG)Special Interest Group (SE DSIG)•• Support development of Support development of UML for Systems EngineeringUML for Systems Engineering, which , which

supports the following goals:supports the following goals:

–– Provide a standard SE modeling language to specify, design, Provide a standard SE modeling language to specify, design, and verify complex systemsand verify complex systems

–– Facilitate integration between systems, software, and other Facilitate integration between systems, software, and other engineering disciplinesengineering disciplines

–– Promote rigor and correctness in the transfer of SE information Promote rigor and correctness in the transfer of SE information between toolsbetween tools

12

Broad Participation & InterestBroad Participation & Interest(First Three SE DSIG Meetings)(First Three SE DSIG Meetings)

•• ArtisanArtisan•• AstriumAstrium GLSHGLSH•• BAE Systems BAE Systems •• BoeingBoeing•• Cubic Defense SystemsCubic Defense Systems•• Deere & CompanyDeere & Company•• FujitsuFujitsu•• General DynamicsGeneral Dynamics•• Georgia TechGeorgia Tech•• Hitachi LtdHitachi Ltd•• HolagentHolagent•• HyrdroHyrdro QuebecQuebec•• II--logix

•• Kennedy CarterKennedy Carter•• Lockheed MartinLockheed Martin•• MitreMitre•• NASA NASA -- JPLJPL•• NISTNIST•• NSWCNSWC•• Open CascadeOpen Cascade•• OSDOSD•• PopkinPopkin•• RationalRational•• RaytheonRaytheon•• TelelogicTelelogic

logix

13

SE DSIG 2002 GoalsSE DSIG 2002 Goals

•• Establish requirements and candidate approaches Establish requirements and candidate approaches for UML for SE for UML for SE

•• Develop a roadmap for implementation through Develop a roadmap for implementation through OMG technology adoption processOMG technology adoption process

•• Influence UML 2.0 responses to address SE Influence UML 2.0 responses to address SE concernsconcerns

14

SE DSIG ProgressSE DSIG Progress•• OMG/APOMG/AP--233 Strategy at INCOSE International Workshop 233 Strategy at INCOSE International Workshop ––

Jan ‘2001Jan ‘2001

•• INCOSE / OMG relationship established at OMG Technical INCOSE / OMG relationship established at OMG Technical Meeting in July 2001Meeting in July 2001–– Liaison exchangeLiaison exchange–– SE DSIG charter (dtc/2001SE DSIG charter (dtc/2001--0707--02)02)

•• SE DSIG kickoff in Toronto SE DSIG kickoff in Toronto -- Sept 13, 2001 Sept 13, 2001 –– Developed preliminary strategy and plansDeveloped preliminary strategy and plans

•• SE DSIG Anaheim meetingSE DSIG Anaheim meeting-- Jan 29 Jan 29 -- 31 , 200231 , 2002–– Presented Initial SE Conceptual ModelPresented Initial SE Conceptual Model–– Reviewed and Issued RFIReviewed and Issued RFI–– Established SE DSIG Teams Established SE DSIG Teams

15

SE DSIG ProgressSE DSIG Progress•• SE DSIG Orlando meetingSE DSIG Orlando meeting-- Jan 24Jan 24--27 , 200227 , 2002

–– Reviewed RFI responsesReviewed RFI responses–– Reviewed updated SE Conceptual ModelReviewed updated SE Conceptual Model–– Presented UML for SE Prototype StatusPresented UML for SE Prototype Status–– Reviewed draft Reviewed draft req’tsreq’ts analysis for UML for SE analysis for UML for SE –– Initiated dialogue with UML 2.0 submittersInitiated dialogue with UML 2.0 submitters–– Updated agenda for OMG SE Information DayUpdated agenda for OMG SE Information Day

•• INCOSE Symposium INCOSE Symposium –– July, 2002July, 2002–– UML for SE PanelUML for SE Panel–– Issue Resolution on SE Conceptual ModelIssue Resolution on SE Conceptual Model

•• SE DSIGSE DSIG--U2P Workshop U2P Workshop –– Sept 12Sept 12--13, 200213, 2002–– Assess the extent to which the U2P UML 2.0 proposals Assess the extent to which the U2P UML 2.0 proposals

address the general requirements of Systems Engineering.address the general requirements of Systems Engineering.

16

Req’tsReq’ts Analysis for SE UMLAnalysis for SE UML

SE SE Conceptual Conceptual

ModelModel

UML for SEUML for SEPrototypingPrototyping

UML for SEUML for SEReq’tsReq’ts

APAP--233 233 ExpressExpressModelModel

Issues &Issues &ApproachesApproaches

UML for SEUML for SERFIRFI

UML MetaUML Meta--ModelModel

IndustryIndustryResponsesResponses

UML for SEUML for SEProfile RFPProfile RFP

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

* Informal Channel * Informal Channel

17

SE DSIG TeamsSE DSIG Teams

•• SE Conceptual Model SE Conceptual Model –– D. OliverD. Oliver

•• SE UML Prototyping & Evaluation SE UML Prototyping & Evaluation –– R. SteinerR. Steiner

•• Requirements Analysis for SE UML Requirements Analysis for SE UML –– S. FriedenthalS. Friedenthal

•• SE DSIG Technology Roadmap SE DSIG Technology Roadmap –– R. BurkhartR. Burkhart–– RFI ResponseRFI Response–– UML 2.0 Submission Team CoordinationUML 2.0 Submission Team Coordination

18

Top Level Conceptual Model Top Level Conceptual Model –– Draft 7Draft 7Domain

of Interest

SE_Thing

System

Property

Structure PhysicalProperty

Environment

C

C

Requirement_S

statement of

Interacts with

exhibits

C

allocated to

StakeholderNeed

Stakeholder

satisfied by

represented by

has

allocated to budgeted to

SystemView

collects(1)

(2)

(4)

(3)

(5)(6)

(7)

derived from

(8)

(9)

Behavior

C

(11) (13) (12)

PropertyReference

(10)

reference for

19

RFI Questions (Top Level)RFI Questions (Top Level)•• How has UML or other modeling languages been used for How has UML or other modeling languages been used for

systems engineering in your organization ?systems engineering in your organization ?

•• If UML was used, what benefits were realized ?If UML was used, what benefits were realized ?

•• If UML was used for systems engineering, or even if UML was If UML was used for systems engineering, or even if UML was considered but NOT used for systems engineering, discuss the considered but NOT used for systems engineering, discuss the limitations and issues perceived.limitations and issues perceived.

•• What are the potential solutions for addressing the What are the potential solutions for addressing the limitations/issues ? Please provide references as appropriate ?limitations/issues ? Please provide references as appropriate ?

•• What is your level of interest in the development of UML for What is your level of interest in the development of UML for Systems Engineering ?Systems Engineering ?

20

RFI RespondersRFI Responders•• ArtisanArtisan•• BAE Systems (CNI Division)BAE Systems (CNI Division)•• Georgia TechGeorgia Tech•• Holistic Systems EngineeringHolistic Systems Engineering•• II--LogixLogix•• INCOSE OOSEM Working GroupINCOSE OOSEM Working Group•• Lockheed Martin Corporation Lockheed Martin Corporation •• MitreMitre•• Project TechnologyProject Technology•• Rational SoftwareRational Software•• Systems Engineering Consulting Systems Engineering Consulting •• TofsTofs ABAB•• Volvo Car CorporationVolvo Car Corporation

21

RFI Response SummaryRFI Response Summary

•• Positive indicators and results from the use of Positive indicators and results from the use of UML for SEUML for SE

•• Increased use of UML for SE, although it is still Increased use of UML for SE, although it is still probably a small percentage of SE effortsprobably a small percentage of SE efforts

•• UML needs to address a broader set of SE UML needs to address a broader set of SE concerns concerns tptp realize the potential benefitsrealize the potential benefits

22

SE Evaluation Matrix ExampleSE Evaluation Matrix Example

SE Concept Cockbur n UseCases

OOSE M Oper ati onal Fl ows

Requi re ment s - User/ st akehol dergoal s, needs.

- Use CaseDescri pti ons, UseCase associ at edi nf or mati on,separ at er equi r ement st abl es

-

- Text Requi r ement scl asses, li nked t ot he modelel ement s

- Act or s- Level 0 Act or

Di agr am- Level 0

Oper ati onal Fl ows- Do mai n Obj ect

Model of Types

Functi onalrequi re ment s

- St eps i n a UseCase Descri pti on,

- Scope of UseCase, li nked dat ar equi r ement s

- Oper ati ons of acl ass, r el at ed t oi nvocati ons onsequencedi agr ams.Const r ai nt s oni nput/ out putval ues, condi ti ons& event s

- Oper ati onal Fl owLi nks

- Syst e mOper ati ons

- Do mai ns andTypes

23

Requirements Analysis for SE UMLRequirements Analysis for SE UML•• Initial draft developed based on multiple sourcesInitial draft developed based on multiple sources

–– SE Conceptual Model baseline from AnaheimSE Conceptual Model baseline from Anaheim–– Previous SE RFI inputsPrevious SE RFI inputs–– Related papers , etc.Related papers , etc.

•• Draft reviewed at June ’02 meeting, and V0.3 made Draft reviewed at June ’02 meeting, and V0.3 made available as early input to UML V2.0 submittersavailable as early input to UML V2.0 submitters

•• Will continue to update and review through Will continue to update and review through November meeting, based on evolving inputsNovember meeting, based on evolving inputs

•• Release V1.0 following Nov ’02 as input to Release V1.0 following Nov ’02 as input to technology roadmap, and continue to evolvetechnology roadmap, and continue to evolve

24

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

•• Continuous time behaviorContinuous time behavior•• Decision tree (e.g. support for trade studies)Decision tree (e.g. support for trade studies)•• Hierarchical modeling of scenarios and behaviorHierarchical modeling of scenarios and behavior•• Input/output flow (including data and mass/energy flow)Input/output flow (including data and mass/energy flow)•• Integration with other specialty engineering modelsIntegration with other specialty engineering models•• Integration with geometric and spatial models Integration with geometric and spatial models •• Parametric relationships (e.g. performance models)Parametric relationships (e.g. performance models)•• Performance, physical and nonPerformance, physical and non--behavioral characteristicsbehavioral characteristics•• Physical interfaces and connectionsPhysical interfaces and connections•• Problem definition and causal analysisProblem definition and causal analysis•• Requirements constructsRequirements constructs•• System, subsystem, element & component representationsSystem, subsystem, element & component representations•• Terminology harmonizationTerminology harmonization•• Verification and validation resultsVerification and validation results

25

SummarySummary

•• Need system modeling language to address system Need system modeling language to address system complexity and bridge systems & software gapcomplexity and bridge systems & software gap

•• Extending UML offers a potential solutionExtending UML offers a potential solution

•• Established OMG SE DSIG with broad participation Established OMG SE DSIG with broad participation to extend UML from software to systemsto extend UML from software to systems

•• INCOSE is leveraging OMG activity to improve the INCOSE is leveraging OMG activity to improve the practice of systems engineeringpractice of systems engineering

26

Upcoming MeetingsUpcoming Meetings

•• OMG Helsinki meeting OMG Helsinki meeting –– Oct 1 ’02Oct 1 ’02

•• SE Conceptual Model Review SE Conceptual Model Review –– Nov 11Nov 11--15 in DC15 in DC

•• OMG Washington DC meeting OMG Washington DC meeting –– Nov 18 Nov 18 -- 2222–– SE Information Day Nov 18 SE Information Day Nov 18 –– 1919

27

OMG SE DSIG WebsiteOMG SE DSIG Website

http//http//syseng.omg.orgsyseng.omg.org