Lifecycle Modeling Language: Difference between revisions

Revision as of 19:50, 10 December 2014

Latest revision as of 15:39, 1 June 2024

(6 intermediate revisions by 6 users not shown)

Line 1:

'''The Lifecycle Modeling Language (LML)''' is an open-standard modeling language designed for [[systems engineering]]. It supports the full [[System lifecycle|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=httphttps://www.lifecyclemodeling.org/spec/LML_Specification_1_0.pdfspecification|accessdateaccess-date=20132023-1003-1701}}</ref>

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

TheThis purposeis behinda themodeling language is to replace predecessor languages, such aslike [[Unified Modeling Language|UML]] and [[SysML]] that overcomplicatesupports theadditional systemsproject engineeringmanagement processuses such as risk analysis and scheduling. 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|accessdateaccess-date=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.{{cite conference |author=Steven Dam and Dr. |author2=Warren Vaneman, [http|url=https://www.slideshare.net/ElizabethSteiner/lifecycle-modeling-language-tutorial-by-dr-dam-and-dr-vaneman?utm_content |title=5253617&utm_medium=social&utm_source=twitter "Lifecycle Modeling Language Tutorial"], ''Presentation at |book-title=SEDC 2014'' |date=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 name="slideshare.net"/> LML is a new approach to analyzing, planning, specifying, designing, building and maintaining modern systems.

Line 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 | accessdateaccess-date=2010-10-17}}</ref>

== Ontology ==

Line 28:

'''Entity (noun)'''

An [[wikt:entity|entity]] is defined as something that is uniquely identifiable and can exist by itself. There are only 12 parent entities in LML: Action, Artifact, Asset, Characteristic, Connection, Cost, Decision, Input/Output, Location, Risk, Statement and Time.

Several child entities have been defined to capture information that stakeholders need. The child entities have the attributes and relationships of the parents plus additional attributes and relationships that make them unique. Child entities include: Conduit (child of Connection), Logical (child of Connection), Measure (child of Characteristic), Orbital (child of Location), Physical (child of Location), Requirement (child of Statement), Resource (child of Asset), and Virtual (child of Location).

Every entity has a name or number or description attribute or combination of the three to identify it uniquely. The name is a word or small collection of words providing an overview of information about the entity.

Line 44:

== List of LML Tools ==

- [https://www.innoslate.com* Innoslate] is the model-based systems engineering tool with LML available on the market. Innoslate implements LML and enables translation to [[Unified Modeling Language|UML]], [[SysML]], [[DoDAF]] 2.0, and other languages.<ref>{{cite web|url=https://www.innoslate.com/solutions/|title=Innoslate Integrated Solutions|accessdateaccess-date=2014-12-09}}</ref></br>

- [http://www.3ds.com* 3DExperience platform] is the enterprise software platform that fully supports LML modeling concepts. Particular tool for schema modeling is "Business Modeler" and basic tool for instance modelling based on that schema is "Matrix Navigator". Software is evolution of MatrixOne and Dassault Systemes V6 platform. CAD, CAM, CAE, PDM and other PLM technologies tools are provided based on that platform.

==See also==

{{col-begin}}

{{col-3}}

* [[Formal specification]]

* [[Functional specification]]

Line 57 ⟶ 55:

* [[Specification (technical standard)]]

* [[Specification tree]]

{{col-end}}

==References==