ESSENCE2 — Streamline and Simplify Language in What is a Kernel

Issues

The following text is repetitive, uses the passive voice, uses the past tense and personal pronouns.

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

Original Text

The kernel is a stripped-down, light-weight set of definitions that captures the essence of effective, scalable engineering in a practice independent way.
The focus of the kernel is to define a common basis for the definition of engineering practices, one that allows them to be defined and applied independently. The practices can then be mixed and matched to create specific engineering methods tailored to the specific needs of a specific engineering community, project, team, or organization. The kernel has many benefits including:

• Allowing you to apply as few or as many practices as you like.
• Allowing you to easily capture your current practices in a reusable and extendable way.
• Allowing you to evaluate your current practices against a technique neutral control framework.
• Allowing you to align and compare your on-going work and methods to a common, technique neutral framework, and then to complement it with any missing critical practices or process elements.
• Allowing you to start with a minimal method adding practices as the endeavor progresses and when you need them.

Suggestion

The kernel is a stripped-down, lightweight set of definitions that captures the essence of effective, scalable engineering in a practice-independent way. Its focus is on defining a common basis for the definition of engineering practices, allowing them to be defined and applied independently. These practices can then be mixed and matched to create specific engineering methods tailored to the needs of a particular engineering community, project, team, or organization.

The kernel offers numerous benefits, including:

• Flexibility in Practice Application: Allows the application of as few or as many practices as needed.
• Capture of Current Practices: Facilitates the easy capture of current practices in a reusable and extendable manner.
• Evaluation Against a Neutral Framework: Enables evaluation of current practices against a technique-neutral control framework.
• Alignment and Comparison: Allows alignment and comparison of ongoing work and methods to a common, technique-neutral framework, complementing it with any missing critical practices or process elements.
• Incremental Method Development: Supports starting with a minimal method and adding practices as the endeavor progresses and as needed.

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.