ESSENCE2 — Update definitions for the area of concerns

Issues

The following text is too informal, uses the passive voice, and uses the past tense.

• https://issues.omg.org/browse/ESSENCE2-2 - Passive Voice
• https://issues.omg.org/browse/ESSENCE2-3 - Present Tense
• https://issues.omg.org/browse/ESSENCE2-5 - Streamline text

Original Text

The Kernel is organized into three discrete areas of concern, each focusing on a specific aspect of engineering. As shown in Figure Error: Reference source not found.2, these are:

• Customer - This area of concern contains everything to do with the actual use and exploitation of the system to be produced.
• Solution - This area of concern contains everything to do the specification and development of the system.
• Endeavor - This area of concern contains everything to do with the team, and the way that they approach their work.

<FIGURE HERE>

Throughout the diagrams in the body of the kernel specification, the three areas of concern are distinguished with different color codes where green stands for customer, yellow for solution, and blue for endeavor. The colors will facilitate the understanding and tracking of which area of concern owns which Alphas and Activity Spaces. We have also added textual labels so the reader need not rely totally on the color codes.

Suggestion

The Kernel is organized into three discrete areas of concern, each focusing on a specific engineering aspect, as seen in Figure 8.2. These areas of concern are:

• Customer: Encompasses everything related to the actual use and exploitation of the system to be produced.
• Solution: Covers everything regarding the specification and development of the system.
• Endeavor: Includes everything concerning the team and how they approach their work.

<FIGURE HERE>

Throughout the diagrams in the body of the kernel specification, the three areas of concern are distinguishable with different color codes: green for customer, yellow for solution, and blue for endeavor. These colors aid in understanding and tracking which area of concern owned which Alphas and Activity Spaces. We also add textual labels so the reader does not rely solely on the color codes.

Close

Generic writing guidelines are not necessarily applicable to the writing of specification documents. Nor does the seeming violation of such guidelines necessarily mean that any specific text is unclear as already written. All text in the specification was reviewed and adopted as is with specific technical interpretation. Any changes to the text for purely stylistic reasons must therefore be done with extreme care, followed by a full review, to ensure that such changes do not alter the interpretation of the text as it was adopted. This would require a considerable level of effort for a possible minor gain in presentation, which itself is likely to be subjective. Therefore, the FTF has chosen not to make such changes to the text for purely stylistic reasons.