ch1

Question 1

database

Answer 1

organized collection of logically related data

Question 2

data

Answer 2

• stored objects that have meaning and importance

- two types: structured (table) and unstructure (media)

Question 3

information

Answer 3

processed data to INCREASE KNOWLEDGE

Question 4

metadata

Answer 4

• data that describes data. gives data meaning. like the headers of the table.
• includes: type, length, range, description

Question 5

file processing systems

Answer 5

• like a file cabinet. each business function has their own different one and format. decentralized, some duplication of data.

Question 6

disadvantages of file processing systems

Answer 6

• program data dependence
• data duplication
• limited data sharing
• lengthy development times
• excessive program maintenance

be careful not to put these in when developing your database

Question 7

data models

Answer 7

graphical representation of nature and relationships of data

Question 8

entity

Answer 8

NOUN. like an object in java.

Question 9

attribute

Answer 9

data you are interested in keeping about entities

Question 10

instance

Answer 10

each record of an entity

Question 11

relational database

Answer 11

establish RELATIONSHIPS between entities by means of COMMON FIELDS. collection of tables that link to each other

Question 12

database management systems (DBMS)

Answer 12

software system that enables use of database approach

Question 13

data independence

Answer 13

separating metadata from applications that use the data. applications are not able to mess with metadata

Question 14

redundant definition

Answer 14

able to be deleted without loss of function

Question 15

user view

Answer 15

different users will have different views of same unified database

Question 16

constraint

Answer 16

rule that cannot be violated by database users

Question 17

data warehouse

Answer 17

combine historical data with new data to make bigger decisions

Question 18

CASE tools

Answer 18

automated computer algorithms used to engineer data design

Question 19

repository

Answer 19

restructure/recombine the data of other databases in a more meaningful manner to your task

Question 20

application programs

Answer 20

allow you to easily use the data

Question 21

system developers

Answer 21

design the database and applications

Question 22

queries

Answer 22

commands against the database. like a command line. AKA ad-hoc querying - takes more technical skills

Question 23

personal database

Answer 23

designed for one user. like your itunes lib. but they are difficult for others to use

Question 24

workgroup

Answer 24

small group <25 users that work on same project

Question 25

two-tier client server database

Answer 25

computers use centralized database. does introduce some new issues to think about. best for <100 users

Question 26

mutitier client server database

Answer 26

heavy application logic is done "in the cloud" and data relayed to client tier. best for 100-1000 users

Question 27

enterprise applications

Answer 27

scope is the entire business

Question 28

ERP

Answer 28

enterprise resource planning. cross functional. allows easy syncronization of activities. best for >100 users

Question 29

extranet

Answer 29

like the internet but only for allowed B2B customers

Question 30

intranet

Answer 30

like the internet but used only by internal employees

Question 31

hierarchial model

Answer 31

files organized like a tree

Question 32

object oriented model

Answer 32

object classes and relationships between them. good for multimedia.

Question 33

object relational model

Answer 33

hybrid between OO and relational models

Question 34

multidimensional database

Answer 34

basis of data warehouse. view in cubes or star schema

Question 35

enterprise data modeling

Answer 35

scope and general contents of databases are designed

Question 36

compendium

Answer 36

brief summary of larger work; paraphrase

Question 37

top up approach

Answer 37

try to meet organization goals; upper management

Question 38

bottom up approach

Answer 38

features requested by users

Question 39

systems development life cycle

Answer 39

methodology used to develop, maintain, and replace info systems

Question 40

enterprise modeling

Answer 40

figure out what data you have and what you in proposed systems. pick the best one system.

Question 41

conceptual data modeling

Answer 41

develop high level data model and then do a detailed plan with everything. same as conceptual schema

Question 42

conceptual schema

Answer 42

detail structure of organizational data, important entities and attributes, NOT database design. high level so management can understand

Question 43

logical database design

Answer 43

different format of conceptual schema. more technical but still somewhat independent from underlying technology

Question 44

physical schema

Answer 44

specifications for how the logical schema will run on actual hardware. what will be on which servers?

Question 45

database maintenance

Answer 45

longest part of life cycle. database will have to evolve according to needs

Question 46

prototyping

Answer 46

iterative process, continual communication between users and analysts to converge on needs. try new things all the time?

Question 47

agile software development

Answer 47

focus on individuals, not the computers

Question 48

three schema architecture

Answer 48

1) external schema (user view) 2) conceptual schema (admin view) 3) internal schema (logical+physical schemas)

Question 49

project

Answer 49

planned undertaking that has specific beginning and end

Question 50

one to many relationship

Answer 50

one entity contains many of another entity

Question 51

primary key

Answer 51

d

Question 52

index

Answer 52

copy some data into another table for ease of access. example: index of all last names starting with L

Question 53

systems development life cycle general steps

Answer 53

1) planning 2) analysis 3) design 4) implementation 5) maintenance