• 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
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

Question part-2

 
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All ,
After many months I finally started putting my class diagrams in place .
I have some questions about it .
I have defined only attributes in my classes .I have only domain level objects .Is it necessary to put methods also. Would those methods really be like actually method calls when doing the sequence diagram or they can be like statements . I would still be doing sequence diagram at the domain level .Some one please correct me if that is the wrong approach for the sequenece diagrams.
For the component diagram I will be taking the approach
A Component Identification Pattern . I read many different options but only this particular article really clarified how /what of components.
http://www.theserverside.com/patterns/thread.jsp?thread_id=17595#86692
Did any one try using that yet and does it work all right for defining components
Thanks
Dhiren
 
Ranch Hand
Posts: 77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Looking at the requirements doc that Sun gives , it is seems like they are focused more on the physical components that make up the system . There is a mention of JSPs etc in the Component diagram . So the component identification pattern that your link points to is an excellent technic to use to get to the solution , but submitting it as a solution ??? I would really try to enhance it to include all that was requested in the requirements doc .
By the way I have just submitted it so I do not know my own results , so take my advice with a spinch of salt.
bye
kpt
 
Dhiren Joshi
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks kpt,
Yes ,
I will be enhancing it the link I posted I will use it to start components designing as I was not getting any where with any approaches I searched on.
Do I need methods in my class diagrams.
For sequence diagrams can I do at a domain level or do I need to go one level deeper like desiging for a developer to develop upon.
I was assusming the component diagram is what would be for developer communication from a design standpoint. Can any one give there feed back if this approach is correct
Thanks everyone
DJ
 
You showed up just in time for the waffles! And 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