| Term | Definition |
|---|
| Enterprise data modeling | The first step in database development, in which the scope and general contents or organizational database are specified. |
| Information systems architecture | A conceptual blueprint or plan that expresses the desired future structure for the information systems in an organization. |
| information engineering | A formal, top-down methodology that uses a data orientation to create and maintain information systems. |
| Top-down planning | A generic information systems planning methodology that attempts to gain a broad understanding of the information system needs of the entire organization. |
| Business function | A related group of business processes that support some aspect of the mission of an enterprise. |
| Function decomposition | A iterative process of breaking down the description of t system into finer and finer detail in which one function is described in greater detail by a set of other, supporting functions. |
| System Development Life Cycle (SDLC) | The traditional methodology used to develop, maintain, and replace information systems. |
| Steps in SDLC | 1)Planning - Enterprise modeling 2)Planning - Conceptual data modeling 3)Analysis - Conceptual data modeling 4)Design - Logical database design 5)Design - Physical database design and definition 6)Implementation - Database implementation 7)Maintenance - Database maintenance |
| Prototyping | 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. |
| Agile Software Development | An approach to database and software development that emphasizes "individual and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and response to change over following a plan." |
| Computer-aided software engineering (CASE) | Software tools that provide automated support for some portion of the systems development process. |
| Project | A planned undertaking of related activities to reach an objective that has a beginning and an end. |
| Incremental commitment | A strategy in systems development projects in which the project is reviewed after each phase and continuation of the project is rejustified in each of these reviews. |
| Three-Schema Components | 1. External schema (mgrs & other employees) 2. Conceptual schema (combines all external views into a single view) 3. Internal schema (logical and physical schema) |
| Conceptual Schema | A detailed, technology-independent specification of the overall structure of organizational data. |
| Logical Schema | The representation of a database for a particular data management technology. |
| Physical Schema | Specifications for how data from a logical schema are stored in a computer's secondary memory by a database management systems. |
| Three-tiered Database Architecture | 1. Client tier 2. Application/Web Server tier 3. Enterprise server tier |
| Client/server architecture | 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 applicatio programs on each client concentrate on user interface functions. |
Combine with other sets
Share on Facebook
Share on MySpace