| 1.1. |
Requirements
for the user interface |
|
1.1.1. |
More
like MS Word |
|
1.1.2. |
Consistency
across releases |
|
1.1.3. |
User
interface objects should always stay in the same place |
|
|
1.1.3.1. |
Icons
should be consistent from release to release |
|
|
1.1.3.2. |
Icons
should stay put |
|
1.1.4. |
For
casual users, entry through plain English language is indispensable: |
|
|
1.1.4.1. |
Type
in a word or phrase that indicates what you want to do |
|
|
1.1.4.2. |
System
should prompt you through doing it |
|
1.1.5. |
Clean,
simple screen drill down to detail |
|
1.1.6. |
Common
sequencing through commands |
|
1.1.7. |
Screen
color should default to white, like mylar or vellum, but be
customizable |
| |
|
| 1.2. |
Requirements
for training and learning curve |
|
1.2.1. |
Short
or nonexistent learning curve |
|
1.2.2. |
Learn
it once |
|
|
1.2.2.1. |
New
releases should have new features |
|
|
1.2.2.2. |
New
releases should not change the user interface to old commands |
|
|
1.2.2.3. |
New
releases should not change the functionality of old commands |
|
1.2.3. |
Training
on demand |
|
|
1.2.3.1. |
Availability
of computer-based instruction to learn more about what the
system can do |
|
|
1.2.3.2. |
Available
anytime, from anyplace -- just-in-time training |
|
1.2.4. |
The
system should be fun to play with, to encourage users to experiment
and develop advanced skills |
| |
|
| 1.3. |
Requirement
to accommodate building professionals in all roles |
|
1.3.1. |
Ability
to examine the model from any view |
|
|
1.3.1.1. |
3D |
|
|
1.3.1.2. |
Plan |
|
|
1.3.1.3. |
Section |
|
|
1.3.1.4. |
Elevation |
|
|
1.3.1.5. |
Schedule |
|
|
1.3.1.6. |
Quantity
take-off |
|
1.3.2. |
Ability
to change the model from any view that makes sense to the user
and have that change automatically propagated through all representations
of the model |
| |
|
| 1.4. |
Requirements
for customizing the application |
|
1.4.1. |
The
system must be easily customizable, through a simple technique
like a macro language |
|
1.4.2. |
The
library of design components must be easily expandable: the
software must permit the creation of new parametric building
elements by end users, without programming |