Final Exam In Info 210 With Darcey

Front 1

Analysis paralysis

Back 1

When too much time is spent documenting project requirements.

Front 2

Beta testing

Back 2

The process of allowing future system users to tr out the new system on their own. Used to locate program failures just prior to product shipment.

Front 3

Brooks's law

Back 3

"Adding more people to a late project makes the project later."

Front 4

Component design phase

Back 4

The third phase in the SDLC, in which developers determine hardware and software specifications, design the database (if applicable), design procedures, and create job descriptions for users and operations personnel.

Front 5

Cost feasibility

Back 5

One of four dimensions of feasibility

Front 6

Implementation phase

Back 6

The fourth phase in the SDLC, in which developers build and integrate new system components, test the system, and convert to the new system.

Front 7

Maintenance phase

Back 7

The fifth and final phas of the SDLC, in which developers record requests for changes, includiing both enhancements and failures, and fix failures by means of patches, service packs, and new releases.

Front 8

Organization feasibility

Back 8

One of the four dimensions of feasibility.

Front 9

Parallel installation

Back 9

A type of system conversion in which the new system runs in parallel with the old one for a while. Parallel installation is expensive because the organization incurs the costs of running both systems.

Front 10

Patch

Back 10

A group of fixes for high-priority failures that can be applied to existing copies of a particular product. Software vendors supply patches to fix security and other critical problems.

Front 11

Phased installation

Back 11

A type of system conversion in which the new system is installed in pieces across the organization(s). Once a given piece works, then the organization installs and tests another piece of the system, until the entire system has been installed.

Front 12

Pilot installation

Back 12

A type of system conversion in which the organization implements the entire system on a limited portion of the business.

Front 13

Plunge, direct, or big-bang installation

Back 13

A type of system conversion in which the organization shuts down the old system and starts the new system. Because of the risk of failure in the new system, organizations should avoid this conversion style if possible.

Front 14

Product quality assurance (PQA)

Back 14

The testing of a system. PQA personnel usualy construct a test plan with the advice and assistance of users.

Front 15

Requirements analysis phase

Back 15

The second phase in the SDLC, in which developers conduct user interviews, evaluate existing systems, determine new forms/reports/queries, identify new features and functions, including security, and create the data model.

Front 16

Schedule feasibility

Back 16

One of the four dimensions of feasibility

Front 17

Service pack

Back 17

A large group of fixes that solve low-priority software problems. Users apply service packs in much the same way as they would apply patches, except that service packs sometimes have hundreds to thousands of fixes in them.

Front 18

System analysts

Back 18

IS professionals that understand both business and technology. They are active throughout the systems development process and play a key role in moving the project from conception to conversion and, ultimately, maintenance. They integrate the work of programmers, testers, and users.

Front 19

System conversion

Back 19

The process of converting business actuvuty from the old system to the new.

Front 20

System definition phase

Back 20

the first phase in the SDLC, in which developers, with the help of eventual users, define the new system's goals and scope, assess its feasibility, form a project team, and plan the project.

Front 21

Technical feasibility

Back 21

One of the four dimensions of feasibility.

Front 22

Test plan

Back 22

Groups of sequences of actions that users will take using the new system.

Front 23

Waterfall

Back 23

The fiction that one phase of the SDLC can be completed in its entirety and the project can progress, without any backtracking, to the next phase of the SDLC. Projects are seldom that simple.

Front 24

System development life cycle (SDLC)

Back 24

The classical process used to develop information systems. These basic tasks of systems development are combined into the following phases: system definition, requirements analysis, component design, implementation, and system maintenance (fix or enhance).

Front 25

Systems development / System analysis and design

Back 25

The process of creating and maintaining information systems.

Front 26

Agile enterprise

Back 26

An organization that can quickly adapt to changes in the market, industry, product, law, or other significant external factors; the term was coined by Microsoft.

Front 27

Chief information officer (CIO)

Back 27

The title of the principal manager of the IT department.

Front 28

Chief technology officer (CTO)

Back 28

The head of the technology group. The CTO sorts through new ideas and products to identify those that are most relevant to the organization.

Front 29

Intangible benefit

Back 29

A benefit of an IS for which it impossible to compute a dollar value.

Front 30

Tangible benefit

Back 30

A benefit of an IS that can be measured by a dollar value.

Front 31

Tuning

Back 31

Adjusting information systems from time to time to changes in the workload.

Front 32

Adware

Back 32

Programs installed on the user's computer without the user's knowledge or permission that reside in the background and, unknown to the user, observes the user's actions and keystrokes, modify computer activity, and report the user's activity to sponsoring organizations.

Front 33

Authentication

Back 33

The process whereby an information system approves a user by checking the user's password.

Front 34

Biometric authentication

Back 34

Authentication via fingerprints, facial scans, retina scans, etc.

Front 35

Cold site

Back 35

A remote processing center that provides office space, but no computer equipment, for use by a company that needs to continue operations after a natural disaster.

Front 36

Data administration

Back 36

A staff function that pertains to ALL of an organization's data assets. Typical data administration tasks are setting data standards, developing data policies, and providing for data security.

Front 37

Database administration

Back 37

The management, development, operation, and maintenance of the database so as to achieve the organization's objectives. This staff function requires balancing conflicting goals: protecting the database while maximizing its availability for authorized use,. Size of the company effects the size of the team responsible for this task.

Front 38

Data safeguards

Back 38

Steps taken to protect databases and other organizational data, by means of data administration and database administration.

Front 39

Denial of service (DOS)

Back 39

Security problem in which users cannot access an IS; can be caused by human errors, natural disasters, or malicious activity.

Front 40

Drive-by sniffer

Back 40

People who take computers with wireless connections through an area and search for unprotected wireless networks in an attempt to gain free internet access. (Logan)

Front 41

Email spoofing

Back 41

A synonym for phishing A technique for obtaining unauthorized data that uses pretexting via email. ie. fake business asks you for your SSN.