[SrcML] Re: UML2.0 representition
Status: Beta
Brought to you by:
crashchaos
From: Claudia L. <C.S...@we...> - 2005-05-23 10:47:30
|
Frank Raiser <fra...@in...> schrieb am 20.05.05 13:30:14: > On Fri, May 20, 2005 at 10:06:58AM +0200, Claudia Lang wrote: > > as I mentioned in the latest meeting I'm going to implement a project representing XML-Code in UML2.0 The chosen language for this project is Java and the name of the project XUML. > > After a quick google for XUML I think you might want to use another name, as > XUML is already heavily used for eXecutable UML (there also seems to be a book > available on this subject). I know that it is already in use but just with a little x: xUML. Well, ok before we start a big discussion I will change the name. > > - template class: exists in Java since version 1.5 but SrcML parses Java version 1.4.2 > > Actually only 1.3, but I'm currently working on a parser for version 1.5 which > should become useable within a few weeks. (Only annotations and enums are currently > missing). Yes, you mentioned this. Ok then template classes will be realized in this project. > > - association and association class > > What are you reasons for not including associations? Simon and me thought that it > should be possible to add aggregation relations, but we haven't yet thought about > all eventualities of course. I'm thinking about. > > - stereotype > > Could you please explain what this means in the context of class diagrams? Stereotypes are (partly user-defined) elements categorizing classes. If you desing e.g. a class and you want to note that its instances has to be saved persistent you write the stereotype "persistent" over the name of the class. You see that stereotypes don't belong to those parts of features who can be implemented in sourcecode. ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 |