System Analysis and Design - Vocabulary Flashcards

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

1/61

flashcard set

Earn XP

Description and Tags

Comprehensive vocabulary flashcards detailing core definitions, concepts, life cycle models, fact-finding methods, data modeling, normalization rules, and testing strategies from the System Analysis and Design module.

Last updated 10:03 PM on 8/25/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

62 Terms

1
New cards

System

An organized set of components which interact in a regulated fashion to achieve a goal, providing a service across both computer-related and non-computer-related elements.

2
New cards

Product

An enabling element of a larger system, typically a physical device or entity with a specific capability (form, fit, and function) and specified performance level that generally lacks intelligence to self-apply without human assistance.

3
New cards

Tool

A supporting product that enables a user or system to leverage its own capabilities and performance to more effectively or efficiently achieve mission objectives.

4
New cards

Capability

The transformational processing that adds value to inputs and produces an output, encompassing both functionality and performance attributes.

5
New cards

Physical Systems

Tangible entities that can be felt and touched, which may be static (like desks) or dynamic (like computer systems).

6
New cards

Abstract Systems

Conceptual, non-physical entities such as formulas, representations, or models of a real system.

7
New cards

Open Systems

Systems that actively interact with their surrounding environment, such as information systems.

8
New cards

Closed Systems

Conceptual systems that do not interact with their environment.

9
New cards

Strategic Information

High-level information required by topmost management for long-term policy setting and decision making.

10
New cards

Managerial Information

Information required by middle management used for making short-term decisions and organizational plans.

11
New cards

Operational Information

Daily or short-term information required at the operational level to carry out day-to-day business activities.

12
New cards

Transaction Processing System (TPS)

An information system that provides information for processing daily operational transactions of an organization, such as order processing or bank entries.

13
New cards

Management Information System (MIS)

An information system designed to cater to middle management's needs for short-term planning and decision making.

14
New cards

Decision Support System (DSS)

An information system that provides top management with strategic information required for long-term decision making.

15
New cards

System Analysis

The process of investigating an existing or proposed system, identifying problems, gathering requirements, and using the information to recommend improvements.

16
New cards

System Design

The process of planning a new business system or one to replace or complement an existing system.

17
New cards

System Analyst

The professional who guides the development of an information system by matching information system objectives with the goals of the organization.

18
New cards

Waterfall Life Cycle Model

A software development lifecycle model where development phases are organized in a strict linear, sequential order.

19
New cards

Throwaway Prototype

A preliminary working model built based on currently known requirements to help clients gain an actual feel of the system and refine requirements before final development.

20
New cards

Spiral Life Cycle Model

A risk-driven software development model organized in cycles or spirals, accommodating specification, prototyping, simulation, and waterfall approaches based on project risks.

21
New cards

Class

In object-oriented design, a template and collection of similar objects that defines their common basic attributes and operations.

22
New cards

Abstraction

The process of observing a set of similar objects, identifying common characteristics of concern to the system under study, and omitting irrelevant details.

23
New cards

Inheritance

An object-oriented feature where a new class is derived from an existing class to reuse functionality and save development time and effort.

24
New cards

Encapsulation

Also known as data hiding, a technique that separates the internal functioning of an object from its external interface to protect code against unintended external changes.

25
New cards

Feasibility Study

A preliminary evaluation undertaken before real project work starts to analyze potential solutions and determine the likelihood of project success across technical, economic, operational, and legal dimensions.

26
New cards

Fact Finding

The formal process of using research, interviews, questionnaires, record reviews, and observation to collect information about systems, requirements, and preferences.

27
New cards

Decision Tree

A tree-like graphical structure representing conditions, priorities, and subsequent possible actions along traversed branches from left to right.

28
New cards

Decision Table

A two-dimensional matrix divided into condition stub, action stub, condition entry, and action entry used to define complex business rules and combinations of conditions.

29
New cards

Structured English

A decision documentation tool that uses narrative statements with logical structures (such as IF, THEN, ELSE) and data dictionary terms to state process rules clearly.

30
New cards

Data Dictionary

A structured catalog or repository containing rigorous definitions and details of data elements, data structures, data flows, data stores, and processes.

31
New cards

Data Flow Diagram (DFD)

A graphical representation showing the movement of data through a system and the series of functional transformations applied to input data to produce outputs.

32
New cards

External Entity

A DFD symbol representing sources that send data into the system or destinations that receive data from the system outside the system boundaries.

33
New cards

Data Flow

A DFD element representing data in motion entering or exiting a process.

34
New cards

Data Store

A DFD element representing a repository of delayed data at rest within the system.

35
New cards

Entity

Any distinguishable physical or abstract object about which information is captured and stored.

36
New cards

Weak Entity Type

An entity type that lacks key attributes of its own and must be identified through its relationship with another entity type.

37
New cards

Key Attribute

An attribute whose values are distinct for each individual entity, uniquely identifying an instance of an entity.

38
New cards

Derived Attribute

An attribute whose value is dynamically calculated or derived from another stored attribute using a formula or summary operation.

39
New cards

Primary Key

An attribute or set of attributes in a relational table whose values uniquely identify each row (tuple) in that relation.

40
New cards

Candidate Key

Any attribute combination within a relation that possesses the unique identification property and can potentially serve as the primary key.

41
New cards

Alternate Key

A candidate key that has not been selected as the primary key.

42
New cards

First Normal Form (1NF)

A relational property where a table contains no duplicate rows, each cell contains a single atomic value, and entries in each column are of the same kind.

43
New cards

Second Normal Form (2NF)

A relational state where a table is in 1NF and all non-key attributes are fully dependent on the entire primary key, eliminating partial functional dependencies.

44
New cards

Third Normal Form (3NF)

A relational state where a table is in 2NF and contains no transitive dependencies among non-primary-key attributes.

45
New cards

Entity Integrity Rule

A relational database constraint stating that no component of a primary key may contain a null value.

46
New cards

Referential Integrity Constraint

A constraint specified across relations ensuring that foreign key values in one table accurately reference existing primary key values in another table.

47
New cards

Extension

The dynamic set of tuples appearing in a relation at any given instance in time.

48
New cards

Intension

The permanent, time-independent schema structure and set of integrity constraints defined for a relation.

49
New cards

Black Box Testing

A software testing approach focused solely on verifying overall inputs and outputs without examining the internal code logic.

50
New cards

White Box Testing

A testing approach that examines and exercises internal program code, procedural logic, and execution paths.

51
New cards

Verification

The process of checking actual software outputs against specified requirements in a simulated environment.

52
New cards

Validation

The process of evaluating software in a live environment to uncover bugs and confirm compliance with user requirements.

53
New cards

Unit Testing

The initial testing phase focused on validating the functionality and internal logic of individual program modules in isolation.

54
New cards

Integration Testing

A systematic technique for constructing the program structure while conducting tests to uncover errors associated with module interfacing.

55
New cards

Alpha Testing

Acceptance testing conducted by the customer at the developer's site within a controlled environment.

56
New cards

Beta Testing

Testing conducted by end users at their own live operational sites without the developer present.

57
New cards

Recovery Testing

A system test that forces software to fail in various ways to evaluate whether automatic re-initialization, restart, and data recovery function properly.

58
New cards

Stress Testing

A system test that executes a program under abnormal quantity, frequency, or volume of demands to test its operational breaking points.

59
New cards

Security Testing

A system test designed to verify that internal protection mechanisms withstand unauthorized penetration attempts.

60
New cards

Corrective Maintenance

Software maintenance activities directed at fixing reported errors in requirements, design, or code.

61
New cards

Adaptive Maintenance

Software maintenance activities performed to adapt system software to a changed environment, such as new hardware or operating systems.

62
New cards

Perfective Maintenance

Software maintenance activities focused on implementing new functional or non-functional requirements requested by users.