CIT 381 Chapter 9, Database Systems: Design, Implementation, and
Management
1. Bottom-Up Design: A design philosophy that beings by identifying individual design components and then
aggregates them into larger units. In database design, the process begins by defining attributes and then groups them
into entities.
2. Boundaries: The external limits to which any proposed system is subjected. These limits include budgets,
personnel, and existing hardware and software.
3. Centralized Design: A process by which all database design decisions are carried out centrally by a small
group of people. Suitable in a top-down design approach when the problem domain is relatively small, as i a single
unit or department in an organization.
4. Clustered Tables: A data storage structure that physically stores related rows from different tables together
to improve the speed at which related data ban be accessed.
1/3
, 5. Cohesivity: The strength of the relationship between a module's components. Module cohesivity must be high.
6. Computer-Aided Software Engineering (CASE): See computer-aided software engineering.
7. Conceptual Design: A process that uses data-modeling techniques to create a model of a database
structure that represents real-world objects as realistically as possible The design is both software-and-hardware-in-
dependent.
8. Database Development: The process of a database design and implementation.
9. Database Fragment: A subset of distributed database. Although the fragments may be stored at different
sites within a computer network, the set of all fragments is treated as a single database. See also, horizontal fragmen-
tation and vertical fragmentation.
10. Database Life Cycle (DBLC): A cycles that traces the history of a database within an information system.
2/3
Management
1. Bottom-Up Design: A design philosophy that beings by identifying individual design components and then
aggregates them into larger units. In database design, the process begins by defining attributes and then groups them
into entities.
2. Boundaries: The external limits to which any proposed system is subjected. These limits include budgets,
personnel, and existing hardware and software.
3. Centralized Design: A process by which all database design decisions are carried out centrally by a small
group of people. Suitable in a top-down design approach when the problem domain is relatively small, as i a single
unit or department in an organization.
4. Clustered Tables: A data storage structure that physically stores related rows from different tables together
to improve the speed at which related data ban be accessed.
1/3
, 5. Cohesivity: The strength of the relationship between a module's components. Module cohesivity must be high.
6. Computer-Aided Software Engineering (CASE): See computer-aided software engineering.
7. Conceptual Design: A process that uses data-modeling techniques to create a model of a database
structure that represents real-world objects as realistically as possible The design is both software-and-hardware-in-
dependent.
8. Database Development: The process of a database design and implementation.
9. Database Fragment: A subset of distributed database. Although the fragments may be stored at different
sites within a computer network, the set of all fragments is treated as a single database. See also, horizontal fragmen-
tation and vertical fragmentation.
10. Database Life Cycle (DBLC): A cycles that traces the history of a database within an information system.
2/3
