I'm pretty new to OO
design and was hoping for some pointers on an app I'm working on as far as
objects I should create to work with.
The part of the app.
I'm working on is for the management of Areas which are groupings of rooms (on a
university campus). The rooms are within buildings (which are also within
campuses) and both buildings and rooms have contacts. The app. has an
interface to select rooms (70,000+) from the buildings(800+) to put into 1 of 10
areas. Once the rooms are added to an area, which just saves this relation to a
DB table, I'm needing to start working with areas and that is where I would
love some advice. (moving rooms between areas, taking rooms out of areas,
adding contacts to rooms, etc.)
Currently, I've been
returning queries from my cfcs in a mach-ii framework to supply the interface
with these list, but I think I need to create an Area object and I'm not sure
the best way to do this. I'm thinking the area object should contain room
objects which have a set of properties and might also contain contact
objects. All of this info sits in a variety of DB tables and I'm wondering if I
should create this hierarchy of objects to work with areas from a bunch of DB
sql statements. I'm thinking I will somehow create an object hierarchy that
looks like area>rooms>contacts and then be able to call methods down to
the contact level to get info or change properties.
Any help
appreciated.
Thanks,
Matt
-----------------------------
Matt Gregg
612.624.5144
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Research Subjects� Protection Programs - University
of Minnesota
http://www.research.umn.edu/subjects
http://www.research.umn.edu/subjects
