File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Part 2 Deliverables - UML Diagram Descriptions required Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Part 2 Deliverables - UML Diagram Descriptions required" Watch "Part 2 Deliverables - UML Diagram Descriptions required" New topic

Part 2 Deliverables - UML Diagram Descriptions required

s patnaik
Ranch Hand

Joined: Jul 17, 2011
Posts: 45


Do I need to describe the sequence diagrams? They seem pretty intuitive to me.

I have added description for deployment diagrams. But I did not add descriptions for class diagrams or component diagrams or sequence diagrams... I have an Architecture Overview section where I give a tier-wise description of the design patterns(specified only 3 ) i have used, the technology i have used (like jsf or ejb) and why i have used that technology. Is that enough?

Class diagrams/component diagrams/sequence diagrams seem self explanatory. Does adding no description mean failure?

I am going crazy about what level of detail i should go into... The more I read about other people's experiences, the more confused I become !

- SP

Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33124

In theory, you didn't need descriptions anywhere. In practice, that isn't a good recipe because you want to communicate some things. I agree that a sequence diagram is pretty straightfoward and only used explanation for anything "odd" like why it didn't match my class diagram exactly.

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
I agree. Here's the link:
subject: Part 2 Deliverables - UML Diagram Descriptions required
It's not a secret anymore!