Project #2CMSC132
Due Thu Sept 27, 6:00 pmFall 2007

Objective

To become familiar with

• Linear Data Structures
• Maps
• Sets
• Java Collections Framework

In case you have not already noticed, this is an closed assignment. You must read the Open/Closed policy before working on this project. The policy can be found at:

http://www.cs.umd.edu/class/fall2007/cmsc132/openClosedPolicy.shtml

Project Clarifications

Any clarifications or corrections associated with this project will be available at: clarifications.html

Specifications

Overview

For this project you will implement several classes that support a calendar application. This application allows users to schedule, remove, and perform other typical calendar activities. The classes you are expected to implement are:

• MyLinkedList → represents an ordered collection (sequence) of elements.
• MyQueue → represents a queue.
• MyStack → represents a stack.
• MySortedLinkedList → represents a sorted collection (sequence) of elements.
• Time → represents time using hours and minutes.
• WeekActivities → represents activities we have in a week.

The javadoc documentation for this project can be found at: doc/index.html. The documentation provides a detailed explanation of what you are expected to implement.

Grading

• Tests(75%)
  • Public Tests(45%)
  • Release Tests(30%)
• Student Tests(15%)
• Style(10%)

Code Distribution

The project's code distribution is available by checking out the project named p2. The distribution includes text files named with a pub prefix and the following packages:

• lists → Includes shells for all the list related classes.
• weeklyCalendar → In this package you will find shells for the classes named Time and WeekActivities. In the monthlyCalendar package you will also find the following support classes and enumerated types: Activity, ActivityComparator, Date, and Day. You will use these classes and enumerated types during the implementation of the calendar application; you should not modify any of them.
• tests → Includes the public tests (PublicTests.java) and a shell for a class (StudentTests.java) that you must complete with your own tests.

Requirements

Testing Requirements

You must provide your own tests in the file StudentTests.java provided with the code distribution. You need to provide tests for all the classes in the lists package and for the Time and WeekActivities classes. The submit server provides information regarding methods that are not covered by public or student's tests; Please look at this information while developing your tests. Notice that even though a public test may exist for a method, the test may not test the method for all the possible arguments it can accept. Therefore provide tests for methods even if they are already tested in a public test.

We encourage you to thoroughly test your code with your own tests. This will allow you to pass the release tests sooner plus will help you develop your testing skills (after all, there is no submit server in the real world :)).

If you define any text files for your tests, you must name those files beginning with "studentTest" and ending with the .txt extension. If you don't name files this way, the submit server will generate an authorization error (even if the tests run fine in Eclipse). By the way, feel free to use the TestingSupport.correctResults method for your own tests. The TestingSupport class is part of the code distribution.

Keep in mind that your can use the debugger with JUnit tests.

Project Requirements

• The MyLinkedList class may not be implemented using any Java API class (e.g., ArrayList, LinkedList, etc.).
• The MyQueue, MyStack, and MySortedLinkedList implementation must be based on the MyLinkedList class.

Style Requirements

• You must use meaningful variable names and good indentation.
• You must indent your code using three or four spaces or by using the Eclipse "Correct Indentation" option.
• You must use the same style for blocks of curly brackets ({ }) throughout your code.
• 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.
• Code Style - From the Style Guide you should focus on the following sections: Indentation, Declarations, Statements, White Space, and Naming Conventions.

Honor Section Requirements

No additional requirements.

Submission

Submit your project using the "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 University's Office of Judicial Programs.