Thanks for your comments.

would you explain what do you mean by "Just bubbles in a use case diagram. A
use case is a textual artifact."

SAD and OOAD are not competitors. But I have to choose which one is more
suitable for my project. I think I cannot use both for a given project?
(correct me if I am wrong)

Not bad!
The collaboration/communication diagram is UML1.? not UML2.

And I don't see any use cases! Just bubbles in a use case diagram. A
use case is a textual artifact.

I disagree with conclusions. The to techniques are complementary not
competitors.
SAD is more about how the enterprise works but

Hello,

It would be very nice if you add Jdeveloper to uml tool to be
evaluated.

Thanks,
--Motaz

--
You received this message because you are subscribed to the Google Groups "UML Forum" group.
To post to this group, send email to umlforum@googlegroups.com.
To unsubscribe from this group, send email to umlforum+unsubscribe@googlegro ups.com.

Hello,

I am preparing a presentation about "structured vs object oriented
analysis and design"

it is available at:

[link]

I would appreciate your comments,
Thank You,
--
Motaz K. Saad

--
You received this message because you are subscribed to the Google Groups "UML Forum" group.

Ken,

Have you looked at SoaML?

-Jim

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "UML Forum" group.
To post to this group, send email to umlforum@googlegroups.com.
To unsubscribe from this group, send email to umlforum+unsubscribe@googlegro ups.com.

We don't really have the user's (actor's) view of themself. I only
show the actors in the context of the SuD and its components, i.e., I
only show the actor's interfaces that are required by the SuD and the
actor's required interfaces provided by the SuD. I do not show any
other actor details or interfaces. In fact, the description of the

So, we have the user's view of themself and other actors plus the
systems view of the user. I'd like to know how this works out in the
long term.... Could you let us know what happens???

RJBotting
"The wise architect designs the pathways on a campus after it has
snowed and
they can see where people actually want to walk."

Well, here's what I did. In my model's "context" package where I used
to just keep my actors and a subsystem artifact for the SuD, I now
have a package for each actor. This package contains an actor to use
on use case diagrams and a subsystem artifact to represent the actor
on sequence and collaboration diagrams. I then used a UML profile to

What is a superclass of a class is called in metamodel

Whether it is the element or classifier and distinguish between them

--
You received this message because you are subscribed to the Google Groups "UML Forum" group.
To post to this group, send email to umlforum@googlegroups.com.
To unsubscribe from this group, send email to umlforum+unsubscribe@googlegro ups.com.

Thanks but I understood they are the same concept ....Can you explain the
one in bold

If you can look into the book I had the doubt because of the figure 2.37

Thanks in Advance

--
You received this message because you are subscribed to the Google Groups "UML Forum" group.
To post to this group, send email to umlforum@googlegroups.com.

Hi Sujatha,

it is almost as you already mentioned: Both are the same concepts with different names. A Property is a structural feature of any classifier, where as an attribute is just a logical concept for UML::Class. But there is no metaclass UML::Attribute in UML. A class owns attributes via the association between UML::Class and UML::Property where the end at the property side is named as ownedAttributes.

Hi all,

Just started with prep I need few clarification regarding properties
and attribute.I didnt understand the differences it means one and the
same.

I know there is a gap in my understanding.

Can any one help me

Thanks
sujatha

--
You received this message because you are subscribed to the Google Groups "UML Forum" group.

Responding to Wkc...

I was agreeing with you that GUI needs to be connected to somebody.

The GUI is not converted; the data that the user provides to the GUI
must eventually be converted into a Supply Order. But to do that the
data must be sent to the Supply Order (or whoever creates it) and that

Responding to Wkc...

The socket library provides the functionality that actually does
something with sockets. So it is the component. The I in API means it is
the interface through which the library component's functionality is
accessed.

<pre>
+-------------+ +-------------+ +-----------------+

Responding to Ken...

That's kind of the corner one gets painted into when the UML meta model
cannot limit model elements to particular diagrams. Speaking for the
translation MDA profiles, you would never be able to use an Actor model
element anywhere but a UCD and you would not be allowed to associate

Hi,

Does anyone used UML Almighty tool ?

Is the simulated Web application cool ?

Which is the level of customization for the Prototype ?

Thanks very much...

Regards.

--
You received this message because you are subscribed to the Google Groups "UML Forum" group.
To post to this group, send email to umlforum@googlegroups.com.

I also not understand here why the GUI get converted to orders ?

I not asking you all to do my assignment but i need verification and
advise from you all.

This is my component diagram.
[link]

I could not understand what u say here. Can u provide a complete
example for my scenario.

I also check your blog but found nothing useful.

Thanks.

--
You received this message because you are subscribed to the Google Groups "UML Forum" group.
To post to this group, send email to umlforum@googlegroups.com.

Hi. I can see how this would work, but it seems like such an indirect
way to show the dynamic usage of an actor's contract, i.e., the usage
of the actor's interfaces required and provided by the System Under
Development. However, I suppose that's just how the UML Spec
crumbles. :)

Maybe UML 3.0 would consider allowing a port on an actor and an