This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes UML Doubt Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "UML Doubt" Watch "UML Doubt" New topic

UML Doubt

Bobby Sh

Joined: Jun 26, 2003
Posts: 17

In SCEA FOR J2EE (PAUL ALLEN AND JOSEPH BAMBARA) , I found the following question

In a class diagram, what does a line with an arrow from one class to another denote ?

A. Attribute visibility
B. Class visibility
C. Method visibility
D. Global visibility

Answer is A.

But my understanding is when we join a class to other class with a line, that means Class visibility. Also Attribute and Method
visibility should be based on the access specifiers (private, public..etc).

Please let me know if this understanding is not correct

Thanks & Regards
Diego Amicabile

Joined: Sep 12, 2004
Posts: 23
I found an explanation for that under

Sending messages requires visibility : a reference or pointer to the receiving object
�For an object A to send a message to an object B, B must be visible to A.�

Ways in which A can have visibility into B:
Attribute Visibility: B is an attribute of A
Parameter Visibility: is a parameter of a method of A
Local Visibility: B is a (non-parameter) local object in a method of A
Global visibility: B is in some way globally visible

so if B is associated to A, there is obviously attribute visibility. Not intuitive.


SCJP 1.4(90%), SCWCD 1.2(94%), SCJD (366/400), SCBCD (91%), SCEA (88%)
Mohamed Raffi

Joined: Apr 08, 2004
Posts: 3
The line with an arrow depicts association relationship.
Association represents the attributes that are not simple (String, Integer, etc) and are Complex Objects.
During implementation these associated objects will be captured as attributes inside the Class from where the arrow starts.

Refer the "Value Objects and Reference Objects" Section in UML Distilled by Martin Flower and
Have a look at the following Link

Hope that helps :-)
I agree. Here's the link:
subject: UML Doubt
Similar Threads
Dependency vs. Association
two questions about ooad
access modifiers
Class Diagram Question
Would you consider them Singletons?