Jorge Coll

Greenhorn
+ Follow
since Sep 02, 2011
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
1
Received in last 30 days
0
Total given
1
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Jorge Coll

Will Myers wrote:I already have SCJP, SCWCD, OCPBCD, Spring Certified Professional all from last year and I have over 10 years development experience in banking.

I started preparation for part 1 in early April and took the exam on the 24th and passed with 78%. I imediately downloaded the assignment (Factory Homes) and got to work. My class diagram had 29 classes on it including the domain model which was pretty much unchanged from the one supplied except I used an interfaces for some of the classes to satisfy the use cases that called for a component. I used classes called xxxxFacade to interface with the web services and the 3rd party 3d tool. The final diagram looked very much like Cade's. The sequence diagrams were pretty straight forward and the component and deployment diargrams were again pretty close to those in Chapter 9 of Cade's book. My assumptions list was approximately 1 page and my risks list was the same with most of that on security.

Part 3 was a breeze, I finished in under an hour.



Hi Will, Congrats!

Some people saying that Component Diagrams (CD) are the right place where they can explain the Design Patterns used but Cade's Diagrams lacks of this type of information. Are you put some info about Design Patterns on your CD? How many CD do you needed (some people has one per use case )? Are you used stereotyped the components? Some note about Deployment Diagrams?

Thanks!
10 years ago
Thanks Kumar!

I know that these steps are programatically corrects without any doubt but I'm thinking that put all this logic together in the sequence diagrams could be a little excesive.

Mr. Cade tell us: "Another common mistake (in all diagrams, not just the class diagram) is to focus on the 'how' and not the 'what'".

I try to put this kind of programatic persistence logic on my sequence diagrams and the result looks very 'dirty'.

I don't know if will be possible to put something like "persist/merge" over the sequence diagrams arrows and left the low level coding details outside.
I've been years waiting for the right professional moment to certify me as an Architect and now Oracle comes to change the rules.

I'm trying to end with part2 and take part3 before sept/30 deadline. If I can't I'm so sure of my answer...
1) Can't afford (No, can't take SCEA)

Finally IMHO, I think that Oracle has choosen the wrost economical moment (to takers of course) to adjust their economic requirements.
Congrats and hurry up with the second part!!! This is a real madness!!!
10 years ago
Hi,


I'm not sure about what's the correct message to invoke the persistence of an entity in my sequence diagrams. I'm using the Cade/Sheil model in which the persistence is realized by an invocation message "persist" to EntityManager (JPA).

My questions are...
  • If the object (maybe) already persisted... I must use another message like "merge"?
  • Can I use "persist" as a generic method for new or already existing objects?
  • I must use notes in these cases?
  • I must use conditional structures in this cases?


  • Maybe one item could answer the others.


    Thanks,
    Jorge

    Jeanne Boyarsky wrote:

    Jorge Coll wrote:

  • Can I be free to assume (guessing) anything about an Use Case?

  • Yes. Just be sure to document your assumptions.

    Jorge Coll wrote:

  • Can I modify the use case steps order when I draw my sequence diagrams?

  • Yes. The sequence diagrams can be run in any order.

    Jorge Coll wrote:

  • Can I skip some use case step when I draw my sequence diagrams assuming by example that certain step could be done transversally (like auth)?

  • That's fine.



    Thanks Jeanne!

    If you know about it... The absence of use cases brief descriptions occurs as well in other assignments or could it be an assigment error?
    Hi,

    I wish to know why I have empties all the use cases brief descriptions. I don't know if this is an assigment error or this is a normal situation.

    I've received an assignment called Retire Early Online Trading. It's got me crazy because there are some ambiguous words like ACCOUNT which sometimes I think that refers to User Account and sometimes looks like refers to Bank Account (Number). Also exists the word ADDRESS which could be a physical address or email address.

    If I have a full brief descriptions I'm sure that this would be more clear.

  • Can I be free to assume (guessing) anything about an Use Case?
  • Can I modify the use case steps order when I draw my sequence diagrams?
  • Can I skip some use case step when I draw my sequence diagrams assuming by example that certain step could be done transversally (like auth)?



  • Thanks.
    Hi,

    I think that temporary queues on a well config cluster could be the best solution. As I understand so many concurrent threads working with message selectors could have the wrost performance.