ch17 - 17 Final Submission and Essay CERTIFICATION...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
17 Final Submission and Essay CERTIFICATION OBJECTIVE Preparing the Final Submission
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Chapter 17: Final Submission and Essay CERTIFICATION OBJECTIVE Preparing the Final Submission You’ve built your project, and now the Big Day is finally here. Submission time. Your exam instructions include very specific details for submission, and you must follow them exactly . Pay attention: any deviation from the submission instructions can mean automatic failure. For example, if your instructions say that you must be able to run your application with a specific command, java -jar runme.jar server you had better have a JAR named runme.jar , and it better take a command-line argument “server”, and it better include a manifest that specifies the class within runme.jar that holds the main() method. In this short chapter we’ll look at a typical submission requirement, and walk through how to build the final JAR along with a project checklist. Finally, we’ll look at some examples of the kinds of essay questions you might see on your follow-up exam. File Organization Imagine the following submission instructions; yours will probably be very similar: All project files must be delivered in one, top-level Java Archive (JAR) file. The top-level, project JAR must be named project.jar . The project JAR must contain the following files and directories: An executable JAR named runme.jar that contains the complete set of classes. The code directory, which must hold the source code for your project, with all source files organized within directories reflecting the package structure of the classes. A version file named versionInfo.txt . This must be a plain ASCII text file describing the specific version of J2SDK that you used (example: java version “1.3.1”). A copy of the data file, exactly as specified in the schema instructions, named db.db .
Background image of page 2
The docs directory, which must hold all project documentation including: A design decision document named designChoices.txt , an ASCII text file documenting design decisions. End-user documentation for the server and client, unless you have used an online help system within your application. The help documents may consist of multiple HTML files but must begin with a HTML file user guide. javadoc HTML files for all classes and interfaces. All public classes, interfaces, and members must be documented. Developer documentation, optional. Figure 17-1 illustrates the directory structure that matches the sample instructions above. Preparing the Final Submission 3 FIGURE 17-1 Sample directory structure for project submission
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Creating the Executable JAR An executable JAR is a JAR file that contains at least two things: A class file with a main() method.
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 09/17/2009 for the course CMPE 126 taught by Professor Gpour during the Fall '07 term at San Jose State University .

Page1 / 11

ch17 - 17 Final Submission and Essay CERTIFICATION...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online