ESSENCE — Inconsistency of definitions for Bounded/Scoped requirements Alpha State.

Issue 176 has a proposed resolution to change the name of the Bounded Requirements alpha state to Scoped.

However there is still a need to change the definition to better reflect the checklist and the concept of scoping with respect to its making the extent of the system clear.

We need to have a high level definition which captures the concept of clear extent and purpose.

the current definition in 8.2.3.1 does not capture the extent concept of scoping or boundedness properly.

"Bounded: The purpose and theme of the new system are clear."

Also, if you look at clause 9.8.3 in the examples of the textual notation there is a another definition which is different than the one in the alpha section, but it uses the "extent" concept

"state Bounded

This is adds extent concept but keeps the "theme" concept.

The concept of "theme" seems too loose for a proper definition.

Proposed Resolution

I suggest that we resolve this issue by replacing the definition in
8.2.3.1 and in 9.2.3 for the new
named state "Scoped" with the following:

"Scoped: The purpose and extent of the new system are clear"

Updated the definition of the Bounded state as suggested (independent of the resolution to Issue 176). (Note, however, that the subclause references given in the issue description are incorrect. They should be 8.3.2.1 and 9.8.3.)