Refining Use Cases User Interface Information Janice Regan 2008 2 Detailed Use Cases Design refine your user interfaces following guidelines given in class and textbook Based on your refined user interfaces add more user interface details to your use cases Update your use cases to inc ID: 233336
Download Presentation The PPT/PDF document "1 High Level Design Phase" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
1
High Level Design Phase
Refining Use Cases
User Interface InformationSlide2
Janice Regan, 2008
2
Detailed Use Cases
Design (refine) your user interfaces following guidelines given in class (and textbook)
Based on your refined user interfaces, add more user interface details to your use cases: Update your use cases to include new User interface informationSlide3
Janice Regan, 2008
3
Check in Resource
Use Case Name :
CheckInResource (Fcn. Req. #7)
Participating actors:
Librarian
Preconditions:
Librarian is a valid librarian
LMS is ready to go (DB has been populated and LMS has been initialized)
Initial Option screen displayed (e.g. see next slide)Slide4
Janice Regan, 2008
4
LMS: Private Mode Screen
Check Resources In
Check Resources Out
Generate interlibrary loan request
Manage online catalogue
Manage patron library numbers
Search online catalogue
Select an operationSlide5
Janice Regan, 2008
5
(cont’d)
Main flow of events:
The use case starts when Librarian selects CheckInResource option.
Librarian enters the Dewey call number for the resource then commits the entry by pressing the accept button
If the Dewey call number for the resource has been entered successfully and it is valid, LMS finds the resource and finds its borrower, then displays the resource information on the screen. Slide6
Janice Regan, 2008
6
LMS: Private Mode Screen
LMS
Check Search Patron Resource
Accept
Finish
Cancel
Enter Patron ID
Enter Resource ID
Title
Author
Call Date
Call Number
Enter Call number
Due Date
Date of Loan
Title
Author
StatusSlide7
Janice Regan, 2008
7
(cont’d)
Main flow of events: (cont)
The DetermineOverdueCharge use case is initiated.
LMS verifies that there is no outstanding request for this resource.
If there are no outstanding request for this resource, LMS changes the status of the resource to "reshelve" and cancels its "due date" and "date of loan" (perhaps updates "date of return").
LMS updates the screen showing the newly checked-in resource along with the updated dates.
The use case terminates when Librarian indicates that she/he is done by pressing the finish button
. Slide8
Janice Regan, 2008
8
(cont’d)
Postconditions:
If the use case was successfully executed:
Patron record updated to reflect the newly checked in resource.
Resource record updated to reflect its checked in status and dates.
Back to initial Option screen. Slide9
Janice Regan, 2008
9
(cont’d)
Exceptional flow of events:
Exceptional flow of events #1
If the Dewey call number was entered incorrectly, LMS states so in a pop up window and the use case terminates.
Exceptional flow of events #2
If the Dewey call number entered is invalid (does not exists in LMS DB), LMS states so in a pop up window and the use case terminates. Slide10
Janice Regan, 2008
10
(cont’d)
Exceptional flow of events:
Exceptional flow of events #3
If there is an outstanding request for this resource, LMS changes the status of the resource to “requested“, cancels its "due date" and "date of loan" (perhaps updates "date of return"), updates the screen showing the new state of the resource.
The librarian presses finish and the use case terminates. Slide11
Janice Regan, 2008
11
Refine the Use Case
Main flow of events:
The use case starts when Librarian selects CheckInResource option.
Librarian enters the Dewey call number for the resource then commits the entry.
...
Another interface, refine the same use case:
SHOWN ON NEXT SLIDESlide12
Janice Regan, 2008
12
LMS: Private Mode Screen
C -- Check Resources In/Out
S -- Search
P -- Manage Patrons
R -- Manage Resources
Q -- Quit
Enter Option (C, S, P, R, Q)
LMSSlide13
Janice Regan, 2008
13
Main flow of events:
The use case starts when Librarian selects CheckInResource option from the LMS menu screen by entering the letter 'C' in the text field provided then pressing the “Enter” key.
The Check In/Out selection form is then displayed. The Librarian selects the In option by double clicking on the menu box item
Revising CheckInResource Use CaseSlide14
Janice Regan, 2008
14
LMS: Private Mode Screen
In
Out
Availability
LMS
Check Search Patron Resource
Prev Screen
QuitSlide15
Janice Regan, 2008
15
Main flow of events:
A window representing a Check In Form is then displayed. The Librarian types the Dewey call number for the resource in the appropriate text field then presses the "Accept" button to commit the entry.
...
Revising CheckInResource Use CaseSlide16
Janice Regan, 2008
16
LMS: Private Mode Screen
LMS
Check Search Patron Resource
Accept
Finish
Cancel
Enter Patron ID
Enter Resource ID
Title
Author
Call Date
Call Number
Enter Call number
Due Date
Date of Loan
Title
Author
StatusSlide17
Janice Regan, 2008
17
Questions about UI?
Who decides what type of user interface should be implemented for a software system?
ALWAYS make sure the user wants the type of user interface you are designing. Client request for a GUI or CLI is a nonfunctional requirement!!Slide18
Janice Regan, 2008
18
Starting you User Manual
Once you have designed (refined) your user interfaces and have refined your use cases, you can start on your User Manual
Note that some of the sections of Deliverable #6 (User Manual) can be started while you are designing (refining) your user interfaces and refining your use cases