1. SysML Overview October 19, 2004 Sanford Friedenthal
(703)

2. SE Practices for Describing Systems
Future
Past
Specifications
Interface requirements
System design
Analysis & Trade-off
Test plans
Moving from Document centric to Model centric

3. Why Model Based Approach ?
Improved communications
Reduced ambiguity
Reduced errors
More complete representation
Enhanced knowledge capture

4. Implications of Model Based Approach
More rigorous and precise than traditional paper specifications and design documentation
Can take more time up front
An incremental process is key to evolve the system models and manage the scope of the effort
Large scale application requires modeling standards

5. 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
Part of larger family of MDA standards
Availability of tool vendor and training support

6. Unified Modeling Language (UML)
Is a visual modeling language
Is not a methodology
Defacto standard for SW level OO modeling
Visual Modeling Language = Notation + Semantics
Semantics = meaning
Notation = representation of meaning

7. UML/SysML Status Current Version – UML V1.5
UML V2.0 adopted in June 2003 and undergoing finalization through OMG
offers significant capability for systems engineering over UML 1.5
UML for Systems Engineering (SE)
UML for SE RFP issued by OMG in March 2003
SysML V1.0 expected for adoption in early 2005
addresses most of the requirements in the RFP

8. SysML Partners Industry
American Systems, BAE SYSTEMS, Boeing, Deere & Company, EADS Astrium, Eurostep, Israel Aircraft Industries, Lockheed Martin, Motorola, Northrop Grumman, oose.de, Raytheon, THALES
Government
DoD/OSD, NASA/JPL, NIST
Vendors
Artisan, Ceira, Gentleware, IBM, I-Logix, PivotPoint Technology, Popkin, Project Technology, 3SL, Telelogic, Vitech
Liaisons/Other Organizations
AP-233, CCSDS, EAST, INCOSE, Rosetta

9. SysML Milestones UML for SE RFP issued – March 28, 2003
Kickoff meeting – May 6, 2003
Overview presentation to OMG ADTF – Oct 27, 2003
Initial draft submitted to OMG – Jan 12, 2004
INCOSE Review – January 25-26, 2004
INCOSE Follow-up Review – May 25, 2004
Revised submission to OMG – August 2, 2004
2nd Revised submission to OMG – October 11, 2004
OMG technology adoption – Q (goal)

10. SysML Diagram Taxonomy
Derived from UML 2
Composite Structure

11. Overview of SysML Extensions

12. UML for SE Requirements Summary
Structure
e.g., system hierarchy, interconnection
Behavior
e.g., function-based behavior, state-based behavior
Properties
e.g., parametric models, time property
Requirements
e.g., requirements hierarchy, traceability
Verification
e.g., test cases, verification results
Other
e.g., trade studies

13. SysML Extensions Behavior Diagrams
Activity diagrams support for Enhanced Functional Flow Block Diagrams
Support for State and Message oriented behavior
Structure Diagrams
Class diagram for multiple uses
Assembly diagram to support system interconnection
Allocation relationship to support relation between behavior and structure, deployment of software to hardware
Parametric diagram to integrate with engineering analysis models
Requirements diagram to model requirements traceability and relationship to design models

14. A Few Sample Diagrams

15. Assemblies, Parts, Ports, Connectors & Flows
Assembly
Item Flow
UML 2 Port
Connector
SysML boundary part notation subject to change

16. Continuous Systems r e v i r D m e k e a t s r y B S S B A « » « » « »
interruptibleRegion r e v
Key
runToDisable i
Turn r
Driving
off D
Key On
{rate= continuous}
{stream }
Brake
Pressure
{stream } e m k e a t r s
runToDisable
ControlOperator B y
Braking S
runToCompletion
Enable on Brake
Pressure > 0
{stream }
Modulation
Frequency
{rate = continuous,
{stream } S
burst} B A
runToDisable
Monitor Traction

17. Sequence Diagram with Reference
Continue
seq:
Question :A :B :C :A :B
ask
ref
Question
alt
DoSth
alt ok ok
yes
nonono
notOK
notOK no
Derived from UML 2 Superstructure

18. State Machine Diagram

19. Requirement Diagram Showing Requirements Flowdown

20. SysML / AP-233 Alignment SysMLTools Systems Engineering Electrical CAE
Engineering Analysis
ISO 10303/AP-233
NEUTRAL SE
DATA EXCHANGE
FORMAT
Mechanical
CAD
Algorithm
Design
SW Dev
Environment
Planning
Tools
Testing
Tools

21. Summary
SysML Partners established in May 2003 to respond to UML for SE RFP
includes wide range of contributors from industry, tool vendors and government agencies
SysML extensively reuses a subset of UML 2 “out of the box”
Extensions needed to address RFP requirements
enhancements to composite structure and activity diagrams
two new diagram types (requirements and parametrics)
allocation relationships and auxiliary constructs
SysML alignment with ISO AP-233
Working towards adoption of SysML v1.0 in Q1 2005

22. References UML for SE RFP OMG doc# ad/03-03-41
SysML V0.8 (refer to
[UML2 2003] UML 2 Superstructure (Final Adopted Specification)
OMG doc# ptc/
[UML2 2003] UML 2 Infrastructure (Final Adopted Specification)
OMG doc# ptc/
INCOSE 2004 Symposium Paper “Extending UML to Support a Systems Modeling Language” – S. Friedenthal, C. Kobryn
INCOSE 2003 Symposium Paper “Extending UML from Software to Systems” – S. Friedenthal, R. Burkhart
INCOSE Insight (June 2004)
[Bock 2003] "UML 2 Activity Model Support for Systems Engineering Functional Flow Diagrams," Journal of INCOSE Systems Engineering, vol. 6, no. 4, October 2003 – C. Bock

23. Further Info
Web
Chairs
Cris Kobryn
Sandy Friedenthal