1 / 18

Database Application Lifecycle

Database Application Lifecycle. DATABASE PLANNING. REQ’MENTS ANALYSIS. CONCEPTUAL DESIGN. APPLICATION DESIGN. DBMS SELECTION. LOGICAL DESIGN. PHYSICAL DESIGN. IMPLEMENTATION. PROTOTYPING. DATA LOADING. TESTING. MAINTENANCE. Database Application Lifecycle. SYSTEMS DEFINITION.

xanti
Download Presentation

Database Application Lifecycle

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Database Application Lifecycle

  2. DATABASE PLANNING REQ’MENTS ANALYSIS CONCEPTUAL DESIGN APPLICATION DESIGN DBMS SELECTION LOGICAL DESIGN PHYSICAL DESIGN IMPLEMENTATION PROTOTYPING DATA LOADING TESTING MAINTENANCE Database Application Lifecycle SYSTEMS DEFINITION DB Design

  3. Planning • Planning factors. • Identify planning objectives

  4. System Definition • Identify boundaries • Identify interfaces within organisation

  5. Requirements Analysis • Information gathering • Use of requirements specification techniques • SAD

  6. Database Design MAIN AIMS • To represent data & relationships required by users and applications • To provide a data model which supports transactions • to specify a design that meets performance requirements

  7. Phases of database Design • Three main phases: • Conceptual Database Design • Logical database design • Physical Database Design

  8. Conceptual Database Design • Create a conceptual data model • Independent of any implementation details • Based on user requirements specification • assists in understanding data • facilitates communication

  9. Logical database design • The data model created in the previous phase is refined • 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 normalisation

  10. Physical Database Design HOW to physically implement: • derive tables & constraints • identify storage structures and access methods • design security features

  11. Database selection • Define terms of reference • Produce shortlist • Evaluate products • Recommend selection and produce report

  12. Application Design • Design transactions • data to be used by transactions • functions of the transactions • output of transactions • programs • Design human interface • various guidelines

  13. Prototyping • Building a working model • Used to check interpretation of requirements • Inexpensive & quick to build

  14. Implementation • Database created using DDL • Implement application programs using selected language • Implement security & integrity controls

  15. Data Loading/Conversion • Transfer any existing data • Insert any new data

  16. Testing • The process of executing the application programs with the intention of finding errors.

  17. Maintenance • Monitoring Performance • Maintaining & Upgrading

  18. Further Reading • Lifecycle • Connolly & Begg, 3rd and 4th edition, chapter 9 • Conceptual Database Design • Connolly & Begg, 3rd edition, chapter 14 • Connolly & Begg, 4th edition, chapter 15 • Logical Database Design • Connolly & Begg, 3rd edition, chapter 15 • Connolly & Begg, 4th edition, chapter 16 • Next Week • Data Modelling & Normalisation

More Related