Systems Analysis and Design (SAD 2026) Study Guide

Flashcards covering core terminology, concepts, testing types, artifacts, and life cycle methodologies from the SAD 2026 lecture.

System

A group of interconnected components that work together to achieve a specific or common goal.

IPO Model

The basic systems model where Input enters, Process transforms it, and Output is the resulting product or service.

Feedback

Information used to evaluate or improve the performance of a system.

Control

The rules or mechanisms that keep a system operating properly.

Information System (IS)

A system combining people, processes, data, and technology to collect, process, store, and provide information.

Systems Analysis

The phase that investigates the current situation, identifies user needs, and determines what is needed ("WHAT is needed?").

System Design

The phase that plans the proposed solution, defining features, data structures, interface, architecture, and security ("HOW will it work?").

Subsystem

A smaller system that is part of a larger system, having its own functions while contributing to the larger system's goal.

System Decomposition

The process of breaking a complex system down into smaller subsystems to make it easier to understand and manage.

Systems Thinking

An approach that looks at the whole system, how components interact, how information flows, and how a change or failure in one part affects others.

System Environment

Everything outside the system that can influence or be influenced by it.

System Boundary

The perimeter that defines what is inside and what is outside the system being studied.

Open System

A system that actively interacts with its external environment.

Closed System

A system that has little or no interaction with its external environment.

Data

Raw facts that have not yet been processed.

Information

Processed or organized data that has meaning and can support decision-making.

Transaction Processing System (TPS)

An information system that records routine, day-to-day business transactions.

Management Information System (MIS)

An information system that provides managers with structured reports to monitor and manage operations.

Decision Support System (DSS)

An information system that analyzes data, models, and scenarios (e.g., what-if analysis) to support decision-making.

Executive Information System (EIS)

An information system that supplies summarized information, market trends, and key performance indicators (KPIs) for senior and strategic decisions.

Enterprise Resource Planning (ERP)

A software system that integrates various core business functions (such as sales, inventory, finance, and HR) into a unified system.

Customer Relationship Management (CRM)

An information system designed to manage and organize interactions, purchases, complaints, and preferences regarding customers.

System Development Life Cycle (SDLC)

A structured process for developing and maintaining an information system through planning, analysis, design, development, testing, implementation, and maintenance.

Functional Requirement

A statement specifying what the system must do (e.g., register a student, record payments).

Non-functional Requirement

A statement specifying how well the system must perform (e.g., speed, security, usability, availability).

Unit Testing

A testing activity that verifies the functionality of an individual component or function.

Integration Testing

A testing activity that evaluates whether separate components work together properly.

System Testing

A testing activity that checks the complete, end-to-end operation of the entire system.

User Acceptance Testing (UAT)

A testing activity where end users evaluate whether the system satisfies their operational requirements and is acceptable for production use.

Waterfall Model

A sequential SDLC methodology where phases follow in order and requirements are planned upfront, best suited for stable, well-understood requirements.

Agile Model

An iterative and incremental SDLC methodology characterized by short delivery cycles, frequent user feedback, and high adaptability to changing requirements.

Spiral Model

An SDLC methodology where development advances through iterative cycles with an explicit, heavy emphasis on risk analysis.

Data Flow Diagram (DFD)

A system design artifact that illustrates how data moves among external entities, processes, and data stores.

Use Case Diagram

A design diagram that shows the users or actors and the specific functions they execute with the system.

Entity Relationship Diagram (ERD)

A design diagram depicting data entities and the relationships among them within a database.

Prototype

An early, working model or preview version used to demonstrate, explore, and test a proposed system before full development.

System Project Initiation

The preliminary stage where an organization identifies a business need or problem and determines whether a project is justified and worth investigating.

5 Whys

A root-cause analysis technique that involves asking "Why?" repeatedly to uncover the foundational cause of a problem.

Fishbone Diagram

A root-cause analysis tool that visualizes and categorizes possible causes of a problem under categories such as people, process, technology, data, and environment.

Stakeholders

Individuals or groups who affect, fund, approve, build, operate, or are affected by a project.

Scope Creep

The uncontrolled, unapproved growth or expansion of a project beyond its agreed-upon scope boundaries.

Constraint

A fixed boundary or restriction placed on a project, such as limitations on budget, schedule, staffing, or policy.

Assumption

A factor or condition temporarily considered to be true during planning that still requires verification.

Risk

An uncertain event or condition that, if it occurs, can have a positive or negative impact on project objectives.

Business Case

A foundational document explaining why a project should be considered, summarizing the problem, strategic alignment, preliminary costs, feasibility, and expected benefits.

Project Charter

A formal document (or initiation brief) recording the preliminary direction, justification, scope, stakeholders, and SMART objectives of a project prior to detailed analysis.