Timeline for How to Model a simple file-system by UML class diagram
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2014 at 20:02 | comment | added | Isaac | @stakx: I didn't know that could be a concern. Thanks for that. | |
| Nov 29, 2014 at 18:33 | vote | accept | Isaac | ||
| Nov 29, 2014 at 9:29 | comment | added | stakx | Regarding your first question: If Directory and File were supposed to be the only possible subtypes of FileSystemElement, you could not enforce that constraint with an interface as the supertype; anyone is allowed to implement an interface they have access to. You would instead need an abstract class with a constructor that has package visibility (~ in UML). So if your package cannot actually deal with any kind of FileSystemElement, but expects only the subtypes that you defined yourself, you'd need an abstract base class. | |
| Feb 10, 2013 at 22:05 | answer | added | Pete Kirkham | timeline score: 1 | |
| Feb 10, 2013 at 16:22 | answer | added | panny | timeline score: 0 | |
| Apr 27, 2012 at 22:34 | answer | added | NoChance | timeline score: 0 | |
| Apr 27, 2012 at 17:57 | answer | added | scarfridge | timeline score: -1 | |
| Apr 27, 2012 at 14:58 | answer | added | marco-fiset | timeline score: 4 | |
| Apr 27, 2012 at 13:50 | history | asked | Isaac | CC BY-SA 3.0 |