The document discusses the database development process, including defining terms like enterprise data models and information systems architecture. It describes the system development life cycle and prototyping approaches for database development. It also covers topics like the roles of individuals, three-schema architecture, and packaged data models in database design.

1. Chapter 2: The Database Development Process Modern Database Management 7 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden

4. Figure 2-1 Segment from enterprise data model (Pine Valley Furniture Company) [simplified E-R diagram, repeat of figure 1.3] Enterprise data model describes the high-level entities in an organization and the relationship between these entities

11. Figure 2-2 -- Example of process decomposition of an order fulfillment function (Pine Valley Furniture) Decomposition -- breaking large tasks into smaller tasks in a hierarchical structure chart

13. Example business function-to-data entity matrix (Fig. 2-3) Business Planning X X X X Product Development X X X X Materials Management X X X X X X Order Fulfillment X X X X X X X X X Order Shipment X X X X X X Sales Summarization X X X X X Production Operations X X X X X X X Finance and Accounting X X X X X X X X Customer Product Raw Material Order Work Center Work Order Invoice Equipment Employee Business Function (users) Data Entity Types

15. Systems Development Life Cycle (Figures 2-4, 2-5) Project Identification and Selection Project Initiation and Planning Analysis Physical Design Implementation Maintenance Logical Design

16. Systems Development Life Cycle (cont.) (Figures 2-4, 2-5) Maintenance Purpose --preliminary understanding Deliverable –request for project Database activity – enterprise modeling Project Identification and Selection Project Identification and Selection Project Initiation and Planning Analysis Physical Design Implementation Maintenance Logical Design

17. Systems Development Life Cycle (cont.) (figures 2-4, 2-5) Purpose – state business situation and solution Deliverable – request for analysis Database activity – conceptual data modeling Project Initiation and Planning Project Identification and Selection Project Initiation and Planning Analysis Physical Design Implementation Maintenance Logical Design

18. Systems Development Life Cycle (cont.) (figures 2-4, 2-5) Purpose – thorough analysis Deliverable – functional system specifications Database activity – conceptual data modeling Analysis Project Identification and Selection Project Initiation and Planning Analysis Physical Design Implementation Maintenance Logical Design

19. Systems Development Life Cycle (cont.) (figures 2-4, 2-5) Maintenance Purpose – information requirements structure Deliverable – detailed design specifications Database activity – logical database design Logical Design Project Identification and Selection Project Initiation and Planning Analysis Physical Design Implementation Maintenance Logical Design

20. Systems Development Life Cycle (cont.) (figures 2-4, 2-5) Purpose – develop technology specs Deliverable – program/data structures, technology purchases, organization redesigns Database activity – physical database design Physical Design Project Identification and Selection Project Initiation and Planning Analysis Physical Design Implementation Maintenance Logical Design

21. Systems Development Life Cycle (cont.) (figures 2-4, 2-5) Purpose – programming, testing, training, installation, documenting Deliverable – operational programs, documentation, training materials Database activity – database implementation Implementation Project Identification and Selection Project Initiation and Planning Analysis Physical Design Implementation Maintenance Logical Design

22. Systems Development Life Cycle (cont.) (figures 2-4, 2-5) Purpose – monitor, repair, enhance Deliverable – periodic audits Database activity – database maintenance Maintenance Project Identification and Selection Project Initiation and Planning Analysis Physical Design Implementation Maintenance Logical Design

32. Figure 2-8a Gantt Chart Shows time estimates of tasks

33. Figure 2-8b PERT chart Shows dependencies between tasks

35. Different people have different views of the database…these are the external schema The internal schema is the underlying design and implementation

36. Figure 2-11 Three-tiered client/server database architecture

37. Pine Valley Furniture Preliminary data model (Figure 2-12)