CIS2303: SYSTEMS ANALYSIS AND

DESIGN

ACTIVITY 1-KEY ANSWER

COURSE LEARNING OUTCOME: CLO1-COMPARE A RANGE

OF SYSTEM DEVELOPMENT METHODOLOGIES

CHAPTERS: CHAPTER 1

COGNITIVE LEVELS: UNDERSTAND AND ANALYZE

AIM: PHASES IN SOFTWARE DEVELOPMENT PROJECT,

OVERVIEW, NEED, COVERAGE OF TOPICS

TOOLS: NONE

PROCEDURE:

OPEN AN APPROPRIATE SYSTEM ANALYSIS AND DESIGN

GUIDE (CHAPTER 1 AND E-TEXTBOOK) AND STUDY THE
SOFTWARE DEVELOPMENT LIFE CYCLE.

STUDY THE CORE PROCESSES OF SDLC.

STUDY THE COVERAGE OF TOPICS SUCH AS SOFTWARE

DEVELOPMENT METHODOLOGIES AND THEIR COMPARISONS.

DOCUMENT REVISION CONTROL:

Version Author Effective Date Change Description DRC No

1.0 Dr. Belsam Attallah June 11, 2020 Define the first version 001
1.1 Dr. Nourchene Benayed June 15, 2020 Validate & Add an 001
example

1
EXERCISE 1-UNDERSTAND
1. What is the purpose of systems analysis? Why is it important?
Systems Analysis is those activities that enable a person to understand and identify what IS should
accomplish (Functionality/Service).

2. What is the difference between systems analysis and systems design?

Systems Analysis is those activities that enable a person to understand and specify what an IS should
accomplish, while systems Design is those activities that enable a person to define and describe in
detail the system that solves the needs.
Systems Analysis emphasizes an investigation of the problem and requirements, rather than a
solution. Systems Design emphasizes a conceptual solution that fulfills the requirements, rather than
its implementation.
Let suppose we would like to implement a registration system. Analyzing the system goes through
identifying its main functionalities (allow the students to register for a course, drop a course, etc…),
while designing the system goes through defining its architecture, components and database to
satisfy functionalities identified in analysis phase.

3. Describe the major elements and issues with structured development.

Major Elements
 System is grown stage by stage
 Structured development is mostly based on the use of traditional approach to analyze, design,
and develop an IS
 Oriented modelling approach can be used in a structured development
Major Issues
 Identify system requirements long before programming begins
 Minimize changes to the requirements as the project proceeds
 Complete design before implementation
 Long elapse between proposal and delivery

4. What is meant by agile development and iterative development?

Agile Development:
 Iterative and incremental development, which means that the system is grown piece by piece
 Customers must continually be involved with the project team
 Customers become part of the technical team, because working software is being developed
throughout the project
 Customers are continually involved in defining requirements and testing components
 Emphasize flexibility to anticipate new requirements during development
 Agile development is mostly based on the use of object-oriented approach to analyze, design,
and develop an IS

EXERCISE 2: ANALYZE
1. Compare and contrast Unified Process and Scrum.
 Both Unified Process (UP) and Scrum are Agile Development Methodologies
 Scrum is about analyzing, designing, coding, testing, and delivering small functional pieces in
iteration with short duration
 UP involves more formal definition of scope, major milestones, and specific dates, while Scrum
uses a project backlog instead of scope.
 UP involves four major phases of the project lifecycle (inception, elaboration, construction, and
transition), whereas Scrum dictates that the whole “traditional lifecycle” fits into one iteration

2
 2. If a system is being developed where the customers are not sure of what they want, the requirements
are often poorly defined. In addition, the project has a short-time schedule. Which of the following
would be an appropriate development process model for this given scenario?

A. Waterfall Methodology

B. Parallel Methodology

C. Scrum Framework

3. CIS2303 work team has the mission to build an IS that automates a certain business process. The work
team members are motivated, familiar with the business domain, but they lack skills on the
development of object oriented applications. The requirements are stable and not subject to change.
Your manager asks you to describe the methodology that you would like to adopt for this project.
Justify your choice by listing 2 arguments.

The Waterfall Methodology of Structured Development is appropriate for this system. This is due to
the following reasons:
1- The requirements are stable and not subject to change
2- The project team is familiar with the business domain
These 2 reasons will enable the project team to complete the system design before
implementation, which is a requirement of a successful application of Waterfall Methodology.

3
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.

4
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.

5
BUSINESS DOCUMENTS

FIGURE 1 WILL CALL RESERVATION FORM

FIGURE 2THE MEDALLION THEATER SEATING DIAGRAM

QUESTIONS
1. Which methodology would you like to adopt for this project? Justify your choice by listing 2 arguments.
The Agile Development Methodology is recommended for this system. This is due to the following
reasons:
1- The system requirements are subject to change
2- The project team have to respond quickly to change
3- The Medallion Theatre really rushed the requirements to have a working system at the earliest

6
 Using Agile, the project team does not need to know all requirements from the beginning, they will
continue refining the requirements. Another important aspect of Agile Development is that customers
must continually be involved with the project team, because working software is being developed
throughout the project. Customers are continually involved in defining requirements and testing
components. In addition, Agile supports analyzing, designing, coding, testing, and delivering small
functional pieces within a sprint with short duration.

2. Conduct the feasibility study for this project.

3. Define, discover, review, document, and understand the user's needs and constraints of the to-be
system using requirements gathering techniques.
4. Create an activity diagram describing the behavior of the business process.
5. What is the perimeter of the to-be system?
6. Identify the functional and non-functional requirements of the to-be system?
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.