Unt Ais 4100 Chapter 15, 16, 4, 5

Front 1

data modeling 585

Back 1

is the process of defining a databse so that it faithfully represents all aspects of the organization, including its interatctions with the external environment.

Front 2

entity-relationship (E-R) diagram pg 585

Back 2

is a graphical technique for portarying a database schema

Front 3

REA data model pg 587

Back 3

was developed specifically for use in desingning AIS.

Front 4

resources pg 587

Back 4

are those things that have economic value to the organization

Front 5

events pg 587

Back 5

are the various business activities about which management wants to collect infoirmation for planning or control purposes.

Front 6

agents pg 587

Back 6

are the people and organizaitons that participate in events and about whom informatin is desired for planning control, and evaluation purposes.

Front 7

cardinalities pg 594

Back 7

describe the nature of the relationship between two entities by indicating how many instances of one entity can be linked to each specific instance of another entity.

Front 8

minimum cardinality pg 594

Back 8

can be either zero or one, depending upon whether the relationship between the two entities is optional or mandatory cardinality is one.

Front 9

maximum cardinality pg 596

Back 9

can be either one or may depending upon whter each instance of entiy A can be linked to at most one instance or potentially many nstances of entity B

Front 10

one-to-one (1:1) relationship pg 596

Back 10

exists when the maximum cardinality for each entity in the relationship is 1.

Front 11

one to many relationship

Back 11

exist when the maximum cardinality of one entity in the relationship is 1 and the maximum cardinality for the other entity in that relationship is many

Front 12

many to many relationship

Back 12

exists when the maximum cardinaltity for both entities in the relationship is many.

Front 13

entity

Back 13

is anything about which the organization wants to collect and store information

Front 14

concatenated keys

Back 14

multiple -attribute primary keys

Front 15

database management system (DBMS) pg 127

Back 15

acts as an interface between the database and the various application programs

Front 16

database system pg 127

Back 16

the combination of the database, the DBMS, and the application programs that access the databse throught the DBMS

Front 17

databse administrator (DBA) pg 127

Back 17

the person responsible for the database

Front 18

data warehouse pg 127

Back 18

as technolgy improves many companies are developing very large databases called

Front 19

data mining pg 127

Back 19

the process of analyszing data repositories for new knowledge about the company's data and business processes

Front 20

record layout pg 129

Back 20

how the record is made up of ie record positons throu 10 fo rcutomer numbers, format of each fields.

Front 21

logical view pg 129

Back 21

is how the user or programmer conceptuallly organizes and understands the data

Front 22

physical view pg 129

Back 22

refers to how and where the data are physically arranged and stored in the computer system.

Front 23

schema pg 129

Back 23

describes the logical structure of a database.

Front 24

conceptual - level schema pg 129

Back 24

is the organizationwide view of fthe entire database.

Front 25

external level schema pg 129

Back 25

consists of a set of individual user views of portions of the databse,

Front 26

subschema pg 131

Back 26

refered to as external level schema

Front 27

internal-level schema pg 131

Back 27

provides a low-level view of the database.

Front 28

data dictionary pg 131

Back 28

which contains information about the structure of the database.

Front 29

data definition language (DDL) pg 131

Back 29

is used to (1) build the data dicitonary, (2) intialize or create the database, (3) describe the logical views for each individual user or programmer, and (4) specify any limitations or constraints on security imposed on database records or fields.

Front 30

data manipulation language (DML) pg 133

Back 30

is used for data maintenance, which includes such operations as updating, inserting, and deleting portions of the database.

Front 31

data query language (DQL) pg 133

Back 31

is used to interrogate the database. DQL retrieves, sorts,orders, and presents subsets fo the database in response to user queries.

Front 32

report writer pg 133

Back 32

which is a language that simplifies reprot creation.

Front 33

data model pg 133

Back 33

is an abstract representation of the contents of a database.

Front 34

relational data model pg 133

Back 34

represents everything in the database as being stored in the form of tables.

Front 35

relation pg 133

Back 35

also known as tables

Front 36

tuple pg 133

Back 36

each row in a relation

Front 37

primary key pg 134

Back 37

is the attribute or combination of attributes, that uniquely identifies a specific row in a table.

Front 38

foreign key pg 134

Back 38

is an attribute in a table that is primary key in another table.

Front 39

update anomaly pg 134

Back 39

changes (updates)to data bvalues are not correctly recorded.

Front 40

insert anomaly pg 136

Back 40

which occurs when trying to store data of customers which can only be mad euntil a customer actually makes a purchase.

Front 41

delete anomaly pg 136

Back 41

error that results when trying to delete a row from a table.

Front 42

relational database

Back 42

A relational database matches data by using common characteristics found within the data set. The resulting groups of data are organized and are much easier for many people to understand.

Front 43

entity integrity rule

Back 43

which states that every table must have a primary key and that the column or columns chosen to be the primary key should be unique and not null.[1] A direct consequence of this integrity rule is that duplicate rows are forbidden in a table

Front 44

referential intergrity rule

Back 44

is a property of data which, when satisfied, requires every value of one attribute (column) of a relation (table) to exist as a value of another attribute in a different (or the same) relation (table).

Front 45

normalization

Back 45

In the design of a relational database management system (RDBMS), the process of organizing data to minimize redundancy is called normalization. The goal of database normalization is to decompose relations with anomalies in order to produce smaller, well-structured relations. Normalization usually involves dividing large, badly-formed tables into smaller, well-formed tables and defining relationships between them. The objective is to isolate data so that additions, deletions, and modifications of a field can be made in just one table and then propagated through the rest of the database via the defined relationships.

Front 46

sabotage

Back 46

the intenten is to destory or harm a system or some of its components

Front 47

cookie

Back 47

is a piece of text stored on a user's computer by their web browser. A cookie can be used for authentication, storing site preferences, shopping cart contents, the identifier for a server-based session, or anything else that can be accomplished through storing text data.

Front 48

fraud

Back 48

can be defined as gaining an unfair advantage over another person.

1. false statement, representation, or disclosure
2. a material fact, which is osmehting that induces a person to act
3. An intent ot deceive
4. A justifiable reliance; that is the person relies on the msirepresenation to take an action
5. An injury or loss suffered by the victim.

Front 49

white-collar criminal

Back 49

a crime committed by a person of respectability and high social status in the course of his occupation"

Front 50

misappropriation of assets

Back 50

theft of company assets