Lifecycle Modeling Language: Difference between revisions

Revision as of 10:29, 22 May 2014

Revision as of 04:41, 28 May 2014

Line 1:

'''The Lifecycle Modeling Language (LML)''' is an open-standard modeling language designed for [[systems engineering]]. It supports the full [[lifecycle]]: conceptual, utilization, support and retirement stages. Along with the integration of all lifecycle disciplines including, [[program management]], systems and design [[engineering]], [[verification and validation]], deployment and maintenance into one framework. <ref name="specification">{{cite web|author=LML Steering Committee|title=LML Specification|url=http://www.lifecyclemodeling.org/spec/LML_Specification_1_0.pdf|accessdate=2013-10-17}}</ref>

LML was originally designed by the LML steering committee. The specification was published October 17th17, 2013.

The purpose behind the language is to replace predecessor languages, such as [[UML]] and [[SysML]] that over complicate the systems engineering process. LML uses common language to define its modeling elements such as entity, attribute, schedule, cost, and relationship. <ref>{{cite web| url = http://www.lifecyclemodeling.org/about-lml/|title=About Lifecycle Modeling Language|publisher=LML Steering Committee|accessdate=2014-06-05}}</ref>

The purpose behind the language is to replace predecessor languages, such as [[UML]] and [[SysML]] that over complicate the systems engineering process. LML uses common language to define its modeling elements such as entity, attribute, schedule, cost, and relationship. <ref>{{cite web| url = http://www.lifecyclemodeling.org/about-lml/|title=About Lifecycle Modeling Language|publisher=LML Steering Committee|accessdate=2014-06-05}}</ref>

== Overview ==

LML communicates cost, schedule and performance to all stakeholders in the system lifecycle.

LML combines the logical constructs with an ontology to capture information. SysML is mainly constructs and has a limited ontology, while DoDAF MetaModel 2.0 (DM2) only has an ontology. Instead LML simplifies both the constructs and ontology to make them more complete, but still easier to use. There are only 12 primary entity classes. Almost all of the classes relate to each other and themselves with consistent words, i.e., Asset performs Action. Action performed by Asset. <ref name="slideshare.net">Dr. Steven Dam and Dr. Warren Vaneman, [http://www.slideshare.net/ElizabethSteiner/lifecycle-modeling-language-tutorial-by-dr-dam-and-dr-vaneman?utm_content=5253617&utm_medium=social&utm_source=twitter "Lifecycle Modeling Language Tutorial"], ''Presentation at SEDC 2014''2014-04-06</ref>

SysML uses object oriented design, because it was designed to relate systems thinking to software development. No other discipline in the lifecycle uses object oriented design and analysis extensively. LML captures the entire lifecycle from cradle to grave. <ref name="specification"/>

Systems Engineers have identified complexity as a major issue. <ref>Dr. Steven Dam and Dr. Warren Vaneman, [http://www.name="slideshare.net/ElizabethSteiner/lifecycle-modeling-language-tutorial-by-dr-dam-and-dr-vaneman?utm_content=5253617&utm_medium=social&utm_source=twitter "Lifecycle Modeling Language Tutorial"], ''Presentation at SEDC 2014''2014-04-06</ref> LML is a new approach to analyzing, planning, specifying, designing, building and maintaining modern systems.

LML focuses on these 6 goals:

1. To be easy to understand

Line 19 ⟶ 20:

== History ==

The LML Steering Committee was formed in February 2013 to review a proposed draft ontology and set of diagrams that forms the LML specification. Contributors from many academic and commercial organizations provided direct input into the specification, resulting in its publication in October 2013. Presentations and tutorials were given at the National Defense Industrial Association (NDIA) Systems Engineering Conference (October 2013) and the Systems Engineering in DC (SEDC) in April 2014.

A predecessor to LML was developed by Dr. Steven H. Dam, SPEC Innovations, as part of a methodology called Knowledge-Based Analysis and Design (KBAD). The ontology portion was prototyping in a systems engineering database tool. Ideas on how to better implement it and the development of key LML diagrams (Action and Asset) were part of their Innoslate product development from 2009 to present. <ref>{{cite web| url = http://www.slideshare.net/ElizabethSteiner/knowledgebased-analysis-and-design-kbad-an-approach-to-rapid-systems-engineering-for-the-lifecycle | title = Knowledge-Based Analysis and Design (KBAD): An Approach to Rapid Systems Engineering for the Lifecycle | accessdate=2010-10-17}}</ref>

== Ontology ==

Ontologies provide a set of defined terms and relationships between the terms to capture the information that describes the physical, functional, performance, and programmatic aspects of the system.

Common ways for describing such ontologies are "Entity", "Relationship", and "Attribute" (ERA). ERA is often used to define database schemas. LML extends the ERA schema with "Attributes on Relationship", a feature that can reduce the number of required "Relationships", in the same way that "Attribute" reduce the number of required "Entities" in ERA.

In alignment with the first goal of LML, "Entity", "Relationship", "Attribute", and "Attribute on Relationship" have equivalent English language elements: [[noun]], [[verb]], [[adjective]] and [[adverb]]. <ref name="specification"/>

'''Entity (noun)'''

Line 43 ⟶ 44:

== List of LML Tools ==

As of right now, Innoslate is the only model-based systems engineering tool with LML available on the market. Innoslate implements LML and enables translation to [UML], [SysML], [DoDAF] 2.0, and other languages. <ref>{{cite web|url=https://innoslate.com/overview/|title=Overview of Innoslate|accessdate=2014-06-05}}</ref>

==See also==