Systems Analysis and Design (SAD) Midterm Reviewer

Vocabulary practice flashcards covering fundamental concepts, definitions, and components across Modules 1 through 4 of Systems Analysis and Design.

System

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

Input

Information or resources entering the system.

Process

Activities that transform the input.

Output

The result produced by the system.

Feedback

Information about the performance or results of a system used to evaluate or improve it, indicating what is happening.

Control

The rules, procedures, standards, or mechanisms that keep the system working properly and determine what action to take.

Information System (IS)

A combination of people, processes, data, and technology that work together to collect, process, store, and provide information to support operations and decision-making.

Systems Analysis

The process of studying a problem, understanding how the current system works, and identifying what users and the organization need (focusing on 'WHAT is needed?').

System Design

The process of planning how the proposed system will work and what it will look like (focusing on 'HOW will it work?').

Systems Analyst

A professional who studies business or organizational problems and helps design information systems that meet user and organizational needs, serving as a bridge between users/business and technology/IT.

Subsystem

A smaller system that is part of a larger system, possessing its own functions while working toward overall organizational objectives.

System Environment

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

System Boundary

The boundary that defines what is inside and outside a system.

Open System

A system that interacts with its environment; most real-world organizations are open systems.

Closed System

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

Data

Raw facts that have not yet been processed.

Information

Processed and organized data that has meaning.

TPS (Transaction Processing System)

A type of information system that records and processes routine day-to-day transactions, such as ATMs, POS systems, and payroll.

MIS (Management Information System)

A type of information system that produces reports and information to help managers monitor, manage operations, and make operational decisions.

DSS (Decision Support System)

A type of information system that assists managers in decision-making by analyzing data, models, and scenarios, supporting forecasting and what-if analysis.

EIS (Executive Information System)

A type of information system that supplies senior executives with summarized information and dashboards to support strategic decision-making.

ERP (Enterprise Resource Planning)

An integrated system that combines multiple core business functions (finance, HR, sales, inventory, purchasing, production) into one platform.

CRM (Customer Relationship Management)

A system that manages interactions and relationships with customers to improve customer satisfaction and service tracking.

Systems Thinking

An analytical mindset of seeing the bigger picture by understanding how interconnected components interact, how data flows, and where the root cause of a problem lies.

SDLC (System Development Life Cycle)

A structured process for planning, analyzing, designing, developing, testing, implementing, and maintaining an information system.

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., protect personal data, respond quickly, remain available).

DFD (Data Flow Diagram)

A graphical tool that shows how information moves between entities, processes, and data stores.

Use Case Diagram

A diagram that shows users and the specific functions they perform with the system.

ERD (Entity Relationship Diagram)

A diagram that shows data entities and how they relate to one another.

Wireframe

A design artifact that shows the planned layout of pages and interface elements.

Unit Testing

A level of testing that checks an individual component of a system.

Integration Testing

A testing stage that checks whether different system components work together properly.

System Testing

A testing stage that checks the behavior and performance of the complete, integrated system.

User Acceptance Testing

A testing stage that checks whether the completed system meets user needs and requirements.

Waterfall Model

An SDLC approach where phases follow a sequential order and requirements are planned early; suitable when requirements are stable.

Agile Model

An iterative and incremental SDLC approach that delivers work in short cycles, designed to adapt to feedback and evolving requirements.

Spiral Model

An SDLC model featuring repeated development cycles with a strong emphasis on risk analysis; suitable for complex, high-risk projects.

System Project Initiation

The early stage in which an organization identifies a need, examines a problem or opportunity, and determines whether an IS project deserves further investigation.

Problem

A current condition that prevents users or an organization from reaching a goal.

Opportunity

A chance to improve service, efficiency, accessibility, or decision-making.

Root-cause Analysis

An analysis approach that helps identify why a problem occurs instead of merely treating its symptoms.

5 Whys

A root-cause technique that involves asking 'Why?' repeatedly until the underlying cause of an issue becomes clear.

Fishbone Diagram

A diagram used in root-cause analysis that groups potential causes into people, process, technology, data, and environment.

Stakeholders

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

Users

People who will directly interact with the system.

Scope Creep

The uncontrolled expansion of project work beyond the agreed scope without proper review or approval.

Constraints

Limits imposed on a project, such as budget, schedule, staffing, infrastructure, or policy.

Assumptions

Conditions believed to be true for initial project planning but needing validation.

Risks

Uncertain events that may affect project objectives, either negatively or positively.

Feasibility

The evaluation of whether a proposed system appears practical and worthwhile across technical, economic, operational, schedule, and legal/regulatory dimensions.

Business Case

A justification document that explains why a project should be considered, summarizing the problem, expected benefits, costs, risks, and alternatives.

Project Charter / Initiation Brief

A document that records the initial direction, scope, objectives, stakeholders, constraints, and justification of a proposed project to keep the team aligned.