USE CASES

 

Case I a: Registering for Annual Competition

 

Description:

This use case will be used by the school coordinator to register students for the annual competition.

 

Actor: 

School Coordinator

 

Pre-Conditions:

The School Coordinator should be signed in to the system.

 

Post-Conditions:

The Registration information has been submitted.

 

Flow Of Events:

1) The School Coordinator will click the “REGISTER FOR ANNUAL COMPETITION” option.

2) The School Coordinator will be shown a screen (or) page where he/she will fill in the individual student information.

3) If the School Coordinator wants to register more students for the annual competition, he/she will click the “ADD MORE STUDENTS” option.

4) After entering the information for all students the School Coordinator will click the “VIEW SUMMARY AND SUBMIT” option.

5) A summary will be shown about the student information that has been entered by the school coordinator with student names as hyperlinks and a “DELETE” option.

Finally the School Coordinator will click the “SUBMIT TO MECSP” button to actually submit the whole information that has been entered about each student to the MECSP registration database.

 

Error: The user cannot submit the form without selecting at least one of the events for each student. An error message will be popped up in the screen.

 

 

Case Ib: Registering for workshop

 

Description:

This use case will be used by the school co-coordinator to register for the workshop.

 

Actor: 

School Coordinator

 

Pre-Conditions:

The School Coordinator should be signed in to the system.

 

Post-Conditions:

The workshop Registration information has been submitted.

 

Flow Of Events:

1) The School Coordinator will click the “REGISTER FOR WOSKSHOP” option.

2) A page opens up with the list of workshops conducted for that year as hyperlinks. The School Coordinator will select a workshop by clicking on it.

3) The School Coordinator will be shown a screen (or) page where he/she can select      

      “YES” if they want to participate in that particular workshop and then enter the  number of students participating in that workshop.     

4) After entering the information for the workshop, School Coordinator will click either the “VIEW SUMMARY” option; it allows the School Coordinator to see the information he/she has filled in (or) “REGISTER FOR MORE WORKSHOPS” option, which will take the School Coordinator to the page where the list of workshops will be displayed with hyperlinks.

5) The SUMMARY page opens up with the details entered by the School Coordinator for various workshops with the “SUBMIT TO MECSP” option.

6) The School Coordinator will click the “SUBMIT TO MECSP” option to finally submit the information into the MECSP database.

 

 

Case Ic-1: Modifying registration Information with respect to workshop

 

Description:

This use case will be used by the School Coordinator to modify the registered information about the workshop.

 

Actor: 

School Coordinator

 

Pre-Conditions:

The School Coordinator should be signed in to the system.

 

Post-Conditions:

The workshop registration modified information has been submitted.

 

Flow Of Events:

1) The School Coordinator will click the “MODIFY/UPDATE WORKSHOP” option.

2) A page opens up with the workshop names as hyperlinks. The school Coordinator will click the name of the workshop to view the details filled for that particular workshop.

3) The school coordinator will make necessary changes and click the “VIEW SUMMARY” option.

4) The “SUMMARY” page opens up with the information filled in by the School Coordinator for all workshops.

5) The School Coordinator will click the “SUBMIT TO MECSP” option to save the modified information in to the MECSP registration database.

 

 

Case Ic-2: Modifying registration Information with respect to annual competition registration

 

Description:

The school coordinator to modify the registered information about the students participating in the annual competition will use this use case.

 

Actor: 

School Coordinator

 

Pre-Conditions:

The School Coordinator should be logged into the system.

 

Post-Conditions:

The annual competition modified information has been submitted.

 

Flow Of Events:

1) The School Coordinator will click the “MODIFY/UPDATE ANNUAL COMPETITION” option

2) The School Coordinator will be shown a SUMMARY PAGE with student names and the events they are participating in.

3) The School Coordinator will either click on the student name, so that a page opens up with all the Information filled up by the school coordinator about that particular student 

      (Or)

The School Coordinator will select multiple students by clicking the check box provided for each student and then click the “DELETE” button.

4) The School Coordinator will change the information filled about that particular student and then will click the “VIEW SUMMARY” option.

5) Finally the School Coordinator will click the “SUBMIT TO MECSP” button in the SUMMARY PAGE to actually submit the modified information into the MECSP registration database.

 

 

Case I d-1: View Workshop Registration Information – school coordinator

 

Description:

This use case allows the school coordinator to view and modify information regarding his/her school’s registration for the Saturday workshops

 

Actor:

School coordinator

 

Pre-conditions:    

The School Coordinator must be logged in and validated

 

Post-conditions:

None.

 

Flow of Events:

1) The school coordinator clicks on the “view and modify workshop registration information” link on her welcome/home page.

2) The Page with the various workshops’ names, in hyperlink will open.

3) The user clicks on a workshop link to view registration information

4) The Page with the details of the schools registration till that point of time opens

This page will have links, which when activated will enable the coordinator to delete, edit, or save the information.

 

Error: The school has not registered so far; the page will have no data and will have a link to add a registration record.

 

 

Case I d-2: View Annual Competition Registration Information – school coordinator

 

Description:

This use case allows the school coordinator to view and modify information regarding his/her school’s registration for the annual competition

 

Actor:

School coordinator

 

Pre-conditions:    

The School Coordinator must be logged in and validated

 

Post-conditions:

None.

 

Flow of Events:

The school coordinator clicks on the “view and modify competition registration information” link on her welcome/home page.

The Page with the details of the schools registration till that point of time opens

This page will have links, which when activated will enable the coordinator to delete, edit, or save the information.

 

Error: The school has not registered so far; the page will have no data and will have a link to add a registration record.

 

 

Case Ie: Send Inquiry to MECSP organizer

 

Description:

This use case will allow school coordinator to send inquiry to MECSP organizer

 

Actor:

School coordinator

 

Pre-conditions:    

School coordinator has signed into the SECME system

 

Post-conditions:

An inquiry message is sent via email to MECSP organizer

 

Flow of Events:

1) The user clicks on ‘Send Inquiry’ link provided on the main page

2) This will lead the user to ‘Send Inquiry’ page. The user will be able to enter his email address, subject and message on this page.

3) The user will click on ‘Send Message’ button to send the message.

4) The system will get the MECSP organizer email address from the system and will send an email to him/her with “MECSP Inquiry:” being appended to the start of the mail subject.

5) The user will be shown a message status (i.e. whether mail send was successful or not) on the next page

 

Error: All information (except school coordinator 2 detail) is a must and must be filled in by the user. In case any of the information is missing user should be informed about it.

 

 

Case II a-b:

Sign into the SECME System

 

Description:

This use case allows the users (both organizers and school coordinator) to log into the system.

 

Actor:

MECSP organizer

School coordinator

 

Pre-conditions:    

None

 

Post-conditions:

The user gets validated and moved to his work area in SECME system.

 

Flow of Events:

1) If the user is a school coordinator and does not already have an account, user invokes ‘Create Account’ use case.

2) The user will enter his/her userid and password. He/She will then click onto ‘Login’ button

3) The system will validate given userid and password.

4) If validated, the system will determine user’s role (MECSP organizer or school coordinator) and then move him to relevant work area.

 

Error: The userid and password are not validated. The user will be displayed an error page and an option to re-enter userid and password.

 

 

Case III a: Definition of Annual Competition

Description:

This use case explains in detailed how the user will define the annual competition

 

Actor:

MECSP user

 

Pre-conditions:

None

 

Post-conditions:

Made changes successfully providing the required information

 

Flow of Events:

1) The user goes to the following site www.mecsp.cecs.ucf.edu

2) Go to: Programs à SECME Regionalà MECSP User

3) The system will bring up a log-in screen

4) After the system validates the user name and password, it will take you to a window with two links: one of them is ‘Annual Competition’.

5) Once the user chooses the event, the system will take the user to the Annual Competition’s page. This page consists of:

- The date and time of the Annual Competition as well as its registration deadline, and a list of events for the competition          

- The user is presented with three options in the mentioned page:

Add Event, Delete Event, and Done

- To Edit an event, the user only needs to click on any of the listed events and edit as he/she wishes

6) Once the user chooses the action and enters new or modifies any information, the ‘Done’ button must be clicked for the new information to be saved. The system automatically will send you back to the main page.

 

 

Case III b: Definition of Workshop

Description:

This use case explains in detailed how the user will define the workshop(s)

 

Actor:

MECSP user

 

Pre-conditions:

None

 

Post-conditions:

Made changes successfully providing the required information

 

Flow of Events:

1) The user goes to the following site www.mecsp.cecs.ucf.edu

2) Go to: Programs à SECME Regionalà MECSP User

3) The system will bring up a log-in screen

4) After the system validates the user name and password, it will take you to a window with two links: one of them is ‘Workshop’.

5) Once the user chooses the event, the system will take the user to the Workshop’s page. This page consists of a list of workshops.

- To edit on a particular workshop, the user will have to click on the desire workshop to be able to make the changes.

- To add a new workshop, the user will have to click on the ‘Add Workshop’; the system will prompt the user a window with the following information to be filled:

Title, Date, Time, and Description of the workshop

6) Once the user chooses the action of adding or making changes on the desire event, the ‘Done’ button needs to be clicked in order for the user to be sent back to the main page.

 

 

Case III c, d, e, f: View School’s Registration Information – MECSP Organizer

 

Description:

This use case allows the MECSP Organizer to view information regarding the school’s registration for the Annual Competitions

 

Actor:

MECSP Organizer

 

Pre-conditions:    

The MECSP Organizer must be logged in and validated

 

Post-conditions:

None.

 

Flow of Events:

1) The MECSP Organizer clicks on the “view records” link on her welcome/home page.

2) The Page with options to “view workshop registration information” and “view competition registration   information”, in hyperlink will open.

3) The user clicks on the  “view competition registration information” link.

4) The Page with 4 choices of data format, viz, “view full summary”(use case III c), “view summary by math level” (use case III d),    “view summary by school type” (use case III e), “view summary by competition” (use case III f).

Each of these links, when activated will display the required summary.

 

 

Case III g: Notification to school coordinators about changes/developments in events

Description:

This use case explains in detailed how the user will notify to school coordinators about any changes and/or developments made in any event(s)

 

Actor:

MECSP user

 

Pre-conditions:

Successful change in an event

 

Post-conditions:

Notify successfully to school coordinators about any changes made in the events

 

Flow of Events:

1) Once the user has completed any changes on the competition or workshop, he will be sent to the main page right after clicking on the ‘Done’ button.

2) A ‘Send Inquiry’ link is provided on the main page to help the user communicate the school coordinators of such change(s).

3) This will lead the user to ‘Send Inquiry’ page. The user will be able to enter his email address, subject and message on this page.

4) The user will click on ‘Send Message’ button to send the message.

5) The system will get the MECSP organizer email address from the system and will send an email to him/her with “MECSP Inquiry:” being appended to the start of the mail subject.

6) The user will be shown a message status (i.e. whether mail send was successful or not) on the next page.

 

 

XXXXXXXXXXXXXXXXXX

Create Account

 

Description:

This use case allows the school coordinator to create an account into SECME system.

 

Actor:

School coordinator

 

Pre-conditions:    

None

 

Post-conditions:

User is sent his userid and password at given email address.

 

Flow of Events:

The user is provided with a form to fill in information about

School name, type, phone no, fax no

School coordinator 1, first, middle, last name and email address

School coordinator 2, first, middle, last name and email address

 

The user will press ‘Create Account’ button to submit the information. User will be informed that his userid and password will be sent via email at school coordinator 1-2 email addresses.

 

Error: All information (except school coordinator 2 related information) is a must and must be filled in by the user. In case any of the information is missing user should be informed about it.