Final
Report
Earlier
Proposals
Tree
Summary
PROJECT SUMMARY
name
of project
subproject
info
number
of subprojects
names
of subprojects
alphabet
info
number
of alphabets
names
of alphabets
property
info
number
of properties
names
of properties
event
info
number
of events
names
of events
most
common behavior in Project
comments
ALPHABET SUMMARY
name
of alphabet
project
name
property
info
number
of properties
names
of properties
event
info
number
of events
names
of events
* alert
if there are unused events
most
common behavior in Alphabet
comments
PROPERTY SUMMARY
name
of property
project
name
alphabet
name
event
info
number
of events
names
of events
behavior
info
behavior
name
action
event
response
event
...
scope
info
scope
name
start
event
end
event
comments
EVENT SUMMARY
name
of event
project
name
alpabet
name
property
names
definition
subtypes
* alert
if event is unused
comments
Table Summary
The events that are
highlighted black are unused events.
They exist within an alphabet, but they dont belong to any properties.
|
Project Summary |
|||||
|
Name |
Subprojects |
Alphabets |
Properties |
Events |
Comments |
|
Testing |
0 |
3 |
3 |
10 |
This
is where comments on the entire project would be put. The user may summarize the project in the
broadest way here. |
|
|
|
Errors |
|
push_ok |
|
|
|
|
error_display |
error_display |
||
|
|
|
ok_button |
|||
|
|
|
Elevator |
floor_arrival |
called@floor |
|
|
|
|
arrive@floor |
|||
|
|
|
second_arrival |
|||
|
|
|
elevator_stop |
|||
|
|
|
Queues |
empty |
enqueue |
|
|
|
|
empty |
|||
|
|
|
dequeue |
|||
|
Alphabet Summary |
|||
|
Name |
Properties |
Events |
Comments |
|
Errors |
1 |
2 |
This
is where the user's comments on individual alphabets would go. |
|
error_display |
error_display ok_button |
||
|
|
push_ok |
||
|
Elevator |
1 |
4 |
It's
a more specific level, but it's still broader than the property comments. |
|
floor_arrival |
called@floor arrive@floor second_arrival elevator_stop |
||
|
Queue |
1 |
3 |
|
|
empty |
enqueue empty dequeue |
||
|
Property Summary |
|||
|
Name |
Behavior |
Scope |
Comments |
|
error_display |
RESPONSE action:
error_display response:
ok_button |
GLOBAL |
Here
is where the comments on properties would go. |
|
floor_arrival |
RESPONSE action:
second_arrival response:
elevator_stop |
BETWEEN start:
called@floor end:
arrive@floor |
It's
much more specific, but still not as specific as glossary comments |
|
empty |
EXISTENSE action:
dequeue |
BETWEEN start:
enqueue end:
empty |
|
|
Glossary Of Events |
|||||
|
Name |
Definition |
Subtypes |
Property |
Alphabet |
Comments |
|
push_ok |
|
|
|
Errors |
This
is where |
|
error_display |
|
|
error_display |
Errors |
comments
on |
|
ok_button |
|
|
error_display |
Errors |
individual
events |
|
called@floor |
|
|
floor_arrival |
Elevator |
would
be made. |
|
arrive@floor |
|
|
floor_arrival |
Elevator |
They
should probably |
|
second_arrival |
|
|
floor_arrival |
Elevator |
be
short and sweet |
|
elevator_stop |
|
|
floor_arrival |
Elevator |
so
they don't take up |
|
enqueue |
|
|
Empty |
Queue |
too
much room and |
|
empty |
|
|
Empty |
Queue |
are
easy to read. |
|
dequeue |
|
|
Empty |
Queue |
|
Here is the website of LASER, the lab where I worked: