On Sunday 23 August 2009 09:36:44 Cristian Gómez wrote: > Hi all, I were following this thread and I think that the most remarkable > post is this one from Martin who resumes the most important things that we > want to have in the showroom page. > > I made this Classes diagram [1] in DIA to make the basis for the > development of the site. It's really basic but I think that it's a start > point.
I'm missing the cardinality and direction in the relations. Second, you should add a Release class (one-to-many) to distinguish versions of applications. Also abstract the File class to a Resource class (You can then subclass File from Resource to specialize), this allows you flexibility in the resource type (which could be a screenshot, like you modeled, but also for example a howto, FAQ, homepage whatever). Application has no 'belongs to' relationship to Distribution. Instead, Distribution has a 'provides' relationship to Application. The Application attribute 'multiplatform' is useless. 'provedOn', 'notWorkingOn', 'distribution' are all one-to-many associations and should be modeled in the diagram. 'author' should be a list or even an association, not a string. popularity is a derived attribute (pun intended) grtz, Sander _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
