Systems Analysis and Design Vocabulary

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/45

flashcard set

Earn XP

Description and Tags

Vocabulary flashcards covering Modules 12, 13, and 14 for Systems Analysis and Design (SAD), including project specification, requirements determination, business process improvement approaches, problem identification frameworks, candidate solutions, and feasibility assessments.

Last updated 6:28 PM on 10/5/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

46 Terms

1
New cards

Preliminary Investigation

The initial step in the Systems Development Life Cycle (SDLC) conducted by a systems analyst to evaluate the current system, identify problems, determine project feasibility, and recommend whether to proceed.

2
New cards

Purpose of a Project

A clear statement that explains why a project is being undertaken, identifying the specific problem or opportunity to be addressed and guiding all decision-making.

3
New cards

Project Scope

The defined boundaries of a project that specify exactly what work, objectives, resources, and deliverables are included and excluded.

4
New cards

Scope Creep

The uncontrolled addition of extra tasks or features to a project beyond its original boundaries, leading to delay and budget overruns.

5
New cards

Data Gathering

The process of collecting information about an existing system and user requirements using methods such as interviews, questionnaires, observation, document analysis, and research.

6
New cards

Interview (Data Gathering)

A face-to-face data collection method in which an analyst asks users direct and follow-up questions to obtain rich, detailed information.

7
New cards

Questionnaire

A data collection method in which users answer written questions, enabling efficient, low-cost information gathering from many respondents.

8
New cards

Observation (Data Gathering)

A data collection method in which an analyst directly watches users perform daily operational tasks to reveal actual workflow and hidden issues.

9
New cards

Document Analysis

A data collection method involving the review of existing forms, reports, registers, receipts, and invoices to understand current organizational procedures.

10
New cards

Research (Data Gathering)

Gathering background information and industry best practices from books, internet resources, company archives, and past projects.

11
New cards

High-Level Investigation (Level 1)

The broadest level of preliminary investigation that provides a general system overview, identifying major issues, primary processes, main users, and core requirements.

12
New cards

Detailed Investigation (Level 2)

An in-depth investigation level focusing on detailed workflows, data flows, user responsibilities, and specific causes of operational problems.

13
New cards

Full Systems Analysis (Level 3)

A comprehensive analysis stage conducted when an organization plans to build a totally new system or undertake major system modifications.

14
New cards

Business Process Automation (BPA)

Applying technology to execute existing manual tasks faster and with fewer errors without significantly altering the underlying business process.

15
New cards

Business Process Improvement (BPI)

Making incremental changes to an existing process to optimize efficiency, quality, speed, or cost without completely redesigning it.

16
New cards

Business Process Re-engineering (BPR)

The radical redesign and complete transformation of existing business processes from scratch to achieve dramatic performance gains.

17
New cards

PIECES Framework

A diagnostic framework used to categorize and analyze problems in an information system under Performance, Information, Economics, Control, Efficiency, and Services.

18
New cards

Problem Analysis

The detailed study of a known issue to establish what is occurring, where it happens, who is affected, when it occurs, and its overall organizational impact.

19
New cards

Root Cause Analysis

An analytical technique used to uncover the underlying fundamental reason a problem exists rather than merely addressing surface symptoms.

20
New cards

Duration Analysis

An analysis technique that measures the time taken by each step in a business process to locate bottlenecks and reduce total processing duration.

21
New cards

Activity-Based Costing (ABC)

A costing methodology that assigns specific expenses to each individual activity performed within a business process.

22
New cards

Informal Benchmarking

The process of comparing an organization's systems, processes, or performance metrics with those of high-performing peers or industry standards.

23
New cards

Internal Benchmarking

A benchmarking practice where processes or operational units within the same organization are evaluated against one another.

24
New cards

External Benchmarking

A benchmarking practice comparing an organization's performance or systems against an independent outside organization.

25
New cards

Best-Practice Benchmarking

Studying peer organizations that demonstrate exceptional excellence in a specific operation to adopt their methods.

26
New cards

Innovative Technology

Modern or advanced technologies—such as AI, cloud computing, IoT, mobile apps, biometrics, and robotics—that deliver enhanced efficiency over conventional methods.

27
New cards

Outcome Analysis

An innovation technique that analyzes the final deliverables or outcomes of a process to evaluate if technology can improve product or service quality.

28
New cards

Technology Analysis

The practice of continuously monitoring emerging software and hardware solutions to evaluate if they can replace legacy systems.

29
New cards

Activity Elimination

A process-simplification strategy that identifies and removes steps that add no value, such as redundant approvals or duplicate data entry.

30
New cards

Candidate Solution

A potential technical or organizational system proposal developed to address an identified business problem.

31
New cards

Technical Feasibility

The assessment of whether an organization possesses or can acquire the hardware, software, network capacity, and technical expertise needed to support a system.

32
New cards

Economic Feasibility

The assessment of whether a project is financially practical, within budget, and capable of generating benefits that exceed costs.

33
New cards

Operational Feasibility

The assessment of how well a proposed system will fit into daily operations and whether managers and end users will adopt it.

34
New cards

Schedule Feasibility

The assessment of whether a project can be completed within required deadlines and timeframe constraints.

35
New cards

Project Feasibility Assessment

A formal evaluation conducted prior to system development to verify if a project is achievable, cost-effective, and aligned with organizational objectives.

36
New cards

Request for Information (RFI)

An exploratory document sent to suppliers early in planning to gather market information regarding available products, technologies, and services without pricing or purchasing commitments.

37
New cards

Request for Proposal (RFP)

A formal procurement document sent to suppliers after requirements are specified, requesting complete proposals including technical plans, timelines, support services, and pricing.

38
New cards

Return on Investment (ROI)

A metric evaluating financial gain relative to cost, calculated using ROI=Benefits−CostsCosts×100%\text{ROI} = \frac{\text{Benefits} - \text{Costs}}{\text{Costs}} \times 100\% or ROI=Net BenefitTotal Cost×100%\text{ROI} = \frac{\text{Net Benefit}}{\text{Total Cost}} \times 100\%.

39
New cards

Cost-Benefit Analysis (CBA)

A quantitative technique comparing total implementation and maintenance costs of a project against its expected quantitative and qualitative benefits.

40
New cards

Development Costs

One-time upfront capital costs incurred during system creation, including hardware purchases, software development, installation, testing, and initial staff training.

41
New cards

Operational Costs

Recurring expenses required to keep a system running post-implementation, such as licensing fees, technical support, maintenance, utility costs, and backups.

42
New cards

Tangible Costs and Benefits

Project expenses and financial returns that can be directly measured and quantified in monetary terms, such as hardware costs or reduced labor spending.

43
New cards

Intangible Costs and Benefits

Project impacts that are difficult to assign a direct financial monetary value to, such as customer satisfaction, brand reputation, or user resistance.

44
New cards

Cash Flow

The tracking of funds moving into a project as financial benefits (cash inflows) and out of a project as expenses (cash outflows) across time.

45
New cards

Net Present Value (NPV)

The calculated difference between discounted future financial benefits and current costs, expressed as NPV=Present Value of Benefits−Present Value of Costs\text{NPV} = \text{Present Value of Benefits} - \text{Present Value of Costs}.

46
New cards

Break-Even Point

The time threshold at which accumulated project benefits equal accumulated project costs, marking the transition into positive financial profit.