java 2 开发 考试 （译文+原文.doc

翻译原文：

In this second example, we will take a nuts-and-bolts approach to exam preparation and code more examples of the major pieces. If you are unfamiliar with one or two of the major areas touched by the assignment------Swing development, say, or RMI implementation------these examples can help accelerate your own practice work. We will also take a closer look at the administrative and scoring details of the exam. To do this, we downloaded our own assignment and wrote a solution, so that we could match our discussion to the degree of difficulty we saw.
The Java 2 Developer’s Exam, as exams of this type go, is not overly complex or subtle. The focus is competence in applying programming, design, and integration skills over a broad range of libraries and problem domains. The power of object-oriented design, of course, is that breaking a job into self-contained pieces is easy. The question lies in effective partitioning of the overall goal, but this is already answered by the assignment requirements. Some elements in the assignment code require fixing, but they are plainly disclosed in the exam notes------no hidden surprises. The top-level objectives are straightforward, and although there are one or two obstacles to extending the code that may appear novel to some candidates, they require less time in thinking than implementation to solve.
在这个第二个例子中，我们将用包含具体细节的准备考试的方法并对更多例子中的核心部分进行编码。如果你还是对任务分配中的一两个主要部分不熟悉，------比如Swing开发，RMI（远程方法调用）执行等------这些例子能帮助你加速你的练习进度。我们也将对管理和考试的评分细节…..为了这些，我们将下载自己的任务分配并撰写解决方案，以使我们能够把我们的讨论匹配我们看到的难度分级。
JAVA 2 开发者考试，就是作为这种类型的考试，不是很复杂或强调细节。重点是考察应用程序编程，设计能力和覆盖一个广泛的库和问题域的集成化能力。面向对象设计的能力的优势是将一个工作分成自包含的许多部分是很容易的。问题存在于将整个目标任务的高效划分，但是这些已经被需求分配阶段所解决。只是一些代码元素需要被组装，但是他们已经在考试的提示中被明白的列出了，没有任何隐藏的部分。那些高级对象是直截了当的，并且即使有一两个模糊不清的，对于一些投考者来说是新鲜的扩展代码部分，他们需要比实行解决更少的时间来思考。
与考试的主要要求同样重要的是对技巧方法的了解，像我们在前面的章节（第15章至第18章）中所做的，现在我们将建一个我们自己的客户端服务器应用程序的主要部分，从头开始。如在前面的例子中，我们将留下一些综合性的细节作为读者的练习。考试的开始的代码是简单的，所以我们将留下前面的例子的讨论作为可腀@鱿值奈侍獾某渥愕母聪啊Ｄ切┪颐鞘盏降南略氐娜挝穹峙湟笪颐钦硪恍┎蝗范ǖ姆椒ǎ颐且脖匦胍砑右桓鱿嘤Φ男薷牡姆椒ú⑸境硪桓觥Ｋ晕颐遣还刈⒛阍诶拥拇胫蟹⑾值摹暗乩住薄？夹闯稣返拇耄憬切┎惶返拇搿Ⅻbr>在这个例子中，我们将沿用技术支持服务系统（trouble-ticket系统）的需求分析.