In this lesson we'll meet with the process of analysis of the use cases. We're going to examine a member's package of use cases and a book's package of use cases. The rest of them are given to you, to try yourself in the use case analysis.
The Member package
The Member's package of use cases developed in earlier stages of the system analysis |
- Enter data for searching | |
The good-one sentence description for this use case may be: The member enters a data for serching into search form. | |
Here initialing actor will be Member, which is also a benefiting actor. | |
The assumptions are that a member wants to find out books or journals. Another assumption is that the Digital Library's interface has a form dedicated for search data entry. | |
The precondition is that a member has a necessary data to make a search. The postcondition is that a member enters necessary data into Digital Library. | |
The steps in the use case are: | |
![]() |
From the Library's LAN or from home/office, the member activates the user interface for search entry. |
![]() |
The search form appears on the screen. |
![]() |
The member enters necessary data patterns into search form. |
- Transmit data for searching | |
The description for this use case may be: Take a data pattern entered in search form, and send it to the Digital Library's database search engine. | |
The assumptions are that we have communication via the Internet or library's LAN, and we have a search form in the member's interface. | |
The precondition is entered data pattern in search form, the postcondition is that the data pattern has arrived in the Digital Library database search engine. | |
The steps in the use case are: | |
![]() |
Click on the SUBMIT button on the search form. |
![]() |
Activate the transmiting mechanizam for data in network(s). |
![]() |
The data pattern arrives in Digital Library database search engine. |
![]() |
On the member's screen appears a message that data has been sent, and to wait a moment during receiveing the data. |
Because this use case is related to the previous one, we must make a change to the Member package. It has to show <<include>> dependency between this one and "Enter data for searching" use case. |
- Take a list of searched items | |
This one use case is the last part for completion the searching process. Description here is: Receive a list of book or journals, after entering a data in search form and send it to the Digital Library database. | |
The assumptions are that a member uses a search form, and a communication via network(s) is good. | |
The precondition is clicked SUBMIT button on search form, and the postcondition is printed list of items on the member's screen. The actor here again is Member. | |
The steps of this use case are: | |
![]() |
Wait until search is performed (in paralell a Digital Library search engine performs a search). |
![]() |
Digital Library database transmits a list of items to the member's interface via the network(s). |
![]() |
The member receives a list of items satisfying entered search-data pattern. |
Inclusion also appears in this use case. <<include>> joins this use case with the previous one. |
- Make reservation | |
Description for this use case will be: The member wants to make a reservation for the item gained from searching process or recommendation process. | |
As you can see this use case depends on two different use cases - search and recommendation. Thus reservation process may take place only when one of these two processes take turn. Thats because an inclusion is presented between these three use cases. | |
The assumptions are a list of items, and a button for reservation. | |
The precondition is clicked RESERVE button, and a postcondition is transmited reservation record to the Digital Library. | |
The steps of this use case are: | |
![]() |
The member receives a list of items (from searching or from recommendation) |
![]() |
The member clicks the RESERVE button for the items that he or she wants to reserve |
![]() |
The member fills in the information in the form that appears for the reservation |
- Transmit reservation |
This use case wouldn't be explained in detail, because it is almost the same with the "transmit the data for searching" use case. Only we'll say that this use case is related with "make reservation" and "receive notification" use cases. The connection is <<include>>. |
- Receive notification | |
Description is: After pressing the SUBMIT button in the reservation form, a notification from the Digital Library must arrive that the reservation has been accepted, and infrom the member with the status of reservation. | |
Here status of reservation is for haveing or not a free sample for reserved item. If a free sample is present how many weeks it'll be holded for the member. | |
The assumptions are good communication in the network(s) and clicked SUBMIT button. | |
The precondition is clicked SUBMIT button, and a postcondition is received status of reservation | |
The steps of this use case are: | |
![]() |
Wait until notification is received |
![]() |
Transmit the necessary information via the network to the member's interface |
![]() |
Members receives the status of reservation |
- Take a list of recommended items | |
Description is: The member activates the recommendation part of the system, and gets a list of recommended items | |
The assumptions are clicking the RECOMMEND button, and a working recommendation algorithm. | |
The precondition is clicked RECOMMEND button, and a postcondition is received list of items. | |
The initiating and benefiting actor is Member. | |
The steps of this use case are: | |
![]() |
Activate the recommendation part from the user's interface. |
![]() |
The Digital Library activates a recommendation algorithm which produces a list of items. |
![]() |
Print this list of items to the member's screen. |
The updated use case diagrams for the Member package |