41
Essences of Interaction
will need to be turned. A book that is quite large may weigh too much to
hold or may not facilitate easy handling to support the turning of pages.
One of the functions of the book is to convey information. Should the book
influence the reader through an interaction with the cognitive structures of
the reader’s perspective, the functional boundary of the book extends
beyond the physical limitations of the words on each page. The publisher
and author of the book have used the book (i.e., an object) to promote a form
of learning. The scope of the work of the publisher is determined by the
work that must be done to have the book accepted by the reader. Consistent
with the Project Management Body of Knowledge, systems engineering parlance determines the scope of the book through the project’s WBS (Turner
1993).* Work that is necessary to develop, integrate, and sell a book is the
scope of the project. The scope of the work deals with the project as an
enterprise rather than with the boundaries of the product or service when
put into operations. Scope and boundaries are indeed quite different, but
they are related. The casual definition that the boundary is or in some manner equal to the scope ignores the relation between the product’s or service’s
boundary of operations and the effort that result in providing the user with
a product or service.
Scope can be managed, whereas boundaries exist because of the design
and use of products and services. When requirements change, scope changes.
When requirements change, boundaries may or may not change. The processes that define a project’s scope include developing a vision for the product or service, a roadmap that shows how the product will evolve over time,
how technologies will mature and be replaced, when various upgrades will
be released, what milestones will be delineated, and how the product or
service criteria will be implemented.
For example, scope considers the contents of a book. When the reader
considers the information gained from the book’s contents and then
integrates that information into their cognitive structures, the book has
been used to convey information. When the reader applies that knowledge
and thereby influences someone else, the boundary of the book has been
extended by behaviors. The boundaries of the book can be said to encompass physical, functional, and behavioral aspects. The physical boundary is
determined by the publisher and enabled by printing, cutting, and binding.
The functional boundary is determined by the book contents and enabled
by the cognitive structures of the reader. The behavioral boundary is determined by the reader and the listener(s). There certainly may be additional
types of boundaries other than physical, functional, and behavioral, but
these three are necessary and sufficient for systems engineering. These
three boundary types capture the objective nature of the product both for
its development and its use. Regardless of the boundaries, the project scope
is defined in terms of procedures and events.
* Referenced in the Project Management Body of Knowledge.
Essences of Interaction
will need to be turned. A book that is quite large may weigh too much to
hold or may not facilitate easy handling to support the turning of pages.
One of the functions of the book is to convey information. Should the book
influence the reader through an interaction with the cognitive structures of
the reader’s perspective, the functional boundary of the book extends
beyond the physical limitations of the words on each page. The publisher
and author of the book have used the book (i.e., an object) to promote a form
of learning. The scope of the work of the publisher is determined by the
work that must be done to have the book accepted by the reader. Consistent
with the Project Management Body of Knowledge, systems engineering parlance determines the scope of the book through the project’s WBS (Turner
1993).* Work that is necessary to develop, integrate, and sell a book is the
scope of the project. The scope of the work deals with the project as an
enterprise rather than with the boundaries of the product or service when
put into operations. Scope and boundaries are indeed quite different, but
they are related. The casual definition that the boundary is or in some manner equal to the scope ignores the relation between the product’s or service’s
boundary of operations and the effort that result in providing the user with
a product or service.
Scope can be managed, whereas boundaries exist because of the design
and use of products and services. When requirements change, scope changes.
When requirements change, boundaries may or may not change. The processes that define a project’s scope include developing a vision for the product or service, a roadmap that shows how the product will evolve over time,
how technologies will mature and be replaced, when various upgrades will
be released, what milestones will be delineated, and how the product or
service criteria will be implemented.
For example, scope considers the contents of a book. When the reader
considers the information gained from the book’s contents and then
integrates that information into their cognitive structures, the book has
been used to convey information. When the reader applies that knowledge
and thereby influences someone else, the boundary of the book has been
extended by behaviors. The boundaries of the book can be said to encompass physical, functional, and behavioral aspects. The physical boundary is
determined by the publisher and enabled by printing, cutting, and binding.
The functional boundary is determined by the book contents and enabled
by the cognitive structures of the reader. The behavioral boundary is determined by the reader and the listener(s). There certainly may be additional
types of boundaries other than physical, functional, and behavioral, but
these three are necessary and sufficient for systems engineering. These
three boundary types capture the objective nature of the product both for
its development and its use. Regardless of the boundaries, the project scope
is defined in terms of procedures and events.
* Referenced in the Project Management Body of Knowledge.