ITECH 3217 Programming 3

Assignment 2 – TP 3, 2010
Due – See course description for due date and policy on late assignments

Marks – 20% of final grade

Preface:
This is an individual assignment – all work must be your own with appropriate
attributions to outside assistance.

Description of task:
You are required to develop a database driven J2EE based Web application to manage a
dance school’s student enrollments. The application allows students to register and enroll
in different classes, such as ballet, tap, jazz and hip-hop. Students will be able to look up
their class list. Teachers can also login to the system and get a class list for each class.
Thirdly, an administrator can manage all the system and assign teachers to classes.

Your site should be written in Java (using the Netbeans IDE) and store all persistent data
in a MySQL Server database.

Information Requirements – MySQL:

Your MySQL Server database should store all persistent data for your site, including
(Note: where a many-to-many is indicated, you will need to add a relationship table):
1. Students’ personal information, for instance: username, password, first-name,
surname, phone, email, and age.
2. Teachers’ information, such as username, password, first-name, surname, phone,
email, and age.
3. Class information, such as name, maximum number of students, scheduled time,
and the room number (eg dance studio 2) the class is to be held.
4. There is a one-to-many relationship between teachers and classes, indicating the
classes each teacher has been assigned to teach.
5. There is a many-to-many relationship between students and classes, indicating the
classes a student is enrolled in.

Level of Access and Functional Requirements:

Your application must provide different levels of access by having students, teachers and
administrators login using their usernames and password. Students can access their own
personal details and their list of enrolled classes. They can also access a list of classes
available (those that have not reached their maximum number of enrollments) for them to
enroll. Teachers can access their own details and list of classes they are assigned to teach,
as well as the student details of those enrolled in the classes they teach. The administrator
can access all user and class details and assign teachers to classes.
 ITECH 3217 Programming 3
Assignment 2 – TP 3, 2010

Administrator:
Administrator is a superuser who is enabled to maintain the database. The administrator
has the ability (password protected) to add, delete and modify records. The following
administration tasks are identified:

1. Login
2. Manage Students (View/Add/Edit/Delete)
3. Manage Teachers (View/Add/Edit/Delete)
4. Manage Classes (View/Add/Edit/Delete)
5. Assign/remove classes to/from teachers

Teachers
A Teacher is enabled to check their own details and class allocations, as well as get class
lists. The following administration tasks are identified:

1. Login
2. Manage their own personal details (View/Edit)
3. View their class allocations.
4. View list of students that s/he has in each class
5. Click on student's name and see student detail (only for their own students)

Students:

A student is enabled to check his/her student details, qualifications and enrollments. The
following student tasks are identified:
1. Login
2. View/edit his/her student details.
3. Manage enrollments (View/add/delete).

Additional Information:
Your application home page should allow existing users to login by providing a
username, password and a user type (student, teacher or administrator). It should also
provide a link for prospective students to register as students.

Your application home page should also provide a link to an “About” page, which will
display your name and student id.
 ITECH 3217 Programming 3
Assignment 2 – TP 3, 2010

Application Page Layout:

The layout (see Figure 1.1) only shows web pages needed to meet application functional
requirements. All web pages shown in the layout need to be written in Java (either
HTML and JSP).

About
Register
Login
Student

Delete Student

Teacher Administrator Student Student

Class List
Details Details List Details

Enrol

Edit Teacher Edit Admin Edit Student

Details Details Details

Class List Class List

Delete Class

Student Edit Class View Class Add Class

List

Figure 1.1 Page Layout to meet minimum Functional Requirements

Further Instructions
Your application should follow a Model/View/Controller paradigm.

• The Model involves the data and should use Enterprise Data Beans. Each table in
your database should be modeled as an entity bean with a session façade.
• The View involves the visible pages and should use JSP and HTML files.
• The Controller involves actual processing (usually without visible components)
and should use Servlets
 ITECH 3217 Programming 3
Assignment 2 – TP 3, 2010

User Interface
Marks will also be given according to your user interface layout and design. Ensure you
put thought into how to layout each page, maintaining consistency across your
application and sing appropriate interface features such as tables.

Note: You are not expected to perform any client side validation (javascript).

“Wow” Factor
If you do everything the specs require perfectly then you could get a mark of 16 out of
20 for the assignment (which is 80% - HD).

The other 4 marks will be assigned according to extra things you have added to your
assignment. This will be marked a lot harder than the other parts of the assignment – so
it should only be done if you want a challenge. The mark is subjective, can cover a lot of
different things and must be a result of careful thought (I will not answer questions like
– is this enough for a Wow factor?).

Note: extra features that are poorly implemented or documented may be detrimental to
your marks.

Documentation
Each submission should:

1. Be fully commented.
2. Include instructions about how to install your application
3. A statement explaining what you have done in addition to the above
specifications. If you add an extra feature but do not mention it in your
documentation it will not be marked.

What to submit:
You should submit a zip file, containing the project folder and the report should be
submitted on disc or USB flash drive to your lecturer.

Assessment Criteria:
Programming 8
Documentation (commenting and instructions) 4
User interface layout and design 4
 ITECH 3217 Programming 3
Assignment 2 – TP 3, 2010
“Wow Factor” 4
__________________________
Total: 20