Specification

Lifecycle Modeling Language Specification (version 1.2)


LML Specification - Official Version

This file contains the current, official, version controlled specification for LML. The specification is broken up into 4 parts: specification information, overview of LML, the ontology, and visualizations. Modifications to this specification can be submitted to the LML Steering Committee.

LML Specification 1.2


LML Specification – Relationship Matrix

This file contains the current version of the LML Relationship Matrix. This matrix provides a visual way of seeing how LML entities relate to other entities. The entities are along the side and top and the connecting relations are in the middle. This matrix shows both parent and children entities, with relations specific to children in parentheses.

LML Relationships Specification 1.1


LML Specification – Ontology File

This XML file contains the ontology-portion of the LML specification for use in any tools. As an open standard, this specification is royalty-free. We appreciate the sharing of any modifications to this ontology and will make them available to other interested parties.

LML Ontology File


LML Charter

A standard Lifecycle Modeling Language (LML) will provide organizations a structured and behavioral language that will provide a simple way to understand and communicate cost, schedule and performance design information to all stakeholders in a standard manner. The combination of a simple structure with appropriate graphical visualizations for every entity class will facilitate the understanding of design for all stakeholders throughout the product lifecycle (concept through disposal). This language will reduce the cost of design and enable more rapid product development to better match information technology and other technical product development timelines.

LML Steering Committee Charter

The LML Steering Committee provides overall governance for the Lifecycle Modeling Language Specification. They will evaluate suggested changes and extensions to the specification to ensure they meet the overall objectives for the language.

LML Steering Committee Objectives

  1. Provide governance to the development of the Lifecycle Modeling Language (LML) specification to meet the charter goals.
  2. Engage various communities across the lifecycle (e.g., systems engineering, design engineering, test engineering, operations and support, and program management) in dialog on the use and benefits of LM, receive feedback on LML’s utility, and document requirements from the communities.
  3. Foster the evolution of LML into a recognized standard.

Draft Problem Statement (what LML is trying to solve)

Complexity is a major issue. With the growth of the Internet and daily changes in Information Technology, systems have become more complex and change more rapid than ever before. Cloud computing gives us new tools to deal with these larger systems. Systems engineering methods have not kept up with these changes. Larger, more complex systems development implies: a need for larger, distributed teams; a need for a clear concise way to express the system design (clear, logically consistent semantics); and new tools to enable collaboration across the entire lifecycle.