Database Application Methodology
Summary
- Assumptions
- The Software Process
- Overview of Methodology
- Analysis - Information Flow Diagram
- In and Out
Assumptions
- Business processes are well-designed
- Documents are known
- Documents are input to, or output from a db application
- Tasks are known
- Tasks are the processing done using the documents
- System boundary is known
- One db schema unifying all views can be designed
- Difficult with different interests, goals, power, politics
The Software Process
Waterfall:
- Business Process (re-)design
- Analysis
- Specification
- Design
- Implementation
- Testing
- Operation
- Maintenance
Overview of Methodology
In db application development process, data is always first.
- Analysis
- Information Flow Diagram
- Specification
- Tasks
- ER Diagram
- Design
- Abstract Code w/ SQL
- Relational Schema
- Implementation
- PHP Code w/ SQL
- MySQL Relational Platform
Analysis - Information Flow Diagram
Maps documents to tasks to db
Example:
IFD for project:
In and Out
- Everything in the database must come from somewhere
- Everything on the input documents must go somewhere
- Everything in the database must be used for something
- Everything on the output documents must come from somewhere