1. 1LMC_SF Sanford Friedenthal INCOSE Liaison/ OMG SE DSIG Chair Lockheed Martin Corporation (703) 293-5557 sanford.friedenthal@lmco.com UML for SE Requirements Review INCOSE IW Tampa, Florida February 4-5, 2003

2. 2LMC_SF Requirements Review PurposePurpose –Review requirements in the Draft RFP for “UML for Systems Engineering” dated Jan 20, 2003 rev A –URL - http://syseng.omg.org/SE_UML_Profile_RFP.htm AgendaAgenda Tue, Feb 4 9:00 – 12:00 SE DSIG Overview & SE UML Req’ts Overview – S. FriedenthalSE DSIG Overview & SE UML Req’ts Overview – S. Friedenthal RFP Process and Roadmap – Roger BurkhartRFP Process and Roadmap – Roger Burkhart UML 2 Status and Proposal Summary – Cris KobrynUML 2 Status and Proposal Summary – Cris Kobryn An Application of UML for SE – Andrew WinklerAn Application of UML for SE – Andrew Winkler Wed, Feb 5 9:00- 4:00 Detailed walk-thru of requirements in draft RFPDetailed walk-thru of requirements in draft RFP

3. 3LMC_SF SE DSIG Overview

4. 4LMC_SF SE DSIG Background Joint INCOSE / OMG Initiative to extend UML to SEJoint INCOSE / OMG Initiative to extend UML to SE Chartered Systems Engineering Domain Special Interest Group (SE DSIG) in July ‘01Chartered Systems Engineering Domain Special Interest Group (SE DSIG) in July ‘01 SE DSIG kickoff in Sept ‘01SE DSIG kickoff in Sept ‘01 Aligned with ISO AP-233 Systems Engineering data interchange standardAligned with ISO AP-233 Systems Engineering data interchange standard

5. 5LMC_SF SE DSIG Goals 20022002 –Analyze requirements and candidate approaches for UML for SE –Influence UML 2.0 responses to address SE concerns 20032003 –Issue RFP for UML for Systems Engineering –Support Submission teams –Determine follow-on roadmap

6. 6LMC_SF Roadmap to “UML for SE” RFP SEConceptModel SE UML Proto. & Eval. SE Req’ts Analysis AP-233, OMG & INCOSE & INCOSEInputs Issues & Approaches SE UML RFI UML Meta-Model & Profiles IndustryResponses UMLV2.0Input Other sources SE UML Profile RFP prep SE DSIG / UML 2.0 Collaborations UML for SE RFP

7. 7LMC_SF Top Level Conceptual Model – Draft 8 Domain of Interest SE_Thing System Property Structure Physical Property Environment C C System Requirement statement of Interacts with exhibits C allocated to Stakeholder Need Stakeholder satisfied by represented by has allocated to budgeted to System View has view derived from Behavior C Property Reference reference for Category categorizes

8. 8LMC_SF UML for SE Req’ts Analysis SE UML Requirements Analysis V0.4 Nov 2002SE UML Requirements Analysis V0.4 Nov 2002 –Initial version July ‘02/updated to V0.4 Nov ‘02 –Identifies req’ts, candidate SE UML approaches, and issues –Made available as early input to UML V2.0 submitters –Resulting req’ts are input to RFP for UML for SE Primary SourcesPrimary Sources –UML specifications –SE Conceptual Model –SE UML RFI responses –SE UML prototyping –UML V2.0 submitter Interaction –Related papers –Other sources as inputs

9. 9LMC_SF System UML Modeling (Notional) Safety Model Performance Model Structure Models Behavior Models

10. 10LMC_SF Summary of Perceived UML 1.x 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 modelsIntegration with geometric and spatial models Parametric relationships (e.g. performance models)Parametric relationships (e.g. performance models) Performance and physical characteristics (incl probabilities)Performance and physical characteristics (incl probabilities) 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

11. 11LMC_SF UML Revision Status Current Version is UMLCurrent Version is UML –V1.41 sent to ISO –V1.5 = V1.41 + action semantics UML V2.0 RFP’sUML V2.0 RFP’s –Superstructure –Infrastructure –OCL –Diagram Interchange Multiple submittersMultiple submitters Final submissions due Jan ’03 / vote in March ‘03Final submissions due Jan ’03 / vote in March ‘03

12. 12LMC_SF SE DSIG / UML V2.0 Collaboration SE DSIG Collaboration goals to ensure UML V2 providesSE DSIG Collaboration goals to ensure UML V2 provides direct support for SE where practicaldirect support for SE where practical doesn’t preclude the ability to profiledoesn’t preclude the ability to profile Significant collaboration with U2P team and othersSignificant collaboration with U2P team and others

13. 13LMC_SF RFP for UML for SE - Draft Requirements Overview

14. 14LMC_SF RFP for UML for SE Draft RFP (Jan 20, 2003)Draft RFP (Jan 20, 2003) –OMG Doc # syseng/2003-01-02 –http://syseng.omg.org/SE_UML_Profile_RFP.htm Scheduled reviewsScheduled reviews –OMG Meeting – Jan 28 – 30, 2003 –INCOSE IW – Feb 4-5, 2003 Issue OMG Orlando Meeting – March 28, 2003Issue OMG Orlando Meeting – March 28, 2003 Initial Submissions to RFP – Jan 12, 2004Initial Submissions to RFP – Jan 12, 2004

15. 15LMC_SF RFP Outline 1.Introduction 2.Architectural Context 3.Adoption Process 4.Instructions for Submitters 5.General Requirements on Proposals 6.Specific Requirements on Proposals Appendix A: References and Glossary

16. 16LMC_SF Scope of RFP Focuses on general purpose modeling of a systemFocuses on general purpose modeling of a system –Includes both software and hardware systems –System level vs detailed hw/sw implementation models (code, 3D geometry, VHDL,..) –Integrate with discipline specific models (I.e. reliability, safety,..)

17. 17LMC_SF Evaluation Criteria (6.8) Ease of useEase of use UnambiguousUnambiguous PrecisePrecise CompleteComplete ScalableScalable Adaptable to different domainsAdaptable to different domains Capable of model interchangeCapable of model interchange Capable of diagram interchangeCapable of diagram interchange Process and method independentProcess and method independent Compliant with UML metamodelCompliant with UML metamodel VerifiableVerifiable

18. 18LMC_SF RFP Outline (Cont.) 6.Specific Requirements on Proposals 1.Problem Statement 2.Scope of Proposals Sought 3.Relationship to Existing OMG Specifications 4.Related Activities, Documents & Standards 5.Mandatory Requirements 6.Optional Requirements 7.Issues to be discussed –Sample problem description 8.Evaluation Criteria 9.Other Information unique to this RFP –Glossary 10.RFP Timetable

19. 19LMC_SF Mandatory Requirements (6.5) SE UML shall provide the capability to model:SE UML shall provide the capability to model: –Structure –Behavior –Property –Requirement –Verification –Other

20. 20LMC_SF Structure Hierarchy of systemsHierarchy of systems Types of system componentsTypes of system components Interconnection of systemsInterconnection of systems Environment and system boundaryEnvironment and system boundary DeploymentDeployment System storeSystem store

21. 21LMC_SF Behavior Functional transformation of inputs to outputsFunctional transformation of inputs to outputs Function activation/deactivationFunction activation/deactivation –control input –control operators –events/conditions State based behaviorsState based behaviors Allocation of behavior to systemsAllocation of behavior to systems

22. 22LMC_SF Property Property association (I.e. system, I/O, function,..)Property association (I.e. system, I/O, function,..) Property attributes (type, value, prob distr...)Property attributes (type, value, prob distr...) Time reference (global variable, time varying properties)Time reference (global variable, time varying properties) Parametric model (parametric relationships)Parametric model (parametric relationships) Parametric plotsParametric plots

23. 23LMC_SF Requirements Requirement type (functional, performance, physical)Requirement type (functional, performance, physical) Requirement attribute (criticality, TBD, verif status, )Requirement attribute (criticality, TBD, verif status, ) Effectiveness measure (optimization criterion)Effectiveness measure (optimization criterion) Requirement relationships (allocation, traceability,..)Requirement relationships (allocation, traceability,..)

24. 24LMC_SF Requirement (Cont.) Problem (ability to satisfy a req’t or need)Problem (ability to satisfy a req’t or need) Problem association with systems, components,..Problem association with systems, components,.. Problem cause (relationship to root cause)Problem cause (relationship to root cause)

25. 25LMC_SF Verification Test case (stimulus and expected response)Test case (stimulus and expected response) Verification resultVerification result Requirement verification, which compares verif result with requirementRequirement verification, which compares verif result with requirement Verification procedure (steps to execute test case)Verification procedure (steps to execute test case) Verification system which implements the procedureVerification system which implements the procedure

26. 26LMC_SF Other Model view as subset of model elements (default diagrams and user defined views)Model view as subset of model elements (default diagrams and user defined views) System role as subset of system behavior, properties, and structure to supportSystem role as subset of system behavior, properties, and structure to support Topology as graph of nodes and arcsTopology as graph of nodes and arcs Representation for simple geometric relationshipsRepresentation for simple geometric relationships

27. 27LMC_SF UML Customization Define UML constructs to support SE requirementsDefine UML constructs to support SE requirements –Use UML as-is where applicable (I.e. a function can be represented by an activity) –Customize UML constructs using UML built in extension mechanisms (I.e. profile) Rename model elementRename model element Add attributes and constraintsAdd attributes and constraints

28. 28LMC_SF Summary Need system modeling language to address system complexity and bridge systems & software gapNeed system modeling language to address system complexity and bridge systems & software gap Systems modeling requires robust capabilitiesSystems modeling requires robust capabilities Extending UML offers a potential solutionExtending UML offers a potential solution INCOSE/OMG established SE DSIGINCOSE/OMG established SE DSIG RFP is initial milestone towards developing a standard SE modeling languageRFP is initial milestone towards developing a standard SE modeling language

29. 29LMC_SF More Information http//syseng.omg.org OMG SE DSIG WebsiteOMG SE DSIG Website

30. 30LMC_SF SE UML Definition Dependencies Dependency

31. 31LMC_SF Challenges to Adopting SE UML Developing a robust modeling language that addresses the broad system modeling requirements Developing a robust modeling language that addresses the broad system modeling requirements The evolution of model based methodologies The evolution of model based methodologies Acceptance of the model based approach by the SE community, implementers, and customers 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) 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 Ensuring adequate infrastructure to support the use of models, including tools and training Continued adaptation and evolution of the modeling framework Continued adaptation and evolution of the modeling framework

32. 32LMC_SF RFP Preparation Milestones OMG SE DSIG Review – Jan 28-30, 2003OMG SE DSIG Review – Jan 28-30, 2003 INCOSE IW Review – Feb 4-5, 2003INCOSE IW Review – Feb 4-5, 2003 Update RFPUpdate RFP Incorporate Sample Problem DescriptionIncorporate Sample Problem Description Submit to OMG – March 3Submit to OMG – March 3 Review and finalize – March 24Review and finalize – March 24 OMG Vote to issue – March 28OMG Vote to issue – March 28