CIS2303: SYSTEMS ANALYSIS AND

DESIGN

ACTIVITY 3

COURSE LEARNING OUTCOME: CLO2- CREATE

BEHAVIORAL MODELS TO DOCUMENT SYSTEM
REQUIREMENTS

CHAPTERS: CHAPTER 3

COGNITIVE LEVELS: UNDERSTAND, APPLY, AND ANALYZE

AIM: IDENTIFY THE REQUIREMENTS AND DETERMINE THE

SYSTEM SCOPE

TOOLS: CASE TOOL (STARUML OR ENTREPRISE ARCHITECT)

PROCEDURE:

OPEN CHAPTER 3 AND STUDY THE CORE PROCESS 3 AND ITS

ACTIVITIES

STUDY THE COVERAGE OF TOPICS SUCH AS DIFFERENT

TYPES OF REQUIREMENTS, REQUIREMENTS GATHERING
TECHNIQUES, AND UML ACTIVITY DIAGRAM

DOCUMENT REVISION CONTROL:

Version Author Effective Date Change Description DRC No

1.0 Dr. Belsam Attallah June 11, 2020 Define the first version 001
2.0 Dr. Nourchene Benayed June 15, 2020 Validate and Draw 002
UML Diagrams

1
EXERCISE 1-UNDERSTAND

THIS EXERCISE IS EXTRACTED FROM THE E-TEXTBOOK, PAGE 64

1. What is the difference between functional requirements and nonfunctional requirements?
Functional requirements define the functions or user services that will be supported by the system.
Such things as support of business processes and reports are included in functional requirements.

Nonfunctional requirements are other technical specifications and include such things as technical,
performance, usability, reliability, and security requirements.

2. Describe the steps in preparing for, conducting, and following up on an interview session.
 Establish an objective for the interview session.
 Determine the persons who should be involved in the interview, both users and team members.
 Develop a list of questions and issues to be discussed.
 Review any related documentation. Existing reports or procedure manuals are a good source of
questions and issues to discuss.
 Set time and location.
 Inform all participants of objective, time, and location. It is especially important that the users be
informed of the objectives so that they can come to the meeting prepared.

3. What are the benefits of doing vendor research during requirements gathering activities?
Doing vendor research, both for vendors of packaged solutions and consulting firms that develop
solutions, allows the project team the opportunity to see what other companies have done. It is less
expensive to buy a solution than to build one, if a viable solution is available. Vendor research helps
the project team see other solutions that may be state-of the-art and able to provide a competitive
advantage to the enterprise.

4. List and briefly describe the six requirements gathering techniques.

 Interview
 Observation
 Document Analysis
 Researching vendor solutions
 Concept Maps
 Story Cards and task Lists

5. What is the purpose of an activity diagram?

An activity diagram is used to document and describe the behavior of a business process, a to-be
system, a use case, or a collection of use cases.

EXERCISE 2- ANALYZE
1. Which of these are functional requirements? Justify your answer.
a. A person can enroll in a course
b. Only 10 persons max can enroll to this course
c. A student is a person
d. A professor is not a student
e. For every exam, a ranking report of all participants is generated
-- Points a, b and e are all related to the functionality of the system (functions, reports, conditions…etc.)

2. Which of the following are non-functional requirements? Justify your answer.

a. The system enables users to lunch orders
b. The system always responds to user clicks in less than one tenth of a second.
c. The system displays a list of hotel vacancies

2
 d. The system notifies the user when a new order arrives.
-- Point b is related to the technical specifications of the system.

EXERCISE 3- APPLY

THIS EXERCISE IS EXTRACTED FROM THE TEXTBOOK

“MODERN SYSTEMS ANALYSIS AND DESIGN”, PAGE 235

Draw an activity diagram that models the following business processes.

1. Employee reimbursement process Version 1. Employees of West Nile Valley University have to follow
a specific procedure to get reimbursed for travel they undertake on behalf of the university. First,
they have to gather and prepare all of the receipts the university requires for reimbursement. At the
same time, they complete the official reimbursement form. They then submit both the receipts and
the form to their departmental secretary. If something on the form is incorrect, the secretary returns
the form to the employee for correction. If the form is correct, the employee is asked to review the
reimbursement amounts, which are determined by an analysis of the reimbursement request. If the
amount shown is not correct, the employee must indicate that this is the case. If the amount shown is
correct, then the employee’s responsibilities for reimbursement are complete.
Actors
Activities
Control Nodes

3
4
 2. Employee reimbursement process Version 2. The travel reimbursement process for employees of
West Nile Valley University involves three different actors: the employee, the employee’s
departmental secretary, and the treasurer’s office. First, the employee has to gather and prepare all
of the receipts the university requires for reimbursement. At the same time, she/he completes the
official reimbursement form. She/he then submits both the receipts and the form to the
departmental secretary. If something on the form is incorrect, the secretary returns the form to the
employee for correction. If the form is correct, the secretary prepares a form required by the
university. That form is then submitted to the treasurer’s office. The treasurer’s office then enters the
amount to be reimbursed into the university’s system. The employee is then asked to review the
reimbursement amounts. If the amount shown is not correct, the employee must indicate that this is
the case. If the amount shown is correct, then the treasurer’s office sends the reimbursement to the
employee’s bank, completing the process.
Actors
Activities
Control Nodes

5
CASE STUDY- APPLY & ANALYZE

THIS CASE STUDY IS EXTRACTED FROM THE

INTERNATIONAL ACADEMY JOURNAL FOR CASE STUDIES.
IT WILL BE INCLUDED IN ALL COURSE ACTIVITIES.
STUDENTS ARE INVITED TO WORK IN GROUP TO ANSWER
ALL QUESTIONS.

AUTHOR
Terry L. Fox
University of Mary Hardin-Baylor, USA

https://www.abacademies.org/articles/case-study--systems-analysis-design-and-development-case-study-
medallion-theater--ticket-sales-system-6509.html

AIM
The primary purpose of this case study is to allow students to examin realistic dialog and Interview Notes, as
well as existing documents. The students should be able to follow this realistic and fairly common case study of
a small organization and conduct the analysis and design phases of the System Development Life Cycle (SDLC),
using an object-oriented approach and following an agile development process.

CASE DESCRIPTION
Dr. Thomas Waggoner, an information systems professor at the local university, is at the Will Call window at
the Medallion Theatre, trying to pick up tickets he had reserved. However, due to an oversight which turns out
to be rather frequent, his tickets were sold to another patron. Fortunately for Dr. Waggoner and his wife, the
box office manager finds two box seats which had not been claimed. In talking with the box office manager, Dr.
Waggoner starts thinking that he could perhaps help the theatre avoid this type of problem in the future. His
students could design and build a system to help keep track of ticket sales, and hopefully help the theatre
become more efficient.

Later that week Dr. Waggoner met with the Box Office Manager to develop an overall understanding of their
business processes, the information they maintain, and the reporting needed. Dr. Waggoner compiled this
information and presented it to a group of his students. The detailed requirements are listed below.

6
Dr. Waggoner explained to his analysis and design students what the Medallion really needed was an
Information system which would maintain information about each event and tickets sold, and the patron to
whom the tickets are sold. The system should also generate reports on the number of tickets sold/available
per performance, and tickets purchased by a specific patron.

Dr. Waggoner also informed his analysis and design students that the requirements are subject to change and
they have to respond quickly to change. In addition, the Medallion really rushed them to have a working
system at earliest.

7
BUSINESS DOCUMENTS

FIGURE 1: WILL CALL RESERVATION FORM

FIGURE 2: THE MEDALLION THEATER SEATING DIAGRAM

QUESTIONS
1. Which methodology would you like to adopt for this project? Justify your choice by listing 2
arguments. (solved in Activity 1)
2. Conduct the feasibility study for this project. (solved in Activity 2)
3. Define, discover, review, document, and understand the user's needs and constraints of the to-be
system using requirements gathering techniques.
A preliminary interview conducted by Dr. Waggoner with the Medallion Theater’s responsible
helped us to identify the following requirement user’ needs and constraints.

8
 User’s Needs:
The Medallion Theater Ticket Office would like to have a system that allows:
 Manage patrons. The Medallion likes to keep track of their patrons so they can notify them
of upcoming events and identify those who frequently support the theatre.
 Manage performances. The Medallion likes to keep track the date of the performance and
whether it is a matinee or evening performance.
 Manage productions. The Medallion would like to maintain information on the name and
type of the production, such as play or concert. A production can, and usually does, have
multiple performances, and can have both a matinee and evening performance on the same
date.
 Manage Seats. The theater has a total of 602 seats. Each seat is available for each
performance. The seats are in four categories, and the seat numbers are assigned as shown
in the provided table.
 Reserve a Ticket. When a patron calls or stops by to reserve a ticket, their name, address,
and contact information are recorded, if they are not already in the files. The patron can then
select the performance, including the date and whether it is matinee or evening. The patron
then selects their seats from those available for a particular performance. The ticket thus
identifies a specific seat for a specific performance.
 Purchase a Ticket. When a patron buys the his/her reserved Ticket.
 Generate a report of seats sold or available for a particular performance and should be able
to show the seats purchased by a patron (based on name or patron number) for a specific
performance.
By manage we mean add/update/delete/find/track

Constraints:
 The business process is not automated, which implies that the workflow is performed
manually and so generates errors.
 Dr. Waggoner also informed his analysis and design students that the requirements are
subject to change and they have to respond quickly to change. In addition, the Medallion
really rushed them to have a working system at earliest.

4. Create an activity diagram describing the behavior of the business process.

The following activity diagram describes the behavior of Reserving/Purchasing Tickets when a patron
calls or stops by the Medallion Theatre.

9
 5. What is the perimeter of the to-be system?
Creating an IS that automates the process of ticket sales in the theater as well as manage patrons,
performances, productions, and seats. The project does not include providing or installing the
hardware required to run the IS, and it does not cover training the theater staff on how to use it.

6. Identify the functional and non-functional requirements of the to-be system?

Functional Requirements:
In addition to the user needs identified in question 4, we propose to extend the perimeter of the
system to handle online Purchase and Payment.
 Manage patrons. The Medallion likes to keep track of their patrons so they can notify them
of upcoming events and identify those who frequently support the theatre.
 Manage performances. The Medallion likes to keep track the date of the performance and
whether it is a matinee or evening performance.
 Manage productions. The Medallion would like to maintain information on the name and
type of the production, such as play or concert. A production can, and usually does, have
multiple performances, and can have both a matinee and evening performance on the same
date.

10
  Manage Seats. The theater has a total of 602 seats. Each seat is available for each
performance. The seats are in four categories, and the seat numbers are assigned as shown
in the provided table.
 Reserve a Ticket. When a patron calls or stops by to reserve a ticket, their name, address,
and contact information are recorded, if they are not already in the files. The patron can then
select the performance, including the date and whether it is matinee or evening. The patron
then selects their seats from those available for a particular performance. The ticket thus
identifies a specific seat for a specific performance.
 Purchase a Ticket. When a patron buys the his/her reserved Ticket.
 Generate a report of seats sold or available for a particular performance and should be able
to show the seats purchased by a patron (based on name or patron number) for a specific
performance.

Non-functional requirements:
 Usability: Appropriate and user-friendly data entry/edit screens need to be created to enter and
edit information for patrons and performances, as well as ticket sales for a specified seat
selection
 Security: A secure online payment system which requires the use of secure HTTP for
communication among client and server nodes.
 Performance: The client portion of a system might be required to have a .5 second response time
to all button presses, and the server might need to support 100 simultaneous client sessions
(with the same response time).

7. Let suppose you chose SCRUM framework to build the to-be system (Question 1), describe the
requirements using a product backlog.
8. For each sprint, create a system sequence diagram describing the behavior of or a user story.
9. For each sprint, create a fragment of the domain class diagram describing the structure of the to-be
system. Merge/Refine all fragments to define the domain class diagram.
10. Which architectural style you like to adopt to design the to-be system?
11. Create a high-level architectural model of the to-be system.

11