ITEC 4020 MIDTERM EXAM 2 [Part 1]

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

1/99

encourage image

There's no tags or description

Looks like no tags are added yet.

100 Terms

1
New cards

System Development Life Cycle (SDLC)

The process of determining how an information system can support business needs, designing and building the system, and delivering it to users.

2
New cards

Planning Phase

The SDLC phase where the project is planned and organized.

3
New cards

Analysis Phase

The SDLC phase where the team's goal is to understand the problem and determine what the system needs to do.

4
New cards

Design Phase

The SDLC phase where the team describes how the system will work and how it will solve the problem.

5
New cards

Implementation Phase

The SDLC phase where the system is built and delivered.

6
New cards

Project Initiation

The process of identifying a business need, finding a project sponsor, completing a system request, and submitting it for approval.

7
New cards

Project Sponsor

The person who supports a project and completes the system request for the business need.

8
New cards

System Request

A document submitted for project approval. It includes the project sponsor, business need, business requirements, business value, and special issues.

9
New cards

Project Methodology

The approach used to guide how a project is planned and completed.

10
New cards

Waterfall Development

A development approach where the project team completes each phase before moving on to the next phase.

11
New cards

Rapid Application Development (RAD)

An approach that uses tools to speed up analysis, design, and implementation so users can evaluate the system and provide feedback quickly.

12
New cards

Computer-Aided Software Engineering (CASE) Tools

Software tools that help automate parts of the SDLC and make development tasks faster

13
New cards

Scope Creep

When project requirements continue to expand beyond the original plan.

14
New cards

Agile Development

An approach that focuses on simple, iterative development, short development cycles, and communication with users.

15
New cards

Extreme Programming (XP)

An Agile method where programmers build and test small, simple modules to meet user needs.

16
New cards

Project Management Trade-offs

The decisions involved in balancing the size and features of a system, the time needed to complete it, and the project's cost.

17
New cards

Project Work Plan

A plan that outlines project activities and is updated by the project manager to monitor progress.

18
New cards

Gantt Chart

A horizontal bar chart that visually displays a project's work plan and tasks.

19
New cards

PERT Chart (Program Evaluation and Review Technique)

A flowchart that displays project tasks and the dependencies between them.

20
New cards

Critical Path Method (CPM)

The longest path of dependent tasks from the beginning to the completion of a project. It identifies tasks that must stay on schedule for the entire project to finish on time.

21
New cards

Upper CASE

CASE tools used during the analysis phase to create system diagrams and store information about system components.

22
New cards

Lower CASE

CASE tools used during the design phase to create diagrams and generate code for database tables and system functionality.Requirement

23
New cards

Requirement

A statement describing what a system must do or what characteristics it needs to have.

24
New cards

Business Requirements

Requirements that describe what the business needs.

25
New cards

User Requirements

Requirements that describe what users need to do with the system.

26
New cards

Functional Requirements

Requirements that describe what the software should do.

27
New cards

System Requirements

Requirements that describe how the system should be built.

28
New cards

Requirement Determination (Elicitation)

The process of gathering information to understand and identify the system's requirements.

29
New cards

Interviews

A requirement-gathering technique where analysts ask people questions to understand how a business process works and what the system needs.

30
New cards

Closed-Ended Questions

Questions that have a limited set of possible answers.

31
New cards

Open-Ended Questions

Questions that allow people to explain their thoughts and provide detailed answers.

32
New cards

Probing Questions

Follow-up questions used to get more information or clarify an answer.

33
New cards

Joint Application Development (JAD)

A structured information-gathering technique where the project team, users, and management work together to identify requirements.

34
New cards

Electronic JAD (e-JAD)

JAD sessions that use groupware and electronic tools to help participants work together.

35
New cards

Problem Analysis

A technique that examines problems in the current system and considers how a new system could solve them.

36
New cards

Root Cause Analysis

A technique used to identify the underlying causes of important problems.

37
New cards

Duration Analysis

A technique that measures how much time each process takes in the current system.

38
New cards

Activity-Based Costing

A method used to understand the costs associated with individual business activities.

39
New cards

Informal Benchmarking

Comparing how other organizations perform similar business processes.

40
New cards

Outcome Analysis

A technique that identifies the main outcomes that provide value to customers.

41
New cards

Technology Analysis

Examining how different technologies could be used to improve a business process.

42
New cards

Activity Elimination

Examining whether an activity can be removed from a business process.

43
New cards

Use Case

A set of activities performed by a user to produce an output. It describes how an event triggers actions involving the user and the system.

44
New cards

Use Case Analysis

The process of using use cases to understand a system's functional requirements, exceptions, special cases, and error-handling needs.

45
New cards

Actor

A person, software system, or hardware device that interacts with the system in a use case.

46
New cards

Trigger

An event that causes a use case to begin.

47
New cards

External Trigger

An event caused by something outside the system, such as a customer placing an order.

48
New cards

Temporal Trigger

An event that occurs at a particular time or when a time-based condition is met, such as an e-book becoming overdue.

49
New cards

Preconditions

Conditions or tasks that must be completed before a use case can begin.

50
New cards

Normal Course

The steps followed when everything works as expected during a use case. Also known as the happy path.

51
New cards

Postconditions

The final results or conditions that exist after a use case is completed.

52
New cards

Exceptions

Errors or unexpected conditions that may occur while a use case is being performed.

53
New cards

Happy Path

The normal sequence of steps in a use case when no problems occur.

54
New cards

Use Case Name

A short, descriptive name that explains the goal of the use case.

55
New cards

Use Case Description

A brief explanation of what the use case does and what result it produces.

56
New cards

Use Case Preconditions

Conditions that must be true before the use case starts.

57
New cards

Use Case Postconditions

Conditions that should be true after the use case finishes.

58
New cards

System

A group of related components that work together to achieve a purpose.

59
New cards

Computer Application

A software program that runs on a computing device to perform a specific function or set of related functions.

60
New cards

Information System (IS)

A set of related computer components that collects, processes, stores, and provides information needed to complete business tasks.

61
New cards

Systems Analysis and Design (SA&D)

The tools and techniques used to understand a business need, define a solution, communicate it, build it, and confirm that it meets the need.

62
New cards

Systems Analysis

Activities used to understand and specify what a new system should accomplish. It focuses on what the system must do.

63
New cards

Systems Design

Activities used to describe in detail how a system will work to solve a problem or meet a need.

64
New cards

Project

A planned undertaking with a beginning and an end that produces a specific result.

65
New cards

Systems Development Life Cycle (SDLC)

The entire process of building, launching, and maintaining an information system.

66
New cards

Initiation Phase

The phase where the problem or need is identified and approval to proceed is obtained.

67
New cards

Deployment Phase

The phase where system testing is completed and the solution is released for use.

68
New cards

Information Systems Development Process

The actual approach used to develop a particular information system.

69
New cards

Predictive Approach

A development approach that plans the project phases in advance and generally follows a defined sequence.

70
New cards

Waterfall Model

A traditional development approach that assumes project phases are completed sequentially, with little or no overlap.

71
New cards

Waterfall Model with Overlap

A variation of Waterfall that allows phases to overlap, providing more flexibility and efficiency

72
New cards

V-Model

A Waterfall variation that gives more attention to testing by defining tests during the analysis and design phases.

73
New cards

Adaptive/Iterative Model

A development approach that repeats development activities through multiple cycles until the system is complete.

74
New cards

Spiral Model

An adaptive SDLC approach that repeatedly cycles through development activities until the system is completed.

75
New cards

Unified Process (UP)

An iterative development process in which each cycle generally ends with a release of the system.

76
New cards

Inception

The Unified Process phase where the project's purpose and scope are established.

77
New cards

Elaboration

The Unified Process phase where the project requirements and system architecture are developed in more detail.

78
New cards

Construction

The Unified Process phase where the system is built through development and testing.

79
New cards

Transition

The Unified Process phase where the completed system is delivered to customers or users.

80
New cards

System Prototyping

Creating an early version of a system so users can evaluate it and provide feedback.

81
New cards

Agile Development

A philosophy and set of guidelines for developing systems in environments where requirements may be unknown or change quickly.

82
New cards

Manifesto for Agile Software Development

A set of values that prioritizes responding to change, individuals and interactions, working software, and customer collaboration.

83
New cards

Scrum

An Agile development method identified in the course as one of the popular Agile methods.

84
New cards

Project Initiation

The process of identifying a problem or opportunity and defining the need for a new system.

85
New cards

System Vision Document

A document that helps define the scope of a new system by describing the problem, business benefits, and system capabilities.

86
New cards

Business Benefits

The benefits a project provides to an organization, usually measured in dollars.

87
New cards

System Capabilities

The functions or abilities that the proposed system must provide.

88
New cards

Cost/Benefit Analysis

Comparing estimated project costs with anticipated benefits to determine whether an investment is worthwhile.

89
New cards

Net Present Value (NPV)

The present value of the dollar benefits and dollar costs of an investment.

90
New cards

Break-Even Point

The point in time when the dollar benefits of a project equal its dollar costs.

91
New cards

Payback Period

The amount of time it takes for the benefits of a project to offset its costs.

92
New cards

Tangible Cost/Benefit

A cost or benefit that can be measured or estimated in dollars.

93
New cards

Intangible Cost/Benefit

A cost or benefit that affects an organization but cannot be accurately measured in dollars.

94
New cards

Project Feasibility

An assessment of whether a project can realistically be completed, considering organizational, technological, resource, and schedule factors.

95
New cards

Project Scope Statement

A statement that describes the boundaries and work included in a project.

96
New cards

Work Breakdown Structure (WBS)

A list or hierarchy of a project's activities and tasks, used to estimate the work and create a detailed schedule.

97
New cards

Critical Path

The tasks that must stay on schedule for the overall project to finish on time.

98
New cards

System Development Methodology

A set of comprehensive SDLC guidelines that includes specific models, tools, and techniques.

99
New cards

Model

A representation of an important aspect of the real world. It can represent inputs, outputs, processes, data, objects, and other system components.

100
New cards

Abstraction

Representing important information while leaving out unnecessary details.