Hi!
When I used to build systems using C++, the major elements of analysis and
design I used were 1. Requirements, 2. UseCases, 3. Identification of
Classes, 4. Class Diagrams, and 5. Sequence Diagrams.
But in the EJB scenario (since OO elements like inheritance,
aggregation/composition are non-existent), the analysis and design would be,
I assume, 1. Requirements, 2. UseCases, 3. Identification of Session and
Entity beans, and 4. Sequence diagrams.
Is it correct?. Are there any new phases added?
Thanks!!
-mj
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".