Here is an excerpt from
Wayne't blog regarding scope statements. The entire blog
post can be found here: https://waynebeaton.wordpress.com/2019/04/08/specification-scope-in-jakarta-ee/
Ivar
Regarding scope, the
EFSP states:
Among other
things, the Scope of a Specification Project is intended
to inform companies and individuals so they can determine
whether or not to contribute to the Specification. Since a
change in Scope may change the nature of the contribution
to the project, a change to a Specification Project’s
Scope must be approved by a Super-majority of the
Specification Committee.
As a general rule, a
scope statement should not be too precise. Rather, it should
describe the intention of the specification in broad terms.
Think of the scope statement as an executive summary or
“elevator pitch”.
Elevator pitch:
You have fifteen seconds before the elevator doors open on
your floor; tell me about the problem your specification
addresses.
The
scope statement must answer the question: what does an
implementation of this specification do? The scope
statement must be aspirational rather than attempt to
capture any particular state at any particular
point-in-time. A scope statement must not focus on the work
planned for any particular version of the specification, but
rather, define the problem space that the specification is
intended to address.
For example:
Jakarta Batch
provides describes a means for executing and managing
batch processes in Jakarta EE applications.
and:
Jakarta Message
Service describes a means for Jakarta EE applications to
create, send, and receive messages via loosely coupled,
reliable asynchronous communication services.
For the scope statement,
you can assume that the reader has a rudimentary
understanding of the field. It’s reasonable, for example, to
expect the reader to understand what “batch processing”
means.