Lekha Sharma

Greenhorn
+ Follow
since Jan 24, 2006
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Lekha Sharma

For Part 1, you don't need to know anything beyond UML distilled. However, for part 2, there are many good article on IBM developer works website that would definitely help, look up in google you can find the pointers to it.
1) Java Swing can be an option. Protocol depends on your architecture. More specifically depends on what your answers are for these questions?
-Are application clients behind/outside the firewall?
-Does Application clients requests go through webtier?

2)Travel system that to developed is different from the existing legacy mileage system. Therefore, option b is correct.

3)You need to present a design not how you create a database schema etc. The point is, you are overworking on the problem.
Thank you all for your wishes.
Component diagram should have all the components in your design and explain how they together fulfill the system requirements. here is a clue..
Client tier may have Application client components, JSPs..
Web tier may have Framework components
Business Tier may have all your Session and Entity bean components and what design patterns they implement( session facade, composite entity, VLH ..)
With UML 2 you can convey more using your diagrams. So I would suggest you to go ahead use a tool that supports UML 2. I have n't used UML 2.0 features for Class and Component diagrams, but felt the need of it for sequence diagrams for presenting the alternative flows. so I have used a tool based on UML 2 only for sequence diagrams.
I dont think one has to go that level of detail. Alternatively, you can give appropriate names to the messages and add notes whereever it is necessary to clarify the meaning.

One thing you can do is, add method parameters(VOs), return values to the client call to business tier and add notes saying that same VO are used in buseinss tier calls.
You can present sequence diagrams in client neutral manner. You can just present the business tier interactions all requeset originating from common client. However, that depends on your design, If your design has common business tier for both client types you can use the above technique.
I have passed part 2 and 3 with 86%. Here is the break up.

Class Diagram (44 maximum) .......................... 36
Component Diagram (44 maximum) ...................... 39
Sequence/Colloboration Diagrams (12 maximum) ........ 11

My submission had 1 class, 1 component, 4 sequence and 1 deployment diagram.

Few things I would like to suggest to those who started working on assignment.

1)Keep things simple. I followed Lowest Common Denominator and tried to cover all requirements. There are many ways to address a requirement, choose one solution and present it right.

2)I realized where I lost the marks. My document was very detailed, but when some one looks at only the diagrams, they may not quite get what I was trying to convey. Try to depict all you can in the diagrams, you can use various means to achieve this. Evaluator may not have time/patience to delve into the details of your documentation. Remember, assignment also asks for diagrams + just assumptions.

3)I guess I had spent anywhere between 70-90 hrs. I could have finished it even in shorter time had I planned it well. I would suggest do not spend too much time on a single diagram, create all diagrams roughly and start improving them. Ofcourse, you need revise the diagrams many times over, that is when you refine and improve the design. Also, start document in parellel, that could save you a lot of time at the end.

4)I started with identifying list of assumptions, then screen flow diagrams, then the rough database schema. Then my class diagram evolved from BDOM + above. Then, I started the component diagram. Sequence diagrams are the last , and they took lot more time than I thought.

5)I have used JUDE for class+ component diags. Rational Architect for sequence diagram, it is UML2.0 based, so you can present all alternative flows in a single diagram.

I prepared my documentation in MS-WORD and saved it as HTML. I found it is easier and faster.

6)My documentation had the following sections- Definitions( I defined all the business terms), assumptions, application tiers, UML diagrams descriptions (I explained why, what, where DP I have used here), application modules, Architecture and Design choices and Service Level Requirements is the last section.

Thank you all!

Lekha
[ February 10, 2006: Message edited by: Lekha Sharma ]
Hello All,

I have recently submitted my assignment and waiting for the results. I never worked as an architect or not even close. I have learnt a lot during my preparation. I have decided to improve my knowledge about design and architecture.

All senior SCEAs/ Practising J2EE architects - Could you please give me some direction on what are the best resources or the best things I should do to improve my knowledge about architecture. What are the next steps in this direction?

I would highly appreciate your response.

Lekha