Thanks. I'll clarify them below...
I guess your mail subsystem is there to be used by some other component, implementing [a piece of] business logics? So that other component will _depend_ on your mail component. What do you mean "dependency will be deferred..."?
Nope. I mean I've got a mail component which is designed for any component which may send mails, but currently it's in the very early stage for development (this assignment). Therefore, maybe ten components will use this mail component, but I'm not sure now, so I would like to put a mail component without any dependency from other components.
I'm wondering if I can put a component without any dependency from other components...
The only interfaces I've shown were those related to EJBs, session and entity beans. I didn't use any other interfaces in my component diagram and got 42/44 for it. Components were tied together by dependency relationships, to show who's used by who.
I also put interface in front of my session beans. However, I also have interfaces for DAOs and business delegate. Cause I think these implementation may be changed due to new technologies.
Is it a good idea?
Some other questions.
Could you tell me how many pages you had for explaining assumptions?
and did you put some more detailed components like View Helper or Transfer Object in the component diagram?
Thanks a lot.
[ July 13, 2005: Message edited by: Kuo-Feng Sun ]