Special Guide for Project Design

The following is a guide that will help you meet the requirements of your Project Design. Some general concepts that should be followed are:

• Stay as simple as possible
• Readable
• Understandable
• Focus on main ideas only (High Level Design)
• No source code
• Draw Diagrams
• Individual work

Your Design consists of 3 Parts:

• The diagram of the individual classes inside their package(see Part A below)
• The class relationship diagram diagrams (see Part B below). You take the classes that you came up with in the first part and you show now the relationships between the classes using:
  • Asssociation
  • Aggregation
  • Inheritance
• A descriptive acounting of your thought process in creating the classes and their relationships (see Part C below).

The security issue does not appear in the design part.

Please provide the following diagrams:

Sometimes, you’ll find the need to organize the elements of a diagram into a group. You might want to show that a number of classes or components are part of a particular subsystem. To do this, you group them into a package, represented by a tabbed folder, as in Figure.

An Example of how a class can be described in an icon. You may not be sure yet about all the attributes, but do your best in defining at least the methods.

C. PACKAGE & CLASS & METHOD DESCRIPTION

In plain text explain all your packages, classes and the methods for each class. 
Some points that should be covered in your description are:
A. Why you created that class
B. The reasoning for each method / attribute
C. How does it fit in the whole project
D. What algorithms are you going to accommodate inside.