Flashcards Systems Analysis & Design Midterm Study Guide

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

1/122

encourage image

There's no tags or description

Looks like no tags are added yet.

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

No analytics yet

Send a link to your students to track their progress

123 Terms

1
New cards

Information Technology (IT)

The combination of hardware, software, and services used to manage, communicate, access, and share information.

2
New cards

Systems Analysis and Design

A step-by-step process for developing high-quality information systems.

3
New cards

System

A set of related components that produces specific results.

4
New cards

Information System

A combination of technology, people, data, and processes used to perform business functions and produce useful results.

5
New cards

Systems Analyst

A professional who investigates, analyzes, designs, develops, installs, evaluates, and maintains information systems that support business requirements.

6
New cards

Five Components of an Information System

Hardware, Software, Data, Processes, and People/Stakeholders.

7
New cards

Hardware

Physical equipment used by the information system, such as computers, servers, keyboards, printers, networks, and storage.

8
New cards

Software

Programs that control hardware and produce desired results, such as operating systems, applications, and database software.

9
New cards

Data

Raw facts that the system stores and transforms into useful information.

10
New cards

Processes

Tasks, rules, procedures, and business functions performed to achieve results.

11
New cards

People / Stakeholders

People who use, manage, develop, support, or are affected by the system.

12
New cards

Stakeholder

A person or group with an interest in an information system, including people who use, manage, develop, support, or are affected by it.

13
New cards

End Users

People who directly interact with the system.

14
New cards

Managers

People responsible for direction, resources, decisions, and performance.

15
New cards

IT Staff

Analysts, programmers, database administrators, network administrators, and other technical personnel.

16
New cards

E-commerce

Internet-based commerce.

17
New cards

B2C

Business-to-customer; a business sells products or services directly to consumers.

18
New cards

B2B

Business-to-business; a business provides products, services, or transactions to another business.

19
New cards

Electronic Data Interchange (EDI)

Electronic exchange of standardized business information between organizations.

20
New cards

Supply Chain Management (SCM)

Management of the companies, materials, services, information, and activities involved in providing a product or service to customers.

21
New cards

Customer Relationship Management (CRM)

Systems and practices used to integrate and manage customer-related events and transactions.

22
New cards

Business Profile

An overview of an organization's mission, functions, organization, products, services, customers, suppliers, competitors, constraints, and future direction.

23
New cards

Business Process

A specific set of transactions, events, and results that can be described and documented.

24
New cards

Business Process Model (BPM)

A graphical representation of one or more business processes.

25
New cards

Business Process Modeling Notation (BPMN)

A standard graphical notation using shapes and symbols to represent events, processes, workflows, and related business activities.

26
New cards

Workflow

The sequence in which activities or tasks are performed to complete a process.

27
New cards

Enterprise Computing

Systems that support company-wide operations and data-management requirements.

28
New cards

Enterprise Resource Planning (ERP)

Systems that provide integrated support for users and managers across an organization.

29
New cards

Transaction Processing (TP) System

A system that processes data generated by day-to-day business operations, such as orders, accounts receivable, and warranty claims.

30
New cards

User Productivity System

Technology that improves employee productivity, such as email, word processing, video conferencing, and related tools.

31
New cards

Groupware

Technology that enables data sharing and coordination of team efforts.

32
New cards

Systems Integration

Combining capabilities such as transaction processing, business support, knowledge management, and user productivity into connected systems.

33
New cards

Knowledge Worker

An employee whose work involves specialized knowledge and information, often requiring analytical or professional skills.

34
New cards

Top Managers

Organizational level focused on long-range strategic planning and organizational direction.

35
New cards

Middle Managers / Knowledge Workers

Organizational level providing direction, resources, analysis, and performance feedback.

36
New cards

Supervisors / Team Leaders

Organizational level that oversees day-to-day operations.

37
New cards

Operational Employees

Organizational level that performs day-to-day operational work.

38
New cards

Modeling

Producing a graphical representation of a concept or process that developers can analyze, test, and modify.

39
New cards

Prototype

An early working version of an information system used to test concepts, inputs, outputs, and user interfaces.

40
New cards

CASE Tools

Computer-Aided Systems Engineering / Computer-Aided Software Engineering tools that support systems development, methodologies, documentation, and sometimes code generation.

41
New cards

Quality Assurance (QA)

Review and testing of applications and system changes to verify specifications and software quality standards.

42
New cards

Structured Analysis

A traditional, systematic approach using models and SDLC phases where processes and data are modeled in a structured way.

43
New cards

Object-Oriented Analysis (O-O)

An approach that models real-world people, things, transactions, and events as objects combining data and processes.

44
New cards

Agile

An incremental development approach with repeated feedback, continuous adjustment, and flexibility to changing requirements.

45
New cards

Systems Development Life Cycle (SDLC)

A structured framework describing the major activities involved in planning, analyzing, designing, implementing, and supporting an information system.

46
New cards

Waterfall Model

A sequential development approach in which major phases are completed in order, with deliverables moving from one phase to the next.

47
New cards

Deliverable

A documented or tangible result produced during a development phase.

48
New cards

Spiral Model

A series of iterations or revisions based on user feedback.

49
New cards

Vertical System

A system focused deeply on a specific industry or niche rather than serving a broad range of industries, such as software designed specifically for hospitals.

50
New cards

Business Case

The reasons or justification for a proposed project or system, considering mission, objectives, costs, benefits, and risks.

51
New cards

Strategic Planning

The process of identifying long-term organizational goals, strategies, and resources.

52
New cards

Mission Statement

Defines what the organization does, its objectives, and how it intends to achieve those objectives.

53
New cards

Vision Statement

Describes where the organization aspires to go in the future.

54
New cards

Critical Success Factor (CSF)

A high-priority objective or factor that is especially important to achieving organizational success.

55
New cards

SWOT Analysis

An analysis of Strengths and Weaknesses (internal factors) and Opportunities and Threats (external factors).

56
New cards

Systems Request

A formal way of asking for IT support that commonly starts the systems development process.

57
New cards

Six Main Reasons for Systems Requests

Stronger controls, reduced cost, more information, better performance, improved services, and more support for new products/services.

58
New cards

Systems Review Committee

A group, often used in larger organizations, that evaluates systems requests and helps establish project priorities.

59
New cards

Operational Feasibility

Asks whether people and the organization will actually use the system effectively after it is developed (USE).

60
New cards

Technical Feasibility

Asks whether the organization has or can obtain the hardware, software, network, skills, and technical resources (TECHNOLOGY).

61
New cards

Economic Feasibility

Asks whether projected benefits outweigh the total cost of ownership (MONEY / TCO).

62
New cards

Schedule Feasibility

Asks whether the project can be completed and implemented in an acceptable time frame (TIME).

63
New cards

Total Cost of Ownership (TCO)

The total cost of acquiring, operating, supporting, and maintaining a system over its relevant life, including indirect costs.

64
New cards

Tangible Cost

A cost that can be measured in dollars.

65
New cards

Intangible Cost

A cost that can significantly affect performance but is difficult to assign an exact dollar value.

66
New cards

Tangible Benefit

A benefit that can be measured financially, such as reduced expenses or increased revenue.

67
New cards

Intangible Benefit

A benefit that matters but is difficult to measure precisely in dollars, such as improved morale.

68
New cards

Discretionary Project

A project management has a choice about implementing.

69
New cards

Nondiscretionary Project

A project management does not have a choice about implementing, often because of legal or regulatory conditions.

70
New cards

Six Steps of a Preliminary Investigation

1. Understand problem/opportunity, 2. Define scope/constraints, 3. Perform fact-finding, 4. Analyze project data, 5. Evaluate feasibility, 6. Present results and recommendations.

71
New cards

Project Scope

The specific boundaries or extent of what the project will and will not include.

72
New cards

Constraint

A requirement or condition that the system or project must satisfy, or an outcome it must achieve.

73
New cards

Project Creep

The gradual expansion of a project's scope without specific authorization.

74
New cards

Fishbone Diagram

A graphical tool used to identify possible causes of a problem and dig toward underlying causes rather than only symptoms (also called Ishikawa or cause-and-effect diagram).

75
New cards

Pareto Chart

A chart that displays causes of a problem in priority order so an analyst can focus on the most important causes first.

76
New cards

XY / Scatter Chart

A chart used to examine correlation between variables; a lack of correlation suggests the variables may be independent.

77
New cards

Project Management

Planning, scheduling, monitoring and controlling, and reporting on information-system development.

78
New cards

Project Triangle

The relationship among cost, scope, and time where changing one side can affect the others.

79
New cards

Work Breakdown Structure (WBS)

A breakdown of a project into smaller, manageable tasks and activities that can be planned, assigned, estimated, and monitored.

80
New cards

Task / Activity

Any work with a beginning and an end that uses resources such as people, time, or money.

81
New cards

Milestone / Event

A recognizable reference point used to monitor project progress.

82
New cards

Predecessor

A task that must be completed before another task can begin.

83
New cards

Successor

A task that follows another task in the dependency sequence.

84
New cards

Gantt Chart

A horizontal bar chart showing tasks on the vertical axis and time on the horizontal axis to display planned and actual progress.

85
New cards

PERT/CPM Chart

A network representation showing task relationships, dependencies, timing, and critical path for complex projects.

86
New cards

Critical Path

The series of tasks that, if delayed, will affect the overall project completion date (the longest dependent path with zero slack).

87
New cards

Slack

The amount of time a task can be delayed without delaying overall project completion.

88
New cards

Project-Manager / PERT Formula

A = (B + 4P + W) / 6, where A is expected duration, B is best-case, P is probable-case, and W is worst-case.

89
New cards

Structured Walk-Through

A review of a project team member's work by other team members, occurring throughout the SDLC.

90
New cards

Risk Management

The process of identifying, analyzing, responding to, and continuously monitoring risks that could affect a project.

91
New cards

Qualitative Risk Analysis

Evaluates risk by estimating probability and degree of impact.

92
New cards

Quantitative Risk Analysis

Estimates actual impact in terms such as dollars, time, scope, or quality.

93
New cards

Requirements Modeling

Using fact-finding and analysis to describe the current system and identify requirements for the new system.

94
New cards

Joint Application Development (JAD)

A structured approach that brings users and stakeholders into the development process as active participants for team-based fact-finding.

95
New cards

Rapid Application Development (RAD)

A group-oriented development methodology that uses prototyping and user involvement to reduce development time and expense.

96
New cards

Scrum

An Agile framework emphasizing teamwork, accountability, time-boxed activities, and iterative progress toward a defined goal.

97
New cards

Product Owner

The Scrum role associated with representing product needs and priorities.

98
New cards

Scrum Master / Facilitator

The role that facilitates the Scrum process and helps the team work effectively.

99
New cards

Functional Decomposition Diagram (FDD)

A top-down representation that breaks a business function or process into lower-level functions and subprocesses.

100
New cards

Data Flow Diagram (DFD)

A graphical model showing how data enters, moves through, is stored by, and leaves a system.