• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

interaction diagrams and navigability !?

 
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Judging from the direction of message passing in an interaction diagram, we can infer 'navigability' between classes. Am I correct in my statement?
If so, which three options in the following question are correct?
When it comes time to write code, an interaction diagram can quickly provide information on which of the following? (choose three)
a)Navigability of associations
b)The sequence of method calls
c)Conditions under which a message is sent
d)State changes in an object
e)Iteration in the control flow
a, b, c, e - four of these choces seem correct to me.
Should (a) be excluded because navigability can not be understood QUICKLY?
Should (e) be excluded because 'control flow' in this context does not imply 'the conditions under which the messages are sent'?
Please comment.
Thanks.
 
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think (b), (c) & (e) are correct answers.
IMHO, (a) is incorrect since, navigability is typically applied during domain modelling and would represent ( kind of ) static modelling.
(e) is correct, since Iteration can be best represented during dynamic modelling, using Interaction diagrams.
Please comment, if the above reasoning is incorrect.
 
Merlin M Koppula
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Suresh,
IMHO, (a) is incorrect since, navigability is typically applied during domain modelling and would represent ( kind of ) static modelling.
Navigability is part of specification and implementation diagrams.
From "UML distilled",
[..] In implementation diagram, this would indicate that Order contains a pointer to Customer, but Customer would not have a pointer [..]
Navigability may be part of static modeling. But the question is if interaction diagram provides information about navigability, which is useful during implementation (writing code).
Please comment..
Thanks.
 
Suresh Ray
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Navigability may be part of static modeling. But the question is if interaction diagram provides information about navigability, which is useful during implementation (writing code).


Since Interaction Diagrams represents Dynamic modelling and navigability is part of static modelling, I think interaction diagrams do not provide (information) navigability of associations (of classes).
Hope it helps.
 
And when my army is complete, I will rule the world! But, for now, I'm going to be happy with this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic