Sample Solution Scenario
Example Solution Scenario
(this heading is not required in actual structured scenarios)
Use Case #42: User_loads_Text Comment by NAME : These are taken directly from the RTM entry for the use case
Requirement: Comment by NAME : The text from requirement column of RTM
The user shall be able to load tab-delimited text files.
Overview: Comment by NAME : Provide a description of what is happening in use case
The use loads a tab-delimited text file into the system, and may then choose to sort the data by the first column or send the spreadsheet to a printer.
Preconditions: Comment by NAME : List numerically the assumptions required before this Use Case can be executed. In this case there are none; all possible erroneous conditions are detailed under Exceptions
none
Scenario:
Action Comment by NAME : Specify an action
Software Reaction Comment by NAME : Describe the software reaction (not all of which will may be visible or obvious to the user)
1. User clicks Open Text File toolbar icon
1. Display Open File View as modal dialog box.
2. User selects file in Open File View and clicks OK
1. Read file contents using text file parser.
2. Split lines into separate cell contents and load into spreadsheet model.
3. Update Main Spreadsheet View.
3. Use clicks Cancel in Open File View
1. none
4. Use clicks Sort By First Column toolbar icon
1. Determine data type in first column: numerical or text.
2. Reorder spreadsheet model using either numerical or lexicographic order.
3. Update Main Spreadsheet View.
5. User clicks Print
1. Determine default printer.
2. Create postscript description of printed page from spreadsheet model.
3. Send postscript data to printer.
Scenario Notes: Comment by NAME : Indicate the currency of Actions, any additional information, such as optional steps and branching and iteration steps
The typical path is actions 1 then 2. Action 3 exits the use case. If there are any errors loading and parsing the text file then the use case ends. After Action 2 the user can perform any combination of Actions 4 and 5.
Post Conditions Comment by NAME : List the conditions expected at the completion of the scenario.
1. Contents of selected file displayed in Main Spreadsheet View
Required Views: (GUIs) Comment by NAME : List the names of the Views (GUIs) utilised by this scenario. This is difficult in this case because we have so little information in the RTM excerpt, so these are just invented examples.
Open File View
Main Spreadsheet View
Toolbar View
Exceptions: Comment by NAME : List sequentially any failure conditions that can affect the Scenarios, and how the system should respond.
1. Text file is locked by another program; inform user and ask them to close the other program or try again later
2. Text file is corrupted or damaged and cannot be parsed; inform user
3. Data in first column cannot be sorted due to mixture of data types; inform user
4. Cannot connect to printer; inform user and ask them to check the connection
Use Cases utilised Comment by NAME : List other Use Cases used. Again, in this case we have to imagine what other ones might be used; sorting and printing would probably be use cases in their own right
None in this imaginary example, but in a real spreadsheet program sorting and printing would be their own uses cases, as might be opening a file (of any sort)