ITAN Ch. 13 Vocab

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

1/53

encourage image

There's no tags or description

Looks like no tags are added yet.

54 Terms

1
New cards

system development

The set of activities involved in building information systems to meet users’ needs.

2
New cards

perpetual license

A license provided for one installation, with new software editions requiring new licenses; usually purchased by the bundle, called seats, and loaded on individual computers.

3
New cards

request for information (RFI)

A document that outlines an organization’s hardware or software needs and requests information from vendors about if and how they can meet those needs and the time and resources required.

4
New cards

performance evaluation test

A comparison of vendor options conducted in a computing environment (e.g., computing hardware, operating system software, database management system) and with a workload (e.g., number of concurrent users, database size, and number of transactions) that matches its intended operating conditions.

5
New cards

Waterfall system development process

A sequential, multistage system development process in which work on the next stage cannot begin until the results of the current stage are reviewed and approved or modified as necessary.

6
New cards

System investigation

The initial phase in the development of a new or modified business information system whose purpose is to gain a clear understanding of the specifics of the problem to solve or the opportunity to address.

7
New cards

Joint application development (JAD)

A structured meeting process that can accelerate and improve the efficiency and effectiveness of the investigation, analysis, and design phases of a system development project.

8
New cards

Functional decomposition

A technique that involves breaking down complex problems or systems into smaller parts, making them easier to manage and understand.

9
New cards

feasibility analysis

An assessment of the technical, economic, legal, operational, and schedule feasibility of a project.

10
New cards

Technical feasibility

The process of determining whether a project is feasible within the current limits of available technology.

11
New cards

Economic feasibility

The process of determining whether the project makes financial sense and whether predicted benefits offset the cost and time needed to obtain them.

12
New cards

Legal feasibility

The process of determining whether laws or regulations may prevent or limit a system development project.

13
New cards

Operational feasibility

The process of determining how a system will be accepted by people and how well it will meet various system performance expectations.

14
New cards

Schedule feasibility

The process of determining whether the project can be completed within a desired time frame.

15
New cards

system investigation report

A summary of the results of the system investigation, with a recommendation of a course of action.

16
New cards

system analysis

The phase of system development that focuses on gathering data on the existing system, determining the requirements for the new system, considering alternatives within identified constraints, and investigating the feasibility of alternative solutions.

17
New cards

data-flow diagram (DFD)

A diagram used during both the analysis and design phases to document the processes of the current system or to provide a model of a proposed new system.

18
New cards

Pareto principle

An observation that for many events, roughly 80 percent of the effects come from 20 percent of the causes.

19
New cards

system design

The stage of system development that answers the question, “How will the information system solve a problem?”

20
New cards

hot site

A duplicate, operational hardware system that is ready for use (or immediate access to one through a specialized vendor).

21
New cards

cold site

A computer environment that includes rooms, electrical service, telecommunications links, data storage devices, and the like.

22
New cards

System construction

The phase of system development that converts the system design into an operational system by acquiring and installing hardware and software, coding and testing software programs, creating and loading data into databases, and performing initial program testing.

23
New cards

Technical documentation

Written details used by computer operators to execute the program and by analysts and programmers to solve problems or modify the program.

24
New cards

User documentation

Written descriptions developed for people who use a program; in easy-to-understand language, it shows how the program can and should be used to meet the needs of its various users.

25
New cards

unit testing

Testing of individual components of code (subroutines, modules, and programs) to verify that each unit performs as designed.

26
New cards

Integration testing

Testing that involves linking all the individual components together and testing them as a group to uncover any defects in the interfaces between individual components.

27
New cards

System testing

Testing the complete, integrated system (hardware, software, databases, people, and procedures) to validate that the information system meets all specified requirements.

28
New cards

Volume testing

Testing to evaluate the performance of the information system under varying yet realistic work volume and operating conditions to determine the work load at which system performance begins to degrade and to identify and eliminate any issues that prevent the system from reaching its required service-level performance.

29
New cards

user acceptance testing (UAT)

Testing performed by trained system users to verify that the system can complete required tasks in a real-world operating environment and perform according to the system design specifications.

30
New cards

user acceptance document

A formal agreement that the organization signs stating that a phase of the installation or the complete system is approved.

31
New cards

User preparation

The process of readying managers, decision makers, employees, other users, and stakeholders to accept and use the new system.

32
New cards

site preparation

Preparation of the location of a new system.

33
New cards

Installation

The process of physically placing the computer equipment on the site and making it operational.

34
New cards

Cutover

The process of switching from an old information system to a replacement system.

35
New cards

Direct conversion

A cutover strategy that involves stopping the old system and starting the new system on a given date; also called plunge or direct cutover.

36
New cards

phase-in approach

A cutover strategy that involves slowly replacing components of the old system with those of the new one; this process is repeated for each application until the new system is running every application and performing as expected; it is also called a piecemeal approach.

37
New cards

Pilot start-up

A cutover strategy that involves running the complete new system for one group of users rather than for all users.

38
New cards

Parallel start-up

A cutover strategy that involves running both the old and new systems for a set period of time and closely comparing the output of the new system with the output of the old system; any differences are reconciled. When users are comfortable that the new system is working correctly, the old system is eliminated.

39
New cards

System operation

The use of a new or modified system under all kinds of operating conditions.

40
New cards

Monitoring

The process of measuring system performance by tracking the number of errors encountered, the amount of memory required, the amount of processing or CPU time needed, and other performance indicators.

41
New cards

System review

The process of analyzing a system to make sure it is operating as intended.

42
New cards

System maintenance

A stage of systems development that involves changing and enhancing the system to make it more useful in achieving user and organizational goals.

43
New cards

slipstream upgrade

A minor system upgrade—typically a code adjustment or minor bug fix; it usually requires recompiling all the code, and in so doing, it can create entirely new bugs.

44
New cards

patch

A minor system change to correct a problem or make a small enhancement; it is usually an addition to an existing program.

45
New cards

release

A significant program change that often requires changes in the documentation of the software.

46
New cards

version

A major program change, typically encompassing many new features.

47
New cards

System disposal

A stage of system development that involves those activities that ensure the orderly dissolution of the system, including disposing of all equipment in an environmentally friendly manner, closing out contracts, and safely migrating information from the system to another system or archiving it in accordance with applicable records management policies.

48
New cards

Agile development

An iterative system development process that develops the system in “sprint” increments lasting from two weeks to two months.

49
New cards

Scrum

An Agile development framework that emphasizes a team-based approach in order to keep the development effort focused and moving quickly.

50
New cards

Scrum master

The person who coordinates all the Scrum activities of a team.

51
New cards

product owner

A person who represents the project stakeholders and is responsible for communicating and aligning project priorities between the stakeholders and development team.

52
New cards

product backlog

A prioritized list of project requirements created by the stakeholders and project team members; from this list, the team selects the highest priorities.

53
New cards

Extreme programming (XP)

A form of Agile software development that promotes incremental development of a system using short development cycles to improve productivity and to accommodate new customer requirements.

54
New cards

DevOps

The practice of blending the tasks performed by the development and IT operations groups to enable faster and more reliable software releases.