Course Title: Systems Analysis and Design

Course Code: MGMT3012 (MS31C)

Lecturer: Mr. Ramon McLaren
Email: ramon.mclaren02@uwimona.edu.jm
Office: ---
Office Hours: Monday & Tuesday, 5 – 7 p.m, Thursday, 7 – 9 p.m.

Course Rationale and Description

Many systems have failed or have been abandoned because analysts built wonderful information systems (IS)
without an in-depth understanding of the organization or the problem the system is supposed to solve. However,
the primary goal of these information systems is to create value for organizations. Since the systems analyst is a key
person for analyzing the business, identifying opportunities for improvement and designing information systems to
implement these ideas, it is important for you, the systems analyst, to understand and develop through practice, the
skills needed to design and implement new, successful information systems.

This course discusses the processes, methods, techniques and tools that organizations use to determine how they
should conduct their business, with a particular focus on how computer-based technologies can most effectively
contribute to the way business is organized. The course covers a systematic methodology for analyzing a business
problem/opportunity, determining what role, if any, computer-based technologies can play in addressing the
business need, articulating business requirements for the technology solution, specifying alternative approaches to
acquiring the technology capabilities needed to address the business requirements, and specifying the requirements
for the information systems solution, in particular, in-house development, development from third-party providers,
or purchased commercial-off-the-shelf (COTS) packages.

Prerequisites
MGMT2005/MGMT2004 (MS21C) – Computer Applications

Objectives
Systems Analysis and Design (SAD) is the art of converting ill-defined, rough, vague, even fuzzy business concepts
into instructions that are clear enough to be implemented and turned into a valuable Information Systems. Systems
analysis is the study of a current business system and its problems, the determination and definition of business
needs and information requirements, and the evaluation of alternative solutions. Systems design is the general and
detailed specification of a computer and human solution that meets the requirements determined during systems

~1~
analysis. The aim of this course is to enable learners to gain an understanding of the principles of systems analysis
and design and equip them with the skills to analyze business requirements and design solutions to meet business
needs.

Learning Outcomes
After successfully completing this course, a learner should gain comprehensive theoretical knowledge as well as
practical skills related to the development process of information systems. Students who successfully complete the
course should be able to:

1. Identify the types of business needs that can be addressed using information technology-based solutions.
2. Initiate, specify, and prioritize information systems projects and determine various aspects of feasibility
(technical, economic, operational, schedule) of these projects.
3. Clearly define problems, opportunities or mandates that initiate projects.
4. Compare and contrast systems development methodologies.
5. Use at least one specific methodology (the SDLC) for analyzing a business situation (a problem or
opportunity), model the situation using a formal technique and specify requirements for a system that
enables a productive change in a way the business is conducted.
6. Write clear and concise business requirements documents and convert them into technical specifications.
7. Manage information systems projects using formal project management methods.
8. Articulate various systems acquisition alternatives, including the use of packaged systems (such as ERP,
CRM, SCM, etc.) and outsourced design and development resources.
9. Use contemporary CASE tools in high-level logical systems design (USE Case, process and data modeling).
10. Compare the acquisition alternatives systematically and analyze and articulate feasibilities among
alternative solutions.
11. Develop an information systems prototype for a business situation.

Assessment
This course provides knowledge and hands-on experience in Systems Analysis and Design. To gain practice and
technical skills, class members will engage in discussions, collaborative and individual assignments and group
projects. Discussions will assist in the ability to reflect about practical issues and discuss these with colleagues.
Individual in-course assignments will test students’ knowledge and understanding of course material. Collaborative
assignments will complement individual ones as critical skill building exercises. A group project will be the
culmination for the course material and provide students opportunities to integrate their knowledge and to learn
from each other. A final exam will be used to test the students’ theoretical knowledge of the course material and
mastery of practical skills. Table 1 shows each component and associated weight.

~2~
 Table 1. Course Components and Weights

Component Weight
Course Work:
 2 In-course Tests (10% each) 20%
 Group Project 30%
TOTAL COURSEWORK 50%
Final Exam 50%
FINAL 100%

In-course Tests (Due Dates: TBA by Instructor) 20%

There will be two (2) in-course tests. Both tests are equally weighted and each will be completed in class and will
take the format of multiple choice, True/False and/or short answer questions.

Group Project 30%

Groups will be assigned by the Instructor and a Group List will be posted on OurVLE. On this project, you will
collaborate with your classmates, in the same way you would if you were working in industry. Each group will select
one of the individual information systems development business situation being developed by a member of the
group. The Group will improve on all aspects of the individual information systems development solution as
necessary, create a design specification for the solution presented as an Entity Relationship Diagram (ERD) and
create a prototype using Microsoft® Access for the business situation. Each group will present a solution for the
business situation in class. The presentation should include a brief overview of the business case and a demo of the
prototype. The presentation will be graded and is worth 5%. Therefore, the documentation and the prototype will
be worth 25%. It is mandatory to evaluate your team members; peer evaluation form can be downloaded from
OurVLE. Table 2 provides an outline of the deliverables for each group’s solution. Each deliverable is to be uploaded
to OurVLE by one member of the group by 6:00 p.m. on the due date. Absolutely NO LATE or emailed
submissions will be accepted

The project must be done in groups of three to four (3-4) students. The project involves the analysis and design of
an information system using Microsoft® Access for an organization. You are responsible for locating this organization
and identifying the problem for which an IS will be developed. There are four project deliverables: Project Proposal
(8%), Requirements Determination and Structuring (15%), Design Specification (7%) and Prototype for New System
(10%). In the last phase the students submit a project report (which compiles all the earlier documentation) and
present their prototype to the class and faculty. The project report should include a title page and a ‘clickable’ table
of content. In view of the greater level of effort required for analysis and design, more of the marks were assigned
to requirements determination and structuring and design specification phases. A detailed list of contents for the
deliverables in each phase is provided in Table 2. Each project deliverable is to be uploaded to OurVLE by one
member of the group by 6:00 p.m. on the due date.

~3~
The Exam 50%
A two (2) hour examination will be conducted at the end of the course. The final examination will be based on all
the material covered in the assigned chapters and any other materials that were discussed in class.

Class Approach
What we do during class will vary throughout the semester. Time will be devoted to discussion of reading material
and to lecture. Lecture will often make use of PowerPoint slides. Because I realize that learning is deepened through
experience, we will also spend class time doing. That includes creating models, diagrams, and where possible design
databases. Time will also be devoted to working on cases covered in the text or any other assigned material. In
addition, you will have the opportunity to use project management tool to create and manage your project, use a
CASE tool to create data flow, entity relationship and use case diagrams. Using these applications to create these
diagrams help you to appreciate how systems analysts use tools to improve productivity and manage activities or
requirements during each phase in the systems development cycle. Throughout the semester it is expected that
students will actively participate in each session. Class participation is the active engagement in questions and
answers, taking part in analysis of business situations, and contribution of comments in class sessions.

Course Schedule

Session Date Topic Reading/ Assignment/Events/Deadlines

1  Welcome, Course Introduction,  Chapters 1, 3 & 5
Overview  Identify a problem in an organizations
 Expectations & evaluation methods
 Systems Analysis & Design: An
Overview
2  Initiating and Planning Systems
Development Projects
o Project Feasibility
 Managing the Information Systems
Project
o Gantt & Pert Charts
3  CASE Tool & Project Management
Software
o Overview of Dia
4  Determining System Requirements
& Structuring System Process
Requirements

~4~
 Session Date Topic Reading/ Assignment/Events/Deadlines
5  BPM & Data Flow Diagrams  Read Use Case Diagrams: An
Introduction
6  Data Flow & Use Case Diagrams
7  Structuring System Data
Requirements
 ER Diagramming
8 NO CLASS – SPORTS DAY
9  ER Diagramming
10  Designing Databases
 Designing Forms and Report
11  Deployment and Maintenance of
Information Systems
12  Review & Catch-up
13  Information System Showcase  DUE : Upload Project Document &
Prototype by 4:00 p.m. Peer
evaluations & FSS Accountability
statements MUST be submitted to
MSBM (South) front office by close of
business.

Prescribed Text, Readings & Course Materials

Required Text
1. Hoffer, Jeffrey A., George, Joey F. & Valacich, Joseph S., (2011). Modern Systems Analysis and Design, 6/E.
Prentice Hall. ISBN-10: 013608821X.

Recommended Texts
1. Kendall, Kenneth E. & Kendall, Julie E., (2011). Systems Analysis and Design, 8/E. Prentice Hall. ISBN-10:
013608916X.
2. Whitten, Jeffrey L. & Bentley, Lonnie D., (2005). Systems Analysis and Design Methods, 7/E. McGraw-
Hill/Irwin. ISBN-10: 0073052337.

Additional Readings and Handouts

Additional readings on topics and real world cases may be provided. These readings should be considered only as a
guide to the topic and will need to be supplemented by your own research. Useful reading for this course can be
found in IS Journals, other IS textbooks and computer magazines, for example:

Computerworld, CIO, Crossroads (ACM): The ACM Student Magazine, InfoWorld, NetworkWorld.

~5~
Course Materials
The following software packages will be used/utilized in this course:

 Dia – http://dia-installer.de/index_en.html – Modeling tool CASE tool, available free for non-commercial
use from http://www.qsee-technologies.com/downloads.htm

General Guidelines
1. All electronic devices (e.g., cell phones, pagers, palm pilots) are considered unnecessary distractions and
are to be placed on silent or turned off during class. If a student must take a call, then the student is
expected to leave the classroom to take that call and only return when the call has been terminated. A
student who fails to comply with this guideline will be asked to leave the class.

2. Students are reminded that for all written work submitted, in this course the group project, they must
ensure that the work submitted is original work. Groups who submit the work of others as your own, or
copying, or failing fully to acknowledge the sources from which materials were adopted/adapted are serious
academic misdemeanors for which appropriate penalties apply. A high standard of presentation is expected
in your work.

3. The final grade of “F” will be given to any assignment where plagiarism or cheating has occurred. And, this
behaviour will be brought to the FSS Dean’s office when additional sanctions may be applied as per The
University of the West Indies Regulation on plagiarism and cheating.

Date Revised: May 2022

~6~