class diagram questions - fig 9.3 Cade's book

[talu singh]

[code]In the Mark Cade book, figure 9.3 - shows a class diagram of a domain model.

I have 3 question about it.

1. Is it normal to show jsps in class diagram?

2. wood, steel, concrete is extending availabiltyItem
Shouldn't this be just an association relationship?

3. On the availabilityNotice, it has properties
wood: List<Wood>, steel:List<Steel>, concreate:List<concreate>

Can this be replaced by a composite object called say product so that I can group three properties into one
product: List<product>

so that in the future more product can be added without changnig availabilityNotice class? or is this too fine grained for scea 5 class diagram?

Thanks[/code]

Some one on the forum has posted a link to scanned copy of the chapter 9. I could not find the link today, sorry.

[Ranganathan Kaliyur Mannar]

1) I am not a fan of having jsp/jsf in the class diagram - class diagram should be technology agnostic...
I would show the jsp/jsf in the component diagram. But, many people do have it in the class diagram - so, there's no rule to it...

2) yah, I too had a abstract base class Product and used that in my design. There was a line in the chapter about 'adding our own thing to make the given model easier' - remember we cannot change the basic model given. I think by having Product, we are making it easier and is perfectly fine for me.