Hi all I would to find out from you guys what is the standard/correct/effective way of doing OOAD for J2EE projects. Currently, that's what I'm doing: (1) Based on the user requirements, produce and confirm the use case. (2) For each use case, produce a framework of high level class diagram. Open source frameworks are applied where suitable. (3) Produce a high level deployment and package diagram (4) From (2), produce the sequence/collaboration diagrams to model the behaviour. (5) From (4), refactor/expand the class diagrams in (2) and consolidate them (6) Using (5), refactor/expand the diagrams into detailed sequence/collaboration. (7) Throughout the process, state / acitivity digrams may be drawn to further analyse the requirements. (8) Finalise the package diagram before distributing the modules to developers for coding. I'm still quite new to J2EE technologies and a bit lost when doing OOAD for J2EE projects. I'm unsure if my above way of doing OOAD is correct or not. I have not read on the Rational process (will find some time to do so) and hence would appreciate anyone who has some experiences in these areas to share his comments. Thanks a lot in advance
Kyle Brown
author
Ranch Hand
Joined: Aug 10, 2001
Posts: 3879
posted
0
Ummm... This looks perfectly fine to me. You're already following the process better than 99% of most developers. My only advice would be be sure in step 2 and 3 to apply high level "Best practices" patterns of interaction from books like mine (below), Deepak Alur's wonderful "Core J2EE Patterns" book and Martin Fowler's Information Systems Architecture site. Kyle
0
