Back to the Conceptual Data Model.
PURPOSE OF THESE FACTS :-
These FACTS define the functional requirements which the Database must meet.
They form the basis for agreement between the User and the Database Designer and are
written in a form of structured English which is clear and unambiguous.
The Draft FACTS have been defined and are detailed here ...
A. The Area being Modelled is :-
An organization providing Consulting services to Clients.
B. The Things of Interest, ('THINGS'), include :-
B.2 Billable Hours
B.4 KPIs (Key Performance Indicators)
B.6 Project Documents
C. These THINGS_OF_INTEREST are Related as follows :-
C.1 A CLIENT can have one or many ADDRESSES. For example, operating from many locations.
C.2 A CLIENT can have zero, one or many KPIs. For example, a KPI of 3 PROJECTS a year.
C.3 A CLIENT can have zero, one or many PROJECTS
c.4 A PROJECT can have many STAFF.
c.5 A PROJECT can have many DOCUMENTS.
c.6 A PROJECT DOCUMENT is always owned by a member of STAFF.
C.7 STAFF can have zero, one or many BILLABLE HOURS.
C.8 STAFF can have zero, one or many KPIs.
C.9 STAFF can work on many PROJECTS.
C.10 STAFF have zero, one or many SKILLS.
D. Sample Data includes :-
To be determined
E. Typical Enquiries include :-
E.1 Which PROJECTS is a specific member of STAFF working on ?
E.2 Who is working on a specific PROJECT ?
6th. August 2004