k201/204 Exam 1 Vocabulary

Vocabulary flashcards covering core concepts, frameworks, software systems, and SDLC methodologies for k201/204 Exam 1.

Data

Raw and unorganized facts/figures without inherent meaning.

Information

Data that has been organized, structured, and processed to give it meaning.

Knowledge

Information combined with experience, context, and judgement to draw conclusions or make decisions.

Sociotechnical System

A system where social elements (people, processes) and technical elements (hardware, software, data) are interdependent and must work together.

PPT Framework

The four essential components of an information system: 1. People, 2. Processes/Procedures, 3. Data, 4. Technology.

TPS

Transaction Processing System - Information systems that handle routine, repeatable operational tasks—such as scanning barcodes at checkout, paying employees, and managing inventory.

DSS

Decision Support System - An interactive system that helps managers analyze data, compare alternatives, and evaluate possible outcomes under different assumptions without replacing managerial judgment.

ERP System

Enterprise Resource Planning system - Large, integrated platforms that unify data and processes across the entire organization into a single database.

Network Effect

Occurs when a system or service becomes more valuable as more people use it (e.g., marketplaces, social platforms), creating high barriers to entry for rivals.

Business Problem

A specific problem you need to clearly define before building, automating, or buying a system.

Business Requirement

A clear, testable statement of what a system must accomplish or support so the organization can achieve a business purpose.

Stakeholder Business Requirement Gathering

Gathering requirements from multiple stakeholders because different stakeholders have different definitions of success; ignoring end users leads to missed daily workflows, errors, frustration, and manual workarounds.

SDLC

System Development Life Cycle - A prescribed plan for developing a system.

Testing Phase

The phase of the SDLC where the team gathers verifiable evidence that the system behaves correctly under specific conditions prior to deployment.

Normal Use Case

Used for testing expected workflow (e.g., an employee requests one vacation day, coverage remains above the threshold, and the manager approves the request).

Edge Case

Used for testing unusual, boundary, conflicting, missing, or high-risk conditions (e.g., two employees in the same critical role request the same shift off, and approving both would violate the coverage threshold).

Acceptance Test

A test that states a specific, verifiable condition that must be true for the feature to be considered complete using the Given/When/Then structure.

Software Solution Types

The three types of software solutions: 1. Buy (commercial off-the-shelf software), 2. Configure/Customize (adapting existing commercial software), 3. Build (custom software development).

System Failure Cause

A system finished on time, within budget, and without defects can still fail if it fails to solve the right business problem.

Waterfall SDLC Approach

A linear development method where one major stage is completed before moving to the next.

Agile SDLC Approach

A development approach using small increments, frequent feedback, and continuous adaptation.

Scrum

A structured Agile framework that organizes work into short, fixed-length cycles with regular reviews.

DevOps

Connects development, deployment, operations monitoring, and support so systems can be released and improved reliably.

Vibe Coding

Creating software primarily by describing what to build in natural language and letting AI generate much of the code.

Prototype

An early system used to explore ideas and gather reactions, not a production-ready system with full security, validation, scalability, and support.

Scope Creep

A new feature request that cannot be tied to a documented business objective and may unnecessarily expand the project's scope, cost, or timeline.

Production Signals

Post-launch measures such as error rates, complaints, adoption numbers, and support tickets that show whether a system is delivering value.

EIS

Enterprise Information System (software that supports and integrates core business processes across the entire organization) OR Executive Information System (an information system that provides executives with easy access to high-level summaries, dashboards, KPIs, and strategic information).

CRM System

Customer Relationship Management system - A system that helps an organization manage customer interactions, track sales pipelines, automate marketing, and log support tickets in a central database.

SCM System

Supply Chain Management system - Used to coordinate the flow of raw materials, demand forecasting, production scheduling, warehouse inventory, and supplier logistics.

Information Silo

Business data that is trapped in one department or system and cannot easily flow to other functions.

Problems Caused by Information Silos

1. Data inconsistency/errors, 2. Wasted time on manual data re-entry, 3. Lack of enterprise-wide visibility, 4. Poor customer service, 5. Higher IT maintenance costs, 6. Compliance/audit failures.

Flowchart

Illustrates the step-by-step actions a person or role performs.

Systems Map

Tracks how data moves between distinct software systems, databases, and departments.

Best of Breed Strategy

Choosing the best standalone software for each department instead of using one all-in-one suite (e.g., best CRM + best SCM).

Duplicate / Inconsistent Data

When multiple versions of the same record contain conflicting or incomplete information, creating a data-quality problem.

Integration Risk

Integration increases the speed and reach of an error; flawed assumptions, incorrect inventory counts, or bad data spread instantly across CRM, SCM, ERP, and executive dashboards.

SIS

Student Information System - The system that checks prerequisites, holds class seats, and sends data to the learning management system and billing office.

Scenario / What-if Analysis

Changing assumptions in a decision-support model to compare different outcomes, such as 10% versus 20% demand growth.

Fulfillment / Operations Purpose

Turns approved sales transactions into physical activity by allocating stock, packaging goods, and dispatching shipments.