IS 236: STRUCTURING

SYSTEM REQUIREMENTS
Salome Maro
29th Nov 2021
OUTLINE
 Use cases
USE CASES
 Used to explain and document the interaction that is required between the
user and the system to accomplish the user’s task

 Traditionally -- Analysts was the user “what should the system

do”
 Problems:
 Users are not likely to truly understand the capabilities and limitations of
information systems
 Users may have difficulty envisioning new ways to redesign business
processes.
 It is common for users to describe things they think they want from the
new system, but our focus should be on the real needs for the new system.
USE CASES
 A use case depicts a set of activities performed to produce some output
result.
 Each use case describes how an external user triggers an event to which
the system must respond.

 For example, in a library system, a student might rent a book or return a

book
Use cases:
1. Rent book,
2. Return book
ELEMENTS OF A USE CASE
 Use cases can vary considerably from one organization to
another in terms of the content included, the format followed,
and the degree of formality employed.
 Common elements of a use case:
 Use case name and ID number
 Priority e.g., high medium, low
ELEMENTS OF A USE CASE
 Actor -- refers a person, another software system, or a
hardware device that interacts with the system to achieve a
useful goal.
 Trigger — the event that causes the use case to begin.
 Preconditions – define the state the system must be in before the use
case commences.
 Normal Course – major steps that are performed to execute the
response to the event
 Alternative Course – the steps followed for alternative paths through
the use case
ELEMENTS OF A USE CASE
 Postconditions – state the system must be in after completion
 Exceptions -- any error conditions or exceptions that may occur as the use
case steps are performed. Not normal branches in decision logic, but are
unusual occurrences or errors that lead to an unsuccessful result
USE CASE
EXAMPLES
 Field Description
Use Case: Login
Actors: User
Short A user wants to log into the social media system
description:
Pre-condition: • The user must have an account
• The user must have correct login credentials
Main flow:   1. The system displays the login page
2. The user enters a username and password
3. The user submits the username and password
4. System acknowledge successfully login to the user

Alternative 1. The user logs in using face recognition

flow(s):

Exception If the username and/or password is incorrect, the system displays and
flow(s) error to the user
Post- The user is successfully logged in
condition:
 Field Description
Use Case: Perform Interview
Actors: Interviewee
Short This is where an Interviewee do interview by answering questions
description:
Pre-condition: • Interviewee registered into the system
• Interview already set by the administrator
Main flow:   1. System displays instructions for the interview and wants an Interviewee to
confirm that he has read and ready to start the interview
2. Interviewee clicks the OK button
3. System displays all interview questions and Clock timing start counting
4. Interviewee provides answers to questions, saves and submits answers
after being done
5. System acknowledge successfully sending of answers to an Interviewee
Alternative 1. System displays one question after the other and Clock timing start
flow(s): counting
2. Interviewee provides answers to a question given and then will be given a
chance to do the following question. Saves and submits answers after
being done (Interviewee can do forward and backwards to navigate to
questions)
Exception If the Interviewee will select to cancel the interview process, then the
flow(s) Interview will be recorded as canceled or un-done interview
Post-condition: Interviewee will be recorded as already he/she has passed through interview
process
CLASS ACTIVITY
 Assume that you want to implement a system to
allow users to automatically rent DVDs at a kiosk
without requiring the assistance of a salesperson.
Mention 3 use cases of the system.
 Field Description
Use Case: Rent DVD
Actors:
Short
description:
Pre-condition:

Main flow:  

Alternative
flow(s):

Exception
flow(s)
Post-condition:
USE CASES AND THE
FUNCTIONAL REQUIREMENTS
 Use cases are very helpful tools to use to understand user requirements.
 Use cases explain the user’s interaction with the system, but they omit a
lot of details that are necessary to know before the system can be
developed.
 Use cases must be transformed into functional requirements for the
developer
 Field Description
Use Case: Perform Interview
Actors: Interviewee
Short This is where an Interviewee do interview by answering questions
description:
Pre-condition: • Interviewee registered into the system
• Interview already set by the administrator
Main flow:   1. System displays instructions for the interview and wants an Interviewee to
confirm that he has read and ready to start the interview
2. Interviewee clicks the OK button
3. System displays all interview questions and Clock timing start counting
4. Interviewee provides answers to questions, saves and submits answers
after being done
5. System acknowledge successfully sending of answers to an Interviewee
Alternative 1. System displays one question after the other and Clock timing start
flow(s): counting
2. Interviewee provides answers to a question given and then will be given a
chance to do the following question. Saves and submits answers after
being done (Interviewee can do forward and backwards to navigate to
questions)
Exception If the Interviewee will select to cancel the interview process, then the
flow(s) Interview will be recorded as canceled or un-done interview
Post-condition: Interviewee will be recorded as already he/she has passed through interview
process
FUNCTIONAL
REQUIREMENTS
 The system must allow the user to register to the system
 The system must allow the administrator to set up the interview
 The system must allow the administrator to add questions to the interview
 The system must display instructions for the interview
 The system must allow the interviewee to confirm that he/she is wants an
ready to start the interview
 The system must allow the interviewee to answer questions
 The system must save all the interviewees answers
STEPS FOR
WRITING USE
CASES
 Sit in your groups

Through discussion, identify major use GROUP

cases of the system you will work on –
at least 4
WORK

For one of the uses cases, write a use

case description.
 Field Description
Use Case: Login
Actors: User
Short A user wants to log into the social media system
description:
Pre-condition: • The user must have an account
• The user must have correct login credentials
Main flow:   1. The system displays the login page
2. The user enters a username and password
3. The user submits the username and password
4. System acknowledge successfully login to the user

Alternative 1. The user logs in using face recognition

flow(s):

Exception If the username and/or password is incorrect, the system displays and
flow(s) error to the user
Post- The user is successfully logged in
condition:
QUESTIONS?