CHAPTER 22: SYSTEM ANALYSIS AND DESIGN BASICS
BSIT 1A – Bachelor of Science in Information Technology
22.1 Introduction
System Analysis and Design (SAD) is the process of studying an existing
system or a proposed system to identify problems, requirements, and
solutions. It ensures that information systems meet user needs and
organizational objectives.
22.2 What is a System?
A system is a collection of components that work together to achieve a
common goal.
Components of a System
Input – Data entered into the system
Process – Actions performed on the data
Output – Information produced
Feedback – Information used to improve the system
Control – Policies and procedures that regulate the system
22.3 System Analysis
System analysis focuses on understanding what the system should
do.
Activities in System Analysis
Identify problems in the current system
Gather user requirements
Study system feasibility
Define system scope and objectives
Fact-Finding Techniques
Interviews
Questionnaires
Observation
Document review
22.4 Feasibility Study
A feasibility study determines whether a proposed system is practical.
Types of Feasibility
1. Technical Feasibility – Availability of technology and skills
2. Economic Feasibility – Cost vs. benefit analysis
3. Operational Feasibility – User acceptance and usability
4. Schedule Feasibility – Time constraints and deadlines
22.5 System Design
System design focuses on how the system will work.
Types of Design
Logical Design – Abstract representation (what the system does)
Physical Design – Actual implementation (hardware, software,
network)
22.6 Design Tools and Techniques
a. Data Flow Diagram (DFD)
Shows how data moves through the system
Includes processes, data stores, data flows, and external entities
b. Flowcharts
Visual representation of program or system logic
c. Entity Relationship Diagram (ERD)
Represents database structure
Shows entities, attributes, and relationships
d. Use Case Diagram
Shows interactions between users and the system
22.7 System Documentation
Documentation provides detailed information about the system.
Types of Documentation
User Documentation – Guides for end users
System Documentation – Technical details for developers and
administrators
22.8 Role of the System Analyst
Acts as a bridge between users and developers
Translates business requirements into technical specifications
Ensures system objectives are achieved
22.9 Importance of System Analysis and Design
Reduces system failure
Improves system quality and efficiency
Ensures user satisfaction
Minimizes development risks
22.10 Summary
This chapter discussed system analysis and design fundamentals,
including system concepts, analysis activities, feasibility studies, design
tools, documentation, and the role of the system analyst. These concepts
are essential for building effective and efficient information systems.