Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Developed
by
The webinar will begin shortly
WEBINAR
LML to SysML and Back
A Look into the Lifecycle Modeling Language and ...
InteractwithUs
LML to SysML and Back
LinkedIn Group:
Innoslate Users
@innoslate
PresenterProfile
LML to SysML and Back
Steven H. Dam, Ph.D., ESEP
President and Founder
steven.dam@specinnovations.com
Exp...
OurAgenda
1
LML to SysML and Back
2
3
4
5
6
The Basics of LML
The Basics of SysML
The Benefits of SysML
Demonstration: Imp...
WEBINAR
“It is common practice for systems engineers to
use a wide range of modeling languages, tools,
and techniques on l...
WEBINAR
The Basics of LML
LML to SysML and Back
1. To be easy to understand
2. To be easy to extend
3. To support both functional and object oriente...
LML to SysML and Back
• ERA form the meta-meta model for the language elements
• An entity is something that can exist by ...
LML to SysML and Back
In this example, the “trigger” attribute on the receives/received by relationship
determines if the ...
LML to SysML and Back
• Entity names were chosen to
provide a clear, easy to
understand general “bin” for
information
• Ex...
LML to SysML and Back
• Many discussions about
keeping “Orbital” as part of
the language
• Has important different
attribu...
LML to SysML and Back
• Key relationships for
traceability
• These represent a
subset of all the
relationship
• See specif...
LML to SysML and Back
• Note how LML
covers all the
different pieces of
information in
these domains
• Entity classes for
...
LML to SysML and Back
• 3 Mandatory Diagrams
• Action for functional modeling
• Asset for physical modeling
• Spider for t...
LML to SysML and Back
• All extensions must be
submitted to the LML
Steering Committee for
adjudication before they
will b...
LML to SysML and Back
• Actual instantiation of the LML
specification will be up to tool
vendors
• Innoslate instantiates ...
WEBINAR
The Basics of SysML
LML to SysML and Back
• SysML is a “profile” of UML
(i.e. it extends UML)
• Consists of a set of diagrams
• No ontology ex...
LML to SysML and Back
• SysML is specified using a
combination of UML modeling
techniques and precise natural
language to ...
LML to SysML and Back
4 Pillars of SysML
1. Structure
definition use
interaction
state
machine
activity/
function
2. Behav...
WEBINAR
The Benefits of SysML
LML to SysML and Back
• Linkage to UML for software-centric systems
• Specific diagrams defined across a number of SE area...
WEBINAR
The Benefits of LML
LML to SysML and Back
• Broad
• Ontology-based (enables translation from LML to SysML and back)
• All the capabilities of ...
LML to SysML and Back
Questions and Answers:
Enter Your Question in the GoToWebinar Control Panel
LML to SysML and Back
WEBINAR
Next Webinar
Time to Build Diagrams
March
Call, Email, Tweet, Chat, or Post we’ll answer your questions
10440 Balls Ford Road
Manassas,VA 20109
Specinnovations.com/...
Upcoming SlideShare
Loading in …5
×

LML to SysML and Back - Systems Engineering Languages

Steven Dam, Ph.D., ESEP shares his knowledge of the Lifecycle Modeling Language and the Systems Modeling Language. He discusses SysML's and LML's vast capabilities and how they work together in Innoslate®. The live presentation also demonstrates both LML and SysML diagrams as they have been developed for Innoslate®.

Related Books

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

LML to SysML and Back - Systems Engineering Languages

  1. 1. Developed by The webinar will begin shortly WEBINAR LML to SysML and Back A Look into the Lifecycle Modeling Language and System Modeling Language
  2. 2. InteractwithUs LML to SysML and Back LinkedIn Group: Innoslate Users @innoslate
  3. 3. PresenterProfile LML to SysML and Back Steven H. Dam, Ph.D., ESEP President and Founder steven.dam@specinnovations.com Expert Systems Engineering Professionals Certificate Participated in the development of LML
  4. 4. OurAgenda 1 LML to SysML and Back 2 3 4 5 6 The Basics of LML The Basics of SysML The Benefits of SysML Demonstration: Implementation of LML and SysML Questions and Answers The Benefits of LML
  5. 5. WEBINAR “It is common practice for systems engineers to use a wide range of modeling languages, tools, and techniques on large systems projects” SysML specification
  6. 6. WEBINAR The Basics of LML
  7. 7. LML to SysML and Back 1. To be easy to understand 2. To be easy to extend 3. To support both functional and object oriented approaches within the same design 4. To be a language that can be understood by most system stakeholders, not just Systems Engineers 5. To support systems from cradle to grave 6. To support both evolutionary and revolutionary changes to system plans and designs over the lifetime of a system [1] 6 Goals of LML
  8. 8. LML to SysML and Back • ERA form the meta-meta model for the language elements • An entity is something that can exist by itself and is uniquely identifiable. LML has defined 12 parent entities (Action, Artifact, Asset, Characteristic, Connection, Cost, Decision, Input/Output, Location, Risk, Statement and Time) [Noun] • A relationship connects entities to each other. • e.g. decomposed by/decomposes, traced to/traced from • An attribute is an inherent characteristic or quality of an entity or relationship • An attribute can be of an entity [Adjective] or relationship [Adverb] Entity, Relationship, Attribute (ERA)
  9. 9. LML to SysML and Back In this example, the “trigger” attribute on the receives/received by relationship determines if the Action must wait to execute until it receives the Input/Output element Attributes on Relationships trigger
  10. 10. LML to SysML and Back • Entity names were chosen to provide a clear, easy to understand general “bin” for information • Example: Action vs. Function or Activity • Child entities have unique attributes and/or relationships • Example: Measure vs. Characteristic • Child entities inherit attributes and relationships from parents LML Entities
  11. 11. LML to SysML and Back • Many discussions about keeping “Orbital” as part of the language • Has important different attributes and relationships • Key to a major part of the SE community (space) • Requirements contain quality attributes LML Entities
  12. 12. LML to SysML and Back • Key relationships for traceability • These represent a subset of all the relationship • See specification for complete set of relationships • Note all parent/child relationships the same for each entity class Traceability
  13. 13. LML to SysML and Back • Note how LML covers all the different pieces of information in these domains • Entity classes for other domains can be added as extensions LML Ontology Mapping to Domains
  14. 14. LML to SysML and Back • 3 Mandatory Diagrams • Action for functional modeling • Asset for physical modeling • Spider for traceability • Suggested diagrams for all classes based on common visualizations of the information (e.g. Risk Matrix for Risks) Diagrams
  15. 15. LML to SysML and Back • All extensions must be submitted to the LML Steering Committee for adjudication before they will be recognized as official extensions to LML • Version 1.1 added entities, attributes and relationships for SysML support Extensions
  16. 16. LML to SysML and Back • Actual instantiation of the LML specification will be up to tool vendors • Innoslate instantiates LML completely • Type attributes are labels • Includes diagrams for every class • Could fairly easily be used by any tools that enable schema extension • However, adding diagrams might be difficult for users to add – tool vendors would have to add them Instantiation
  17. 17. WEBINAR The Basics of SysML
  18. 18. LML to SysML and Back • SysML is a “profile” of UML (i.e. it extends UML) • Consists of a set of diagrams • No ontology explicitly (at this time) • Compliance with SysML requires that the subset of UML required for SysML is implemented, and that the SysML extensions to this subset are implemented Language Architecture
  19. 19. LML to SysML and Back • SysML is specified using a combination of UML modeling techniques and precise natural language to balance rigor and understandability • “Use of more formal constraints and semantics may be applied in future versions to further increase the precision of the language” • Consists of nine (9) diagrams Language Formalism
  20. 20. LML to SysML and Back 4 Pillars of SysML 1. Structure definition use interaction state machine activity/ function 2. Behavior 3. Requirements 4. Parametrics From: Object Management Group.
  21. 21. WEBINAR The Benefits of SysML
  22. 22. LML to SysML and Back • Linkage to UML for software-centric systems • Specific diagrams defined across a number of SE areas • Requirements Diagram • Parametric Diagram • SysML has encouraged model-based SE Benefits of SysML
  23. 23. WEBINAR The Benefits of LML
  24. 24. LML to SysML and Back • Broad • Ontology-based (enables translation from LML to SysML and back) • All the capabilities of SysML (with v1.1 extensions) • Simple structure • Useful for stakeholders across the entire lifecycle Benefits of LML
  25. 25. LML to SysML and Back
  26. 26. Questions and Answers: Enter Your Question in the GoToWebinar Control Panel LML to SysML and Back
  27. 27. WEBINAR Next Webinar Time to Build Diagrams March
  28. 28. Call, Email, Tweet, Chat, or Post we’ll answer your questions 10440 Balls Ford Road Manassas,VA 20109 Specinnovations.com/blog Innoslate.com/blog info@Innoslate.com support@innoslate.com 571-485-7800 LinkedIn: Innoslate User Group Twitter: @innoslate innoslate.com specinnovations.com Connect with Us! LML to SysML and Back

×