Have got couple of questions regarding the assignment. And many in the forum like me will be having similar questions.
1) What level of details are need in the class diagram. Is it necessary to show all the attributes/operation for the class. 2) Do the class diagram needs to be J2EE dependent (means show the EntityEJBs,SessionEJBs,etc). If it is J2EE independent then do we need to show the command classes as simple classes and make that SessionEntityEJBs in the component Diagram. 3) JSPs can be a different component but how about the application client. Can the application client be shown as a component or need to create a Class Diagrams for that too. 4) Do we need to create the package diagram 5) In sequence diagram for each different type of client do we need to show the different sequence diagram or can be represented as a "Client". 6) Can class diagram and component diagrams can be broken into multiple diagrams or needs to be shown as single diagram.
Answer to above questions are truely appreciated. Do not need the specifics but any suggestions will be helpful.
well Raj, u hvae got more than a couple of questions. Altough i would invite comments from guys who have already done SCEA, at least i can add that -- 1. u dont need to show all the attrib/operations in class diag; just pick the essential ones which relate to the DOMAIN and that too gradually ..not in 1st go... 2. nopes..class diagrams should be PREFERABLY tech independent...and yes u can show ejb's etc in component diag. 3. Application client can find its place in component diagram but usually not in class diagrams unless it is affecting the process and not just triggering the processes. 4. to avoid clutterring of classes, u can have package diagrams. It also helps in identifying dependencies. 5. If it's a diff workflow or a major alteration, u should show a diff sequence diagram. 6. Its good if u show gradual breakups, i mean start from the overall system, then in diff diagrams show the subsystems. opinions invited plz. It seems a good thread for starters. thnx n rgds
thanxs Nishant... Well have couple more questions ... only couple more this time 1) Do we need to show VOs or objects that are used in messaging passing parameters, etc in class diagrams.. 2) Also wanted to know whether to show VOs etc in the component diagram. Do we need to show the objects passing between the component etc in the component Diagram and sequence diagram Thanxs Raj
1) Do we need to show VOs or objects that are used in messaging passing parameters, etc in class diagrams..
Yes, you may just show the type in the method signature instead of both type and variable ie., doSomthing(personVO) instead of doSomething(PersonVO vo ). If you decide to adopt this convention, make sure to use intuitive object names ie., personVO is better than just aVO !
2) Also wanted to know whether to show VOs etc in the component diagram. Do we need to show the objects passing between the component etc in the component Diagram and sequence diagram
Ask yourself - what is a component? Among other things, it provides behavior (aka functionality). IMO VOs don't fit this definition. I also don't know how one can even represent messages and arguments in a component diagram.
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).