Term
| enterprise resource planning system |
|
Definition
business management system that integrates all functions of the enterprise, such as manufacturing, sales, finance, marketing, inventory, and human resources.
Software applications that provide the data necessary for the enterprise to examine and manage its activities |
|
|
Term
|
Definition
| an integrated decision support database whose content is derived from the various operational databases |
|
|
Term
|
Definition
| planned undertaking of related activities to reach an objective that has beginning and an end |
|
|
Term
| agile software development |
|
Definition
| an approach to database and software development emphasizing individuals, interaction, working software, customer collaboration, and response to change over processes, tools, contract negotiation, and strict plans |
|
|
Term
|
Definition
| 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 |
|
|
Term
|
Definition
| specifications for how data from a logical schema are stored in a computers secondary memory by a database management system |
|
|
Term
|
Definition
| the representation of a database for a particular data management technology |
|
|
Term
|
Definition
| detailed, technology independent specification of the overall structure of organization data |
|
|
Term
| systems development life-cycle |
|
Definition
| transitional methodology used to develop, maintain, and replace information systems |
|
|
Term
|
Definition
| a centralized knowledge base of all data definitions, data relationships, screen and report formats and other system components |
|
|
Term
|
Definition
| the first step in database development in which the scope and general contents of organizational databases are specified |
|
|
Term
| computer aided software engineering |
|
Definition
| software tools that provide automated support for some portions of the systems's development process |
|
|
Term
|
Definition
| a rule that cannot be violated by database users; business rules |
|
|
Term
|
Definition
| the separation of data descriptions from the application programs that use the data; allows organization data to change and evolve (within limits) without changing applications that process the data; stored in a repository |
|
|
Term
|
Definition
| a logical description of some portion of the database that is required by user to perform some task |
|
|
Term
|
Definition
| a database that represents data as a collection of tables in which all data relationships are represented by common values in related tables |
|
|
Term
|
Definition
| a person, place, object, event, or concept in the user environment about which the organization wishes to maintain data |
|
|
Term
|
Definition
| graphical systems used to capture the nature and relationships among data |
|
|
Term
| database management system |
|
Definition
| a software system that is used to create, maintain and provide controlled access to user databases |
|
|
Term
|
Definition
| 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 |
|
|
Term
|
Definition
| data that describes the properties or characteristics of end-user data and the context of those data; data about data |
|
|
Term
|
Definition
| data that have been processed in such a way as to increase the knowledge of the person who uses the data |
|
|
Term
|
Definition
| stored representations of the objects and events that have meaning and importance in the user's environments; data is raw and information is processed |
|
|
Term
|
Definition
| an organized collection of logically related data |
|
|
