"TEST Plan" for real project using "test plan template", "documenation" and "Project Deliverable".

I D:

Level-0

Level-0:

System Administrator Registration 

Description:

The System Administrator (SA) will have access to register the student data along with the program information. System Administrator will register all require student information to the system. Each student will have their unique identifier.

Priority:

High

Trigger:

 Students require to register their information for enrollment.

Primary Actor:

System Administrator 

Preconditions:

Student enrollment

Normal Course:

System Administrator will enter student’s basic information

Alternative Course:

 Hard paper or hand-written form base registration

Admin can also take students fingerprint for unique identification.

Postconditions:

Student record management 

Main Success Scenario:

System Administrator should be able to login and view all student information.

System Administrator can register any new student to the system.

System Administrator can update/delete any student program information. 

Exceptions:

 Unavailability of student, student data or hardware failure

Summary Input

Source

Output

Destination

SA Id

List of Student Ids

Date Range

Course/Program Id

Student registration

Student

Student data

Program Data

System admin

ID:

Level-1

Level 1.1:

Student Record Management

Description:

The System Administrator (SA) will have the authority of student management. It means that The System Administrator (SA) can add new student record, edit existing student record, and delete student record.

Having admin authority to manage records means admin can easily handle student information and can perform add, edit and delete operation on student data. The System Administrator (SA) also have the authority to search student’s enrollment history.

Maintaining latest student information is very important for any institute. This student record management allow admin to achieve this task easily.

Priority:

Medium

Trigger:

Enrollment of new student – add

Modify or correct existing student info – edit

Student left institution - delete

Search student enrollment - search

Primary Actor:

System admin

Preconditions:

Student enrollment, student data management

Normal Course:

· New student enrollment – add student information

· Existing student – edit or correct existing student information

· Discontinue student – delete student data

· Search Student enrollment – search student information

Alternative Course:

· Handle student information in hard paper (in hard pages record book)

Postconditions:

Updated student information available in system 

Exceptions:

 Unavailability of student, student data or hardware failure

Main Success Scenario:

When all student’s information is available, system can easily search, add, edit or delete student information.

Summary Input

Source

Output

Destination

Student registration 

Student Ids

Course/Program Ids

Student

Student data

System admin

ID:

Level-2

Level 2.1:

Program Record Management

Description:

The System Administrator (SA) will have the authority of Program management. It means that The System Administrator (SA) can add new Program information, edit existing Program record, and delete existing Program record. Having admin authority to manage records means admin can easily handle Program details and can perform add, edit and delete operation on Programs information.

Priority:

Medium

Trigger:

 Require adding new Program info – add

Modify or correct existing Program info – edit

Finish of curriculum - delete

Actor:

System Administrator

Preconditions:

Programs information and curriculum details

The System Administrator (SA) identity is authenticated.

The SA has necessary training and credentials on file.

The system can send and receive emails

The system can send and receive alert messages

The SA can view and update the communication method.

The system datastore is up-to-date and on-line.

Normal Course:

Create new Program to meet curriculum

Edit or modify existing Program details

Delete existing Program once curriculum or academic year has been over

Alternative Course:

Handle Program information in hard paper (in hard pages record book)

Postconditions:

Updated Program information available in system

Exceptions:

Unavailability of Program data or curriculum or hardware failure

Main Success Scenario:

Once academic year starts and curriculum available, admin can add Program according to curriculum requirement.

If it requires to adjust existing Program, admin do have control to perform edit operation as well.

In case of finish subject or curriculum, admin can delete all Programs associate with that subject as well.

Summary: Inputs

Source

Output

Destination

Course/Program Id

SA ID

System admin

Program details data

System Administrator (SA)

ID:

Level-3

Level 3.1:

Communication Management

Description:

The system will be able to integrate and work with other services like alert messages and Email regarding students’ enrollment. The System Administrator (SA) only has the authority to access/ manage communication method.

Priority:

Medium

Trigger:

Requires sending student enrollment information via Email and alert message.

Actor:

System Administrator

Preconditions:

The System Administrator (SA) identity is authenticated.

The SA has necessary training and credentials on file.

The system can send and receive emails

The system can send and receive alert messages

The SA can view and update the communication method.

The system datastore is up-to-date and on-line.

Normal Course:

System will send alert message and email for Student new enrollment to SA.

System will send alert messages and email for enrollment to SA.

The SA can view all communication page/method

Alternative Course:

The student enrollment is very low. But the student submitted sick certificate manually to professor.

The email server is down.

Postconditions:

The system stores all email and alert communication in the database.

The student enrollment is updated and maintain real-time in database.

The student enrollment notification/alert sent to student and SA.

The student enrollment update/modification alert sent to student and SA.

Exceptions:

The system displays message “The enrollment is too low. Please contact professor or principal office.”

The email server is down and system unable to send the email message to student.

System displays alert notification to student for upcoming change in schedule for the course.

The system terminates the use case

Summary: Inputs

Source

Output

Destination

· Enrollment Id

· List of Student Ids

· Email Id

· Course/Program Id

· Application

· Application datastore

· Email

· Alert message

· Student

· Enrollment report

· System Administrator (SA)

· Student

ID:

Level-4

Level 4:

Report Management

Description:

The system will be able to generate an enrollment report on the weekly, monthly and yearly basis of entry/exit entries. The system admin has the authority to generate reports according to the requirements and print the reports.

Priority:

Medium

Trigger:

Requires generate and print enrollment report

System Admin

Actor:

System Administrator

Preconditions:

The System Administrator (SA) identity is authenticated.

The SA has necessary training and credentials on file.

The system can generate enrollment reports

The system can print enrollment reports

The SA can view and update the enrollment report.

The system datastore is up-to-date and on-line.

Normal Course:

System can send weekly, monthly and yearly enrollment report for Student(s).

System can print weekly, monthly and yearly enrollment report for Student(s).

System can retrieve and print report for selected date range.

Alternative Course:

The professor requested student enrollment for specific date range.

Postconditions:

The system stores all student enrollment in the database.

The student enrollment is updated and maintain real-time in database.

Exceptions:

The system displays message “The printer is offline. Please save your report.”

The database is down due to maintenance. System displays “Schedule maintenance message”

The system terminates the use case

Summary: Inputs

Source

Output

Destination

SA ID

Enrollment Id

List of Student Ids

Date Range

Course/Program Id

Application

Application datastore

Student Enrollment report

System Administrator (SA)

Student