OMIS 3730 Chapter Notes - Chapter 1-3: Enterprise Architecture, Database Application, Subtyping

118 views3 pages
Chapter 1
Data: Stored representations of objects and events that have meaning and importance in the users
Information: Data that have been processed in such a way that they can increase the knowledge of the
person who uses it.
Metadata: Data that describes the properties or characteristics of end-user data and the context of that
Database application: 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.
Data model: graphical systems used to capture the nature and relationships among data.
Data warehouse: An integrated decision support database whose content is derived from the various
operational databases.
Constraint: A rule that cannot be violated by database users.
Database: An organized collection of logically related data.
Entity: A person, place, object, event, or concept in the user environment about which the organization
wishes to maintain data.
Database management system: A software system that is used to create, maintain, and provide controlled
access to user databases.
Relational database: a database that represents data as a collection of tables in which all data
relationships are represented by common values in related tables.
Data independence: the separation of data description from the application programs that use the data.
User view: a logical description of some portion of the database that is required by a user to perform
some task.
Data modeling and design tools: software tools that provide automated support for creating data models.
Repository: a centralized knowledge base of all data definitions, data relationships, screen and report
formats, and other system components.
Enterprise data modeling: the first step in database development, in which the scope and general
contents of organizational databases are specified.
Systems development life cycle (SDLC): A traditional methodology used to develop, maintain, and
replace information systems.
Conceptual data model (or schema): A detailed, technology-independent specification of the overall
structure of organizational data.
Logical data model (or schema): The representation of data for a particular data management
technology (such as the relational model). In the case of a relational data model, elements include tables,
columns, rows, primary and foreign keys, as well as constraints.
Physical data model (or schema): A set of specifications that detail how data from a logical data model
(or schema) are stored in a computers secondary memory for a specific database management system.
There is one physical data model (or schema) for each logical data model
Prototyping: an iterative process of systems development in which requirements are converted to a
working system that is continually revised through close work between analyst and users.
Agile software development: An approach to database and software development that
emphasizes “individuals and interactions” over processes and tools, “working software” over
comprehensive documentation, “customer collaboration” over contract negotiation, and “response to
change” over following a plan.
Project: a planned undertaking of related activities to reach an objective that has a beginning and an end.
Enterprise resource planning: a business management system that integrates all functions of the
Unlock document

This preview shows page 1 of the document.
Unlock all 3 pages and 3 million more documents.

Already have an account? Log in

Get access

$10 USD/m
Billed $120 USD annually
Homework Help
Class Notes
Textbook Notes
40 Verified Answers
Study Guides
1 Booster Class
$8 USD/m
Billed $96 USD annually
Homework Help
Class Notes
Textbook Notes
30 Verified Answers
Study Guides
1 Booster Class