A scenario outlines the order of the events and operations that a tool will expect to perform and have performed. For example, the following scenario outlines the events that the ToolTalk demo program CoEd expects to perform and have performed:
User double-clicks on a document icon in the File Manager.
The file opens in the editor, which is started by the system if one is not already running.
If another tool has modifications to the text pending for the document, User is asked whether the other tool should save the text changes or revert to the last saved version of the document.
User inserts text.
User saves the document.
If another tool has modifications pending for the document, User is asked whether to modify the document.
User exits the editor.
If text has unsaved changes, User is asked whether to save or discard the changes before quitting the file.
Once the scenario is done, you can answer your basic questions.
The File Manager will request that CoEd open a document for editing.
Each instance of CoEd will notify other interested instances of changes it makes to the state of the document.
Each instance of CoEd can answer questions about itself and its state, such as "What is your status?"
Each instance of CoEd has the capability of performing operations such as:
Iconifying and de-iconifying
Raising to front and lowering to back
Editing a document
Displaying a document
Quitting
The File Manager must request that CoEd open a document for editing.
An instance of CoEd can ask another instance of CoEd to save changes to the open document.
An instance of CoEd can ask another instance of CoEd to revert to the last saved version of the open document.
The document has been opened.
The document has been modified.
The document has been reverted to last saved version.
The document has been saved.
An instance of CoEd has been exited.
The document has been opened.
The document has been modified.
The document has been reverted to last saved version.
The document has been saved.
An instance of CoEd has been exited.