Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
94 Cards in this Set
- Front
- Back
|
stored representations of objects and events that have meaning and importance in the user's environment
|
data
|
|
|
an organized collection of logically related data
|
database
|
|
|
data that have been processed in such a way such that the knowledge of the person who uses the data is increased
|
information
|
|
|
data that describe the properties or characteristics of end-user data and the context of that data
|
metadata
|
|
|
software system used to create, maintain, and provide controlled access to user databases
|
DBMS (database management system)
|
|
|
graphical systems used to capture the nature and relationships among data
|
data models
|
|
|
a graphical model that shows the high-level entities of the organization and the relationships among those entities
|
enterprise data models
|
|
|
a person, place, object event, or concept in the user environment about which the organization wishes to maintain data
|
entity
|
|
|
a database that represents data as a collection of tables in which all data relationships are represented by common values in related tables
|
relational database
|
|
|
an application program (or set of related programs) that is used to perform a series of database activities (create, read, update, and delete) on behalf of database users
|
database application
|
|
|
the separation of data descriptions from the application programs that use the data
|
data independence
|
|
|
a logical description of some portion of the database that is required by a user to perform some task
|
user view
|
|
|
a rule that cannot be violated by database users
|
constraint
|
|
|
a centralized knowledge base of all data definitions, data relationships, screen and report formats, and other system components
|
repository
|
|
|
10 advantages of the database approach
|
1. program-data independence
2. planned data redundancy 3. improved data consistency 4. improved data sharing 5. increased productivity of application development 6. enforcement of standards 7. improved data quality 8. improved data accessibility and responsiveness 9. reduced program maintenance 10. improved decision support |
|
|
5 disadvantages of file processing systems
|
1. program-data dependence
2. duplication of data 3. limited data sharing 4. lengthy development times 5. excessive program maintenance |
|
|
5 costs and risks of the database approach
|
1. new, specialized personnel
2. installation and managment cost and complexity 3. conversion costs 4. need for explicit backup and recovery 5. organizational conflict |
|
|
a business management system that integrates all functions of the enterprise, such as manufacturing, sales, finance, marketing, inventory, accounting, and human resources
|
enterprise resource planning (ERP)
|
|
|
software applications that provide the data necessary for the enterprise to examine and manage its activities
|
ERP systems
|
|
|
an integrated decision support database whose content is derived from the various operational databases
|
data warehouses
|
|
|
the first step in database development, in which the scope and general contents of organizational databases are specified
|
enterprise data modeling
|
|
|
a conceptual blueprint or plan that expresses the desired future structure for the information systems in an organization (of which an enterprise data model is a part)
|
information systems architecture (ISA)
|
|
|
a formal, top-down methodology (for IS planning) that uses a data orientation to create and maintain information systems
|
information engineering
|
|
|
a generic information systems planning methodology that attempts to gain a broad understanding of the information system needs of the entire organization
|
top-down planning
|
|
|
to align information technology with the business strategies of the organization
|
goal of IS planning
|
|
|
organization goals, critical success factors, problem areas
|
strategic planning factors that are identified in 1st step of planning phase of information engineering
|
|
|
a related group of business processes that support some aspects of the mission of an enterprise
|
business functions
|
|
|
5 corporate planning objects to be indentified in 2nd step of planning phase of information engineering
|
1. organizational units
2. ogranization locations 3. business functions 4. entity types 5. information systems |
|
|
3 components of a comprehensive enterprise model (last step of planning phase of information engineering)
|
1. a fuctional breakdown (decomposition) model of of each business function
2. an enterprise data model 3. various planning matrixes |
|
|
an iterative process of breaking down the description of a system into finer and finer detail in which one function is decribed in greater detail by a set of other, supporting functions
|
functional decomposition
|
|
|
the traditional methodology used to develop, maintain and replace information systems
|
systems development life cycle (SDLC)
|
|
|
an iterative process of systems development in which requirements are converted to a working system that is continually revised through close work between analysts and users
|
prototyping (a rapid application development RAD method)
|
|
|
an approach to database and software development that emphasizes "individuals and interactions over processing and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and response to change over following a plan"
|
agile software development
|
|
|
software tools that provide automated support for some portion of the systems development process
|
computer-aided software engineering (CASE)
|
|
|
a planned undertaking of related activities to an objective that has a beginning and an end
|
project
|
|
|
a strategy in systems development projects in which the project is reviewed after each phase and continuation is rejustified in each of these reviews
|
incremental commitment
|
|
|
a detailed, technology-independent specification of the overall structure of organizational data
|
conceptual schema (or data model)
|
|
|
the representation of a database for a particular data management technology
|
logical schema (or data model)
|
|
|
specifications for how data from a logical schema are stored in a computer's secondary memory by a database management system
|
physical schema (or data model)
|
|
|
a LAN-based environment in which database software on a server (called a database server or database engine) performs database commands sent to it from client workstations, and application programs on each client concentrate on user interface functions
|
client/server architecture
|
|
|
a statement that defines or constrains some aspect of the business. it is intended to assert business structure or to control or influence the behavior of the business.
|
business rule
|
|
|
a word or phrase that has specific meaning for the business
|
term
|
|
|
an association between two or more terms
|
fact
|
|
|
a logical representation of the data for an organization or for a business area using entities for categories of data and relationships for associations between entities
|
entity-relationship model (E-R model)
|
|
|
a graphical representation of an entity-relationship model
|
entity-relationship diagram (ERD)
|
|
|
a person, place, object, event, or concept in the user environment about which the organization wishes to maintain data
|
entity
|
|
|
a collection of entities that share common properties or characteristics
|
entity type
|
|
|
a single occurrence of an entity type
|
entity instance
|
|
|
an entity that exists independently of other entity types
|
strong entity type
|
|
|
an entity type whose existence depends on some other entity type
|
weak entity type
|
|
|
the relationship between a weak entity type and its owner
|
identifying relationship
|
|
|
a property or characteristic of an entity or relationship type that is of interest to the organization
|
attribute
|
|
|
an attribute that must have a value for every entity (or relationship) instance with which it is associated
|
required attribute
|
|
|
an attribute that may not have a value for every entity (or relationship) instance with which it is associated
|
optional attribute
|
|
|
an attribute that has meaningful component parts (attributes).
|
composite attribute
|
|
|
an attribute that cannot be broken down into smaller components that are meaningful to the organization
|
simple (or atomic) attribute
|
|
|
an attribute that may take on more than one value for a given entity (or relationship) instance
|
multivalued attribute
|
|
|
an attribute whose values can be calculated from related attribute values
|
derived attribute
|
|
|
an attribute (or combination of attributes) whose value distinguishes instances of an entity type
|
identifier
|
|
|
an identifier that consists of a composite attribute
|
composite identifier
|
|
|
a meaningful association between (or among) entity types
|
relationship type
|
|
|
an association between (or among) entity instances where each relationship instance associates exactly one entity instance from each participating entity type
|
relationship instance
|
|
|
an entity type that associates the instances of one or more entity types and contains attributes that are peculiar to the relationship between those entity instances
|
associative entity
|
|
|
the number of entity types that participate in a relationship
|
degree (of a relationship)
|
|
|
a relationship between instances of a single entity type
|
unary relationship
|
|
|
a relationship between the instances of two entity types
|
binary relationship
|
|
|
a relationship between the instances of three entity types
|
ternary relationship
|
|
|
specifies the number of instances of one entity that can (or must) be associated with each instance of another entity
|
cardinality constraint
|
|
|
the minimum number of instances of one entity that may be associated with each instance of another entity
|
minimum cardinality
|
|
|
the maximum number of instances of one entity that may be associated with each instance of another entity
|
maximum cardinality
|
|
|
a time value that is associated with a data vale, often indicating when some event occurred that affected the data value
|
time stamp
|
|
|
the model that has resulted from extending the original E-R model with new modeling constructs (like supertypes / subtypes)
|
enhanced entity-relationship (EER) model
|
|
|
a subgrouping of the entities in an entity type that is meaningful to the organization and that shares common attributes or relationships distinct from other subgroupings
|
subtype
|
|
|
a generic entity type that has a relationship with one or more subtypes
|
supertype
|
|
|
a property by which subtype entities inherit values of all attributes and instances of all relationships of the supertype
|
attribute inheritance
|
|
|
the process of defining a more general entity type from a set of more specialized entity types
|
generalization
|
|
|
the process of defining one or more subtypes of the supertype and forming supertype/subtype relationships
|
specialization
|
|
|
a type of constraint that addresses the question whether an instance of a supertype must also be a member of at least one subtype
|
completeness constraint
|
|
|
specifies that each entity instance of the supertype must be a member of some subtype in the relationship
|
total specialization rule
|
|
|
specifies that an entity instance of the supertype is allowed not to belong to any subtype
|
partial specialization rule
|
|
|
a constraint that addresses the question whether an instance of a supertype may simultaneously be a member of two (or more) subtypes
|
disjointness constraint
|
|
|
a rule that specifies that an instance of a supertype may not simultaneously be a member of two (or more) subtypes
|
disjoint rule
|
|
|
a rule that specifies that an instance of a supertype may simultaneously be a member of two (or more) subtypes
|
overlap rule
|
|
|
an attribute of the supertype whose values determine the target subtype or subtypes
|
subtype discriminator
|
|
|
a hierarchical arrangement of supertypes and subtypes, where each subtype has only one supertype.
|
supertype/subtype hierarchy
|
|
|
a set of one or more entity types and associated relationships grouped into a single abstract entity type
|
entity cluster
|
|
|
a generic or template data model that can be reused as a starting point for a data modeling project
|
universal data model
|
|
|
a statement derived from other knowledge in the business
|
derivation (a classification of business rules)
|
|
|
a statement that expresses some aspect of the static structure of the organization
|
structural assertion (a classification of business rules)
|
|
|
a statement of a constraint or control on the actions of the organization
|
action assertion (a classification of business rules)
|
|
|
a fact that is derived from business rules using an algorithm or inference
|
derived fact
|
|
|
a business rule (a fact) on which actions are limited
|
anchor object
|
|
|
an operation, such as create, delete, update, or read, which may be performed on data objects
|
action
|
|
|
a business rule (a fact) that influences the ability to perform an action on another business rule
|
corresponding object
|
