Chapter 20: Introduction to Systems Development and Systems Analysis Flashcards

1
Q

systems development life cycle (SDLC)

A

a five-step process used to design and implement a new system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

systems analysis

A

first SDLC step where the information needed to purchase, develop, or modify a system is gathered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

conceptual design

A

second SDLC step where analysts decide how to meet user needs, identify and evaluate design alternatives, and develop detailed specifications for what the system is to accomplish and how it is to be controlled

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

physical design

A

third SDLC step where broad, user-oriented conceptual design requirements are translated into the detailed specifications used to code and test software, design input/output, create files/databases, develop procedures, and implement controls

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

implementation and conversion

A

fourth SDLC step where the company hires and trains employees, tests and modifies procedures, establishes standards and controls, completes documentation, moves to the new system, and detects and corrects design deficiencies

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

operations and maintenance

A

fifth SDLC step where the system is periodically reviewed and necessary modifications and improvements are made

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

information systems steering committee

A

high-level management who plan and oversee the IS function, setting IS policies that govern the AIS, ensuring top-management guidance and control, and coordinating and integrating systems activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

systems analysis

A

people who help users determine their information needs, study existing systems and design new ones, and prepare specifications used by computer programmers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

computer programmers

A

people who write and test programs using the specifications developed by the analysts and modify and maintain existing computer programs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

project development plan

A

document showing project requirements (people, hardware software, and financial), a cost-benefit analysis, and how a project will be completed (modules or tasks to be performed, who will perform them, and completion dates).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

master plan

A

it describes what a system will consist of, how it will be developed, who will develop it, when it will be developed, how needed resources will be acquired, the status of projects in process, the prioritization of planned projects, and the prioritization criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

program evaluation and review technique (PERT)

A

a way to plan, develop, coordinate, control, and schedule systems development activities; all activities, and precedent and subsequent relationships among activities, are identified and shown on a PERT diagram

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

critical path

A

the PERT path requiring the greatest amount of time to complete a project; if a critical path activity is delayed, the whole project is delayed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Gantt chart

A

a bar graph used for project planning. It shows project activities on the left, units of time across the top, and the time each activity is expected to take a horizontal bar

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

feasibility study

A

an investigation to determine whether it is practical to develop a new application or system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

economic feasibility

A

determining whether system benefits justify the time, money, and resources required to implement it

17
Q

technical feasibility

A

determining if a proposed system can be developed given the available technology

18
Q

legal feasibility

A

determining if a proposed system will comply with all applicable federal and state laws, administrative agency regulations, and contractual obligations

19
Q

scheduling feasibility

A

determining if a proposed system can be developed and implemented in the time allotted

20
Q

operational feasibility

A

determining if the organization has access to people who can design, implement, and operate the proposed system and if employees will use the system

21
Q

capital budgeting model

A

a return-on-investment technique use to compare estimated benefits and costs to determine whether a system is cost beneficial

22
Q

payback period

A

a return-on-investment technique used to calculate the number of years required for the net savings of a system to equal its initial cost

23
Q

net present value (NPV)

A

a return-on-investment technique that discounts all estimated future cash flows back to the present using a discount rate that reflects the time value of money

24
Q

internal rate of return (IRR)

A

a return-on-investment technique that calculates the interest rate that makes the present value of total costs equal to the present value of total savings

25
Q

behavioral aspects of change

A

the positive and negative ways people react to change; managing these behavioral reactions is crucial to successfully implementing a new system

26
Q

aggression

A

resistance to change intended to destroy, cripple, or weaken system effectiveness, such as increased error rates, disruptions, or deliberate sabotage

27
Q

projection

A

resistance to change that blames anything and everything on the new system, such that it becomes the scapegoat for all real and imagined problems and errors

28
Q

avoidance

A

resistance to change where users ignore a new IS in the hope that the new system will eventually go away

29
Q

request for systems development

A

a written request for a new or improved system that describes the current system’s problems, the reasons for the change, and the proposed system’s objectives, benefits, and costs

30
Q

initial investigation

A

a preliminary investigation to determine whether a proposed new system is both needed and feasible

31
Q

proposal to conduct systems analysis

A

a request to complete the systems analysis phase for a project that makes it through the initial investigation

32
Q

systems survey

A

an extensive study of the current AIS

33
Q

systems documentation

A

a complete description of how the system is supposed to work, including questionnaire copies, interview notes, memos, document copies, and models

34
Q

physical model

A

the description of how a system functions by describing document flow, computer processes performed, the people performing them, and the equipment used

35
Q

logical model

A

system description that focuses on what essential activities are performed and the flow of information irrespective of how the flow is actually accomplished

36
Q

systems survey report

A

a report that summaries all the activities that took place during the systems survey, including all relevant documentation

37
Q

systems analysis report

A

comprehensive report summarizing systems analysis that documents the findings of analysis activities