What Makes a Good System Element?
General
The System Element is the final record of an idea created as an
integral part of the system. As such, it contains everything necessary
to communicate its qualities to the development teams to follow
the planning process. It is similar to the Solution Element, and
can use parts of a Solution Element's information, but it substantially
extends that document's descriptive material to at least two pages
(and often more). Well done, it leaves nothing to be guessed about
the nature of the concept.
Originator, Contributors and Dates
Names and dates must accurately reflect the development of the System
Element's content, and the last date should agree with the version
date at the bottom of the form. The Date of First Version at the
bottom of the form should be the date when the form was originated.
Status
A check in the appropriate box should be made to indicate whether
the System Element already exists E, has been modified from
an existing source M, or is speculative (wholly new) S.
If it exists or has been modified from an existing entity, the source
should be given (see below).
Source
Necessary only for Existing or Modified System Elements, the Source
identifies manufacturer, author and document or other original producer
of the idea. If the source is a company or organization, its name,
address and (if possible) telephone number or web site should be
listed. If the source is an author, a complete bibliographic entry
should be given as for Source/s listed on Defining Statements and
Design Factors. As a general rule, Source information should include
everything necessary to find the existing material.
Superset Elements
Where System Elements can be organized hierarchically as components
of one another, this is a useful organizational tool. Listing of
a Superset Element for a System Element expresses that relationship
for the next level up.
Subset Elements
The Subset Element listing also contributes to the establishment
of structure in the organization of the System Elements. Subset
Elements are those which are components of the System Element described.
Related Elements
The Related Elements section performs the same organizational function
as Superset and Subset sections, but extends that service to a navigational
aid. In terms of organization, other System Elements should be listed
here that are part of any Superset listed. For navigation, other
elements should be listed that are not so closely associated that
they are in the same Superset, but are associated in that
they should be "considered next" in any attempt to understand the
system.
Description
The Description should be general. In the Properties and Features
sections, specific aspects of the idea can be developed in enough
detail to take care of specific questions about what it is or what
it does. A good format for Description begins with a nominative
clause that would finish a sentence beginning "X is _", e.g.,
A probe able to sense temperature and consistency of food, coupled
with... This may be sufficient. If not, another clause or sentence
may be added, but the whole description should not require more
than four or five lines. If the System Element is derived from an
earlier Solution Element, the Description may be identical or appropriately
modified to reflect the derivation.
Properties
Properties are what it is. In this section short phrases
are used to single out components of the concept and their characteristics.
The purpose is to highlight what must be designed, assembled or
integrated to bring the concept into being. When writing Properties,
the planner should think of how an engineering department would
react to them-Properties are prescriptions for what must be produced.
Along with Features, these are the "specification" for follow-on
development. The final produced version of the system must at least
have these characteristics.
In form, Properties should be described with bullet noun
phrases. Short in length, direct and well-suited to eliciting images,
bullet noun descriptions fit significant detail into a small space.
Features
Features are what it does. Like Properties, Features are
described with short phrases. Unlike Properties, the phrases should
be bullet verb phrases because Features are operational descriptions.
The verb phrase is better for describing what the concept is intended
to do in operation.
To tie Features and Properties together, a parenthetical reference
should be included at the end of a Feature giving the title of the
particular Property or Properties responsible for the Feature. If
no reference is present, the assumption is that the Feature is one
operational characteristic of the System Element as a whole.
Fulfilled Functions
Fulfilled Functions are those which the System Element fulfills
wholly or in part. When the System Element is derived directly from
a Solution Element (without change), these Functions can be listed
from the interaction matrix or the original input to the RELATN
computer runs. If the System Element was modified during the Synthesis
process or developed then as a wholly new idea, it must be checked
against the entire Function list to establish which (besides those
it was developed for) it fulfills. Functions should be listed by
number and title.
Associated Design Factors
As Fulfilled Functions do, Associated Design Factors establish links
between the System Element and those Design Factors with insights
relevant to the development of the ideas expressed in its concept.
As was done for Fulfilled Functions, all Design Factors should be
given a final review to identify which have a bearing on each System
Element's ideas.
Discussion
The primary difference between Solution Elements and System
Elements is this section. The Discussion section allows the planning
team to add as much detail to the description of the System Element
as its members choose. It is a section designed to maximize the
transfer of information without placing restrictions on the development
team using it. In effect, it passes on all the thoughts and specific
ideas the team had during the planning process without requiring
their use.
Two kinds of description should be included:
