-
Notifications
You must be signed in to change notification settings - Fork 0
Class design
Fyger edited this page Mar 22, 2012
·
3 revisions
This shows the re-working of our current classes into more concise designs that follow the design patterns laid out in our class.
| The Mole class is used to dictate the moles that are being tracked by the user. It will contain values for the name of the mole, the id associated with the mole in the database, the description associated with the mole, the id's of the pictures assocaited with the image (ids of the pictures in the database), and lastly tag(s) to indicate the location of the picture, and potentially tags to indicate the description of the mole itself
unsigned int id string name string description ArrayList<string> tags OR unsigned int[] tags (if we have a database of tags) unsigned int[] picture_ids |
|
| The Picture class will be storing data associated with each picture taken in the application. Within in model will be the id of the picture data stored in the picture database, the picture description (as indicated in the newest requirements), the date in which the picture was taken, the tag(s) associated with the picture (as indicated by our features list and the newest requirements), a list of mole ids that are associated with this image (as more then one mole may be present in the image), and lastly we will have the image loaded into the picture file.
unsigned int id string description date taken ArrayList<string> tags OR unsigned int[] tags (if we have a database of tags) unsigned int[] mole_ids URI image |
| The MoleFactory class is going to be used as a means of generating new moles and loading moles from the database. The duel nature of this factory is to ease the transition of new moles into the database as well as the pulling of moles from the database. |
|