For all certified ranchers with my congratulations.
Sequence diagrams are modeled at the analysis level and further detailled at the design level as the project involves What is the best approach for the submission ? I think analysis level....(boundary, control, life cycle, entity...) Am i wrong ?
Sorry if my question was a bit ambigous, by analysis level, i mean that the technology isn't yet selected and only important messages are shown(significant behavior has been discovered). Usually we have a boundary object for the user interface and a control object per actor/use case pair and all entity objects related to this use case with their corresponding lifecycle objects ( boundary objects for external interfaces are added if necessary). If the sequence diagram describes interactions between components, that means that the technology has been already selected and we should model EJB, servlets...
Please correct me if i'm wrong Thanks for all your replies
Hi, because this is an certification on J2EE, so the technology has been already selected. It is all J2EE related. Yes, in real life, that is what we architect have to do to discover a suitable technology to use. However, this exam, this constraint has already been placed, and you are required to show that. [ August 31, 2005: Message edited by: Jeremy Hsu ]
Your're right: according to the assignment the delivrables are (the order is important....): Class diagram Component diagram Sequence or collaboration diagram for each use case Listing of any assumptions And we should architect and DESIGN the system! Thanks again
If technology has already been chosen ,then why class diagram being technology independent. BTW in general should seq. diagram depict the classes as boundary,control etc(technology independent)..or should it show the interaction between the realized classes?
Hi, this is the experiences from many people who already pass the SCEA exam. SCEA looks for business domain objects in class diagram. Those are technology independent. The component and sequence diagram is where you put all the J2EE related stuff plus external systems.
Many people also point out that in real life they will not architect their system in this way. I am just sharing my experience on passing the SCEA.
And to answer your seq diagram question, it really depends on what level of detail you want to show the marker. Some people passed by giving very detailed classes interaction. Some passed by just showing interaction between components. I prefer showing the interaction between components and tiers because to me, showing the detail classes interactions are too low level. (by the way, sometimes class is depicted as component because it is really important, such as an stateless session bean used as a session facade) [ September 01, 2005: Message edited by: Jeremy Hsu ]
J2EE systems are built upon reusable components( ), component based developpement is one of the main advantages of J2EE technology (not always true @#@!$ in real world), you should do the best effort to build your solution with respect to this strategy. EJBs, servlets, jsp pages, applcation client, applets... are J2EE components.
Akar [ September 01, 2005: Message edited by: Akar Rafidj ]