April 4, 1999 - Jack Harich - Go Back
| Here we use the BA Requirements to create a High Level Model and Implementation Plan. These can then be used for jcon package reorganization, kernel improvement and creating the second generation of visual tools. |
High Level Model
This proceeds directly from the Use Cases, with a nod to everything else. For convenience we reproduce the Use Case List here:
|
No. |
User's Goal |
Done by Subsystem |
|
1 |
Run a system | Kernel, aka System Engine |
|
2 |
Start BA, navigate to any tool or main command | BA Main Menu (better name?) |
|
3 |
Understand, navigate, manipulate a system's structure | System Tree |
|
4 |
Understand, edit a System Tree container | Container Editor |
|
5 |
Understand, edit a part's DK | DK Editor, varies per part type |
|
6 |
Get parts to add to the System Tree | Part Shop |
|
7 |
Get frameworks to add to the System Tree | Part Shop, possibly Frame Shop |
|
8 |
Understand and manipulate a part directly | Inspector |
|
9 |
Understand how to do something | User Education (1) |
|
10 |
Get assistance to do something complex | Wizard, various |
(incomplete)
Implementation Plan
(discuss strategy, phases, work units, etc)
(incomplete)
(to be continued)