• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Class Diagram

 
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Pamir,
concratz! Go and party!
Concerning your class-diagram (I think this is the crux in most assignments and you have negotiated it):
- Did you show attributes and ops in the class diagram?
- How many classes do you have?
- Have you changed the BDM?
- Have you consolidated some BDM classes?
Best regards
Roger
 
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


- Did you show attributes and ops in the class diagram?


I recommend showing *all* attributes and ops that are involved in business transactions and process flow. As the assignment mentions, you don't have to show other insiginficant attributes and you can safely ignore showing getters and setters.


- How many classes do you have?


It greatly depends on your solution and how you count them. Some people have chosen to show classes outside the scope of the solution( such as standard Java classes ) for the sake of clarity whereas others have not included them to avoid clutter. Same is true for showing/hiding Home, Remote and Bean implementation classes for every EJB.


- Have you changed the BDM?


The keyword is not change but extend. As the name suggests, it is the Business Domain Model that represents very high level relationships between domain level entities. Normally problem analysis yields more classes and refines the BDM. Note that the final design model cannot contradict( omit, render vague or nullify ) any association and cardinality specified in the BDM.


- Have you consolidated some BDM classes?


See my response above.
[ September 22, 2003: Message edited by: Ajith Kallambella ]
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic