Cis Final

Front 1

part of a DBMS that contains facilities to help you develop transaction-intensive applications.

Back 1

Application Generation Subsystem

Front 2

a copy of the information stored on a computer

Back 2

Backup

Front 3

collective information about your customers, your competitors, your business partners, your competitive environment, and your own internal operations that gives you the ability to make effective, important, and often strategic business decisions.

Back 3

Business Intelligence (BI)

Front 4

business intelligence focused on the external competitive environment

Back 4

Competitive Intelligence

Front 5

the function in an organization that plans for, oversees the development of, and monitors the information resource

Back 5

Data Administration

Front 6

part of a DBMS that helps you manage the overall database environment by providing facilities for backup and recovery, security management, query optimization, concurrency control, and change management

Back 6

Data Administration Subsystem

Front 7

a collection of information that you organize and access according to the logical structure of that information

Back 7

Database

Front 8

the function in an organization that is responsible for the more technical and operational aspects of managing the information contained in organizational information repositories (databases, data warehouses, and data marts).

Back 8

Database Administration

Front 9

helps you specify the logical organization for a database and access and use the information within a database. Contains five important software components – DBMS engine, data definition subsystem, data manipulation subsystem, application generation subsystem, data administration subsystem

Back 9

Database Management System (DBMS)

Front 10

part of a DBMS that helps you create and maintain the data dictionary and define the structure of the files in a database

Back 10

Data Definition Subsystem

Front 11

contains the logical structure for the information in a database

Back 11

Data Dictionary

Front 12

part of a DBMS that helps you add, change, and delete information in a database and query it for valuable information

Back 12

Data Manipulation Subsystem

Front 13

a subset of a data warehouse in which only a focused portion of the data warehouse information is kept

Back 13

Data Mart

Front 14

the software tool you use to query information in a data warehouse

Back 14

Data-Mining Tool

Front 15

a logical collection of information – gathered from many different operational databases – used to create business intelligence that supports business analysis activities and decision-making tasks

Back 15

Data Warehouse

Front 16

accepts logical requests from the various other DMBS subsystems, converts them into their physical equivalent, and actually accesses the database and data dictionary as they exist on a storage device

Back 16

DBMS Engine

Front 17

displays key information gathered from several sources on a computer screen in a format tailored to the needs and wants of an individual knowledge worker. Can provide up-to-the-minute snapshots of any type of information

Back 17

Digital Dashboard

Front 18

a primary key of one file that appears in another file

Back 18

Foreign Key

Front 19

a rule that helps ensure the quality of the information

Back 19

Integrity Constraint

Front 20

focuses on how you as a knowledge worker need to arrange and access information to meet your particular business needs

Back 20

Logical View

Front 21

slice-and-dice techniques that allow you to view multidimensional information from different perspectives

Back 21

Multidimensional Analysis (MDA) Tool

Front 22

the manipulation of information to support decision making

Back 22

Online Analytical Processing (OLAP

Front 23

the gathering of input information, processing that information, and updating existing information to reflect the gathered and processed information
Operational Database: databases that support OLTP

Back 23

Online Transaction Processing (OLTP)

Front 24

deals with how information is physically arranged, stored, and accessed on some type of storage device such as a hard disk

Back 24

Physical View

Front 25

a field (or group of fields in some case) that uniquely describes each record

Back 25

Primary Key

Front 26

similar to QBE tools, SQL, and report generators in the typical database environment. Data warehouses users use these types of tools to generate simple queries and reports

Back 26

Query-and-Reporting Tool

Front 27

helps you graphically design the answer to a question
Recovery: the process of reinstalling the backup information in the event the information was lost

Back 27

Query-by-Example (QBE) Tool

Front 28

describes each two-dimensional table or file in the relational model

Back 28

Relation

Front 29

uses a series of logically related two-dimensional tables or files to store information in the form of a database

Back 29

Relational Database

Front 30

helps you quickly define formats of reports and what information you want to see in a report

Back 30

Report Generator

Front 31

a standardized fourth-generation query language found in most DBMS. Performs the same function as QBE, except you perform the query by creating a statement

Back 31

Structured Query Language (SQL

Front 32

allows you to see the contents of a database file, make whatever changes you want, perform simple sorting, and query to find the location of specific information

Back 32

View

Front 33

form of XP, aims for customer satisfaction through early continuous delivery of useful software components. Agile is similar to XP buy with less focus on team coding and more on limiting project scope

Back 33

Agile Methodology

Front 34

this is the second part of the SDLC, which involves end users and IT specialists working together to gather, understand, and document the business requirements for the proposed system. There are two parts to the Analysis phase, gathering the business requirements and prioritize the requirements

Back 34

Analysis Phase

Front 35

are the detailed set of end user requests that the system must meet to be successful. It states what the system must do from the business perspective and drives the entire system.

Back 35

Business Requirement

Front 36

It is a general approach to systems development that focuses on building small self contained blocks of code (components) that can be reused across a variety of applications within an organization. Example: Write software once, place it in a library of software components, and then allow software development teams to plug in that component.

Back 36

Component-based development (CBD)

Front 37

factor critical to you organization’s success, and allows an organization to strategically decide which system to build. Is used in the defining the system to be developed activity of the planning phase of the SDLC

Back 37

Critical Success Factor (CSF)

Front 38

third part of the SDLC and the goal is to build a technical blueprint of how the proposed system will work. Take the business requirements generated during the analysis phase and define the supporting technical architecture in the design phase.

Back 38

Design Phase

Front 39

breaks a project into tiny phases and developers cannot continue on to the next phase until the current phase is complete. There are many small pieces that make no sense individually but when they are combined together an organization can gain visibility into the entire system. XP divides its phases into iterations.

Back 39

Extreme Programming methodology (XP)

Front 40

Part of the set the project scope part of the planning phase of SDLC. It occurs when developers and end users add extra features that were not part of the initial requirements

Back 40

Feature Creep

Front 41

part of the Maintenance phase of SDLC and is a way to support users. Help Desk is a group of people who respond to users’ questions.

Back 41

Help Desk

Front 42

is a phase of SDLC in which you distribute the system to all the users and they begin using the system to perform their everyday jobs. It includes writing detailed user documentation and providing training for the system users

Back 42

Implementation Phase

Front 43

in house IT specialists within the organization is tasked with developing the system

Back 43

Insourcing

Front 44

Verifies that separate systems can work together

Back 44

Integration Testing

Front 45

list of all systems that an organization needs to develop but – because of the prioritization of systems development needs – never get funded because of the lack of organizational resources. (Benefit of Selfsourcing)

Back 45

Invisible Backlog

Front 46

users and IT specialists meet to define and review the business requirements of a system

Back 46

Joint Application Development (JAD)

Front 47

is the seventh and last part of the SDLC, in which you monitor and support the new system to ensure it, continue to meet the business goals.

Back 47

Maintenance Phase

Front 48

is contracting an outsourcing arrangement with a company in a nearby country, usually this country will share a border

Back 48

Nearshore outsourcing

Front 49

is contracting with a company that is geographically far away, usually for certain IT services like application development, maintenance, and help desk support. Is a growing trend and not only cost effective but provides sophisticated and highly efficient quality services

Back 49

Offshore outsourcing

Front 50

runs over the internet or off CD or DVD. Employees perform the training at any time, on their own computers, at their own pace and are convenient because they can set their own schedule to undergo training.

Back 50

Online training

Front 51

process of engaging another company in the same country for services

Back 51

Onshore outsourcing

Front 52

Third Party is delegated a specific work for a specified length of time, at a specific cost, and at a specified level of service

Back 52

Outsourcing

Front 53

uses both the old and new systems until you’re sure that the new system performs correctly.

Back 53

Parallel implementation

Front 54

installs the new system in phases until you’re sure it works correctly and then the remaining phases of the new system are implemented.

Back 54

Phased implementation

Front 55

has only a small group of people using the new system until you know it works correctly and then the remaining people are added to the system

Back 55

Pilot implementation

Front 56

is the First part of the SDLC in which you create a solid plan for developing your information system. The three primary activities are defining the system to be developed, setting the project scope, and develop the project plan.

Back 56

Planning phase

Front 57

discards the old system completely and immediately uses the new system

Back 57

Plunge implementation

Front 58

is an individual who is an expert in project planning and management, defines and develops the project plan, and tracks the plan to ensure that all key project milestones are completed on time.

Back 58

Project manager

Front 59

represent key dates by which you need a certain group of activities performed.

Back 59

Project milestones

Front 60

defines what, when, and who questions of systems development including all activates to be performed, the individuals, or resources, who will perform the activities, and the time required to complete each activity. It is the guiding force behind ensuring the onetime delivery of a complete and successful information system

Back 60

Project plan

Front 61

– is a written document of the project scope, which defines the high level requirements and is the basic definition of the system

Back 61

Project scope document

Front 62

is prototype you use to prove the technical feasibility of a proposed system

Back 62

Proof-of-concept prototype

Front 63

is a model of a proposed product, service, or system

Back 63

Prototype

Front 64

emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process

Back 64

Rapid Application Development methodology (RAD) (Rapid Prototyping)

Front 65

is a formal document that describes in excruciating detail your logical requirements for a proposed system and invites outsourcing organizations to submit bids for its development.

Back 65

Request for proposal (RFP)

Front 66

Prioritize all the business requirements in order of business importance and place them in a formal comprehensive document

Back 66

Requirements Definition Document

Front 67

development and support of the IT systems by end users (knowledge workers) with little or no help from IT specialists

Back 67

Selfsourcing (End-User Development)

Front 68

is a prototype that you use to convince people of the worth of a proposed system

Back 68

Selling prototype

Front 69

is a formal contractually obligated agreement between two parties, usually for systems, defines the work to be done, the time frame, the metrics that will be used to measure the success of the systems development effort, and the costs.

Back 69

Service level agreement (SLA)

Front 70

same as SLS

Back 70

Service level objective (SLO)

Front 71

technical specifications are included in a supporting document (similar to a contract addendum)

Back 71

Service level specifications (SLS)

Front 72

is the users’ actual signatures indicating they approve all the business requirements

Back 72

Sign Off

Front 73

is a structured step by step approach for developing information systems that includes seven key phases and numerous activities in each. (Planning – Analysis – Design – Development – Testing – Implementation – Maintenance)

Back 73

Systems development life cycle (SDLC)

Front 74

Verifies that the units or pieces of code written for a system function correctly when integrated into the total system

Back 74

System Testing

Front 75

in the design phase, defines the hardware, software, and telecommunications equipment required to run the system

Back 75

Technical Architecture

Front 76

is the fifth part of SDLC and it verifies that the system works and meets all the business requirements defined in the analysis phase. It includes writing the test conditions and performing the testing of the systems.

Back 76

Testing Phase

Front 77

Tests individual units or pieces of code for a system

Back 77

Unit Testing

Front 78

determines if the system satisfies the business requirements and enables users to perform their jobs correctly

Back 78

User Acceptance Testing (UAT)

Front 79

this is something provided to employees when you install the system, it highlights how to use the system.

Back 79

User documentation

Front 80

is a sequential, activity based process in which one phase of the SDLC is followed by another, from planning through implementation.

Back 80

Waterfall methodology

Front 81

is held in a classroom environment and is led by an instructor, more suitable for difficult systems.

Back 81

Workshop Training

Front 82

infrastructure is the most basic setup because it involves a single tier on a single machine. An example of a 1-tiered application is a basic word processor or desktop file utility program.

Back 82

1-tier

Front 83

infrastructure is the basic client/server relationship. The client handles the display, the server handles the request and the application tier is contained on one or both of the two tiers.

Back 83

2-tier

Front 84

infrastructure is the most common approach used for Web applications today. An example is the Web browser that acts as the client, an application server that handles the business logic and a separate tier that handles database functions.

Back 84

3-tier

Front 85

percentage of callers who hang up while waitin for their call to be answered

Back 85

Abandon rate

Front 86

number of visitors who start the process f completing a registration page and then abandon

Back 86

Abandoned registration

Front 87

the number of visitors who create a shopping cart and start shopping and then abandon the activity before paying for the merchandise

Back 87

Abandoned shopping carts

Front 88

also usually measured inversely as error rate, or the number of errors per thousand that a system generates.

Back 88

Accuracy

Front 89

supplies software applications over the inernet that would otherwise reside on customers; computers

Back 89

Application service provider (ASP)

Front 90

the average time to get answered by a real person

Back 90

Average Speed to Answer (ASA)

Front 91

baseline values a system seeks to attain

Back 91

Benchmark

Front 92

is the process of continuously measuring system results and comparing those to benchmarks

Back 92

Benchmarking

Front 93

a step by step guideline defining how the organization will recover from a disaster or extended disruption of its business process

Back 93

Business continuity plan

Front 94

a rigorous and ell informed organizational methodology for developing a business continuity plan

Back 94

Business continuity planning (BCP)

Front 95

measure the success of call center efforts

Back 95

Call center metrics

Front 96

involves sharing information systems in one central area or on one central mainframe.

Back 96

Centralized infrastructure

Front 97

count the number of people who visit a site, click on an ad, and are taken to the site of the advertiser

Back 97

Click through

Front 98

has one or more computers that are servers which provide services to other computers called clients

Back 98

Client/server infrastructure

Front 99

is a separate facility that does not have any computer equipment but is a place where employees can move after the disaster

Back 99

Cold Site

Front 100

is available to a company that rents space and telecommunications equipment from another company.

Back 100

Collocation facility

Front 101

percentage of potential customers who visit your site who actually buy something

Back 101

Conversion rate

Front 102

sales dollars generated per dollar of advertising

Back 102

Cost Per Thousand (CPM)

Front 103

involves little or no sharing of IT and other resources such as information.

Back 103

Decentralized infrastructure

Front 104

charts the cost to your organization of the unavailability of information and technology and the cost to your organization of recovering from a disaster over time

Back 104

Disaster recovery cost curve

Front 105

involves distributing the information and processing power of IT systems via a network

Back 105

Distributed infrastructure

Front 106

doing the right thing

Back 106

Effectiveness

Front 107

doing something right

Back 107

Efficiency means

Front 108

the percentage of calls that can be resolved without have to call back

Back 108

First Call Resolution (FCR)

Front 109

is a separate fully equipped facility where the company can move immediately after a disaster and resume business

Back 109

Hot Site

Front 110

is a relative term meaning the structure beneath a structure

Back 110

Infrastructure

Front 111

centric metric measures of efficiency, speed and/or capacity for technology

Back 111

Infrastructure

Front 112

refers to the capability of two or more computing components to share information and other resources, even if they are made by different manufacturers

Back 112

Interoperability