Embed Size (px)
Citation preview
University of Sunderland COM 220 Lecture Three Slide 1
Database Application Database Application LifecycleLifecycle
University of Sunderland COM 220 Lecture Three Slide 2
DATABASE PLANNING
SYSTEMS DEFINITION
REQ’MENTS ANALYSIS
IMPLEMENTATION
DB Design
CONCEPTUAL DESIGN
LOGICAL DESIGN
PHYSICAL DESIGN
APPLICATION DESIGN
DBMS SELECTION
PROTOTYPING
DATA LOADING
TESTING
MAINTENANCE
Database Application Database Application LifecycleLifecycle
University of Sunderland COM 220 Lecture Three Slide 3
•Planning factors.
•Identify planning objectives
PlanningPlanning
University of Sunderland COM 220 Lecture Three Slide 4
• Identify boundaries
• Identify interfaces within organisation
System DefinitionSystem Definition
University of Sunderland COM 220 Lecture Three Slide 5
• Information gathering
• Use of requirements specification techniques– SAD
Requirements Requirements AnalysisAnalysis
University of Sunderland COM 220 Lecture Three Slide 6
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
Database DesignDatabase Design
University of Sunderland COM 220 Lecture Three Slide 7
Phases of database Phases of database DesignDesign
• Three main phases:
– Conceptual Database Design
– Logical database design
– Physical Database Design
University of Sunderland COM 220 Lecture Three Slide 8
Conceptual Database Conceptual Database DesignDesign
• Create a conceptual data model
• Independent of any implementation details
• Based on user requirements specification– assists in understanding data– facilitates communication
University of Sunderland COM 220 Lecture Three Slide 9
Logical database Logical database designdesign
• 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
University of Sunderland COM 220 Lecture Three Slide 10
HOW to physically implement:
– derive tables & constraints
– identify storage structures and access methods
– design security features
Physical Database Physical Database DesignDesign
University of Sunderland COM 220 Lecture Three Slide 11
• Define terms of reference
• Produce shortlist
• Evaluate products
• Recommend selection and produce report
Database selectionDatabase selection
University of Sunderland COM 220 Lecture Three Slide 12
• Design transactions– data to be used by transactions– functions of the transactions– output of transactions– programs
• Design human interface– various guidelines
Application DesignApplication Design
University of Sunderland COM 220 Lecture Three Slide 13
• Building a working model
• Used to check interpretation of requirements
• Inexpensive & quick to build
PrototypingPrototyping
University of Sunderland COM 220 Lecture Three Slide 14
• Database created using DDL
• Implement application programs using selected language
• Implement security & integrity controls
ImplementationImplementation
University of Sunderland COM 220 Lecture Three Slide 15
• Transfer any existing data
• Insert any new data
Data Data Loading/ConversionLoading/Conversion
University of Sunderland COM 220 Lecture Three Slide 16
• The process of executing the application programs with the intention of finding errors.
TestingTesting
University of Sunderland COM 220 Lecture Three Slide 17
• Monitoring Performance
• Maintaining & Upgrading
MaintenanceMaintenance
University of Sunderland COM 220 Lecture Three Slide 18
Further ReadingFurther 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
