Conceptual Schema (ERM) for Client/Server Architecture
I'm working through a report and proposal for a new Timetabling system for a college split over several areas. Now that I've gone through the grunt work (physical details, hardware, backup/recovery procedures, explanations, etc) I've got an Entity Relationship Model to write. The information I have is that:
Students can access and read their timetables from any area
Lecturers have read only access to only their timetables
Database holds several details (rooms, courses, departments, students, and staff)
Working under Client/Server architecture, where the database will be centrally held
I'm not asking for someone to come up with a schema for me, but I am having a lot of trouble getting this started since I've only really had experience writing small ERD's for small Starbucks problems, so any help to get me on my way would be amazing.