CS272 – SYSTEMS ANALYSIS AND DESIGN

COURSE SYLLABUS

I. COURSE OVERVIEW

A. Course Number : CS272

B. Course Title : Systems Analysis and Design
C. No. of Units : 3 Units
D. Semester Offered : First Semester
E. Lecturer : Oneil B. Victoriano
F. Consultation Hours : 10:00–11:00am, 3:30-5:30pm MWF
G. Course Description

This course provides an introduction to Systems Analysis and Design. Topics

include analyzing the business case, requirements modeling, enterprise
modeling, and development strategies. Students also learn about data design,
the user interface, input, and output design, system architecture, systems
implementation and systems operations and support.

H. General Objectives:

This course will serve as an avenue for enhancing student’s skills in software
development specifically on systems planning, analysis, design,
implementation and support. Students will be able to translate business
requirements into information systems that support a company’s short- and
long-term objectives.

I. Course Objectives:

A much better understanding of the entire software development life cycle:

from analyzing the business case to implementation of an improved system
Improved communication skills, both oral and written, wherein students will
able to communicate with both technical and non-technical people using
proper tools.
Improved software design and development skills, wherein students will be
able to find solutions to problems of an existing system and be able to
recommend more efficient implementations.

J. Linkage with Subsequent Courses

This course will be the foundation for the CS 315 -Practicum/Major Project
course. Skills that students learn in this course will be necessary for the
implementation of the information system that they intend to pursue.

Page 1 of 11
K. Values to be integrated

This course aims to develop the critical thinking skills of the students as they
try to portray the role of a systems analyst. They are expected to become good
development planners equipped with the proper knowledge and values as
they try to formulate humane decisions and solutions to real-world issues.

L. Textbook and References

1. Gary Shelly, Thomas Cashman, Harry Rosenblatt, Systems Analysis and

Design, Course Technology, 2010 - Textbook
2. John Satzinger, Robert Jackson, Stephen Burd Systems Analysis and Design in a
Changing World, Course Technology, 2010
3. Kenneth Kendal and Julie Kendall, Systems Analysis and Design, Prentice Hall,
2010
4. Jeffrey Hoffer, Joey George, Joseph Valacich, Modern Systems Analysis and
Design, Prentice Hall, 2010
5. Roger Pressman, Software Engineering A Practitioner’s Approach, McGraw Hill,
2009

Page 2 of 11
II. COURSE OUTLINE

1. Introduction to Systems Analysis and Design

1.1. The Impact of IT
1.2. Information System Components
1.3. Understanding the Business
1.4. Impact of the Internet
1.5. How Business Uses Information Systems
1.6. Information System Users and Their Needs
1.7. Systems Development Tools and Techniques
1.8. Systems Development Methods
1.9. The Systems Development Life Cycle (SDLC)
1.10. Information Technology Department
1.11. The Systems Analyst Position

2. Analyzing the Business Case

2.1. Strategic Planning
2.2. Information Systems Project
2.3. Evaluation of Systems Request
2.4. Overview of Feasibility
2.5. Evaluating Feasibility
2.6. Setting Priorities
2.7. Preliminary Investigation Overview

3. Financial Analysis Tools

3.1. Describing Costs and Benefits
3.2. Cost-Benefit Analysis
3.3. Payback Analysis
3.4. Return on Investment Analysis
3.5. Present Value Analysis

4. Requirements Modeling
4.1. Systems Analysis Phase Overview
4.2. Joint Application Development
4.3. Rapid Application Development
4.4. Modeling Tools and Techniques
4.5. System Requirements Checklist
4.6. Future Growth, Costs and Benefits
4.7. Fact-Finding
4.8. Interviews
4.9. Other Fact-Finding Techniques
4.10. Documentation
4.11. Preview of Enterprise Modeling

5. Data and Process Modeling

5.1. Enterprise Modeling Tools
5.2. Entity-Relationship Diagrams

Page 3 of 11
 5.3. Data Flow Diagrams
5.4. Data Dictionary
5.5. Process Description Tools
5.6. Logical vs. Physical Models

6. Data Design
6.1. Data Design Concepts
6.2. DBMS Concepts
6.3. Web-based Database Design
6.4. Data Design Terminology
6.5. Data Relationships
6.6. Normalization
6.7. Steps in Database Design
6.8. Database Models
6.9. Data Storage
6.10. Data Control

7. Development Strategies
7.1. Development Strategies Overview
7.2. Web-based Software Trends
7.3. Software Outsourcing Options
7.4. In-House Software Development Options
7.5. Role of the Systems Analyst
7.6. Cost-Benefit Analysis Software Acquisition Example
7.7. Completion of Systems Analysis Tasks
7.8. The Transition to Systems Design
7.9. Systems Design Guidelines
7.10. Prototyping
7.11. Using Codes During System Design

8. Output and User Interface Design

8.1. User Interface Design
8.2. Input Design
8.3. Output Design Issues
8.4. Printed Output

9. System Architecture
9.1. System Architecture Checklist
9.2. Planning the Architecture
9.3. Client/Server Architecture
9.4. Impact of the Internet
9.5. Processing Methods
9.6. Network Models
9.7. System Management and Support
9.8. Systems Design Completion

Page 4 of 11
III. COURSE SYLLABUS

LECTURE

ACTIVITIES/
WEEK # TOPIC(S) LEARNING OBJECTIVES
APPROACHES
– Reach classroom agreements with teacher
– Express the importance of SAD in the field of Computer Science
– Appreciate the value of this course for their possible career as systems
analysts, designers and developers
– Discuss the impact of information technology on business
– Define an information system and describe its components
Orientation – Use profiles and models to understand business functions and operations
 LECTURE
1 Introduction to Systems – Explain how the Internet has affected business strategies and relationships
 ASSIGNMENT
Analysis and Design – Identify various types of information systems and explain who uses them
– Explain systems development tools, including modeling, prototyping, and
CASE tools
– Distinguish between structured analysis and object-oriented methodology
– Describe the systems development life cycle
– Discuss the role of the information technology department and the systems
analysts who work there
– Explain the concept of a business case and how a business case affects an IT
project
– Describe the strategic planning process and why it is important to the IT
team
– Explain the purpose of a mission statement  LECTURE
Analyzing the Business
2 – Describe the SDLC, and explain how it serves as a framework for systems  QUIZ #1
Case
development and business modeling  ASSIGNMENT
– List the reasons for information systems projects and the factors that affect
such projects
– Explain the initial review of systems requests and the role of the systems
review committee
– Define operational feasibility, technical feasibility, economic feasibility, and
schedule feasibility  LECTURE
Analyzing the Business
3 – Describe the steps in a preliminary investigation and the end product of an  QUIZ #2
Case
investigation  ASSIGNMENT
– Write a preliminary investigation report given business specifications
– Define economic feasibility
– Classify costs and benefits into various categories, including tangible or  LECTURE
4 Financial Analysis Tools intangible, direct or indirect, fixed or variable, and developmental or  QUIZ #3
operational  ASSIGNMENT
– Understand chargeback methods and how they are used

Page 5 of 11
 – Use payback analysis to calculate the length of time that it takes for a project
to pay for itself
– Use return on investment analysis to measure a project’s profitability
– Use present value analysis to determine the value of a future project
measured in current dollars
– Describe the systems analysis phase activities and the end product of the
systems analysis phase
– Understand joint application development (JAD) and rapid application
development (RAD)
– Explain how systems analysts use a functional decomposition diagram
(FDD)  LECTURE
5 Requirements Modeling – Describe the Unified Modeling Language (UML) and explain use case  QUIZ #4
diagrams and sequence diagrams  ASSIGNMENT
– List and describe system requirements, including outputs, inputs, processes,
performance, and controls
– Explain the importance of scalability in system design
– Define total cost of ownership (TCO) and explain the concept
– Define total cost of ownership (TCO) and explain the concept
– Use fact-finding techniques, including interviews, documentation review,
observation, questionnaires, sampling, and research
6 Requirements Modeling – Conduct a successful interview  PRELIM EXAM
– Develop effective documentation methods to use during systems
development
– Describe enterprise modeling concepts and tools, including entity-
relationship diagrams, data flow diagrams, a data dictionary, and process
Data and Process  LECTURE
7 descriptions
Modeling  ASSIGNMENT
– Explain how entity-relationship diagrams provide an overview of system
interactions
– Describe the symbols used in data flow diagrams and explain the rules for
 LECTURE
Data and Process their use
8  SEATWORK
Modeling – Draw data flow diagrams in a sequence, from general to specific
 ASSIGNMENT
– Explain how to level and balance a set of data flow diagrams
– Describe how a data dictionary is used and what it contains
 LECTURE
Data and Process – Use process description tools, including structured English, decision tables,
9  QUIZ #6
Modeling and decision trees
 ASSIGNMENT
– Describe the relationship between logical and physical models
– Explain data design concepts and data structures
– Describe file processing systems and various types of files
 SEATWORK
– Understand database systems and define the components of a database
10 Data Design  LECTURE
management system (DBMS)
 ASSIGNMENT
– Describe Web-based data design and characteristics
– Explain data design terminology, including entities, fields, common fields,

Page 6 of 11
 records, files, tables, and key fields
– Describe data relationships, draw an entity relationship diagram, define
cardinality and use cardinality notation
– Explain the concept of normalization
– Understand the steps in database design
– Describe the hierarchical, network, relational, and object-oriented database
models
– Explain data warehousing and data mining
– Differentiate between logical and physical storage and records
– Explain data control measures
– Describe software trends, including the concept of software as a service
– Explain software acquisition alternatives, including traditional versus Web-
 SEATWORK
based software development strategies
 LECTURE
11 Development Strategies – Describe software outsourcing options, including the role of service
 QUIZ #7
providers
 ASSIGNMENT
– Explain the advantages and disadvantages of developing software in-house
versus other alternatives
– Explain cost-benefit analysis and financial analysis tools
– Explain the differences between a request for proposal (RFP) and a request
for quotation (RFQ)
– Describe the contents of the system requirements document  LECTURE
12 Development Strategies
– Explain the transition from systems analysis to systems design, and the  MIDTERM EXAM
difference between logical and physical design
– Explain the transition to systems design and the importance of prototyping
– Discuss guidelines for system design, and explain the importance of codes
13 – Major Project Proposal Defense  REPORTING
– Explain the concept of user interface design and human-computer
interaction, including the basic principles of user-centered design
– List specific guidelines for user interface design
Output and User Interface  LECTURE
14 – Describe user interface techniques, including screen elements and controls
Design  ASSIGNMENT
– Explain input design concepts, techniques, and methods
– Describe guidelines for data entry screen design
– Use validation checks for reducing input errors
– Design effective source documents and input controls
Output and User Interface – Discuss output design issues and various types of output  LECTURE
15
Design – Design various types of printed reports and suggest output controls and  QUIZ #8
security
– Provide a checklist of issues to consider when selecting a system
architecture
 LECTURE
16 System Architecture – Describe servers, server-based processing, clients, and client-based
 QUIZ #9
processing
– Explain client/server architecture, including tiers, const-benefit issues, and
Page 7 of 11
 performance considerations
– Describe the impact of the Internet on system architecture
– Explain the difference between online and batch processing
– Define network topology, and provide examples of hierarchical, star, bus,
and ring network models
– Explain network protocols and licensing issues
– Explain system management tools and techniques, including performance  LECTURE
17 System Architecture
management, system security, fault management, backup, and disaster  ASSIGNMENT
recovery
– Describe the systems design specification and explain the contents of each
section
18 FINAL EXAM FINAL EXAM

LABORATORY

WEEK # TOPIC(S) LEARNING OBJECTIVES ACTIVITIES/ APPROACHES

 Chapter 1 Case Studies: New Century
Introduction to Systems – Learn to answer Case Study dealing with different
1 Health Clinic & Original Kayak
Analysis and Design Information Systems issues
Adventures
 Chapter 2 Apply your Knowledge: Last
Analyzing the Business – Learn to answer Case Study dealing with Evaluation of Chance Securities; Case Studies: New
2
Case Systems Requests issues Century Health Clinic, Personal Trainer
Inc.
Analyzing the Business – Learn to answer Case Study dealing with Setting  Chapter 2 Case Studies: Action Office
3
Case Priorities and Project Feasibility issues Products, Original Kayak Adventures
– Learn to use Financial Analysis assessment that would
4 Financial Analysis Tools  Toolkit Part 3: Projects 1-4
evaluate Economic Feasibility issues

– Learn to answer Case Study dealing with systems  Chapter 3 Case Studies: New Century
5 Requirements Modeling
requirements checklist issues Health Clinic

– Learn to answer Case Study dealing with Fact-finding  Chapter 3 Case Studies: Personal Trainer
6 Requirements Modeling
issues Inc.
Data and Process  Chapter 4 Case Studies: New Century
7 – Learn to use prototyping tools to create DFDs and ERDs
Modeling Health Clinic
Data and Process  Chapter 4 Case Studies: Personal Trainer
8 – Learn to use prototyping tools to create DFDs and ERDs
Modeling Inc

Data and Process  Chapter 4 Apply your Knowledge:

9 – Learn to use prototyping tools to create DFDs and ERDs
Modeling Claremont School

Page 8 of 11
 – Learn to use DBMS software to create physical database
10 Data Design  ERD Laboratory Exercise/Assignment
structures

– Learn to answer Case Study dealing with other

11 Development Strategies  Chapter 5 Exercises Projects 1 – 4
development methodologies

– Learn to answer Case Study dealing with other

12 Development Strategies  Chapter 5 Personal Trainer Inc
development methodologies

13 – Major Project Proposal Defense

Output and User Interface – Learn to use prototyping tools or visual programming  Create User Interface Design Documentation
14 for the Major Project/Practicum
Design application to create graphical user interface

Output and User Interface – Learn to use prototyping tools or visual programming  Create User Interface Design Documentation
15 for the Major Project/Practicum
Design applications to create graphical user interface

 Create System Architecture Documentation for

16 System Architecture – Learn to use prototyping tools to create network models
the Major Project/Practicum
 Create System Architecture Documentation for
17 System Architecture – Learn to use prototyping tools to create network models
the Major Project/Practicum

18 FINAL EXAM

Page 9 of 11
IV. COURSE POLICIES

A. Class Policies
 An appointed class beadle will check the attendance of the students in
every session. As stipulated in the handbook, the students are only
allowed to commit 10 absences. There will be no excused absences. The
excuse letter will only be regarded for the purposes of granting make-up
exams and activities. For more information, please refer to the General
School Policy regarding attendance in the Student Handbook.
 All cellular phones must be put in silent mode for the duration of the
class, whether inside the classroom or laboratory. Anybody caught
violating this rule for three times will be given a penalty, which depends
on the circumstances of the offense.
 Candies are the only food allowed inside the classroom and laboratory
areas.
 No one is allowed to go out of the classroom during the class period.
Anybody who violated this rule without proper permission from the
teacher will also be given a penalty.

B. Course Requirements

 Take quizzes and long quizzes

 Pass papers, assignment and projects
 Submit laboratory activities
 Take each of the major exams
 Major Project Proposal Defense

C. Grading System

Final Grade

 30% Major Project Proposal Defense

 70% Prelim/Miderm/Prefinals Grades

Prelim/Miderm/Prefinals Grades

 50% Quizzes/Papers/Assignments
 30% Laboratory Activities
 20% Periodical Exam

D. Special Arrangements

Make-up Examinations and Laboratory Activities may be granted to students

who missed them provided that the reasons are valid and documents are
shown to support them.

Page 10 of 11
E. Software Used

 Microsoft Word/PowerPoint/Excel 2003

 Microsoft Project 2003
 Microsoft Visio 2003
 Microsoft Visual Studio .Net or any Visual programming application
 Microsoft Access 2003
 Sequel Server 2003
 MySQL other DBMS software available

Page 11 of 11