This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of Darcy DeClute's Scrum Master Certification Guide: The Definitive Resource for Passing the CSM and PSM Exams and have Darcy DeClute on-line!
See this thread for details.
  • 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Devaka Cooray
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Jeanne Boyarsky
  • Tim Cooke
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Mikalai Zaikin
  • Carey Brown
Bartenders:

ooad artifact

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can Use Case be called as an OOAD artifact?
I guess there is some confusion between OOAD and UML artifacts.
Any takes?
yup
- Raj
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Raj Waters:
Can Use Case be called as an OOAD artifact?


I don't know. A use case diagram doesn't have much to do with objects at all, though it does have something like inheritance defined. On the other hand, I don't think that an "analysis class diagramm" has much to do with objects as we know them in design/programming, so I don't know what OOA would mean at all - other than being a buzzword...
But why do you care in the fist place???


I guess there is some confusion between OOAD and UML artifacts.


And also between use case *diagrams* (which are a UML artifact) and use cases (which aren't - they are textual in nature)...
 
Raj Waters
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ilja
The reason for putting this coz there is a question on IBM ICE exam where it says
Which OOAD artifact......?
and the answer is Use Case
and hence the confusion
 
Ranch Hand
Posts: 662
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Raj Waters:
Can Use Case be called as an OOAD artifact?


I don't think so. Use cases and Use case diagrams are UML artifacts. OOAD has nothing to do with UML, which is just a visual presentation tool.

The reason for putting this coz there is a question on IBM ICE exam where it says
Which OOAD artifact......?


I guess the question was improperly framed.
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Jayadev Pulaparty:
OOAD has nothing to do with UML, which is just a visual presentation tool.


Correct. But what the hell *is* OOA??? Can you define it?
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
OOAD is Object Oriented Analysis & Design - everything up to coding. UML is a good notation for recording certain parts of analysis and design. A lot of other stuff lives as plain text, pictures, etc.
Use cases are not really object oriented, and could be used for purely procedural systems. But they are often used in OOAD, and I'd buy the test answer.
I think of UML as more than a visual presentation standard. It is a language with complex semantics that represents different aspects of a common underlying model. It can be (but is not always) linked to a concrete underlying model by a drawing tool.
UML defines thirteen diagrams as artifacts. The use case diagram with a symbol for use case is one of them, but I agree that use case itself is not a UML artifact.
[ June 30, 2003: Message edited by: Stan James ]
 
Yes, of course, and I accept that blame. In fact, i covet that blame. As does this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic