Systems Analysis and Design Practice Flashcards

These vocabulary flashcards cover the fundamental concepts of classic and modern SDLC models, systems analysis tools, feasibility metrics, and requirement engineering as detailed in the lecture transcript.

"Code and Fix" Approach

A 1950s–1960s method where developers coded without planning or documentation, addressing errors only after software crashes.

Systems Development Life Cycle (SDLC)

A risk-management strategy and roadmap used to organize human effort over time to manage uncertainty in project development.

Waterfall Model

A sequential development structure where each of the six classic phases (Feasibility, Analysis, Design, Code, Test, Deploy) must be verified before moving forward.

RA 9184

The Government Procurement Reform Act in the Philippines that legally requires government agencies to use Waterfall-style fixed prices and detailed specifications for bidding.

V-Model

A model designed for critical systems that bends the Waterfall structure into a "V", mapping verification (building) on the left side to validation (testing) on the right side.

Verification

The process of determining "Are we building the system right?" by checking if the product conforms to specifications.

Validation

The process of determining "Did we build the right system?" by checking if the software meets the actual needs of the user.

Incremental Model

A phased approach where the core system is built and delivered first, and additional features are added in subsequent pieces to provide early working software.

Rapid Application Development (RAD)

A prototype-focused approach developed by James Martin in the 1990s that emphasizes speed, user collaboration, and strict timeboxing.

Joint Application Design (JAD)

Collaborative workshops between users and developers used during the design phase of models like RAD.

Spiral Model

A risk-driven model created by Barry Boehm where the project starts small at the center and loops outward, with the radius representing the cumulative cost.

Implementation

The construction phase of development, such as coding and compiling on a developer's laptop, analogous to "cooking the meal."

Deployment

The delivery phase where the software goes live on a production server, analogous to "serving the meal."

Baseline

A "frozen" set of requirements where any modifications require formal approval.

Agile Manifesto (2001)

A declaration by 17 experts shifting software development toward adaptability, functional increments, continuous feedback, and short delivery cycles.

Scrum

An Agile framework that replaces long phases with short, cross-functional development periods called Sprints lasting 1 to 4 weeks.

Kanban

A visual management method (To Do -> Doing -> Done) that uses WIP limits to flow work continuously, similar to a "sushi belt."

WIP (Work In Progress) Limit

An explicit cap on the maximum number of active tasks allowed in a workflow stage to eliminate bottlenecks.

Extreme Programming (XP)

An Agile engineering discipline involving practices like Pair Programming, Continuous Integration, and Test-Driven Development (TDD).

DevOps

An union of Developers and Operations using CI/CD pipelines to release software frequently while maintaining stability.

Operational Feasibility

An analysis of human and organizational factors, such as whether users will accept and effectively adopt a new system.

Technical Feasibility

An assessment of whether the organization has the necessary technology, expertise, and time to execute a project.

Economic Feasibility

An evaluation of the financial aspects of a project, including Return on Investment (ROI), costs, and benefits.

Sunk Costs

Past, unrecoverable expenses (such as money spent on a failed phase) that should not influence future investment decisions.

Present Value (PV)

A calculation that converts future cash flows into today's dollars using the formula $\text{Present Value } (P) = \frac{F}{(1 + i)^n}$.

Payback Analysis

Determining the time needed for accumulated benefits to equal total costs using $\text{Payback Period } (T) = \frac{\text{Development Costs } (D)}{\text{Annual Net Benefits } (P)}$.

Net Present Value (NPV)

The difference between the present value of total benefits and total costs; a project is feasible if $\text{NPV} > 0$.

Functional Requirements

Statements defining the specific services, functions, and behaviors the system must or must not execute.

Non-Functional Requirements

Constraints on the services offered by the system, such as response timing, performance, or standards compliance.

Enterprise Application

Software systems designed for company-wide management, such as ERP, CRM, or payment processing systems.

Legacy Systems

Outdated computer systems, methods, or applications that are still kept in active use.

Knowledge Management Systems (KMS)

Also called Expert Systems, these collect and manage organizational knowledge using inference rules and fuzzy logic to simulate human reasoning.

Negative Feedback

Informational feedback that provides data for corrective action in a dynamic system.

Strategic Information

Data used by top management for long-range planning, typically supported by Decision Support Systems (DSS).