Cheers for the reply.
Aggregation relationship of folder class e.g. if one folder is deleted inside a folder then the container still exists. So to draw this as UML would I have a aggregation relationship line going from the folder class to the folder class again or have more than one folder class?
So far I have 2 classes and one relationship being aggregation of 1 to 0 or many i.e. folder to file. Does this sound roughly right?
Main Topics
Browse All Topics





by: mhuntsPosted on 2007-05-01 at 22:59:13ID: 19013841
You would need a Folder class. The Folder class has a aggregation relationship to itself.
The Folder class would have methods for expand, collapse, add, delete, rename, cut, copy, paste
The File class would be related to the Folder class by aggregation.
The File class would have methods for add, rename, cut, copy, paste, open, delete