ESL0008 - Documentation comment tags¶

LEP	ESL0008
Author(s)	Wilschut
Reviewer(s)	T.J.L. Schuijbroek
Status	Draft
Type	Standard (S)
Created	23-08-2021
Finalized	t.b.d.

Abstract¶

In this LEP it is proposed to introduce a lightweight syntax to explicitly tag documentation comments. This omits the need for a user to post-process documentation comments to extract information with respect to a certain topic. For example, information regarding design-decisions, stakeholders, and verification and validation methods.

Motivation¶

In general, the systems engineering literature, such as the NASA Systems engineering Handbook [Kap16], advocates the importance of annotating specification elements with information such as an owner, stakeholders, verification method, validation method, and rational in support of efficient requirement and stakeholder management.

Currently, an ESL-user has to resort to placing such information within the ESL doc-comment section and post-processing the text with a custom script to extract information with respect to certain topics. This route is being used by several active users of ESL.

However, it is desirable to support this natively to increase the user-friendliness and functionality of ESL in support of the overall Systems Engineering process.

Rationale¶

It is proposed to introduce a lightweight syntax to explicitly tag documentation comments for several reasons.

First of all, the systems engineering literature presents a create variety of (meta) information that is being attached to elements of system specifications, such as requirements, constraints, and components. Moreover, the same information is often referred to using different terminology. For example, some may use the term ‘project actor’ while others use ‘project stakeholder’ to refer to organizations, departments or people that are involved within a design project. As a consequence, the literature presents a create variety in ontologies that are used to characterize the information that is contained within system specifications.

Secondly, the primary goal of ESL is to create a structured system specification from which system architecture models can be derived automatically. It is not meant as a means to create a full formally defined dependency network between all bits of information that are used throughout the systems engineering process.

Third of all, it is preferred to keep the number of language elements as small as possible to ensure ESL will remain an easy to learn and easy to use language.

Therefore, it is proposed to not consider the tags as being elements part of the specification that need to be (formally) defined, but rather consider them as keys for making sense of the documentation comments that are attached to a specification element. As a consequence, it is the responsibility of the user to ensure the consistent usage of tags throughout the specification. At this time, we are willing to accept that cost to the benefit of flexibility and ease of use.

Listing 7 shows an example specification in which the documentation tags rationale, stakeholders, and expertise are used. The @ symbol is used to indicate that the following word should be considered as being a tag. These tags allow for easy filtering on the reasoning behind the goal requirement, the people that are involved in stating the requirement, and the expertise needed to implement the requirement.

Note that the tags are optional and that one can use the same tag multiple times. All comments attached to a specification element tagged with the same tag will be stored within a dictionary stored within the esl_info property of the ragraph.generic.Annotations object of the respective ragraph.node.Node object within the output ragraph.graph.Graph.

Listing 7 Example 1 🔗 File¶

define verb
  provide to

world
  variable
    power is a real

  component
    power-supply is a PowerSupply
    drive-mechanism is a ElectricalDriveMechanism

  goal-requirement
    provide-power: power-supply must provide power to drive-mechanism

  comments
    provide-power #< Regular comment
                  #< @rationale Explanation of the 'why' of this requirement.
                  #< @rationale More explanation of the 'why' of this requirement.
                  #< @stakeholders Those who require this goal.
                  #< @expertise The expertise you need to implement this goal.

define component PowerSupply
  empty

define component ElectricalDriveMechanism
  empty

Specification¶

Listing 8 shows the updated EBNF specification of the comment section syntax in which the optional tag is added. A tag can be added to inline documentation comments as well.

Listing 8 EBNF specification of comment section syntax.¶

comment-section ::=
"comment"
 { target-name "#<" ["@"TAG-NAME] { WORD } \n }+

target-name ::=
   argument-name
 | COMPONENT-NAME
 | NEED-NAME
 | GOAL-NAME
 | TRANSFORMATION-NAME
 | RELATION-NAME

Backwards Compatibility¶

As the documentation tags are optional no backwards compatibility issues are expected.

Proof of concept¶

The tagged comments are stored within the esl_info property of the annotations property of the ragraph.node.Node objects within the output ragraph.graph.Graph.

Listing 9 show the esl_info dictionary of node world.provide-power generated based on Listing 7. From this dictionary one can easily retrieve the information tagged with rationale, stakeholders and expertise using the "tagged_comments" key. Regular (untagged) comments are stored in esl_info["comments"]

Listing 9 The esl_info dictionary attached to the provide-power goal requirement. 🔗 File¶

{
    "sub_kind": "goal",
    "form": "requirement",
    "body": {
        "active": "world.power-supply",
        "auxiliary": "must",
        "verb": "provide",
        "variables": [
            "world.power"
        ],
        "preposition": "to",
        "passive": "world.drive-mechanism",
        "subclauses": []
    },
    "comments": [
        "Regular comment"
    ],
    "tagged_comments": {
        "rationale": [
            "Explanation of the 'why' of this requirement.",
            "More explanation of the 'why' of this requirement."
        ],
        "stakeholders": [
            "Those who require this goal."
        ],
        "expertise": [
            "The expertise you need to implement this goal."
        ]
    }
}

If one converts the ESL specification into a PDF document one can find the tags as bold headings within the requirement table of goal world.provide-power. As such, one can enrich the output document with as much information as one would like.

Rejected Ideas¶

The following ideas were rejected:

Enforcing the the user to define all allowed tags within a separate define comment-tag section. For now, we preferred ease of usage and ease of implementation above rigorousness. At some point in the future we might reconsider this decision. However, we first want to gain some experience in how this functionality will be used in practice.

Open Issues¶

No open issues were identified.

Copyright¶

ESL0007 - Function traceability Language Enhancement Proposals Reference