SEEM 3430

1
SEEM 3430 Tutorial 2

• Two Examples on
• Requirement Definition and Use Cases

2
Outline

• Simplified Library System
• Online Product Catalog

3
Simplified Library System

• Users Registration
• Books Information Database
• Book Reservation
• Not discussed. i.e. we assume the number of users
  and books are fixed, and no reservations are
  allowed.
• Books Searching
• Books Lending
• Assume no renewals and early recalls.
• Automatic Notifications
• Checking Users Record
• Assume their personal information does not need
  updates.
• Books Returning

4
Books Searching

• On the online database, users can search for any
  books, by keywords, authors, year of publish and
  so on.
• A list of search results will be shown after the
  user has entered the search criteria.
• The user can view the detailed information,
  including the call number and status of the book
  by clicking on its entry on the list.

5
Books Lending

• If a user find a book (nobody has borrowed it),
  and he would like to borrow it, he could bring it
  to the counter for checking out.
• Staff will check the status of the book and the
  record of the user to see if he has borrowed
  books more than the limit. This is done by
  inputting the books information into the system
  and the system will do the checking
  automatically.
• If the user is legitimate to borrow the book, a
  record will be made in the systems database.

6
Automatic Notification

• Before 2 days for any books being overdue, a
  notification showing the books information will
  be sent to the users email account by the
  system, automatically.

7
Checking Users Record

• Users can check their borrowing record online.
• They need to log in the system before doing that.
• They can check what books they have borrowed and
  the due dates and the incurred fines due to
  overdue.

8
Books Returning

• If a user return a book, his borrowing record
  will be checked to see if the book has been
  overdue. If yes, he will need to pay the fine,
  which is calculated by the system.
• The checking is done when the information of the
  book is entered to the system by staffs.
• The record will be updated accordingly.

9
Functional Requirements Book Searching

• Process
• The system must have an interface for users to
  enter search criteria for books with keywords,
  authors, year of publish and so on.
• The system must show a list of search results to
  users upon they entered the search criteria.
• The system must show the detailed information of
  the book if the user has clicked on the entry.
• Data
• The system must contain detailed data of books.

10
Functional Requirements Book Lending

• Process
• The system must check the status of book and the
  record of user to determine the legitimacy of him
  to borrow a book, when a staff entered the books
  information and the user ID.
• Data
• The system must contain users information and
  his borrowing record.
• The system must contain status of the book.

11
Functional Requirements Automatic Notification

• Process
• The system must check continuously if there are
  any overdue for any user in the next two days and
  send email notifications to them.
• Data
• Mentioned in previous slides.

12
Nonfunctional Requirements

• Operational
• The online system must work on any browser.
• (If appropriate) The system must be able to
  integrate with other systems of the organization.
• Performance
• The system must allow more than 100 users using
  it at the same time.
• The system must maintain the consistency of
  records in the database/ deal with concurrencies.
• The system should respond user/staff within 10
  seconds.
• Security
• The system must require users/staff to login for
  performing particular actions.
• The system must only allow authorized person to
  access the data.
• Cultural?

13
Use Cases

• Can be developed based on the functional
  requirements plus some other description from end
  users.
• No fixed format. But need to be easily understood
  by end users.

14
Use Case Name Enter data for book searching Use Case Name Enter data for book searching ID 1 Importance Level Medium Importance Level Medium
Primary Actor User Primary Actor User Primary Actor User Primary Actor User Primary Actor User
Short Description It describes how users enter data or search criteria in the interface or online system for searching books and receive a list that fit his criteria. Short Description It describes how users enter data or search criteria in the interface or online system for searching books and receive a list that fit his criteria. Short Description It describes how users enter data or search criteria in the interface or online system for searching books and receive a list that fit his criteria. Short Description It describes how users enter data or search criteria in the interface or online system for searching books and receive a list that fit his criteria. Short Description It describes how users enter data or search criteria in the interface or online system for searching books and receive a list that fit his criteria.
Trigger User browsing the online catalogue website Type External/ Temporal Trigger User browsing the online catalogue website Type External/ Temporal Trigger User browsing the online catalogue website Type External/ Temporal Trigger User browsing the online catalogue website Type External/ Temporal Trigger User browsing the online catalogue website Type External/ Temporal
Major Inputs Description Sources Major Outputs Description Major Outputs Description Destination
1. Criteria in keywords and dropdown lists, etc User 1. List of book names and partial details of book that fit users criteria 1. List of book names and partial details of book that fit users criteria User
2. All Books details and status from the database Database 2. Further details of the selected book 2. Further details of the selected book User
3. Book selected User
Major Steps Performed Major Steps Performed Information for Steps Information for Steps Information for Steps
1. Users enter keywords and do all the settings on the search page and click the Submit button 1. Users enter keywords and do all the settings on the search page and click the Submit button Keywords and settings Keywords and settings Keywords and settings
2. The page shows a list of book names and partial details of book that fit users criteria 2. The page shows a list of book names and partial details of book that fit users criteria ID, names, and partial details of books ID, names, and partial details of books ID, names, and partial details of books
3. User click on an entry to view details 3. User click on an entry to view details ID of the selected book ID of the selected book ID of the selected book
4. The page shows details and status of the book selected 4. The page shows details and status of the book selected Further details and status of the book Further details and status of the book Further details and status of the book
5. 5.
15
Use Case Name Lending of Books Use Case Name Lending of Books ID 2 ID 2 Importance Level Medium Importance Level Medium
Primary Actor User, staff Primary Actor User, staff Primary Actor User, staff Primary Actor User, staff Primary Actor User, staff Primary Actor User, staff
Short Description It describes how staff can determine if the user can borrow a book away and update the records. Short Description It describes how staff can determine if the user can borrow a book away and update the records. Short Description It describes how staff can determine if the user can borrow a book away and update the records. Short Description It describes how staff can determine if the user can borrow a book away and update the records. Short Description It describes how staff can determine if the user can borrow a book away and update the records. Short Description It describes how staff can determine if the user can borrow a book away and update the records.
Trigger User bringing a book that he want to borrow to the counter. Type External/ Temporal Trigger User bringing a book that he want to borrow to the counter. Type External/ Temporal Trigger User bringing a book that he want to borrow to the counter. Type External/ Temporal Trigger User bringing a book that he want to borrow to the counter. Type External/ Temporal Trigger User bringing a book that he want to borrow to the counter. Type External/ Temporal Trigger User bringing a book that he want to borrow to the counter. Type External/ Temporal
Major Inputs Description Sources Sources Major Outputs Description Major Outputs Description Destination
1. Borrowers user ID, books ID Staff Staff 1. The users information, borrowing record, and the legitimacy of him to borrow the book. 1. The users information, borrowing record, and the legitimacy of him to borrow the book. Staff
2. All users information, borrowing records and books information Database Database 2. Record of lending 2. Record of lending Database
3. Staffs decision for lending Staff Staff 3. Notification 3. Notification Staff
Major Steps Performed Major Steps Performed Major Steps Performed Information for Steps Information for Steps Information for Steps
1. Staff enter user ID and book ID by scanning devices. 1. Staff enter user ID and book ID by scanning devices. 1. Staff enter user ID and book ID by scanning devices. User ID and book ID User ID and book ID User ID and book ID
2. The interface shows users information, borrowing record, and show the legitimacy of him to borrow the book after some computation. 2. The interface shows users information, borrowing record, and show the legitimacy of him to borrow the book after some computation. 2. The interface shows users information, borrowing record, and show the legitimacy of him to borrow the book after some computation. users information, borrowing record, and the legitimacy of the user to borrow the book. users information, borrowing record, and the legitimacy of the user to borrow the book. users information, borrowing record, and the legitimacy of the user to borrow the book.
2.1 If the action is not legitimate, the use case exits. 2.1 If the action is not legitimate, the use case exits. 2.1 If the action is not legitimate, the use case exits. - - -
2.2 If the action is legitimate, then the staff click on the Lent button to lend out the book. 2.2.1 A record is inputted with the due date calculated by the system. 2.2 If the action is legitimate, then the staff click on the Lent button to lend out the book. 2.2.1 A record is inputted with the due date calculated by the system. 2.2 If the action is legitimate, then the staff click on the Lent button to lend out the book. 2.2.1 A record is inputted with the due date calculated by the system. Staff decision/ click Borrowing record Staff decision/ click Borrowing record Staff decision/ click Borrowing record
16
Use Case Name Automatic Notification for Due Dates Use Case Name Automatic Notification for Due Dates Use Case Name Automatic Notification for Due Dates ID 3 Importance Level Medium Importance Level Medium
Primary Actor Time Primary Actor Time Primary Actor Time Primary Actor Time Primary Actor Time Primary Actor Time
Short Description The system sends out reminder to users email account if he has books that will be overdue within two days Short Description The system sends out reminder to users email account if he has books that will be overdue within two days Short Description The system sends out reminder to users email account if he has books that will be overdue within two days Short Description The system sends out reminder to users email account if he has books that will be overdue within two days Short Description The system sends out reminder to users email account if he has books that will be overdue within two days Short Description The system sends out reminder to users email account if he has books that will be overdue within two days
Trigger The system searched the database and find a user has books that will be overdue in two days Type External/ Temporal Trigger The system searched the database and find a user has books that will be overdue in two days Type External/ Temporal Trigger The system searched the database and find a user has books that will be overdue in two days Type External/ Temporal Trigger The system searched the database and find a user has books that will be overdue in two days Type External/ Temporal Trigger The system searched the database and find a user has books that will be overdue in two days Type External/ Temporal Trigger The system searched the database and find a user has books that will be overdue in two days Type External/ Temporal
Major Inputs Description Sources Major Outputs Description Major Outputs Description Major Outputs Description Destination
1. Users borrowing records Database 1. Records showing overdue in 2 days 1. Records showing overdue in 2 days 1. Records showing overdue in 2 days System
2. Users information, book information for records showing overdue in 2 days System 2. Email notification with details 2. Email notification with details 2. Email notification with details User
Major Steps Performed Major Steps Performed Information for Steps Information for Steps Information for Steps Information for Steps
1. System scan through the record to sort out records that will be overdue in two days 1. System scan through the record to sort out records that will be overdue in two days Borrowing records Borrowing records Borrowing records Borrowing records
1.1. If no records found, the use case exits. 1.1. If no records found, the use case exits. - - - -
1.2. If records are found, email notifications are produced and sent to the user 1.2. If records are found, email notifications are produced and sent to the user Borrowers information and book information. Borrowers information and book information. Borrowers information and book information. Borrowers information and book information.
17
Online Product Catalog

• Assumption
• For simplicity, we consider database need no
  updating and the purpose of the webpage is just
  for users quick searching of products.

18
Product Searching

• On the online database, users can search for any
  goods/product, by category, keywords, brands,
  prices etc.
• A list of search results will be shown after the
  user has entered the search criteria.
• The user can view the detailed information.

19
Illustration
20
(No Transcript)
21
(No Transcript)
22
Functional Requirements

• Process-oriented requirements
• The system must have an interface for users to
  enter search criteria for product with category,
  keywords, brands, price.
• The system must check validity of the users
  input.
• The system must show a list of search results to
  users upon they entered valid search criteria.
• The system must show the detailed information of
  the product if the user has clicked on the entry.

23
Functional Requirements Cont

• Data-oriented requirements
• The system must contain data of product,
  including
• Name
• Description
• (Paths of) Photos (any number)
• Price
• Information of stores the product is available at
  (any number)

24
Nonfunctional Requirements

• Operational
• The online system must work on any browser.
• Performance
• The system must allow more than 100 users using
  it at the same time.
• The system must maintain the consistency of
  records in the database/ deal with concurrencies.
• The system should respond user/staff within 10
  seconds.
• Security, cultural

25
(No Transcript)