Failed SCEA Part 2 with 64%

[adewale shobajo]

Hello,

I failed Part2 of the SCEA exam getting 64 out of the required 70 to pass. Here is my result outline.

The maximum number of points you could have received is 100, minimum to pass is 70.
 Class Diagram (44 maximum) .......................... 33 
 Component Diagram (44 maximum) ...................... 20 
 Sequence/Colloboration Diagrams (12 maximum) ........ 11
 

Class Diagram.
I have got about 19 classes in my class diagram. My class diagram was technology neutral. My Diagram was very neat. I also didnt change any associations or multiplicities in the BDOM, just extended it. I think i have got reasonable marks in that section.

Component Diagram.
What can i say, i am still trying to understand what went wrong here. I have drawn this diagram using MagicDraw9.5. My diagram followed this structure JSP --> Servlet --> Business Delegate --> Service Locator --> Session Bean --> DAO. I also put streotypes on the components. <<JSP>> <<servlet>> <<BusinessDelegate>> <<SessionBean>> <<DAO>>. The digram didnt contain anything on the java client app. I noticed my components didnt take the normal shape you find in cade's book. It looked more like a class with a component icon by the side.

Sequence Diagram.
My Sequence diagram was detailed. I guess i did it right in the eyes of the grader to score 11.


Any Tips as to what i did fundamentally wrong?
Do i need to sit for Part3 again? or i just re-submit the assignment and i am ok.
Any insights as regards improving my

Class

and Component diagrams?

Your Opinions and comments would be greatly appreciated.
regards
wale.

[Ricardo Ferreira]

Originally posted by adewale shobajo:
Hello,

I failed Part2 of the SCEA exam getting 64 out of the required 70 to pass. Here is my result outline.

The maximum number of points you could have received is 100, minimum to pass is 70.
 Class Diagram (44 maximum) .......................... 33 
 Component Diagram (44 maximum) ...................... 20 
 Sequence/Colloboration Diagrams (12 maximum) ........ 11
 

Class Diagram.
I have got about 19 classes in my class diagram. My class diagram was technology neutral. My Diagram was very neat. I also didnt change any associations or multiplicities in the BDOM, just extended it. I think i have got reasonable marks in that section.

Component Diagram.
What can i say, i am still trying to understand what went wrong here. I have drawn this diagram using MagicDraw9.5. My diagram followed this structure JSP --> Servlet --> Business Delegate --> Service Locator --> Session Bean --> DAO. I also put streotypes on the components. <<JSP>> <<servlet>> <<BusinessDelegate>> <<SessionBean>> <<DAO>>. The digram didnt contain anything on the java client app. I noticed my components didnt take the normal shape you find in cade's book. It looked more like a class with a component icon by the side.

Sequence Diagram.
My Sequence diagram was detailed. I guess i did it right in the eyes of the grader to score 11.


Any Tips as to what i did fundamentally wrong?
Do i need to sit for Part3 again? or i just re-submit the assignment and i am ok.
Any insights as regards improving my

Class

and Component diagrams?

Your Opinions and comments would be greatly appreciated.
regards
wale.

Hi adewale,

First, I really apreciate your coragem to post your results in the JavaRanch forum. It's very easy to be glad and post a sucessfull result score. But, need to have corage to admit some failure. At this point, you're a winner.

Second, don't give up of re-submit the assignment again, try to find out your misses, and improve your design.

What can I say is, you should to worry about your business domain analysis and do not worry about the application architecture (component diagram). Try to ask you if your current design meets all the use cases and the workflows of the application.

This change will cause an impact at you class diagram and your iteration diagrams. Remember, the architecture (component diagram) manage only how the application works ensuring non functional requirements. But is the domain model that defines the idea behind the architecture; that's the thing that make your system works.

Good luck, and move on!

[Rick Wagner]

Wale,

I agree with Ricardo on two points:

1) A review of the use cases might be productive.

2) You should be applauded for sharing details of your score and seeking improvement. It would have been much easier to hide in the shadows, but then nothing is learned, right? Good for you-- I applaud your integrity!

Best of luck on the next one!

Rick

P.S. If your UML tool is too limiting, you might consider using Jude UML. The community edition doesn't save to HTML, but you can do great things with screen prints and Word documents!

[Thomas Taeger]

Hello Adewale, hello all,

Originally posted by Ricardo Ferreira:
First, I really apreciate your coragem to post your results in the JavaRanch forum. It's very easy to be glad and post a sucessfull result score. But, need to have corage to admit some failure. At this point, you're a winner.

Yes, that's true!

Try to ask you if your current design meets all the use cases and the workflows of the application.

... and the non-functional requirements. List all requirements in a table and tick off each one that you have done.

Originally posted by Ricardo Ferreira:
What can I say is, you should ... worry about your business domain analysis and do not worry about the application architecture (component diagram).

I can not agree here, and more important I miss any reasoning.

Getting 11 of 12 points for Sequence diagrams is excellent.

Getting 33 of 44 points for Class diagrams still is 75% - passed ...

Adewale, I think you are quite right to think over your Component diagram[s]
- which components have been missing
- which dependencies better should have been shown throuhg interfaces
- which dependencies are missing
- which dependencies are wrong
- ...

The deliverables say: "Your architecture and design will be graded on how well it supports both web clients and application clients...". How did you prove this? Even if nothing within your class diagrams was wrong, how did you show the classes and components of the Java GUI subsystem so the examiners could understand?

Originally posted by Ricardo Ferreira:
This change will cause an impact at [...] your i[n]tera[ct]tion diagrams.

Need not - 11 of 12 ...

Originally posted by Ricardo Ferreira:
Remember, the architecture (component diagram) manage only how the application works ensuring non functional requirements.

? Non-functional requirements must be solved in each diagram and each diagram type. This is not specific to Component diagrams.

Originally posted by Ricardo Ferreira:
But is the domain model that defines the idea behind the architecture; that's the thing that make your system works.

Not only, and not specifically, too.

But the Component diagram has to ensure that each component is presented, for each class a component is presented that the class is a member of, all dependencies (= enimies of loose coupling) are as minimal as possible.


For you, Adewale, like for many forum members it could be worth to read old postings acc. to Component diagrams. There have been lots of discussions on that in the near past (and before).

Thomas

[Thomas Taeger]

Hello Rick,

Originally posted by Rick Wagner:
... consider using Jude UML. The community edition doesn't save to HTML, ...

The ghost has been awaken again - shivering ...

What should be saved to HTML? Diagrams? Probabely you mean .gif or similar?

Thomas

[adewale shobajo]

Hello Ricardo Ferreira,Rick Wagner,Thomas Taeger. I would like to thank you guys on your support and encouragement. I have seen your suggestions,comments and opinions which i have decided to take very seriously.

I also hope this time around i will nail the exam on the head.
Thanks once again guys.
wale.

[wise owen]

Good luck!

[Parag Bharambe]

Hi,

If you focus your attenction on Component Diagram for what went wrong, you will get quite a few points to ponder on

1 You mentioned that your component diagram and class diagram were (mostly) same except component sign on Component diagram.
>> Component is a replacable part of system. So all the classes cannot be component. i.e You can show Customer as one Component and need not show all the dependent classes in Component diagram.
>> You can show packages, for logical grouping of classes, which you do not show in Class diagram.
>> You can attache the notes to Component mentioing the Pattern used by Component.

I hope this helps. Feel free to raise any queries.
Parag

Parag