LML Specification 1.2 Update

Last year the LML Steering Committee saw a lot of interest in ontologies and decided to develop a set of updates to the LML standard, which had not been changed since 2015. These updates will focus on extensions of the language to support new domains in systems engineering and program management. As such, they will be developed as Appendices to the LML 1.1 standard. The first of these to be released was LML Specification 1.2. It was released in March 2022. This version added two new appendices: Appendix C. Application to Verification and Validation; and Appendix D. Structuring Artifacts. Appendix C provided 3 new classes: Test Case (or Verification Event), a subclass of the Action class; Test Suite, a subclass of the Artifact class or a type of Artifact; and Verification Requirement, a subclass of Statement. The Test Case attributes include: Expected Result, Actual Result, Status, Setup, Event Conditions, and Event Constraints. The Test Suite is a container for Test Cases, much like the Artifact is a container for Statements and Requirements. The Verification Requirement attributes include: Verification Method (which was a type of Requirement), Acceptance Criteria, Evidence, and Rationale. No new relationships were suggested, only adding new targets to existing relationships. Appendix D provides a single new class: Heading. In this formulation of the LML Documentation Model, The Heading is sourced by an Artifact and contains any other class. This approach becomes useful for large documents and sets of documents that want to reuse information from other classes in multiple documents. The LML Specification 1.2 also contains a number of technical edits to improve the readability of the document. We anticipate a number of additional releases this year, building up to a LML Specification 2.0 next year. LML Steering Committee will review the cumulative suggested enhancements and determine which of those should be part of the updated standard. We expect that a number of the changes will become part of the main LML standard, but that we will have a number of them remaining as appendices, which means they are not required for full LML compliance.