Ridgeway Billing System
Description
problem and proposed
solutions
a high level description of problems with current billing
system. then propose solution for those problems.
DATA Flow Diagram
ER diagram and note
Entity Relational diagram and a short explanation with their relations
level 0 diagram
context level diagram
level 1 diagram
high level description about the functionalities provide by billing
system. detailed data flow are in lower lever data flow diagram
the following are child processes shown in level 1 diagram. process 1, process 2 and its children 2.1, 2.2, 2.3, 2.4, 2.5 follow the link to view those diagrams
child process 3, 7, 8, 9, 10, 11, 13
data dictionary
As information flows in the data flow diagram, I use short name or abbreviations for those
information. the elements for them are defined in data dictionary
process specifications
this is the definition for process specifications. for every process ends with a
'+' sign, there is a process specification in this file. both data dictionary and
process specifications are still updating before complete data flow diagram.
Normalized table and other related information
relational table details
this file includes all tables with their attributes and constraints.
referential integrity
this file shows all referential relationship between all table. this will become
the guild for referential integrity when implement physical database
functional dependencies
shows functional dependencies for each table. this explains how key is chosen for table.
normal form
In order to eliminate information redundancy which may lead to update anomaly.
In my normalization process, all table will be in BCNF which will guarantee no
redundancy in any table. this file will also explain normal form from 1NF to
BCNF
this is a list of forms, reports and queries in Ridgeway billing system. reports are explicitly required by management from interview. some queries like ending balance for each member are used to help to generate reports. others queries are not explicitly required, but I think it's necessary to have those. like query of refund for each member, company would like to know how much refund for each member. if any member get a lot of refund every month, then special attention should be given and employee who give those refund also should be monitored because a fraud might be involved.
form design
form design and sample
Ridgeway billing system is implemented in Oracle 9i. this link will show you all source code including script file to create eight tables( notice how constraints build into the database and how to realize the referential integrity), eight script files with sample data for each table, the results after executing those script files, triggers, queries, views, and reports.
