<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
<br>
<br>
Andrew Sutton wrote:<br>
<blockquote type="cite" cite="mid200211052304.50016.ansutton@kent.edu">
<pre wrap="">
so what you're talking about is the capability of transforming other aspects
of UML into code too - like statechart diagrams.</pre>
</blockquote>
Right.<br>
<blockquote type="cite" cite="mid200211052304.50016.ansutton@kent.edu">
<pre wrap="">that might be kind of hard.
collaboration and sequence diagrams would be "a little" easier.</pre>
</blockquote>
The point is not to specify a C++ mapping of all UML semantics (including
dynamic ones). It is just to allow user to do that in some specific context
by providing him navigation methods and entry points to overwrite standard
code generation.<br>
<blockquote type="cite" cite="mid200211052304.50016.ansutton@kent.edu">
<blockquote type="cite">
<pre wrap="">If you need more realistic information about the need, I can try to
build an example.
</pre>
</blockquote>
<pre wrap=""><!---->
that probably wouldn't hurt :)
</pre>
</blockquote>
OK. Here it is.<br>
Imagine (first example) you're building an application that contains an interface
to a database. Some classes will have methods to access database. Database
acccess methods can be easily deduced from the attributes description (if
not, let's suppose it for the example). So, the user is able to specify (in
that project) an automatic generation of database methods. What he needs
to realize that is:<br>
<ul>
<li>a tagged value (say {persistant}, for example, and the name of the
database management system),</li>
<li>an entry point to act on code generation, and</li>
<li>a way to get required information (attributes description and presence
of tagged value).</li>
</ul>
This first example is just to illustrate needs for customization in code
generation.<br>
Let me give an other one.<br>
Imagine now a simulation application (this example is easy for me because
I did that work a few years ago). I don't know simulation standards but I
guess this application should deal with actors (not UML actors) that reacts
to events and so on. Oh ! I know a UML semantic which allow to specify that
sort of behaviour : statecharts. Same that in previous example, what is needed
to realize that is:<br>
<ul>
<li>a tagged value (say {actor}, for example),</li>
<li>an entry point to act on code generation, and</li>
<li>a way to get required information (statechart information and presence
of tagged value).</li>
</ul>
That's all. Do you feel it is a real need or is it a too strange usage of
CASE-tool ?<br>
<br>
<br>
Jean<br>
<br>
PS : Note that those (customization) functionalities can be found in an existing
CASE-tool : Objecteering (of Softeam). That used to be a good tool, especially
for code for generation (I used it a few years ago).<br>
<blockquote type="cite" cite="mid200211052304.50016.ansutton@kent.edu">
<pre wrap="">
andy
</pre>
</blockquote>
<br>
</body>
</html>