Information Systems & Project Management (Ch. 9)

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

1/103

encourage image

There's no tags or description

Looks like no tags are added yet.

104 Terms

1
New cards

Conversion

Process of transferring information from a legacy system to a new system

2
New cards

Legacy system

Old system that is fast approaching or beyond the end of its useful life within an organization

3
New cards

Systems development life cycle (SDLC)

Overall process for developing information systems, from planning and analysis through implementation and maintenance

4
New cards

Planning phase

Establishes a high level plan of the intended project and determines project goals

5
New cards

Brainstorming

Technique for generating ideas by encouraging participants to offer as many ideas as possible without immediate analysis

6
New cards

Change agent

Person or event that is the catalyst for implementing major changes for a system to meet business changes

7
New cards

Project

Temporary activity a company undertakes to create a unique product, service or result

8
New cards

Project management

Application of knowledge, skills, tools, and techniques to project activities to meet project requirements

9
New cards

Project plan

Formal, approved document that manages and controls the entire project

10
New cards

Project manager

Individual expert in project planning and management who defines, develops, and tracks the project plan

11
New cards

Project scope

Describes the business need, problem to solve, justification, requirements, and current boundaries for the project

12
New cards

Analysis phase

The firm analyzes end user business requirements and refines project goals into defined functions and operations

13
New cards

Business requirements

Specific business requests that the system must meet to be successful

14
New cards

Requirements management

Process of managing changes to the business requirements throughout the project

15
New cards

Requirements definition document

Prioritizes all of the business requirements by order of importance to the company

16
New cards

Sign off

Users' actual signatures indicating they approve all of the business requirements

17
New cards

Process modeling

Involves graphically representing processes that capture, manipulate, store, and distribute information

18
New cards

Data flow diagram (DFD)

Illustrates the movement of information between external entities and the processes and data stores within a system

19
New cards

Design phase

Establishes descriptions of desired features and operations of the system, including screen layouts, business rules, and pseudocode

20
New cards

Figma

Cloud based design and prototyping tool that allows users to create, collaborate, and iterate on digital designs in real time

21
New cards

Development phase

Transforms all detailed design documents from the design phase into the actual physical system

22
New cards

Coders

People who write the programs that operate computers

23
New cards

Software engineering

Disciplined approach for constructing information systems through common methods, techniques, or tools

24
New cards

Programming language

Unique set of keywords along with special syntax for organizing program instructions

25
New cards

Fourth generation languages

Programming languages that look similar to human languages

26
New cards

Low code and no code

Software development approaches that aim to simplify creating applications by reducing manual coding

27
New cards

Technical review (peer review)

Meeting where an independent team of experts provides in depth analysis of project results

28
New cards

Testing phase

Brings project pieces together into a testing environment to eliminate errors and verify business requirements

29
New cards

Bugs

Defects in the code of an information system

30
New cards

Test conditions

Details the steps the system must perform along with the expected result of each step

31
New cards

Alpha testing

Assesses if the entire system meets the design requirements of the users

32
New cards

Development testing

Tests the system to ensure it is bug free

33
New cards

Integration testing

Verifies that separate systems can work together, passing data back and forth correctly

34
New cards

System testing

Verifies that units or pieces of code function correctly when integrated

35
New cards

User acceptance testing (UAT)

Determines if the system satisfies the user and business requirements

36
New cards

Unit testing

Tests individual units or pieces of code for a system

37
New cards

Implementation phase

Organization places the system into production so users can perform actual business operations

38
New cards

Parallel implementation

Uses both legacy and new systems until all users verify that the new system functions correctly

39
New cards

Plunge implementation

Discards the legacy system and immediately migrates all users to the new system

40
New cards

Pilot implementation

Assigns a small group to use the new system until verified, then migrates remaining users

41
New cards

Phased implementation

Installs the new system in phases by department until verified

42
New cards

Online training

Runs over the internet and employees complete it on their own time at their own pace

43
New cards

Workshop training

Held in a classroom environment and led by an instructor

44
New cards

Help desk

Group of people who respond to users' questions

45
New cards

User documentation

Created for users to highlight how to use the system and troubleshoot issues

46
New cards

Maintenance phase

Organization performs changes, corrections, additions, and upgrades to ensure system continues to meet goals

47
New cards

Corrective maintenance

Makes system changes to repair design flaws, coding errors, or implementation issues

48
New cards

Preventive maintenance

Makes system changes to reduce the chance of future system failure

49
New cards

Internal report

Presents data distributed inside the organization intended for employees

50
New cards

Detailed internal report

Presents information with little or no filtering or restrictions of the data

51
New cards

Summary internal report

Organizes and categorizes data for managerial perusal

52
New cards

Exception report

Highlights situations occurring outside of the normal operating range for a condition or standard

53
New cards

Information system control report

Ensures reliability of information via policies, physical implementation, access restrictions, or record keeping

54
New cards

Information system audit report

Assesses a company's information system to determine necessary changes and ensure availability, confidentiality, and integrity

55
New cards

Post implementation report

Presents a formal report or audit of a project after it is up and running

56
New cards

Methodology

Set of policies, procedures, standards, processes, practices, tools, and tasks applied to technical challenges

57
New cards

Waterfall methodology

Sequence of phases in which output of each phase becomes input for the next; inflexible and expensive

58
New cards

Prototyping

Modern design approach by which designers and users use an iterative approach in building the system

59
New cards

Iterative development

Consists of a series of tiny projects

60
New cards

Agile methodology

Aims for customer satisfaction through early and continuous delivery of useful software components using iterative process

61
New cards

Minimum viable product (MVP)

Version of a product developed with the minimum features required to meet core needs

62
New cards

Rapid application development (RAD)

Emphasizes extensive user involvement in the rapid construction of working prototypes

63
New cards

Extreme programming (XP)

Breaks a project into four phases where developers cannot continue until the previous phase is complete

64
New cards

Scrum methodology

Uses small teams to produce small pieces of software using 30 day sprints

65
New cards

RUP methodology

Framework owned by IBM for breaking down software development into four gates

66
New cards

Tangible benefits

Easy to quantify and typically measured to determine project success

67
New cards

Intangible benefits

Difficult to quantify or measure, such as improved decision making or morale

68
New cards

Feasibility

Measure of the tangible and intangible benefits of an information system

69
New cards

Economic feasibility

Measures the cost effectiveness of a project

70
New cards

Operational feasibility

Measures how well a solution meets identified system requirements to solve problems

71
New cards

Schedule feasibility

Measures the project time frame to ensure timely completion

72
New cards

Technical feasibility

Measures the practicality of a technical solution and resource availability

73
New cards

Political feasibility

Measures how well the solution will be accepted in a given organization

74
New cards

Legal feasibility

Measures how well a solution can be implemented within existing legal and contractual obligations

75
New cards

Program management

Managing a group of related projects designed to achieve a common strategic objective

76
New cards

Portfolio management

Focuses on managing a collection of projects, programs, and other initiatives within an organization

77
New cards

Communication plan

Defines the how, what, when, and who regarding project information flow to stakeholders

78
New cards

Executive sponsor

Person or group who provides the financial resources for the project

79
New cards

Project assumption

Factors considered to be true, real, or certain without proof or demonstration

80
New cards

Project constraint

Specific factors that can limit options, including budget, delivery dates, and available resources

81
New cards

Project deliverable

Any measurable, tangible, verifiable outcome or item produced to complete a project

82
New cards

Project management office (PMO)

Internal department that oversees all organizational projects and educates on techniques

83
New cards

Project milestone

Represents key dates when a certain group of activities must be performed

84
New cards

Project objectives

Quantifiable criteria that must be met for a project to be considered a success

85
New cards

Project requirements document

Defines specifications for the product of the project and is key for controlling scope

86
New cards

Project scope statement

Links the project to the organization's overall business goals

87
New cards

Project stakeholder

Individuals and organizations actively involved in the project or whose interests are affected

88
New cards

Responsibility matrix

Defines project roles and indicates what responsibilities are associated with each role

89
New cards

Status report

Periodic reviews of actual performance versus expected performance

90
New cards

Project charter

Concise written description of the project's intended work

91
New cards

Kill switch

Trigger that enables a project manager to close a project before completion

92
New cards

PERT chart

Graphical network model that depicts a project's tasks and the relationships between them

93
New cards

Critical path

Series of activities that determine the earliest time by which a project can be completed with least slack

94
New cards

Critical path analysis

Project diagramming method used to predict total project duration

95
New cards

Slack

Amount of time an activity may be delayed without delaying a succeeding activity or project finish date

96
New cards

Scope creep

Tendency to permit changes that exceed a project's scope and wreak havoc on schedule and budget

97
New cards

Gantt chart

Simple bar chart listing project tasks vertically against time frame horizontally

98
New cards

Dependency

Logical relationship that exists between project tasks or between a task and a milestone

99
New cards

Work breakdown structure (WBS)

Plan that breaks down a project's goals into the many deliverables required

100
New cards

In sourcing

Uses professional expertise within an organization to develop and maintain IT systems