Hello there
I have a couple of basic questions how the component diagram should be modeled and what it should contain or not. Let me know your thoughts.
- Which kind of stereotypes should be used? Should I use generic ones as "application", "library" or only
J2EE Patterns releated as "Business Delegate"? or both?
- When should I use a stereotype, when a label on a dependency link? Should I prefer therefore labels instead of stereotypes?
- Should I include a component "BDOM" with stereotype <<library>> in my component model, which represents the business domain class model?
- Should I model only one component for the
JSP's or each JSP separately?
- What is about the DAO's, should I show DAO separately or only one and add there some note?
- what is about the interfaces, I saw some component diagrams there has been shown interfaces as "HTTP" or "XML". I don't thikn that this should be part in a component diagram, this is more related to a deployment diagram. To list all home and remote interfaces of a bean makes also no sense in my eyes. So what type of interfaces do you suggest to show?
Thank you
regards
Mark
[ January 01, 2005: Message edited by: Mark Egloff ]
[ January 01, 2005: Message edited by: Mark Egloff ]