DBS Development Lifecycle & DB Analysis

1. DBS Development Lifecycle&DB Analysis Chapter 10 & 11 in Textbook

2. Stages of DBS Development lifecycle

5. Database Planning • Identifying how the stages can be completed in the most effective & efficient way. • During planning phase, four major activities are performed: • Review and approve the database project request. • Prioritize the database project request. • Allocate resources such as money, people and tools. • Arrange a development team to develop the database project.

6. Database Planning • Database planning should also include the development of standards that govern how data will be collected, how the format should be specified, what necessary documentation will be needed. • Two steps: • Mission Statement : Major aims for the Database Project. • Mission Objectives : Tasks that DB should support, Driven through Fact Finding techniques: interviews, questionnaire.

7. Database Planning Mission Statement • Interviewing the business director: • What is the purpose of your company? • Why do you need the DB? • How can the DB solve your problem?

8. Database Planning Mission Statement • Interviewing Burger King Director: • What is the purpose of your company? To prepare and sell quick service food to fulfill our guest's needs in a cleaner environment than our competitors. • Why do you need the DB? We have many branches over the world , that offers different cosines, which drive a data management problem, sharing of information between branches ( for examples : favorite meals, number of employees) which help in business decision making. • How can the DB solve your problem? No more paperwork, automating daily tasks, corporation between branches.

9. Database Planning Mission Statement Burger King DB project mission statement The purpose of BK DB project is to maintain the data that is used & generated to support the fast food business for our client and to support sharing information between branches and in decision making. Clearer view of the project

10. Database Planning Mission Objectives • Interviewing different staff: • Job description. • Daily tasks. • Data that they deal with. • Daily reports. • Type of things they keep track on. • Customer services.

11. Database Planning Mission Objectives • To manage (add, delete, update) data on branches. • To manage (add, delete, update) data on staff. • To manage (add, delete, update) on meals. • To manage (add, delete, update) on clients. • To perform searches on branches. • To perform searches on staff. • To perform searches on meals. • To perform searches on clients

13. System Definition • Identify System boundaries at a very high level, e.g.: • Current users. • Current application areas. Example: DreamHome Database System

14. System Definition • Identify User views; Define what is required of a database application from the perspective of: • A particular job role (such as Manager or Supervisor) or • Enterprise application area (such as marketing or personnel). Example: User Views

16. Requirements Collection & Analysis • Collecting and analyzing information about the part of organization to be supported by the database system, and using this information to identify users’ requirements of new system. • Identifying the required functionality for a database system is crucial, as systems with inadequate functionality will fail. • Information is gathered for each major user view including: • a description of data used or generated; • details of how data is to be used/generated; • any additional requirements for new database system.

17. Requirements Collection & Analysis • An important activity is to decide how to manage the requirements for a database system with multiple user views. • Three main approaches: • Centralized approach; • View integration approach; (we use this approach) • Combination of both approaches.

18. Requirements Collection & Analysis Centralized Approach

19. Requirements Collection & Analysis View Integration Approach

20. Requirements Collection & Analysis • Critical to capture necessary facts to build the required database application. • These facts are captured using fact-finding techniques. • When Are Fact-Finding Techniques Used? • Fact-finding used throughout database application lifecycle. • Crucial to early stages including database planning, system definition, and requirements collection and analysis stages.

21. Requirements Collection & Analysis • Fact-Finding Techniques: • Examining documentation, • Interviewing (unstructured/structured & open/closed ended questions), • Observing organization in operation, • Research, • Questionnaires (free-format and fixed-format).

23. Database Design • Creating a design for a database that will support the enterprise’s mission statement and mission objectives for the required database system. • Main aims: • To represent data and relationships required by users and applications. • To provide a data model which supports transactions. • To specify a design that meets performance requirements.

24. Database Design • Three main phases of DB design: • Conceptual Database Design. • Create a conceptual data model Independent of any implementation details. • Logical Database Design. (What) • At this point you know which type of DBMS you will implementing in - e.g. relational, object-oriented etc (but not the actual DBMS). • Test the correctness of the data model through normalization. • Physical Database Design. (How) • Derive tables & constraints. • Identify storage structures and access methods. • Design security features.

26. DBMS Selection • Selection of an appropriate DBMS to support the database system. • Undertaken at any time prior to logical design. • Main steps for selecting a DBMS: • Define Terms of Reference of study; • Shortlist two or three products; • Evaluate products; • Recommend selection and produce report.

28. Application Design • Design of user interface and application programs that use and process the database. • Database design and application design are parallel activities. • Includes two important activities: • transaction design; • user interface design.

30. Prototyping • Building working model of a database system to evaluate how the final system will look and function. • Purpose: • to identify features of a system that work well, or are inadequate; • to suggest improvements or even new features; • to clarify the users’ requirements; • to evaluate feasibility of a particular system design.

32. Implementation • Physical realization of the database and application designs. • Create database schemas and empty database files. (DDL) • Create the application programs. (DML and JAVA or C++ ...)

34. Data Conversion and Loading • Transferring any existing data into new database and converting any existing applications to run on new database. • Only required when new database system is replacing an old system.

36. Testing • Process of running the database system with intent of finding errors. • Use carefully planned test strategies and realistic data. • Demonstrates that database and application programs appear to be working according to requirements.

38. Operational Maintenance • Process of monitoring and maintaining database system following installation. • Operational Maintenance Activities: • Monitoring performance of system. • Maintaining and upgrading database application. • Incorporating new requirements into DB application.