Lifecycle Modeling Language: Difference between revisions

Content deleted Content added
MertyWiki (talk | contribs)
m URL to spec pointed to non-existing place. Updated to page with 1.3 specifications
m link systems thinking
 
Line 7:
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">{{cite conference |author=Steven Dam |author2=Warren Vaneman |url=https://www.slideshare.net/ElizabethSteiner/lifecycle-modeling-language-tutorial-by-dr-dam-and-dr-vaneman |title=Lifecycle Modeling Language Tutorial |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.