_files/image002.jpg)
N E W
T R A C S
HAWARD SOFT DESIGN UNIVERSITY
The
project goal is to design and analyze a new web base tracs software for Haward
Soft Design Unviersity (not real). This system allow the the users to access,
update, or even create course information (depend on who users they are) in
real time from internet browser.
Ten
years ago, Haward Soft Design University (HSD University) had 4.001 students,
who 156 students were international students. Because the HSD University is
wellknown in the world, now; it has 45.893 students with 15.523 International
students.
The existing system for adding, dropping
course(s), updating students’ grades is through TRACS System which can only
access by local phone. With this current system. This system cannot allow the
students or instructors to add or modify something (unless they make a
international or long distance calls). It also won’t give any information about
the current seats available for a specific couse. The other thing who is also concerned
by HSD University is about the limitied seats for courses while the students intend to hold the courses until it almost close to dropping
course deadline, this doesn’t give any chance for those students who
want to enroll the same courses.
Realizing
there are huge students want to enroll the courses and the existing system doesn’t give an equal opportunity for those
students who are not currently in the university nearby by the course request
period, the university make a decision to change the old TRACS System to a new
web base TRACS System.
The
New TRACS System provides year-round access for requesting courses for every
semesters and to inform students of registration and other important academic
status messages and holds. The New TRACS System has a new feature which can let students in waiting list if the courses are fulled. The
System let the students check their study list and check for holds and other
messages.
For
the Instructor Part, the New TRACS System enable the instructors to input the students’
grades online, giving assignments, making notes at any part in the world. This
make the instructors’ lifes more easily.
I
believe by using the virtual model as the backbone design, it ensures better
control on software development. For designing the system, I use Rational
Software.
The
reasons for using the Rational Software are:
More
over, I have selected ORACLE and JAVA language for platform independence. With
all the risks of being too early to decide, I feel that in the present and the
near future there is no other feasible alternative yet.
REQUIREMENTS
In
New TRACS System, the Course Request Period is provided for many weeks through
the orientation and advisng periods each semester. This allow the students
plenty of time to meet with the adviser, clear all holds, take or verify
required test statuses, and make additional changes to students’ requests as
well.
The
Course Add/Drop Course Period is schedule for five weeks, the three weeks
before classes begin and the first two weeks of the semester. This is a
“real-time or live registration,”
first-come, first served, add and drop period using the same TRACS
system. The students will be able to add classes which are still opend after
the Scheduler is run and drop most classes without special permission during
the period.
There
is a new feature that allow students to put themselves in waiting list if they
still hope to get seats in specific courses. Realizing that many students will
apply to waiting list without other considerations, the system will make the
students to think twice before putting themselves in waiting list. I’ll discuss
more detail after this.
Administrator,
course manager, intructors, and students .
The
hardware to access the New TRACS is the complete PC or Mac which connects with
the internet. This PC or Mac can be anywhere, in Library or home.
The
software I am going to design must be platform browser independent, reasonable
response time, can uses GUI.
Before
the users can get through the New TRACS System, they need to have unique
Personal Identification Number (PIN). At the first time registering the system,
they need their Social Security Numbers and Student Card Numbers. (for
Students) / Employee Card Numbers (for Administrator, Course Manager,
Intructor). This is only one time use. After that, they can choose the unique
user name and password for each student. The user can’t modify the user name,
but he/she can change his/her own password.
Mainly,
there are four types of users who can access the system. They are the
admistrator, course manager, instructors, and students. I devide the users by
limiting the features they can have.
The
Administrator is the person who can start up / shut down the system, create /
remove account, manage files, and login to the system.
The
Course Manager can:
1.
Add student to students records.
2.
Delete a student.
3.
Add a course to the course records.
4.
Update a course.
5.
Delete a course.
If
a student is being deleted, then all the courses which he/she is currently
enrolled must also be removed.
The
Instructors features are:
1.
Display the course list.
2.
Input the Students’ Grades.
3.
Giving notes.
4.
Giving assignments.
5.
Giving quizzes.
If
the instructor wants to drop his/her class, he/she must make a written request
to the Course Manager with Chair’s approval.
The
Students features are:
1.
Displaying Courses Information.
2.
Displaying Grades.
3.
Attempting to Add a course.
4.
Dropping a course.
5.
Adding their own id# to waiting list.
6.
Removing their own id# to waiting list.
7.
Sending Assignments.
8.
Taking quizzes.
If there are students in waiting list, then the first
priority in waiting list is the person who in the first waiting line on the
list. If somebody drop the course, then the first priority waiting list student
automatically assigns to that course. Those who get enroll in the course from
wating list, cannot drop the course if it is already accepted in the course,
except they are still in waiting list.
Use Case Documentation
_files/image003.gif)
_files/image004.gif)
|
Use Case: Login |
|
|
Actors |
Administrator, Course
Manager, Instructor, Admission,
Student. |
|
Purpose |
To access the system
according to user categories with each privileges. |
|
Overview |
Before the system can be
access, the user must enter login name and password to know whether the user
is a valid user and what previleges he/she can have. |
|
Type |
Primary and essential |
|
Note |
Each user must has their
own unique name and password to login the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
This use case begins when the user starts to access the tracs system. |
|
|
2.
The user input the user’s name. |
3. Store the user’s name in variable
userName. |
|
4.
The user input his/her password. |
5. Store the user’s password in
variable userPassword. |
|
|
6. The system checks whether the userName
and userPassword exists in the userList. |
|
|
7. The system gives the valid user
notification that he/she can start accessing the system with the specific
previleges. |
|
Alternatif
Courses |
|
Line 6 |
Invalid username and
password entered. Indicate error. |
|
|
|
|
|
|
|
|
|
_files/image005.gif)
|
Use Case: Start Up / Shut Down |
|
|
Actors |
Administrator. |
|
Purpose |
To start up / shut down
the tracs system. |
|
Overview |
The administrator can
start up the system after his/her user name and password has been verified.
After the system has been started up, other users can access the system. But
if the system has been shut down, no other users can access the system. |
|
Type |
Primary and essential |
|
Note |
Although the admistrator
has privileges to shut down the system, but if it is not indeed important to
shut down (for example: for maintenance purpose), the administrator will keep
the system on. |
|
Typical Course of
Events – Start Up |
|
Actor Action |
System Response |
|
1.
The Administrator starts to make the system works by turning on the
computer network. |
|
|
2.
The Administrator input his/her user’s name. |
3. Store
the user’s name in variable userName. |
|
4.
The Administrator input his/her password. |
5. Store
the user’s password in variable userPassword. |
|
|
6. The
system checks whether the user is the Administrator. |
|
|
7. The
system gives the administrator notification that he/she can start using the
system. |
|
8.
The Adminstrator connects the system to the network. |
9. The
system gets connection through the network and make other users able to
access the system. |
|
|
10. Indicates Start Up success. |
|
Alternatif
Courses |
|
Line 6 |
Invalid username and
password for adminstrator entered. Indicate error. |
|
Line 9 |
Network down and cannot be
accessed. Indicate error. |
|
|
|
|
|
|
|
Typical Course of
Events – Shut Down |
|
Actor Action |
System Response |
|
1.
The Administrator chooses an option to shut down the system. |
|
|
2.
The Administrator reinput his/her user’s name. |
3. Store
the user’s name in variable userName. |
|
4.
The Administrator reinput his/her password. |
5. Store
the user’s password in variable userPassword. |
|
|
6. The
system checks whether the user is the Administrator. |
|
|
7.
Determine no important application(s) still processing in the system. |
|
|
8. The
system asks the administrator to reconfirm shutting down the system. |
|
9.
The Adminstrator makes a confirmation that he/she wants to shut down
the system. |
10. The system was shutted down. |
|
Alternatif
Courses |
|
Line 6 |
Invalid username and
password for adminstrator entered. Indicate error. |
|
Line 7 |
If there is/are important
application(s) still in process. Give options to the administrator to wait or
terminate the process. |
|
|
|
|
|
|
_files/image006.gif)
|
Use Case: Manage Files |
|
|
Actors |
Administrator. |
|
Purpose |
To manage the files in the
system hardisk. |
|
Overview |
The Administrator manage
the files by creating, modifying, deleting files, changing the files status
to make the files accessible by the group members or everyone in the world. |
|
Type |
Primary and essential |
|
Note |
This feature available for
Administrator after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The Administrator chooses an option to create / modifying / delete
files / changing files status. |
2. The
system read the administrator’s option and ready to invoke the option’s
command. |
|
3.
The Administrator assigns target for that the option he/she has
chosen. |
4. The
system invokes the option’s command (to create / modiying / delete / changing
file(s) status. |
|
|
5.
Indicate action success. |
|
Alternatif
Courses |
|
Line 4 |
If the target file has an
important constraint integrity with another file in the system. Indicate
error. |
|
|
|
|
|
|
_files/image007.gif)
|
Use Case: Create / Remove Account |
|
|
Actors |
Administrator. |
|
Purpose |
To create user
account in the system and remove the
existing account. |
|
Overview |
The Administrator creates
new account that hasn’t existed in the system and removes the existing
account in the system. |
|
Type |
Primary and essential |
|
Note |
This feature available for
Administrator after he/she has logged in to the system. |
|
Typical Course of
Events – Create Account |
|
Actor Action |
System Response |
|
1.
The Administrator chooses an option to create a new account for a new
user. |
2. The
system read the administrator’s option and ready to invoke the option’s
command. |
|
3.
The Administrator assigns new user name and password and user type
(instructor/student) for the new user. |
4.
Determine that the new user that input by the administrator is not
existed in the system. |
|
|
5. Create
an account for the new user. |
|
|
6.
Indicate that the account has been created. |
|
Alternatif
Courses |
|
Line 4 |
The user name has already
existed in the system. Indicate error. |
|
|
|
|
|
|
|
Typical Course of
Events – Remove Account |
|
Actor Action |
System Response |
|
1.
The Administrator chooses an option to remove an existing account in
the system. |
2. The
system read the administrator’s option and ready to invoke the option’s
command. |
|
3.
The Administrator input new user name and user type
(instructor/student) for that exists in the system. |
4.
Determine that the user is existed in the system. |
|
|
5.
Display all the user information including the courses and sections
that he/she has. |
|
|
6. Ask
the administrator deletion confirmation. |
|
7.
The administrator confirm for that user target. |
8. Remove
the account from the system and the courses & sections that relate with
him/her. |
|
|
9.
Indicate that the account has been removed. |
Additional Note:
|
Alternatif
Courses |
|
Line 4 |
The user name is not
existed in the system. Indicate error. |
|
|
|
|
|
|
_files/image008.gif)
_files/image009.gif)
|
Use Case: Send Grades |
|
|
Actors |
Instructor |
|
Purpose |
To send the students’
grades to the system. |
|
Overview |
The instructor sends the
students’ grades . This grades is useful for records purpose and for students
to get their own grades from the system. |
|
Type |
Primary and essential |
|
Note |
This feature available for
instructor after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The instructor chooses an option to input students’ grades in the system. |
2. The
system read the instructor’s option and ask for the course code. |
|
3.
The instructor enter the course code. |
4.
Display all the students id, name
and ready to get input. |
|
5.
The instructor inputs all the students’ grades. |
6. Save
all the students grades in the system. |
|
|
7.
Indicate that the grades have been inputed to the system. |
|
Alternatif
Courses |
|
Line 4 |
The course code is not
existed in the system or the instructor doesn’t teach at that course.
Indicate error. |
|
|
|
|
|
|
_files/image010.gif)
|
Use Case: Give Assignment |
|
|
Actors |
Instructor |
|
Purpose |
To give the assignment to
the students that enroll the instructor course. |
|
Overview |
The instructor sends
assignment to the system so that the students can read it from the system.
The assignment can just be an assignment notes or it will need students to
take the assignment online and the students can submit their work from the
computer. This kind of submitted assignment must have due date. |
|
Type |
Optional |
|
Note |
This feature available for
instructor after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The instructor chooses an option to give assignment to the students. |
2. The
system read the instructor’s option and ask for the course code. |
|
3.
The instructor enter the course code. |
4.
Determine the course code is existed and this course is taught by the
instructor. |
|
5.
The instructor inputs the assignment and the due date. |
6. Save
the assignment & due date. |
|
|
7.
Indicate that the assignment has been added in the system. |
|
Alternatif
Courses |
|
Line 4 |
The course code is not
existed in the system or the instructor doesn’t teach at that course.
Indicate error. |
|
|
|
|
|
|
_files/image011.gif)
|
Use Case: Give Quizze |
|
|
Actors |
Instructor |
|
Purpose |
To give the online quizze
to the students that enroll the instructor course. |
|
Overview |
The instructor sends
quizze question to the system so that the students can read from the system.
This online quizze can be in multiple choices or questions with short
answers. The instructor must also provides the answer to the system so that
it will automatically generate the
scores after the student finishs taking the quizze. This kind of submitted
quizze must have due date with specific deadline time. |
|
Type |
Optional |
|
Note |
This feature available for
instructor after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The instructor chooses an option to input quizze to the system. |
2. The
system read the instructor’s option and ask for the course code. |
|
3.
The instructor enter the course code. |
4.
Determine the course code is existed and this course is taught by the
intructor. |
|
5.
The instructor inputs the quizze questions, the answers and the due
date and deadline time. |
6. Save
the quizze, answers, due date and deadline time. |
|
|
7.
Indicates that the quizze has been succeed input to the system. |
|
Alternatif
Courses |
|
Line 4 |
The course code is not
existed in the system or the instructor doesn’t teach at that course.
Indicate error. |
|
|
|
|
|
|
_files/image012.gif)
|
Use Case: Send Notes |
|
|
Actors |
Instructor |
|
Purpose |
To give the lecturer’s
notes to the students that enroll the instructor course. |
|
Overview |
The instructor sends the
lecturer notes to the system so that the students can read it from the
system. The instructor can send the whole semester notes/files to the system
and allow the students browse each note/file after the specific date that
assigns by the instructor for each note/file. |
|
Type |
Optional |
|
Note |
This feature available for
instructor after he/she has logged in to the system. |
|
Typical Course of
Events |
||
Actor Action |
System Response |
|
|
1.
The instructor chooses an option to input notes/files to the system. |
2. The
system read the instructor’s option and ask for the course code. |
|
|
3.
The instructor enter the course code. |
4.
Determine the course code is existed and this course is taught by the
instructor. |
|
|
5.
The instructor inputs the notes or upload file(s) to the system, assigns
date for each notes for students’ browsing enable. |
6. Save
notes / file(s) and date to the system. |
|
|
|
7.
Indicates sending notes success. |
|
|
Alternatif
Courses |
||
Line 4 |
The course code is not
existed in the system or the instructor doesn’t teach at that course.
Indicate error. |
|
|
|
|
|
|
|
|
|
_files/image013.gif)
|
Use Case: Display Class List |
|
|
Actors |
Instructor |
|
Purpose |
To display the specific
class list with the number of current enrollment students and current
students in waiting list. |
|
Overview |
This feature is for the instructor to decide whether he/she
has to open another course section if there are many students in waiting list
for a specific course. The cours that the instructor can display is not
limited although at the time he/she browses the course information, he/she
hasn’t teached that course yet. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
instructor after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The instructor chooses an option to display a course that is offered
for students. |
2. The
system read the instructor’s option and ask for the course code. |
|
3.
The instructor enter the course code. |
4.
Determine the course code is existed. |
|
|
5. The
course id, section, name, students enroll, students in waiting list is
displayed to monitor. |
|
Alternatif
Courses |
|
Line 4 |
The course code is not
existed in the system. Indicate error. |
|
|
|
|
|
|
_files/image014.gif)
|
Use Case: Add Student to Course |
|
|
Actors |
Course Manager |
|
Purpose |
To add student for
enrolling the specific course. |
|
Overview |
This feature is to add the
student by course manager to the specific course. Although the course manager
has this feature, he/she needs a written approval letter from the instructor
and the chair before adding the student to the course. Although the course
section is fulled, the course manager can still adding student to that course
section which means he/she automatically adds the seats availability. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
course manager after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The course manager chooses an option to add a student to a specific
course section. |
2. The
system read the instructor’s option and ask for the course code. |
|
3.
The instructor enter the course section id & student id. |
4.
Determine the course section id & student id are existed in the
system. |
|
|
5.
Displayed the student’s id, name, course name, section # that want to
be added. |
|
|
6. Ask
the course manager confirmation. |
|
7.
Confirm the student to add the course. |
8.
Register the student to the specific course section. |
|
|
9.
Indicates registration success. |
|
Alternatif
Courses |
|
Line 4 |
The course section id or
student id is not existed in the system. Indicate error. |
|
|
|
|
|
|
_files/image015.gif)
|
Use Case: Delete Student from Course |
|
|
Actors |
Course Manager |
|
Purpose |
To drop student from the
specific course. |
|
Overview |
This feature is to delete
the student by course manager to the specific course. Although the course
manager has this feature, he/she needs a written approval letter from the
instructor and the chair before deleting the student from the course. After
the students has been deleted from the course, he/she is no more enrolled in
that course, neither in waiting list. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
course manager after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The course manager chooses an option to remove a student in a specific
course section registration. |
2. The
system read the course manager’s option and ready to invoke the option’s
command. |
|
3.
The course manager inputs target course section id and student id that
want to be removed. |
4.
Determine that the student id and the course section id is existed in
the system. |
|
|
5. Search
and display the student status (enroll/waiting list) in that course section. |
|
|
6. Ask
the course manager deletion confirmation. |
|
7.
The course manager confirms for that student target. |
8. Remove
the student from that course section. |
|
|
9.
Indicates remove success. |
|
Alternatif
Courses |
|
Line 4 |
The course section id or
student id is not existed in the system. Indicate error. |
|
Line 5 |
The student id is not
registered in that course section. Indicate error. |
|
|
|
_files/image016.gif)
|
Use Case: Update Course |
|
|
Actors |
Course Manager |
|
Purpose |
To modify the existing
course. |
|
Overview |
This feature is to change
the class seats offer, course name, change the course instructor’s name,
course title, course hours, course units, course schedule, course sections
and others that related to the existing course. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
course manager after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The course manager chooses an option to modify the class seats
avalability / course name / instructor’s name / course title / course
schedule / course id / course sections. |
2. The
system reads the course manager’s option and ready to invoke the option’s
command. |
|
3.
The course manager inputs the course code that needs to modify. |
4.
Display all the course information and enable the course manager to modify
it. |
|
4.
Modify the course. |
5. Update
the course in the system. |
|
|
6.
Indicates update success. |
|
Alternatif
Courses |
|
Line 4 |
The course code is not
existed in the system. Indicate error. |
|
|
|
|
|
|
_files/image017.gif)
|
Use Case: Delete Course |
|
|
Actors |
Course Manager |
|
Purpose |
To delete the existing
course. |
|
Overview |
This feature is to delete
the existing course. By deleting the course, it means that the course at
specific section has been cancelled and the students that registered at the
course are being dropped from enrollment and waiting list status. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
course manager after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The course manager chooses an option to delete a course. |
2. The
system reads the course manager’s option and ready to invoke the option’s
command. |
|
3.
The course manager inputs the course section id that needs to remove
from the system. |
4.
Display all the course section information. |
|
|
5. Ask
the course manager deletion confirmation. |
|
6.
The course manager confirms for that course section. |
7. Remove
the specific course section from the system. |
|
|
8.
Indicates delation success. |
|
Alternatif
Courses |
|
Line 4 |
The course section code is
not existed in the system. Indicate error. |
|
|
|
|
|
|
_files/image018.gif)
|
Use Case: Add Course |
|
|
Actors |
Course Manager |
|
Purpose |
To add a new course
section. |
|
Overview |
This feature is to add a
new course section. After the new course section has been added, the students
can register to that course section. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
course manager after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The course manager chooses an option to add a new course. |
2. The
system reads the course manager’s option and ready to invoke the option’s
command. |
|
3.
The course manager inputs the course section id that needs to be added
to the system. |
4. Determine
that the course section id is not existed in the system. |
|
5.
The course manager inputs the instructor’s name, class capacity,
course course schedule, course units. |
6. Ask
the course manager adding confirmation. |
|
7.
The course manager confirms for adding that course section. |
8. Adding
the course section and the information to the system. |
|
|
9.
Indicates adding course section success. |
|
Alternatif
Courses |
|
Line 4 |
The course section id is
already existed in the system. Indicate error. |
|
|
|
|
|
|
_files/image019.gif)
_files/image020.gif)
|
Use Case: Display Course Info |
|
|
Actors |
Student |
|
Purpose |
To display the specific
course info. |
|
Overview |
This feature is for the student to display course info. There
are different types of course info that the student can choose. There are
options for displaying all courses for specific semester, displaying all
courses that only have seat(s) available for a specific semester, displaying
a course containing its sections information for a specific semester. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
student after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The student chooses an option to display a course that is offered for
students. |
2. The
system read the student’s option and ask the student what kind of choices
he/she need to display. |
|
3.
The instructor chooses an option provided on the screen to displaying
all courses for specific semester / displaying all courses that only have
seat(s) available for a specific semester / displaying a course containing
its sections information for a specific semester |
4.
Display the course(s) information according to the student’s option. |
|
Alternatif
Courses |
|
Line 4 |
The courses is not being
provided yet. Indicate error. |
|
|
|
|
|
|
_files/image021.gif)
|
Use Case: Display Grades |
|
|
Actors |
Student |
|
Purpose |
To display the student
grades that he/she has earned. |
|
Overview |
This feature is for the student to display all the courses
he/she has followed and display all the grades that he/she has achieved. The
student has options whether he/she wants to display his/her grades for
specific semester or display all the entire grades for all semester that
he/she followed. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
student after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The student chooses display grades option from the menu. |
2. The
system read the student’s option and ask the student what kind of choices he/she
need to display. |
|
3.
The student chooses an option provided on the screen to display all
grades for specific semester or to display all grades for the semester he/she
followed. |
4.
Display the grades information according to the student’s option. |
|
Alternatif
Courses |
|
Line 4 |
The grades are not provided yet in the system.
Indicate error. |
|
|
|
|
|
|
_files/image022.gif)
|
Use Case: Enroll Course |
|
|
Actors |
Student |
|
Purpose |
To register to a specific
course section. |
|
Overview |
This feature is for the student to register specific course
section online from the TRACS system. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
student after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The student chooses enroll a course option from the menu. |
2. The
system read the student’s option and ask the student to enter the course
section id. |
|
3.
The student input the course section id. |
4.
Display the course name, course units, instructor’s name, schedule,
and available seats. |
|
|
5. Ask
the student confirmation to enroll this course. |
|
6.
Confirms enrollment for the course section. |
7. The
student has been registered to the course section. |
|
|
8.
Indicates enrollment success. |
|
Alternatif
Courses |
|
Line 4 |
The course code id is not
provided in the system. Indicate error. |
|
Line 4 |
If the course section is
fulled, Line 5,6,7,8 are omitted. Displays message and suggests the student
to reserve course on waiting list. |
|
|
|
_files/image023.gif)
|
Use Case: Drop Course |
|
|
Actors |
Student |
|
Purpose |
To drop a specific course
section. |
|
Overview |
This feature is for the student to drop course section online
from the TRACS system. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
student after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The student chooses drop a course option from the menu. |
2. The
system reads the student’s option and asks the student to enter the course
section id. |
|
3.
The student input the course section id. |
4.
Display the course name, course units, instructor’s name, schedule. |
|
|
5. Ask
the student confirmation to drop this course. |
|
6.
Confirms dropping for the course section. |
7. Drops
the student from the course section. |
|
|
8. Check
the first existing waiting list student. |
|
|
9. If
there are student on waiting list, move the first waiting list student to
enroll the course section. |
|
|
10.
Indicates dropping success. |
|
Alternatif
Courses |
|
Line 4 |
The course code id is not
provided in the system. Indicate error. |
|
Line 4 |
If the student is not
registered in the course section. Indicate error. |
|
|
|
_files/image024.gif)
|
Use Case: Add to Waiting List |
|
|
Actors |
Student |
|
Purpose |
To add the student id on
waiting list for a specific course section.
|
|
Overview |
This feature is for the student to add his/her student id to
specific course section on waiting list.
If there is student drops the course section, then the first student
on waiting list will get enrollment. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
student after he/she has logged in to the system. The student who get
enrollment from waiting list is not able to drop the course section. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1. The student chooses add to waiting list option from the menu. |
2. The
system reads the student’s option and asks the student to enter the course
section id. |
|
3.
The student input the course section id. |
4.
Determines that the course section is fulled and the student is not
registered to the course section enrollment and waiting list. |
|
|
5.
Display the course name, course units, instructor’s name, schedule,
and the waiting list position. |
|
|
6. Ask
the student confirmation to add on waiting list for this course section. |
|
7.
Confirms waiting list registration for the course section. |
8. The
student has been registered to waiting list for the course section. |
|
|
9.
Indicates waiting list registration success. |
|
Alternatif
Courses |
|
Line 4 |
The course code id is not
provided in the system. Indicate error. |
|
|
|
|
|
|
_files/image025.gif)
|
Use Case: Drop From Waiting List |
|
|
Actors |
Student |
|
Purpose |
To drop the student id
from waiting list for a specific course section. |
|
Overview |
This feature is for the student to drop his/her student id
from specific course section on waiting list. After the student has done it, he/she is no more on the waiting
list line. If he/she want to add to waiting list again, his/her status will
be at the end of the waiting list. |
|
Type |
Primary and essential. |
|
Note |
This feature available for
student after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The student chooses drop from waiting list option from the menu. |
2. The system
reads the student’s option and asks the student to enter the course section
id. |
|
3.
The student input the course section id. |
4.
Display the course name, course units, instructor’s name, schedule,
student’s position on waiting list. |
|
|
5. Ask the
student confirmation to drop this course section from waiting list. |
|
6.
Confirms dropping for the course section from waiting list. |
7. Drops
the student from the course section waiting list. |
|
|
8.
Indicates dropping success. |
|
Alternatif
Courses |
|
Line 4 |
The course code id is not
provided in the system. Indicate error. |
|
Line 4 |
If the student is not
registered in the course section waiting list. Indicate error. |
|
|
|
_files/image026.gif)
|
Use Case: Taking Quizze |
|
|
Actors |
Student |
|
Purpose |
To take the quizze online
for a specific course section. |
|
Overview |
This feature is for the student to take the quizze online. The
quizze has due date and time. The student must do this quizze in a limited
time period. |
|
Type |
Optional. |
|
Note |
This feature available for
student after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The student chooses taking quizze list option from the menu. |
2. The
system reads the student’s option and asks the student to enter the course
section id. |
|
3.
The student input the course section id. |
4.
Display the course name, instructor’s name, deadline to take the
quizze time period for taking the quizze. |
|
|
5. Ask
the student confirmation to start the quizze. |
|
6.
Confirms taking the quizze now. |
7.
Displays the quizze’s question and starts the timer. |
|
7.
Starts doing the quizze’s problems and clicks save button for each
question. |
8. Save
each answer. |
|
9.
Click finished after doing all the problems. |
|
|
|
10. If
the time period for the quizze is over, terminate the quizze. |
|
|
11.
Generates the quizze’s score. |
|
|
12. Display
the score. |
|
Alternatif
Courses |
|
Line 4 |
The course code id is not
provided in the system. Indicate error. |
|
Line 4 |
If the student is not
registered in the course section, indicate error. |
|
Line 4 |
If no quizze available,
indicate error. |
|
|
|
|
|
|
_files/image027.gif)
|
Use Case: Sending Assignment |
|
|
Actors |
Student |
|
Purpose |
To take the quizze online
for a specific course section. |
|
Overview |
This feature is for the student to read the assignment notes.
If the instructor requires assignment must be done or sent to the system,
then the student must done the assignment online or upload his/her work in
file(s) to the system. |
|
Type |
Optional. |
|
Note |
This feature available for
student after he/she has logged in to the system. |
|
Typical Course of
Events |
|
Actor Action |
System Response |
|
1.
The student chooses sending assignment option from the menu. |
2. The
system reads the student’s option and asks the student to enter the course
section id. |
|
3.
The student input the course section id. |
4.
Display the course name, instructor’s name, deadline to take the
assignment for taking the quizze. |
|
|
5.
Display the assignment notes. |
|
6.
Do the assignment online (if required by the instructor) or upload the
work to the system (if required). |
7. Save
the student’s work to the system (if required by the instructor). |
|
|
8.
Display assignment has been succeed saving in the system. |
|
Alternatif
Courses |
|
Line 4 |
The course code id is not
provided in the system. Indicate error. |
|
Line 4 |
If the student is not
registered in the course section, indicate error. |
|
Line 4 |
If no assignment
available, indicate error. |
|
|
|
|
|
|
File:C:\My
Documents\211\HawardNewTracs.mdl Class Diagram:Logical View
Narrative explanations which
justify any uses of inheritance, aggregation and association
The
InstructorGUI, RegistrationGUI, ClassListGUI, EnterGradeGUI, ReguestGradeGUI,
CourseGUI, StudentGUI, AdmissionGUI are inherited from GeneralGUI class.
The
InstructorGUI has an association relation 1-1 with InstructorManager class, the
RegistrationGUI has an association relation 1-1 with RegistrationManager class,
the ClassListGUI has an association relation 1-1 with ClassListManager class,
the EnterGradeGUI has an association relation 1-1 with EnterGradeManager class,
the RequestGradeGUI has an association relation 1-1 with RequestGradeManager
class, the CourseGUI has an association relation 1-1 with CourseManager class,
the StudentGUI has an association relation 1-1 with StudentManager class, the
AdmissionGUI has an association relation 1-1 with AdmissionManager class.
The InstructorManager class has an association relation 1-n with InstructorRecord class, the RegistrationManager class, ClassListManager class, EnterGradeManager class, RequestGradeManager class, CourseManager class have an association relation 1-n with Course class, the AdmissionManager class has an association relation 1-n with Student Record.
The
CourseSection class has an association with StudentRecord class while the
StudentRecord class is inherit from StudentManager class (CourseSection is registered by the students, and
CourseSection has waitinglist students data) . The StudentRecord
class has an association 1-n with Assignment class (Student does the Assignment). The assignment
class, InstructorNote class and Quizze class are the aggregation from the
CourseSection class. The Quizze class and Assignment class has an association
relation 1-n with the Grade Class. (for inserting
the quizze and assignment grade purposes).
CLASS
DESCRIPTION
This
class is for login and display purpose. It identifies the users and displays
all the necessary general information about the course and other related
matters. It display important announcements.
This
class is inherited from GeneralGUI class. This class has feature to display
forms that deal with the InstrutorManager class to submit request about the
instructor records.
This
class is inherited from GeneralGUI class. This class has features to display
options and forms that deal with the RegistrationManager class to submit
request about the new Course that the university is going to open.
This
class is inherited from GeneralGUI class. This class has feature to display
forms that deal with CourseListManager class to submit request about the
course’ classes.
This
class is inherited from GeneralGUI class. This class has feature to submit
request that deal with RequestGradeManager class to input the students’ grades by the instructor.
This
class is inherited from GeneralGUI class. This class has feature to submit
request that deal with RequestGradeManager for getting the overall students’
grades and GPA.
This
class is inherited from GeneralGUI class. This class has features to submit
request and display information that deal with the CourseManager class
regarding the courses status.
This
class is inherited from GeneralGUI class. This class has feature to display
forms that deal with the StudentManager class to submit request about the
student records.
This
class is inherited from GeneralGUI class. This class has feature to display
form that deal with the AdmissionManager class regarding the courses that the
students currently registered and dropped.
This
class is to set and get Instructor’s name, ID, Social Security Number, Address,
Phone, Course that he/she can teach.
This
class is to register a new Course that hasn’t been teached before.
This
class is to get all the classes information about the courses.
This
class is to input the students’ grades by the instructor.
This
class is to get the students’ grades for courses they took and printout the
GPA.
This
class is to add new session, update course session, delete course session, add
enroll student from the course, delete enroll student from the course, and also
delete the student from the waiting list of a course.
This
class is to set and get student’s name, ID, Social Security Number, Address,
and Phone.
This
class is for the billing system to know information about the students
enrollments and the latest students’ dropping courses.
This
class has important features that it can display information about the number
students enroll for the specific course, check which courses are fulled, get
the waiting list students, get information about the current instructors teach
this course, set and get the instructors’ notes, set and get instructors’
assignments, set and get instrocturs’ quizze and get information about the
total section is currently available.
This
is the component class from the parent course class. This class contains
individual information about the course section. This class can give features
of the current registered students, know the class status (full / not full),
get the waiting list student, know the instructor id and name, set and get instructor notes, set and get
instructor assignments, set and get quizze.
This
class is inherited from StudentManager class. In this class, it has more
features about the students’ status in enrolling the course. It gives the
students feature to drop the course, get the courses information that the
students took before, get the courses grades, add and drop the waiting list of
specific course(s).
This
class si to get and set quizzes’ grades. It also get and set instructors’
assignments’ grades.
This
is another class which special for CourseSection class in providing the
instructors’ names and IDs.
SCENARIOS
Display Grade:
Successfully display student
grade by the student himself/herself.
_files/image030.gif)
Course
Code : CSCI-211
Section : 01
Instructor : Dr. Melody
Stapleton
Schedule : MW 2:00-4:00
Student
: Haward Jie
Student
ID : 12345
Assignment
Grade : A
_files/image032.gif)
_files/image034.gif)
SCENARIOS
Enroll Course:
Successfully enrolls a course
by the student.
_files/image035.gif)
Course
Code : CSCI-211
Section : 01
Instructor : Dr. Melody
Stapleton
Schedule : MW 2:00-4:00
Student
: Haward Jie
Student
ID : 12345
Succeed
in registering this course.
_files/image037.gif)
_files/image039.gif)
SCENARIOS
Display Class List: Successfully the class list
information has been displayed to the instructor.
_files/image040.gif)
Course
Code : CSCI-211
Section : 01
Instructor : Dr. Melody
Stapleton
Schedule : MW 2:00-4:00
Student
enroll :
|
Student ID# |
Student Name |
|
12345 |
Haward Jie |
|
12346 |
Saddam Husein |
|
12347 |
Micheal Jackson |
|
12348 |
Monica Lewensky |
Student
in waiting list :
|
Student ID# |
Student Name |
|
12302 |
Ben Johnson |
|
12326 |
Magic Jordan |
|
12337 |
Micheal Harbour |
|
12349 |
Monica Haha |
_files/image042.gif)
_files/image044.gif)
SCENARIOS
Summit Grade:
Successfully summits student
assignment grade by the instructor.
_files/image045.gif)
Course
Code : CSCI-211
Section : 01
Instructor : Dr. Melody
Stapleton
Schedule : MW 2:00-4:00
Student
: Haward Jie
Student
ID : 12345
Assignment
Score : 0.9
Grade : A
has
been successfully in summiting
assignment
grade.
_files/image047.gif)
_files/image049.gif)