Downloaded 11 times
More Related Content
Similar to What is the Lifecycle Modeling Language?
What is the Lifecycle Modeling Language?
- 1. WhatistheLifecycle ModelingLanguage? Steven H. Dam,Ph.D., ESEP President, SPEC Innovations 571-485-7805 steven.dam@specinnovations.com Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 1
- 2. AboutUs We are theexperts in systems engineering Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 2 • SPEC Innovations provides software, training, and consulting to the defense and aerospace industries and the intelligence community. • Our flagship software product, Innoslate is the first cloud-native, model-based systems engineering software solution made solely in the United States of America. • Our engineers built Innoslate to help systems engineers develop full lifecycle solutions to complex system of systems. • Innoslate software supports Requirements Management, Modeling and Simulation, Verification and Validation, and more in one seamless package.
- 3. MeetYourInstructors Steve Dam,Ph.D, ESEP Presidentand Founder of SPEC Innovations Executive Systems Engineer Ph.D. and BS in Physics Over 40 Years of Experience in Program Management, Systems Engineering, and Software Development Past President of INCOSE WMA Past Director of the Americas for INCOSE Adjunct Professor of Systems Engineering at GMU Member of INCOSE, NDIA, and AFCEA Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 3
- 4. WhatIsLifecycleModelingLanguage(LML)? • LML combinesthe logical constructs with an ontology to capture information • SysML – mainly constructs – limited ontology • DoDAF Metamodel 2.0 (DM2) ontology only • LML simplifies both the “constructs” and ontology to make them more complete, yet easier to use • Goal: A language that works across the full lifecycle Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 4
- 5. LMLOntology*Overview • Taxonomy**: • 12primary element classes • Many types of each element class • Action (types = Function, Activity, Task, etc.) • Relationships: almost all classes related to each other and themselves with consistent words • Asset performs Action/Action performed by Asset • Hierarchies: decomposed by/decomposes • Peer-to-Peer: related to/relates *Ontology = Taxonomy + relationships among terms and concepts ** Taxonomy = Collection of standardized, defined terms or concepts Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 5
- 6. LML’sSimplifiedSchema • Action • Artifact •Asset • Resource • Characteristic • Measure • Connection • Conduit • Logical • Cost • Decision • Input/Output • Location • Physical, Orbital, Virtual • Risk • Statement • Requirement • Time Supports capturing information throughout the lifecycle Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 6
- 7. Documentation Model Parametric andProgram Model LMLModels Functional Model Physical Model Primary Entities • Asset/Resource • Conduit Primary Entities • Action • Input/Output Statement/ Requirements Cost Time Characteristic/ Measure Location Artifact Risk Decision Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 7
- 8. LMLPrimaryEntitiesandRelationshipsforSESupport Artifact decomposed by/ decomposes Statement (Requirement) Characteristic (Measure) sourceof/sourced by Action traced to/traced from Asset (Resources) performed by/performs Input/Output specified by/specifies Connection (Conduit) transferred by/transfers connected by/ connects generated by/ generates received by/ receives decomposed by/ decomposes decomposed by/ decomposes decomposed by/ decomposes decomposed by/ decomposes decomposed by/ decomposes decomposed by/ decomposes Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 8
- 9. Action Artifact Asset (Resource) Characteristic (Measure) Connection (Conduit, Logical) Cost DecisionInput/Output Location (Orbital, Physical, Virtual) Risk Statement (Requirement) Time Action decomposed by* related to* references (consumes) performed by (produces) (seizes) specified by - incurs enables results in generates receives located at causes mitigates resolves (satisfies) traced from (verifies) occurs Artifact referenced by decomposed by* related to* referenced by referenced by specified by defines protocol for referenced by incurs referenced by enables referenced by results in referenced by located at causes mitigates referenced by resolves referenced by (satisfies) source of traced from (verifies) occurs Asset (Resource) (consumed by) performs (produced by) (seized by) references decomposed by* orbited by* related to* specified by connected by incurs enables made responds to results in - located at causes mitigates resolves (satisfies) traced from (verifies) occurs Characteristic (Measure) specifies references specifies specifies decomposed by* related to* specified by* specifies incurs specifies enables results in specifies specifies located at specifies causes mitigates resolves specifies (satisfies) spacifies traced from (verifies) occurs specifies Connection (Conduit, Logical) - defined protocol by references connects to specified by decomposed by* joined by* related to* incurs enables results in transfers located at causes mitigates resolves (satisfies) traced from (verifies) occurs Cost incurred by incurred by references incurred by incurred by specified by incurred by decomposed by* related to* enables incurred by results in incurred by located at causes incurred by mitigates resolves incurred by (satisfies) traced from (verifies) occurs Decision enabled by result of enabled by references result of enabled by made by responded by result of enabled by result of specified by enabled by result of enabled by incurs result of decomposed by* related to* enabled by result of located at causes enabled by mitigated by result of resolves alternative enabled by traced from result of date resolved by decision due occurs Input/Output generated by received by references - specified by transferred by incurs enables results in decomposed by* related to* located at causes mitigates resolves (satisfies) traced from (verifies) occurs Location (Orbital, Physical, Logical) locates locates locates locates specified by locates locates locates locates decomposed by* related to* locates mitigates locates (satisfies) traced from (verifies) occurs Risk caused by mitigated by resolved by caused by mitigated by references resolved by caused by mitigated by resolved by caused by mitigated by resolved by specified by caused by mitigated by resolved by caused by incurs mitigated by resolved by caused by enables mitigated by results in resolved by caused by mitigated by resolved by located at mitigated by caused by* decomposed by* related to* resolved by* caused by mitigated by resolved by occurs mitigated by Statement (Requirement) (satisfied by) traced to (verified by) references (satisified by) sourced by traced to (verified by) (satisified by) traced to (verified by) (satisified by) specified by traced to (verified by) (satisified by) traced to (verified by) incurs (satisified by) traced to (verified by) alternative of enables traced to results in (satisified by) traced to (verified by) located at (satisfied by) traced to (verified by) causes mitigates resolves decomposed by* traced to* related to* occurs (satisified by) (verified by) Time occurred by occurred by occurred by occurred by specified by occurred by occurred by date resolves decided by occurred by occurred by occurred by occurred by mitigates occurred by (satisfies) (verifies) decomposed by* related to* LMLRelationshipsProvideLinkageNeededBetweentheClasses • decomposed by/decomposes • orbited by/orbits • related to/relates Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 9
- 10. DiagramsAreNeededforEveryClass • Action Diagram(Mandatory) • Asset Diagram (Mandatory) • Spider Diagram (Mandatory) • Interface Diagrams • N2 (Assets or Actions) • Hierarchy Diagrams • Automatically color coded by class • Time Diagrams • Gantt Charts • Timeline Diagram • Location Diagrams • Maps for Earth • Orbital charts • Class/Block Definition Diagram • Data modeling • Risk Chart • Standard risk/opportunity chart • Organization Charts • Showing lines of communication, as well as lines of authority • Pie/Bar/Line Charts • For cost and performance • Combined Physical and Functional Diagram Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 10
- 11. ActionDiagram • Functional behavior model •Decision points are a special case of the Action class • Input/Output entities represented by a parallelogram • Can be verified through simulation Basic Action Entity Loop Action Construct Input/Output Entity Resource Entity Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 11
- 12. AssetDiagram • Physical model •Rectangles represent Assets • Lines represent Conduits • Adding pictures and having special lines types is encouraged Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 12
- 13. SpiderDiagram • Traceability Diagram •Boxes show entities (any class) • Lines represent the relationship between the entities Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 13
- 14. LMLSummary • LML providesthe fundamental foundation for a tool to support SE • LML contains the basic technical and programmatic classes needed for the lifecycle • LML defines the Action Diagram to enable better definition of logic as functional requirements • LML uses Physical Diagram to provide for abstraction, instances, and clones, thus simplifying physical models • LML provides the “80% solution” • It can be extended to meet specific needs (e.g. adding Question and Answer classes for a survey tool that feeds information into the modeling) Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 14
- 15. Who“Owns”LML? • LML isan open standard • It was developed and is overseen by the LML Steering Committee • The chair of this committee has been and currently is a professor at US Naval Postgraduate School • Go to www.lifecyclemodeling.org for more information Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 15
- 16. ImplementingLML • Innoslate® wasdeveloped to provide a means to test and enhance LML • Other tools can use this open standard • With the exception of the Action Diagram, you can apply LML in any tool that allows schema modification • LML is easy to map to other ontologies (e.g., DoDAF Meta Model 2.0) and/or diagramming frameworks (e.g., SysML) Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 16
- 17. Questions and Answers Use thepanel on the right to ask your questions Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 17
- 18. NextWebinar Become an expertin Innoslate by learning the ins and outs of the tool Innoslate 101: A Webinar for New Users Thursday , January 7th @2pm EST Go To Webinar
- 19. Proprietary of SPECInnovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 19 The Model-Based Systems Engineering Conference #MBSECON Virtually | February 22 – 24, 2021 www.mbse.heysummit.com Join us for MBSECON, the conference for dedicated systems engineers who want to achieve the digital future. Listen to experienced speakers, invited papers, panel sessions and learn more about our sponsors with our unique and immersive networking platform. Save the Date: MBSECON The Lifecycle Modeling Language Presents:
- 20. MoreResources SPEC Innovations offerstraining, books, videos, documentation, trails, and more 20 Training: specinnovations.com/training Books: “Real MBSE” textbook and lab manual available on Amazon Videos: Visit the SPEC Innovations Youtube channel LinkedIn: Innoslate and Systems Engineers User Group Documentation: help.Innoslate.com Trial: cloud.Innoslate.com Proprietary of SPEC Innovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam
- 21. Proprietary of SPECInnovations® 10/06/2020 at 2pm EDT, Dr. Steven Dam 21 Thank you! Visit cloud.innoslate.com for a trial. SPEC Innovations @Innoslate Innoslate User Group Innoslate.com/blog 571.485.7800 innoslate.com
Editor's Notes
- #5 LML brings together the language elements needed along with the visual context required.
- #6 The smallest number of classes possible, along with the clearest relationships – in both directions.
- #7 Note the specific inclusion of orbital locations. We recognize these require a different set of attributes to describe location, as opposed to the typical physical and virtual locations.
- #10 The complexity of the relationships (as represented by everything being connected to everything) is actually simpler than that provided in most schemas. Attributes on relationships also are allowed, which enables the complexity, but abstracts it in a way to make it seem easier to a user.