I would like to decompose the system according to the high-level view of
subsystems described in the wiki at http://argouml.tigris.org/wiki/Design. Oon
the other hand, that is not the real truth. We could also decompose the
system in the projects (java trees) and within that the java packages and
classes. I guess the best way is somewhere in between.
/Linus
On Wed, Jun 2, 2010 at 1:10 AM, Alberto Bacchelli
<[email protected]>wrote:
> Dear developers,
>
> I am finalizing the questionnaire (it is taking a lot of time to make
> it as more usable
> as possible). I believe that your suggestion to split the question of the
> "most
> important classes" in the concerns/subsystems of ArgoUML is important.
> Could you please tell me what the concerns/subsystems of Argo are in
> your opinion? In other words, how would you decompose the system?
>
> Thank you in advance,
> Alberto
>
> On 27 May 2010 06:56, Linus Tolke Tigris <[email protected]> wrote:
> > As we are working with UML and modelling I find the focusing on classes
> > (hotspots or important classes) interesting. I would assume that the
> > important classes would have prominent places in the class diagrams (many
> > associations or associations to many different groups of classes). The
> > question is then, could an algorithm to find important classes help the
> > automatic layout algorithm in ArgoUML to do a better job or is it the
> other
> > way around that a good graphical layout could help in identifying the
> > important classes. I guess it works both ways.
> > In any case, it will be interesting to see the resulting tool.
> >
> > /Linus
> >
> > On Wed, May 26, 2010 at 10:47 PM, Tom Morris <[email protected]> wrote:
> >>
> >> On Wed, May 26, 2010 at 3:57 PM, Bob Tarling <[email protected]>
> >> wrote:
> >>
> >> > I would think such a tool should preferably operate without any
> >> > developer input but could then be tuned.
> >>
> >> My impression was that Alberto's questionaire was to establish a
> >> ground truth of expert opinion against which to measure the results of
> >> his tool(s). This is something that would be done during the
> >> development/evaluation phase of the tool, not something that you'd do
> >> as a matter of course if he were able to come up with suitable
> >> automatic algorithms.
> >>
> >> > When viewing the results of the above the seasoned developwe may spot
> >> > anomalies and then choose to remove items that are not relevant (for
> >> > argouml that would almost certainly be the critics).
> >>
> >> Except for a developer who wanted to extend the critics to cover UML
> >> 1.4 or 2.x or modify the critic infrastructure to operate differently.
> >> That was my point about importance being context sensitive. I agree
> >> that for developers focused on other areas, critics could be largely
> >> irrelevant (although the general knowledge that ArgoUML has multiple
> >> threads of execution is probably important context for all
> >> developers).
> >>
> >> BTW Alberto, I'd avoid the term "hot spots" and stick to "important
> >> classes" or something similar. For me, hotspots is something I
> >> asssociate with performance profiling (which may also be why Bob was
> >> referencing code coverage utilities).
> >>
> >> Tom
> >>
> >> ------------------------------------------------------
> >>
> >>
> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2613763
> >>
> >> To unsubscribe from this discussion, e-mail:
> >> [[email protected]].
> >> To be allowed to post to the list contact the mailing list moderator,
> >> email: [[email protected]]
> >
> >
>
> ------------------------------------------------------
>
> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2615699
>
> To unsubscribe from this discussion, e-mail: [
> [email protected]].
> To be allowed to post to the list contact the mailing list moderator,
> email: [[email protected]]
>
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2615800
To unsubscribe from this discussion, e-mail:
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email:
[[email protected]]
