Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Regular classes versus specification classes

 
Ray James
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The more I think about this, the more confused I get.
In Craig Larman's Applied UML book, he talks about the concept of regular classes (like Item) versus definition/specification classes (like ProductSpecification) where an Item refers to a ProductSpecification that describes the Item.
However, this concept seems to clutter the class diagram when you are planning to implement the classes as Entity EJBs. Now, you end up creating both a reference class and a definition class for every entity bean.
Is it better to make this distinction in the class diagram, or is it better to combine these concepts (i.e. only use a Item entity)?
Ray
[ August 25, 2003: Message edited by: Ray James ]
[ August 25, 2003: Message edited by: Ray James ]
 
Rufus BugleWeed
Ranch Hand
Posts: 1551
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm assuming your reading somewhere around p. 141 in the second edition, section 10.7 of Larman's work.
I'm assuming your trying to create a class diagram for part II.
In this contrived project, you might consider just where on the time line of life where this project is.
In this contrived project, who is the audience this class diagram is being created for.
The class diagram drawn in SCEA for J2EE Technology Study Guide shows 13 classes.
If you had the money, time, and legal status to attend Java One to go to Cade's seminar on successfully passing the cert, you would know you should keep it simple.
Think conceptual, not specification.
[ August 26, 2003: Message edited by: Rufus BugleWeed ]
 
Ray James
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I get the point, i.e. use the KISS principle. I think I was getting my goals mixed up for entity persistence and JDBC queries and how to show them on the class diagram. After I made the post I went back to my class diagram an separated these concepts, which simplified the matter. Now I am getting closer to the right number of classes!
Thanks,
Ray
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic