DATABASE DEVELOPMENT STRATEGIES TOP DOWNTOP DOWN –Large scale application driven by strategic...
-
Upload
beverly-osborne -
Category
Documents
-
view
216 -
download
2
Transcript of DATABASE DEVELOPMENT STRATEGIES TOP DOWNTOP DOWN –Large scale application driven by strategic...
DATABASE DEVELOPMENT DATABASE DEVELOPMENT STRATEGIESSTRATEGIES
•TOP DOWNTOP DOWN–Large scale application driven by strategic objectives –General Specific–Organization-wide (“data management philosophy”)–“Industrial strength” DBMS required (e.g., Oracle, DB2, SQL Server)–Done well, captures global view and integrates data–Danger: “paralysis analysis”
•BOTTOM UPBOTTOM UP–Application-centric–Produces useful systems more quickly–Smaller DBMS such as M/S Access–Less risky, more user involvement–Danger: “stovepipes”
DATABASE DEVELOPMENT DATABASE DEVELOPMENT STRATEGIESSTRATEGIES
• PROTOTYPING
Version 0
Test
Adapt
Improve
TOP DOWN DATABASE TOP DOWN DATABASE DEVELOPMENTDEVELOPMENT
Requirements
Analysis
Design
ImplementationDatabaseAdministration
EXTREME PROGRAMMINGEXTREME PROGRAMMING
•High speed waterfall approachHigh speed waterfall approach
•Component-based constructionComponent-based construction
•Build off “proof of concept”Build off “proof of concept”
EP MANIFESTOEP MANIFESTO
• Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Customer collaboration over contract negotiation.
• Responding to change over following a plan.
While there is value in the items on the right, EP values the items on the left more.
OVERVIEW OF EP PROJECTOVERVIEW OF EP PROJECT• User stories: written by stakeholders• Release planning meeting: which user stories will be
implemented and when• Iteration: code the stories (days, weeks vice months)
• Acceptance test: user accepts changes
DATABASE REQUIREMENTS
• Identify Strategic Planning Factors– Goals, critical success factors, risk analysis
• Identify Corporate Planning Objects– Organizational stakeholders (Actors), business
functions (Processes), entities (Objects)
• Requirements Statements– Inputs and outputs from existing systems (manual and
computer)– INTERVIEW END USERS FOR FORMS, REPORTS AND
QUERIES
DB REQUIREMENTS ANALYSISDB REQUIREMENTS ANALYSIS
• Develop conceptual data model (logical database design)– Entity-Relationship– Semantic Object Model (SOM)– UML
• Develop process models– Old way: data flow diagrams, process
decomposition– UML way: actor diagrams, use cases
ENTITY-RELATIONSHIP DIAGRAM
INVOICE
CUSTOMER
ORDER
EQUIPMENT
RAWMATERIAL
VENDOR
EMPLOYEE
PRODUCT
WORKCENTER
WORKORDER
Fulfills
Places Bills
ShipsRequests
Supplies
BuildsUses
Schedules
Works Assigned
ACTOR DIAGRAMIn fo rm a tion C onsum er
M arke t R esea rch M anager
M arke t R esea rch A na lys t
M arke t R esea rchS pec ia lis t
BusinessIntelligence Data
System
S ystem A dm in is tra to r
S ys tem D a tabaseA dm in is tra to r
Cendon
Tracking YellowPages Success
Files
ReceivablesM anagem ent
SystemDatabase
DecisionSupportSystem
Database
PublishingAdvertisingCustom erEnterpriseDatabase
Custom erCare
SytstemDatabse
BagelDatabase
S a les S ys tem sO pns S upport
F o recas ting A na lys t
P roduc t D eve lope r
M arketResearch
Data
G eocodedData Files
P roduc t S pec ia lis t
Claritas
N ationa l A ccoun tM anager
M arke ting D irec to r
P ric ing and P roduc tD eve lopm en t M anager
P roduc t M anagem en tM anager
P roduc t M anager
S a les D irec to r
S a les M anager N a tiona l M anager A na lys tS a les O pera tion
M anager
R eg iona l S a lesA na lys t
A d jus tm en t A na lys t
C red it A na lys t
C red it A na lys t
DATABASE DESIGN
• Logical design– Convert conceptual data model into a database schema of
normalized relations (tables)
• Physical design– Map normalized relations into actual tables– Establish indexes, keys, and file access methods– Implement referential integrity– Specify security, recovery and backup parameters
• Process design– User interfaces: menus, screens, reports– Functional design: detailed logic for each process
DB IMPLEMENTATION AND DB IMPLEMENTATION AND TESTINGTESTING
• Data– Populate database with data– Data cleansing
• Procedures– Program code– Implement user interfaces– Implement stored procedures
DATABASE ADMINISTRATION
• Maintain data integrity through execution of security, backup/recovery, and transaction procedures
• Monitor performance of database
• Establish procedures for identifying and ranking new requirements