Activity 2 - Solutions
Activity 2 - Solutions
DESIGN
CHAPTERS: CHAPTER 2
TOOLS: NONE
PROCEDURE:
1.0 Dr. Belsam Attallah June 11, 2020 Define the first version 001
1.0 Dr. Nourchene Benayed June 15, 2020 Validate the first 001
version
EXERCISE 1-UNDERSTAND
1. Explain how the core processes are performed in a structured and iterative development.
With a Structured development, the core processes are performed in a sequence
With an Iterative and agile, these core processes are performed multiple times—during each
iteration/sprint
1
3. Describe the purpose of each feasibility test.
Legal Feasibility Test: Involves testing whether the system adapts to the legal and ethical
requirements.
Economic Feasibility Test: Involves conducting a Cost Benefit Analysis to identify how well, or how
poorly, a project will be conducted.
Technical Feasibility Test: Involves validating the technical resources and capabilities to convert the
idea into a working system.
Operational Feasibility Test: Involves understanding how the proposed system will solve the problem
and fit into the current day-to-day operations of the organization.
Scheduling Feasibility Test: Involves measuring how reasonable the project duration is.
2
CASE STUDY- APPLY & ANALYZE
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.
3
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.
4
BUSINESS DOCUMENTS
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.
Feasibility Study will:
Verify whether the project can be started and completed successfully
Measure how suitable the development of the system will be to the company
5
1- Legal Feasibility Test: Involves testing whether the system adapts to the legal and ethical
requirements. The new IS for Medallion Theatre will not breach any regulations/laws in the
city/country, nor involve any ethical aspects. The proposed system conforms the legal and ethical
requirements.
2- Economic Feasibility Test: Involves conducting a Cost Benefit Analysis to identify how well, or how
poorly, a project will be conducted. The proposed system will be completed in a short duration,
and will be carried out by students on a no-profit basis.
3- Technical Feasibility Test: Involves validating the technical resources and capabilities to convert
the idea into a working system. The work will be carried out by information systems’ analysis and
design students, and will be supervised by Dr. Thomas Waggoner, an information systems
professor at a local university, who is a professional person in this field.
4- Operational Feasibility Test: Involves understanding how the proposed system will solve the
problem and fit into the current day-to-day operations of the organization. Dr. Thomas 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 his students. The selected methodology (in Activity 1) supports
the change and development of requirements during the implementation of the project.
5- Scheduling Feasibility Test: Involves measuring how reasonable the project duration is. The
selected methodology (in Activity 1) enables analyzing, designing, coding, testing, and delivering
small functional pieces in iteration with short duration. Dr. Waggoner also agreed with his
students that the Medallion Theatre really rushed the requirements to have a working system at
the earliest, and that the project team have to respond quickly to change.
3. Define, discover, review, document, and understand the user's needs and constraints of the 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.