Bmgt 301 Exam 1

Front 1

char of high quality info

Back 1

Accuracy
completeness
consistency
Unique
timeliness

Front 2

database

Back 2

structured collection of data and info about entities of interest

Front 3

DBMS

Back 3

software app with which you can create, store, organize, and retrieve data
can access multiple files at a time

Front 4

DB admin

Back 4

person responsible for the development and mgmt of an org's DBs

Front 5

entity

Back 5

person, place, thing, or event about which data and info are collected

ex: customer, order, item, distributor

Front 6

attribute

Back 6

a category of data that describes an entity

ex: customer #, F name, L name

Front 7

Relational databases

Back 7

relates data in different tables through the use of a common data element or field in those tables

used a 2D table structure

any data can be related as long as each table shares a common field

Front 8

Relational Database advantages

Back 8

increased: flexibility, scalability and perf, info intergrity, security

decreased: info redundancy

Front 9

problems with redundancy

Back 9

extra data, storage space
data inconsistency, anomalies

Front 10

info integrity

Back 10

measures the quality of info

Front 11

integrity constraint

Back 11

relational: rule that enforces basic and fundamental info-based constraints

business critical: enforce bus rules vital to an org's success and often req more insight and knowledge

Front 12

DB security features

Back 12

password
access lvl
access control

Front 13

ER diagram

Back 13

pic of pple, places, objects, etc and their relationships
visual rep
comm tool

entities: nouns (wish to collect data)
relationships verbs (associations btwn entities)

relationships can be:
1-1
1-many
many-many

Front 14

why do conceptual modeling?

Back 14

indep of tech
understandable rep of org data
helps to elicit business rules
strong foundation for dev process
com and validation of reqs and business validity

Front 15

primary key

Back 15

attribute/group that uniquely ids a row (record) in a relation
-every record has one, often numeric

Front 16

composite key

Back 16

2 or more attributes

Front 17

foreign key

Back 17

non-key attribute in one relation
primary key in another

Front 18

normalization

Back 18

break one lg table into several smaller ones
elim: repeating groups, redundant data

Front 19

problems caused by redundancies

Back 19

storage inefficiencies - wasted space and $$
processing ineffs - multiple updates
errors - requiring multiple updates leads to inconsistencies

Front 20

3 basic operations in a relational DB

Back 20

select [subset of rows that meet specific criteria]
join [combine rel tables]
project [enable users to create new tables w/only relevant data]

Front 21

first degree price discrimination

Back 21

Willingness to pay

Front 22

2nd degree p discrim

Back 22

self-selection, versioning, peak load

Front 23

3rd degree p discrim

Back 23

mkt separated into 2 or more segments

Front 24

pure bundling v mixed bundling

Back 24

A and B only sold together vs. also sold individually

Front 25

scenario manager:

Back 25

what if? used to create different scenarios by changing variables.

Front 26

goal seek:

Back 26

Use to find out how much of a specific quantity is needed to generate a number such as net income.

Front 27

solver:

Back 27

you need an objective, alternative course of action, the constraints/limitations and you use all of these things to solve for a business problem such as maximizing revenue.

Front 28

• Moore’s Law

Back 28

The number of transistors that can be placed on a semiconductor die doubles every 18-24 months.

Front 29

Metcalfe’s Law

Back 29

The value of a network increases with the square of the number of users

Front 30

public goods

Back 30

non rival/excludable

Front 31

property rts

Back 31

possession
transfer

Front 32

Porter's 5 forces

Back 32

rivalry among existing competitors
threat of subs
threat of new entrants
power of buyers
power of suppliers