wood burning stoves 2.0*
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes I found out wher ethe success really lies in the SCJD exam. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "I found out wher ethe success really lies in the SCJD exam." Watch "I found out wher ethe success really lies in the SCJD exam." New topic
Author

I found out wher ethe success really lies in the SCJD exam.

Yucca Nel
Ranch Hand

Joined: Nov 20, 2008
Posts: 147

I am about to do my essay exam tomorrow and I stumbled upon some ideas that may assist those that are busy with the exam.

1stly I would like to say that there are two ways one can read the instructions...
1) Reading the musts... OR
2) Read everything again and again... which helps...

Here is how I read the requirements without the must..
1)I am required to create a system that improves the performance upon the existing system (The CSR are not happy).
2) The system in use is probably not going to be used again...
3) The Interface provided for me gives clues to what really is required.

We start by coding the interface implementation and we do so by trying to improve the performance. The only way we can garuntee that performance improves is by insisting that a good multithreaded server is in place
and that the clients are thin clients...

Hope you still with me

We now can cater for a multithreaded server that does a lot of the load on behalf of the client. This means the locking API can be coded with the expectation of multiple threads. This also means that should we chose to have a thin client, A lockMangager can be used with RMI as the server spawned thread IDS for client requests can be used with the lock manager but care must be taken for deadlock if client crashes. (I wont say how but it can be done and I have given clues to why it is acceptable).

Can we make our DataAccess class be a singleton? Again I think yes I explianed

Thats about as much as I can say

wish me luck for tomorrow


SCJP 6.0, SCJD (400/400), SCBCD for JEE 5, SCWCD 1.4 I do videos for development at
http://www.youtube.com/user/thejartender?feature=mhee
I am probably the only developer ever to have had an orange sized brain tumor in my brain while learning development!!
K. Tsang
Bartender

Joined: Sep 13, 2007
Posts: 2242
    
    7

Nice breakdown of the assignment approach. For me I looked at it this way. The only thing I cared was the interface provided by Sun, plus multithreading (hence locking including). Another thing to keep in mind is the scoring topics (OO, GUI, docs, server, data class etc).

Given the scoring topics, the ideal approach is to get the data class and locking working on its own. Then the server side (RMI or sockets) working. Then the GUI. Of course the OO design in everywhere.

This is why in my choices.txt file I have sections called Overview, Requirements and Assumptions. The assumptions are really important to your design and architecture.


K. Tsang JavaRanch SCJP5 SCJD/OCM-JD OCPJP7 OCPWCD5
Yucca Nel
Ranch Hand

Joined: Nov 20, 2008
Posts: 147

This is why in my choices.txt file I have sections called Overview, Requirements and Assumptions. The assumptions are really important to your design and architecture.


Well I cant say I made many assumptions as I think it is pretty clear what is required. For eg we know we need a Lock Manager class and a Data Access class. We also know we have a junior developer and must keep code short. These in themselves provide nice counter arguments for anything. eg. RMI vs sockets. I chose RMI because we know the benefits of sockets are not that critical in this application.(B&S) Its a small firm and only has CSR and there cant be more than 100 CSR so RMI is def sufficient to deal with the amount of data and scalability.
Does the junior developer understand sockets or RMI? Well RMI is newer isn't it? I dont know about you but I started Java about 14 months ago and def did not start with Java 1. Surely the new developer is gonna be more familiar with the newer technology? What about fat vs thin client? Well I don't know what kind of cpu the CSR clients have (as they are they only multiple clients we know of). Seeing as they are the ones that complain then I suggest we make thin clients and upgrade the server to deal with a lot of the work concurrently. The choice is the customer... ask the customer if they want to upgrade each pc or just the server? O.O
K. Tsang
Bartender

Joined: Sep 13, 2007
Posts: 2242
    
    7

It looks like to me your assumptions based on your post is about client/user but what I was referring to is the assumptions for the actual assignment (design, architecture, computer location, etc). Assumptions like:
* CSR understand that 48 hour thing
* CSR should know what the remote server IP/port are
* All computers are in the same LAN (meaning no firewall stuff between clients and server)
* CSR will not run local mode and network mode at the same time

Stuff like these. Not about CPU on client machines or what JDK version those computers have. Besides who cares about these.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: I found out wher ethe success really lies in the SCJD exam.
 
Similar Threads
Why Swing client at all?
NX: Locking and Unlocking and Sun's Must Conditions
Local Adapter Issue
Local Mode Considerations
URLyBird Unimplemented Fucntionality