Your SlideShare is downloading. ×
  • Like
SysML Overview
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

SysML Overview

  • 1,138 views
Published

 

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,138
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
60
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SysML Overview Conrad Bock NIST [email_address] SysML Submission Team
  • 2. Topics
    • Background
      • Motivation/Why UML?
      • INCOSE/OMG
      • SysML Collaborators
    • Overview
      • UML for SE Requirements
      • UML Reuse
      • Diagram Examples
      • AP233 Alignment
  • 3. Background
  • 4. Motivation
    • Systems Engineers need a standard language for analyzing, specifying, designing, verifying and validating systems
    • Many different modeling techniques
      • Behavior diagrams, IDEF0, N2 charts, …
    • Lack broad-based standard that supports general purpose systems modeling needs
      • satisfies broad set of modeling requirements (behavior, structure, performance, …)
      • integrates with other disciplines (SW, HW, ..)
      • scalable
      • adaptable to different SE domains
      • supported by multiple tools
  • 5. Why UML for SE ?
    • De facto standard for software engineering
      • Tools and training are widely available, mature
    • Extensible and adaptable to support SE requirements
      • Not just for software modeling.
      • Wide lifecycle, including logical specifications and deployment.
      • Behavior models with virtual machines.
      • More than pictures:
        • Includes a repository model/API and
        • … and XML interchange.
    • OMG standardization process supports UML customization for specific domains (e.g., systems engineering)
  • 6. INCOSE/OMG Joint Initiative
    • OMG Systems Engineering Domain Special Interest Group chartered by INCOSE-OMG initiative in 2001
    • Extend UML for specifying, designing, and verifying complex systems
    • Provide capability for rigorous transfer of specifications among tools used by systems, software and hardware engineers
    • Bridge the semantic gap, the professional engineering discipline gap, and the training gap that exists between systems engineering and software engineering
    • Create a semantic bridge between ISO 10303-233 standard and ISO/IEC 19501 UML standard
  • 7. SE DSIG Tasks
    • Drafted UML for SE RFI, issued by OMG in 2002 to validate SE usage and limitations
    • Supported development of SE concept model
    • Collaborated with UML 2 submission teams
    • Performed detailed requirements analysis
    • Drafted UML for SE Request for Proposal, issued by the OMG in March 2003 (ad/03-03-41)
    • Extensive coordination with OMG, INCOSE, and ISO AP233 WG
  • 8. SysML Collaborators
    • Partnership of modeling tool users, vendors, and government agencies.
      • O rganized in May 2003 to respond to UML for Systems Engineering RFP
      • Industry
        • Lockheed Martin, Raytheon, Northrop Grumman, Boeing, BAE SYSTEMS, Motorola, Deere & Company, Eurostep, American Systems, Astrium Space, Israel Aircraft Industries, oose.de, THALES
      • Government
        • DoD/OSD, NASA/JPL, NIST
      • Tool Vendors
        • IBM/Rational, Telelogic, Vitech, Artisan, I-Logix, Popkin, Project Technology, Gentleware, Ceira, PivotPoint Technology, 3SL, EmbeddedPlus
      • Liaisons
        • AP233, CCSDS, EAST, INCOSE, Rosetta
  • 9. Stakeholder Review & Feedback Process
    • SysML Development
      • Writing initial submission 5-12/04
      • INCOSE review 1/04
      • Initial submission to OMG 2/04
      • INCOSE review 5/04
      • Extensive coordination with UML 2 FTF
      • Revised submission 10/04
      • Publications
        • INCOSE Symposium 2003, 2004 papers
        • INCOSE Insight article
        • INCOSE Journal article
        • Product Development Journal article
      • Initial vendor prototypes were favorably received during MDSD WG demo at INCOSE Symposium, 7/05
        • Artisan, EmbeddedPlus, I-Logix, Telelogic
  • 10. Internal Process
    • Applying systematic approach to language development
      • requirements analysis
      • language architecture & design
      • verification & validation
      • requirements traceability
      • reviews with stakeholders
    • Partnership collaboration mechanisms
      • weekly telecons
      • monthly physical meetings
      • intranet, web site, and mailing lists
  • 11. SysML Overview
  • 12. OMG RFP 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, spatial relationships
    RFP = Request for Proposals
  • 13. UML 2 Reuse
    • Identify UML 2 subset needed to support the UML for SE RFP requirements and evaluation criteria
      • reduce tool implementation requirements for SE vendors
      • reduce training requirements for SE’s
    • SysML complements UML 2
      • Two languages can be used together by teams that include both software and system engineers
  • 14. UML 2 Reuse
  • 15. SysML Diagram Taxonomy SysML Diagram Structure Diagram Behavior Diagram Use Case Diagram Activity Diagram Assembly Diagram Sequence Diagram Interaction Overview Diagram State Machine Diagram Timing Diagram Parametric Diagram Requirement Diagram Class Diagram Modified from UML 2 New diagram type As-is from UML 2 Diagram category As of v0.90
  • 16. Assemblies wa : WheelAssembly abs : ABSControlSystem mc : MasterCylinder Car h : Hub c : Caliper r : Rotor : Mechanical Feedback Port s : Sensor cu: Control Unit mv: ModulatorValve Command Port : Mechanical : Mechanical : Mechanical : Hydraulic : Hydraulic : Electronic
  • 17. Activities « runToDisable » Driving « runToDisable » Braking « runToDisable » Monitoring Traction {stream} {stream} {stream} {stream} Turn Key To On {rate= continuous} {rate = continuous, intermittent} Brake Pressure Modulation Frequency « controlOperator » « runToCompletion » Enable on Brake Pressure > 0 «requirement» Traction “ Slip no more than 1% of any meter travelled.” «satisfy» «satisfy» Bock, C., “UML 2 Activity Model Support for Systems Engineering Functional Flow Diagrams” INCOSE Journal, 6:4 (2003) & “SysML and UML 2 Support for Activity Modeling” to appear.
  • 18. Parametrics «property» Car.minStoppingDistance «parametricRelation» F = ma «parametricRelation» C f = F resistive / F normal «property» Car.mass «property» Earth.gravity m a «property» Car.tire.cFriction C f F resistive F normal F «parametricRelation» F = ma m a F «parametricRelation» d stop = - ½ v 2 / a d stop v a «property» Car.speed
  • 19. Allocation « runToDisable » Braking « runToDisable » Monitoring Traction « ControlOperator » « runToCompletion » Enable on Brake Pressure > 0 «allocate» «allocate» «allocate» «allocate» «allocate» wa : WheelAssembly abs : ABSControlSystem mc : MasterCylinder Car h : Hub c : Caliper r : Rotor : Mechanical Feedback Port s : Sensor cu: Control Unit mv: ModulatorValve Command Port : Mechanical : Mechanical : Mechanical : Hydraulic : Hydraulic : Electronic
  • 20. Requirements «requirement» Transportation Safety Requirement 1 “ Vehicle shall have less than 10 deaths per 100 million km / yr” «document» Transportation Safety «trace» «design» Small Scale Vehicle One to ten passengers, distances typically less than 1000 km per trip. «design» Dry Land Vehicle «requirement» Traction “ Slip no more than 1 % of any meter travelled.” «design» Wheel «trace» «requirement» Stopping Distance “ Less than half the length of the vehicle per 10 km/h. «satisfy» «satisfy» «satisfy» «design» Car «trace» «satisfy» «requirement» Wheel Rotation on Curves “ Slip no more than 1 % of any 360 O rotation.” «trace» «design» Differential «design» Axle «satisfy» «satisfy» «satisfy»
  • 21. ISO 10303 (STEP) / AP233
    • Data interchange protocol for Systems Engineering data
    • Tool independent format
    • Captures concepts of different tools involved in SE process
    • Defined based on the ISO 10303 modeling environment
    • Captures versioning information of data elements
      • enables configuration control
  • 22. SysML and AP233 Alignment AP233 NEUTRAL DATA EXCHANGE FORMAT SysML Modeling Tools Electrical CAE Mechanical CAD SW Dev Environment Systems Engineering Engineering Analysis Testing Tools Planning Tools Algorithm Design
  • 23. Conclusion
    • SE DSIG established as joint INCOSE/OMG initiative to
      • extend UML to support SE
      • align with AP233
    • Broad collaboration established to respond to RFP
      • includes wide range of contributors from industry, tool vendors and government agencies
      • multiple stakeholder reviews
    • SysML approach architecturally extends UML 2 Superstructure
      • reuses a subset of UML 2 “out of the box”
    • Changes to UML 2 include:
      • enhancements to composite structure and activity diagrams
      • two new diagram types (requirements and parametrics)
      • other changes include allocation relationships and auxiliary constructs
      • Alignment with ISO AP233
    • Working towards adoption of SysML v1.0 in Q1 2006
    • Latest draft specification:
      • http://www.omg.org/cgi-bin/doc?ad/05-01-03