We live in a time period where information technology grows on a daily basis. Budgets and schedules have become more constrained. Systems have become even more complex. Complexity is a major issue for systems engineers. We are approaching an even more challenging future. System designs need to deal with this complexity.
Systems engineers need to use languages that are:
- Easy to understand
- Easy to extend
- Supporting both functional and object-oriented approaches
- Useful for both systems engineers and the other stakeholders across the system lifecycle
- Supporting system development processes from concept to disposal.
The goal of Lifecycle Modeling Language (LML) is to meet all five of those needs in one modeling language.
Easy to understand
If complexity is a major issue for systems engineers, then why do current systems engineering languages tend to add complexity to already complex problems? These current systems engineering languages make it more difficult to communicate the underlying issues and develop effective solutions.
The first priority in setting goals for LML was to create a simpler language that could be easy to understand through all the stages of the lifecycle.
The LML authors wanted to define a common, simpler language that can be used for information capture, as well as modeling and simulation, of all stages of the lifecycle. LML provides an easy to understand ontology, yet robust enough to use clear diagrams to express the system design information.
Easy to extend
A benefit to LML that was lacking in previous systems engineering languages is its ability to extend.
Since, LML is designed to be a simple language it becomes more extensible to the entire set of lifecycle stakeholders. LML supports the needs of a specific customer, organization, and/or project in any lifecycle discipline.
All lifecycle disciplines can use LML, including systems and design engineering, program management, and one more. LML also allows you to test and evaluate data into a single framework. As we all know, communication is critical for systems engineers. LML allows for easy communication across many different disciplines.
If you would like to know more about the process for extension submission, then visit lifecyclemodeling.org.
Supporting both functional and object-oriented approaches
A systems engineering language that supports both functional and object-oriented approaches is something systems engineers have needed for a long time. LML has an elements correspondence that allows for both functional and object-oriented approaches to work within the same design.
LML can translate to object languages, such as UML / SysML. The LML formulation uses the (ERA) meta-meta model; entity, relationship, and attribute. These language elements correspond to object language elements; classes (entity), relations (relationship), and properties (attribute).
Useful for both systems engineers and the other stakeholders across the system lifecycle
Current systems engineering languages do not allow for easy interaction with systems engineers and other critical groups (program managers, enterprise architects, etc.) on all stages of the system lifecycle. The need for this interaction has been growing with the changes to information technology.
The program manager is primarily concerned with cost, schedule, tasks, resources, and risks. Enterprise architects capture their information using the “5WH” model (What, Why, When, Where, Who, and How). The systems engineer’s goal is to optimize cost, schedule, and performance (form, fit, function). LML overlaps the program manager’s, the enterprise architect’s, and the systems engineer’s concerns and goals and incorporates them into one comprehensive set of design elements.
The table below shows you how LML does just this.
Systems Engineering Architecture Program Management Lifecycle Modeling Language Cost (How much) Cost Cost Schedule When Schedule Time/Action Performance Form Who Organization Asset What Resource Resource Where Location Location Why Goal, Objectives, Decisions Decision & Statement / Requirement Function How Task Action Metric(Fit) Metric Characteristic / Measure Interface Connection (Conduit) & Input / Output Risk Risk Risk Artifact Artifact
Supporting system development processes from concept to disposal.
The final goal LML accomplishes is the ability to support system development processes from the concept development phase to the final disposal of the systems. LML gives you the ability to complete a full lifecycle across many different disciplines and stakeholders. Through accomplishing the first four goals, LML can support the full lifecycle. Without the ability to support function and object approaches, interact with systems engineer and critical groups through the lifecycle, and easy to understand / extend LML would not be able to completely support the lifecycle.
Today’s technology is moving so fast, but sometimes our methods do not move with it. LML seeks to meet the needs of today’s systems engineers. Current systems engineers require a language that allows them to communicate with other lifecycle stakeholders, while completing a full lifecycle. LML does simply just that.
Many MBSE tools have made their languages privatized. LML was designed to be an open standard, for anyone to use. Though LML has not become a common systems engineering language yet, hopefully more systems engineers will realize the benefit to using LML.
What do you think of the Lifecycle Modeling Language? Do you think it meets current systems engineer’s needs?