Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes forum!

Tom Doyle

Greenhorn
+ Follow
since Apr 23, 2002
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Tom Doyle

I think this is a design decision that would be argued either way. I chose to ignore case and qualified that approach by documenting it among my design decision points.
I am following the same strategy as Karen by using the recordID as my unique identifier. This would appear to be the simpliest and most intuitive available approach.
There is only one basic path to become a physician -- an academic hoop jumping process followed by their practical internship, i.e. their equivalent of certification. There is no corresponding unique means to become a IT professional. Those with computer science degrees must compete with the motivated high school dropout who picked up a copy of "Java in 24 Days". Understanding the efficiency order of a sort algorithm might not be as desirable as getting the payroll out on time. Both skills are valuable but the relative value is dependent upon context.

If the job is Information Technology the job requirement is more oriented toward vocational expertise rather than holding academic credentials. Certification is one measure of said vocational expertise. Those kinds of individuals wouldn't have a prayer in getting into many doors that would be open to someone of your background. However if the name of the game is IT/DP/MIS then it is your skills as a programmer rather than that of a academic that are valued. Some of the best programmers that I've seen in a 30+ year career career have never seen the inside of a University classroom.
13 years ago
Even though the GUI that is required for us to implement is quite limited, I agree with Jeffry that we need to implement all the methods of the documented interface. This would include methods such as record creation which would not be leveraged by our GUI.

Part of the exam is to assess our skills as OO designers. OO frequently targets implementation of functionality for future envisioned requirements or reuse in a different application. For example the current exam is to produce a GUI suitable for CSRs -- some objects we develop could be reused by the B&S Marketing Department in the future.
I think that Jeffry's approach would work, but I suggest there might be a more intuitive approach. If the goal is to set two bytes to 0x8000 then why not just do a .writeShort(0x8000)?

The objective is to set the highest order bit of a two byte field. When doing bit operations it seems advisable to keep to a bit oriented numeric base such as hexadecimal or octal. Of course decimal will work, but it isn't always intuitive when doing bit manipulations and can become more problematic when two's complement numbers come into play.
Hi Pete,

I interpreted "Magic Cookie" as a file signature, i.e. the "magic number" that is embedded at the beginning of many data files identifying the file type or originating application. This conclusion would seem to be consistent with the comment in the instructions denoting, "magic cookie value identifies this as a data file".

The remaining fields in the header (1) indicate where the first contractor data record begins and (2) tells us how many time the three fields in the schema section repeat.

Best of luck,
Tom

[ November 15, 2008: Message edited by: Tom Doyle ]
[ November 15, 2008: Message edited by: Tom Doyle ]
I found the book to be well worth the financial and reading time investment. I have refactored several aspects of my solution based upon concepts I found in their sample project. For example, my original record locking code was reduced in size by at least half from some thoughts that their narrative inspired.
Don't buy this book if you are expecting to simply parrot their code as it addresses the high level requirements of the SCJD without giving away the specific solution.
Due to work-related travel I had not touched my SCJD project for several months This book was an excellent tool to help me brush the rust off of my Java skills and finally complete the project.
My hat is off to the authors for a valuable aid in the SCJD process.
Tom Doyle
Ohio State University '76
If maintaining configuration parameters is an objective, why not look at the Preferences mechanism that is available in JDK 1.4 and above. The "Java 1.4 Tutorial" by Gregory Travis has an excellent overview of its' capabilities which I highly recommend.
The project is supposed to implement an end-user interface rather than an administrative interface.
End-users (i.e. travel agents and the general public) would be limited to booking flights. In the real world Delta Airlines wouldn't take kindly to a travel agent changing flight times.
The application could be extended to administrative functions but would then require multiple levels of security authentication and access that would unnecessarily complicate the exercise.
I agree that the lock-modify-lock flow is appropriate. This is similar to the row locks that RDBMS engines such as Oracle and DB2 perform during uncommitted updates.