Passed Part 2/3 with 93%

Here's a repost of what I put on the yahoo group:
Just got the results back, 4 weeks and 1 day after taking part 3:
The maximum number of points you could have received is 100, minimum
to pass is 70. Class Diagram (44 maximum) ......... 42
Component Diagram (44 maximum) .................... 39
Sequence/Colloboration Diagrams (12 maximum) ...... 12
Pretty happy with the results, waiting for them is a pain

Thanks to this group for the help (mostly with Part I). Here's some
advice if you're interested:
1) Like most news groups, ignore 80% of everything said here about
the project. There are too many different ways to execute the
solution, and deconflicting the advice from the group (and figuring
out who is full of BS) can drive you nuts.
The solution needs to make sense to *you*, and you should be able to
justify your decisions. I modified the domain model, and gave a good
explanation of why I did it, how it helped simplify the solution, etc.
2) Do the project iteratively -- treat it like a real OOA/D
exercise. It will save time in the long run. If you don't know
OOA/D, this project is a perfect way to learn. It's something an
architect should know.
3) Pay attention to non-functional requirements. That is the
architect's job.
Cheers,
Steve

congratuations.
I have a question for you. After read the assigment, I still have no clue where do I need to start to do the assignment. Do I need to start from design the database schema? Because that it is where my entity bean come from. How did you start to do it?

Hi --
I started with the data model, assuming the domain model objects as tables (not a good assumption, but a starting point). As I developed the data schema, things started getting clearer. Whenever things got confusing, I used the use cases as the point of reference. The domain model may be dodgy, but there is nothing wrong with the use cases, IMHO.
Hope it helps,
Steve

Congrats Johnson,
I do not know when I will finally attempt part II and III

Hi Johnson,
Congratulations! I did download the assignment, however, the scoring proportion is slightly different from yours. Mine is :-
Class Diagram - 40%
Component Diagram - 40%
Collaboration / Sequence Diagram - 20%
Thanks for your advise. By the way, would you elborate more about 'paying attention the non-functional requirement'. I mean in what way you pay attention on that and what we should pay attention to?
Have you read for any examples on helping to design the assignment?
Thanks/Franky

Hi --
I guess they didn't update the assignment text, but I'm pretty sure everyone will be graded on the 44/44/12 scheme -- bummer, since my score would have been higher using the 40/40/20

Anyway, the non-functional requirements are things like: scalability, maintainability, reliability, etc. A software designer is responsible for the *what*, an architect is responsible for the *how*. Look at the number of customers, agents, legacy requirements, security, etc. That is the focus of the assignment -- not building a web app.
I looked at petstore, but didn't use it. If you read the J2EE Patterns book (and understand it), you're halfway there.
If you're not an IT guy, talk to some sysadmins or network engineers about security, loads, and bandwidth requirements.
Good Luck,
Steve

Hi Johnson,
About the pattern book, are you talking about the book named "Java Enterprise Design Pattern" or "EJB Design Pattern" that are both published by Wiley?
Thanks/Franky