This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
Now that I have passed the SCJD certification, I have two questions: 1. I passed the FBN assignment, and would be curious to see the newer assignment. Would it be appropriate to get a copy of that assignment from someone or does SUN have a way for FBN candidates to see the newer assignment. 2. Two people have asked about approach. My design choices document is nearly 14 pages explaining my approach. I would gladly share this document, if appropriate to the forum.
-Ahmad<br />Sun Certified Java Developer (SCJD)<br />Sun Certified Java Programmer (SCJP)<p>"You got to be careful if you don't know where you're going, because you might not get there." -Yogi Berra
#1. No, you would have to sign up to take the new assignment to see it. It would be inappropriate for someone to send it to you, just as you sending the FBN assignment to someone else. #2. I think they wanted a basic overall approach, rather than 14 pages. Mark
hi Ahmad, Your design decision's document was 14 pages!? The user-documentation doesn't specify much weight on it unlike the new assignment. Sun told me not to go overboard on this. I'm also tempted to write more rather than less to be on the safe side. Did you include many class diagrams?.. or any other sorts of diagram? Which areas did you put most emphasis on? Feel free to send me a copy of your document, i will happily take notes and return some comments. congrats on being a SCJD!
Joined: Aug 29, 2002
We were told to have a "Design Choices" file which details our overall approach. From my table of contents, you can get a sense about what I discussed: Filename: DesignChoices.txt Table of Contents 1.0 Background and General Assumptions2 1.1 Roadmap2 2.0 Use-Case View2 2.1 Actors2 2.2 Use-Cases3 2.2.1 Server-Side3 2.2.2 Client-Side3 2.3 Requirements3 2.3.1 Client-Side4 2.3.2 Database Client4 2.3.3 Data Server4 2.3.4 Data Resources4 3.0 Architectural Design4 3.1 Data Server4 3.1.1 Data Server Interfaces5 3.1.2 Implementation of the Data Server Interfaces5 3.1.3 Connection Factory5 3.1.4 Implementing suncertify.client.ConnectionFactory6 3.2 Implementation of the Data Server7 3.2.1 Modifying suncertify.db.Data7 3.2.2 Implementing criteriaFind(String) method within suncertify.db.Data7 3.2.3 Implementing suncertify.db.lock(int) and suncertify.db.unlock(int)8 3.3 Administrator GUI9 3.3.1 Design9 3.4 Traveler GUI9 3.4.1 Design9 3.5 Analyst GUI9 3.5.1 Design9 4.0 Coding and Documentation Standards10 4.1 Deprecated Methods10 4.2 Java Coding Standards10 4.3 Javadoc Standards10 5.0 Deployment10 6.0 Testing10 7.0 References10 A1.0 Concurrency and Isolation11 A1.1 Locks11 A1.2 Granularity11 A1.3 Escalation11 A1.4 Isolation Levels12 A1.5 Lock Modes and Read/Write Permissions13 A1.5.1 Read Uncommitted13 A1.5.2 Read Committed13 A1.5.3 Repeatable Read14 A1.5.4 Serializable14 A1.6 Deadlocks14 One can see that pages 11 to 14 refer mainly to the concept of concurrency and isolation, which I needed to better, so I had an appendix for the interested reader.