Overview

For this project you will implement the data manager of an online test system. The system allows for the definition of exams with three possible kinds of questions: true and false, multiple choice and fill-in-the-blanks questions. The system will grade submitted exams and generate some statistical information. The first part of your project consists of submitting an UML class diagram representing the design of the data manager; the second part consists of implementing your design. Keep in mind that each part has a separate deadline.

Objectives

• Practice the design and implementation of object-oriented software systems.
• Learn to use UML class diagrams to represent object-oriented designs.

Grading

• (35%) Design (UML Class Diagram)
• (20%) Implementation of provided design
• (35%) Tests (all public tests)
• (10%) Style

Clarifications

Any clarifications or corrections associated with this project will be available at Clarifications

Code Distribution

The project's code distribution is available by checking out the project named OnlineTest. The code distribution provides you with the following:

• A package named onlineTest - Package where all the classes representing your design will be implemented.
• A package named tests - Includes the public tests (PublicTests.java). Notice that you are not required to write student tests for this project; however, we recommend you do so.

Specifications

Data Manager

For this project you will implement the data manager (model component of the MVC paradigm) for an online test system.The system allows for the definition of exams with three possible kinds of questions: true and false, multiple choice and fill-in-the-blanks questions. The system will grade submitted exams and generate some statistical information.The first part of your project consists of submitting an UML class diagram representing the design of the data manager; the second part consists of implementing your design.

The functionality of the system you will implement is represented by the interface Manager. The interface represents the methods available to anyone trying to make use of the system. The javadoc documentation for the project can be found at javadoc. Your task for the design part of the project is to come up with a set of classes and interfaces that together provide the functionality defined by the Manager interface.

Access to the data manager functionality will be possible through a class named SystemManager that you must define. This class implements the Manager interface. Feel free to add any instance variables and private methods to this class. Public tests create an instance of the SystemManager class in order to test your system.

Keep in mind that your implementation must match your design, otherwise you will lose significant points. We encourage you to start working on this project as soon as possible, as there are a lot of details that can not be completely specified in this description. The earlier you start, the sooner you will get the feedback you need to complete this assignment.

Your design should make use of object-oriented design concepts (e.g., generalization, specification, etc.) discussed in class. Keep in mind that having a large number of classes does not guarantee a better design grade. Your UML class diagram does not need to include all the parameters to each method, though return types are interesting. You are encouraged to list all the class fields and their types. Your UML class diagram does not need to include the Manager interface. In addition, the class diagram for the SystemManager class does not need to include the Manager methods. You should use some graphic tool (e.g., AmaterasUML) to generate the UML class diagram. You will not get any extra credit for using a particular tool; just make sure you provide the file representing your design.

Requirements

• We expect to see at least four classes (SystemManager and three additional classes) in your design.
• You should use maps/sets to keep track of your data. In particular, do not use arrays and then call Collection.sort to sort the data.
• Verify that your project passes the submit server tests (https://submit.cs.umd.edu/)
• See StudentTests.html for information regarding the implementation of student tests.
• You must attempt to submit your project immediately after checking out the project (even if you have not implemented any methods). This will allow you to verify that the submission process is working as expected.
• You should submit your project often. This will keep versions of your project in the submit server that are easy to retrieve (you can also get previous versions from your CVS repository). If your computer crashes or you experience any other problem you will have a permanent backup in the submit server.
• Make sure you check your project results in the submit server. Those are the results we use to compute your grade.
• You have three tokens for this project in the submit server.
• Style
  • Good variable names.
  • You must avoid code duplication by calling appropriate methods (rather than cutting and pasting code). You may define your own private utility methods to perform often repeated tasks.
  • Style as defined by the Eclipse Format Element option (Source → Format → Format Element) or as specified in Code Conventions for the JavaTM Programming Language (focus on the following sections: Indentation, Declarations, Statements, White Space, and Naming Conventions).
  • Although you should avoid source lines exceeding 80 characters, you will not be penalize if they are present in your code.

Good Faith Attempt

The UML design represents the good faith attempt for this project.

Submission

Design Submission

Submit a UML class diagram with your design by creating a pdf document or image file named uml (e.g., uml.pdf or uml.jpg) and then uploading this file to the submit server (use the "submit" link for "Online Test UML Design"). Double-check your submission is correct by downloading it from the submit server after submitting.

In a Windows environment you can create pdf files by using CutePDF Writer, a free tool available at:

http://www.cutepdf.com/Products/CutePDF/writer.asp.

You Must Verify Your UML Design Submission

The submit server allows you to download any submissions you have made. It is your responsibility to verify that the UML Design document you have submitted is the correct one. If you submit an incorrect one, you will not have the opportunity to resubmit it after the deadline for the design submission has passed. See your Teaching TAs (in lab session) if you want to verify that you submitted the expected design.

Implementation Submission

Submit your implementation using the Eclipse "Submit Project" option (available by right clicking on the project folder).

Academic Integrity

Please make sure you read the academic integrity section of the syllabus so you understand what is permissible in our programming projects. We want to remind you that we check your project against other students' projects and any case of academic dishonesty will be referred to the Office of Student Conduct