Cade Sheil SCEA FAQ   

See the [SceaFaq] or [SceaLinks]

If you want to post discussion about anything on this page, see cade/sheil - sample solution issues

Introduction

The Cade/Sheil study guide was a great help for part 1. For part 2/3, I found it mostly useful. I had some issues with the "fully worked solution" though. I'd like to use this thread for people to brainstorm issues they see in the provided solution. It's going to be up to individual exam takers to decide whether to follow this or improve their own.

Here's what I recall. There were a couple other things that bugged me, but they aren't jumping to mind right now. Please edit this page so this serves as a reference to others using Cade/Sheil.

For me issues fell into a few categories:

• Category 1 - I've never seen anybody do that in the real world (I think the exams want what the authors did though)
• Category 2 - UML syntax type errors
• Category 3 - Other oddities

Observations

Class diagram

• Who puts JSPs in a class diagram? (category 1)
• Some relationships don't show a multiplicity (category 2)
• Missing classes in class diagram that are referred to from other diagrams (category 3)
• I don't think the class diagram in the book is worth 40 points (category 3)
• User is not an entity? (category 3)
• Some classes like Density are used and not defined anywhere? (category 3)
• Cade/Sheil say it’s not important to put methods with signatures, however they do that on their book! I didn’t get yet what Oracle really expect in this diagram. via comment left on blog (category 3). See blog for one school of thought.
• the class diagram should be technology agnostic… other people say to put as much information as you can, because everything that appear in the Sequence Diagrams must be defined in the class diagram via comment left on blog (category 3) - More advice says to put everything on the sequence diagram in the class diagram and use stereotypes about the technology in the class diagram
• Cade/Sheil only put domain classes in the class diagram, but sequence diagrams should not refer to classes outside the class diagram.
• Cade/Sheil only denote a central Controller within their Class Diagram, but the go on to use view specific Cotrollers within their Sequence Diagrams.

Component diagram

• I think the component diagram is too detailed. (category 1)
• Component diagram for the "fully worked solution" correctly uses UML 2 style, however earlier in chapter examples use UML 1 style (category 2)
• Listing all the classes/JSPs in a component diagram (category 1)

Sequence diagram

• Uses async arrows for synchronous calls
• Missing return arrow from entity manager
• Inconsistencies between sequence and class diagram such as controller

---

CategoryCertification