Functional requirements R.1 Coordinator R.1.

1 Registration Description: This function facilitates the faculty coordinator to be the part of the system and allows only authenticated information to be displayed on the portal and has access to the entire data associated. Precondition: Coordinator must be a faculty. Input: Output: Your account is successfully registered. And notification has been sent to your email. Processing: After submission of details, system will create coordinators account and status will be changed to coordinator. And notification will be sent to coordinator via email. Scenario1: Main line sequence 1. Coordinator: select admin registration option 2. System: displays the registration details 3. Coordinator: fills the details and select submit option 4. System: accept the details and send the message Scenario2: at step-4 of main line sequence 4a. display the message Coordinator already exist. R.1.2 Login: Description: This function facilitates the coordinator to login to their profile. In login coordinator has to enter the user-id and password, if the id and password are authorized then they can access the data otherwise respective message will be displayed. Precondition: Coordinator must be registered. Input: User-id (30, alpha numeric, unique) Output: Coordinator profile will be displayed. Processing: As the user enter the id and password, system will check the authorization, if the user is valid system will display the account otherwise prompt the respective message. Scenario1: Main line sequence 1. Coordinator: enter user-id and password. 2. System: check for correct user-id and password Scenario2: at step-2 of main line sequence 2a. User-id or password does not match. Password ((minimum 8), alphanumeric)

First Name (string, max char length 15,enter, mandatory ) Last Name (string, max char length 15, enter, mandatory) User-id (max char length 20, alphanumeric , mandatory ,unique, select ) Gender (10, string, mandatory, select) D.O.B (15, Date-time, mandatory, select) Phone number(numeric, max length 10,enter, mandatory) Email id (alphanumeric, unique, special symbols(@,dot,_,-), enter) password(alphanumeric, special symbols(@,dot,_,-), enter, mandatory) re-type password

R.1.3 View coordinator profile Description: This function facilitates the coordinator to view their profile. This function displays the details of the coordinator of CSI portal. Output: First name Last name Email-id Date of birth

R.1.4 Edit coordinator profile Description: Edit coordinator profile function helps to edit/modify the details of the coordinator of CSI portal. Input: Output: Message The Changes are made and information is recorded successfully. and notification has been sent to your email id. R.1.5: Logout:

First name (20, String, Mandatory, Enter) Last name (20, String, Mandatory, Enter) E-mail (50, Character( ., -, _, @, $), Unique) Password(alphanumeric, special symbols(@,dot,_,-), enter) Retype Password

Description: This function helps the coordinator to temporary close the activation of his/her account. After login the profile one can opt that.

Precondition: Coordinator must be logged in. Input: Selects the logout option. Output: Display message logout successfully and display the home page. Processing: As coordinator selects the logout option, the display should transfer to the home page of CSI portal and his/her account should be closed temporary. Scenario 1: Mainline sequence 1. 2. R.1.6 Add events: Description: This function facilitates coordinator to add events to the CSI portal. Precondition: The applicant should be authorized user. Input: Coordinator: Selects the logout option. System: logged out and display the home screen.

Name of event(20,string,mandatory,enter) Description of event(120,string,mandatory,enter) Name of faculty coordinator(20,string,mandatory,select) Name of student coordinator(20,string,mandatory,enter) Date of event(date,mandatory,select) Day of event(10,string,select) Venue(20,string,mandatory,enter) Timing of event(Start-end)(time, enter) Fee(if any)(5,numeric,enter) Criteria(if any)(20,string,enter) Contact details(10,numeric,enter)

Output: Message-Your Event is successfully uploaded. Processing: Event details will be saved in database. And these events will be visible to the members of CSI portal as well as the visitors. Scenario1: Main line sequence 1. 2. 3. 4. Coordinator: Selects Add event option. System: Displays the Add event details. Coordinator: Fills the details & selects upload option. System: Accepts the details and stores it.

Scenario2: At step 4 of main line sequence. 4a. Date of event is already passed.

R.1.7 Edit event: Description: This feature enables the coordinator to edit/modify events of the CSI portal. Precondition: The coordinator should be authorized user i.e. the coordinator who added the event can only modify it. Event should exist. Input: Output: Message-Your Event is successfully updated. Processing: Check for pre-condition validity. Changes made will be reflected in database. Scenario1: Main line sequence 1. Coordinator: Selects Edit event option. 2. System: Displays the Edit event details. 3. Coordinator Modify the details & selects upload option. 4. System: Accepts the details and stores it. Scenario2: At step 4 of main line sequence R.1.8 view event: Description: This feature enables the User to view the details of the CSI events. Precondition: Event should exist. . Input: Visitors/Members/Coordinator: clicks on view event option. Output: Name of event Description of event Name of faculty coordinator

Description of event(120,string,mandatory,enter) Name of faculty coordinator(20,string,mandatory,select) Name of student coordinator(20,string,mandatory,enter) Date of event(date,mandatory,select) Day of event(10,string,select) Venue(20,string,mandatory,enter) Timing of event(Start-end)(time, enter) Fee(if any)(5,numeric,enter) Criteria(if any)(20,string,enter) Add more fields Contact details(10,numeric,enter)

Name of student coordinator Date of event Day of event Venue Timing of event(Start-end) Fee(if any) Criteria(if any) Contact details

Processing: Check for pre-condition validity (Event should exist). Scenario1: Main line sequence 1. Coordinator: Selects View event option. 2. System: Displays the View event contents

R.1.9 Add Technical updates: Description: This function will facilitate the coordinator to add technical updates which will be displayed to the home page as well as on the users profile. Precondition: The coordinator should be logged in. Input: Output: Message Technical updates successfully uploaded. Processing: Coordinator will give the details of technical updates. Title will be saved in the database. R.1.10 Edit technical updates: Description: This function facilitates the coordinator to edit/modify technical updates. Precondition: The coordinator should be logged in. Input: Title (20, Alphanumeric, Enter) Output: Message Technical updates successfully modified/edited. Processing: Coordinator will modify the details of technical updates and the modified/edited details will be saved in the database.

Title (20, Alphanumeric, Enter)

R.1.10 Calculate Funds: Description: This function facilitates the coordinator to calculate the funds collected for a particular event or for all events. Precondition: Coordinator must be logged in. Output: Calculated fund will be displayed. Processing: System will calculate the sum of all collected funds stored in database.

R.2 USER R.2.1 Registration: Description: This feature facilitates the user to register in CSI portal. Input: Output: Message Your registration has been successfully done Processing: Records will be submitted and saved in a database and student will be registered to the CSI portal. Notifications will be sent via emails. Scenario1: Main line sequence 1. User: Select student registration option. 2. System: Display the registration details 3. User: fills the details and select the submit option. 4. System: Accept the details and send the message. Scenario2: At step 4 of the main line sequence 4a. Display message enrolment number already exists. R.2.2 Login: Description: Log in is the function by which user can visit into their profile and can take participation in the forum. In log in user has to enter the user-id and password, if the id and password are authorized then they can access the data otherwise respective message will be displayed. First Name (string, max char length 15,enter, mandatory ) Last Name (string, max char length 15, enter, mandatory) Enrolment no (max char length 20, alphanumeric , mandatory ,unique, select ) Gender (10, string, mandatory, select) D.O.B (15, Date-time, mandatory, select) Branch (50,string, mandatory, select) Semester (10, numeric, mandatory, select) Phone number(numeric, max length 10,enter, mandatory) Email id (alphanumeric, unique, special symbols(@,dot,_,-), enter) password(alphanumeric, min length) re-type password

Pre-condition: User should be registered. Input: User-id (30, alpha numeric, unique) Password ((minimum 8), alphanumeric)

Output: Users profile displayed. Processing: As the user enter the id and password, system will check the authorization if the user is valid it displays the account otherwise prompt the respective message . Scenario 1: Mainline sequence 1. User: Selects login option. 2. System: Display login form.

3. User: Enter user-id and password and submit the form. 4. System: Checks authorization and open the account. Scenario 2: At step 4 of the mainline sequence. 4a. System: Displays the message Invalid user-id or password.

R.2.3 View Student Profile:

Description: View student profile function displays details of the students who are a part of CSI Society. Output: Enrollment no. First name Last name E-mail Date of Birth

Gender Branch Semester Phone number

Processing: Coordinator: The information is viewed and managed by them. Student: The information is viewed and managed by them.

Scenario1: Mainline Sequence. 1. 2. Student: Views the details of the students. System: Displays the details.

R.2.4 Edit Student Profile. Description: Edit student profile function will allow changes in the students profile who are a part of CSI portal. Input:

E-mail (50, Character (. -, _, @, $), Mandatory, Unique, Select) Semester (10, numeric, mandatory, select) Phone number (numeric, max length 10, enter, mandatory) Password (alphanumeric, min length) Re-type password (alphanumeric, min length)

Processing: Record is viewed by: Coordinator: The information is viewed and managed by them. Student: The information is viewed and managed by them.

R.2.5 Register for events: Description: This feature facilitates the user to register for the events. Precondition: The user must be logged in to register into the events. Input: Output: Message You are registered for the event. Notification will be sent to you via email. First Name (string, max char length 15,enter, mandatory ) Last Name (string, max char length 15, enter, mandatory) Enrolment no (max char length 20, alphanumeric , mandatory ,unique, select ) Gender (10, string, mandatory, select) D.O.B (15, Date-time, mandatory, select) Branch (50,string, mandatory, select) Semester (10, numeric, mandatory, select) Phone number(numeric, max length 10,enter, mandatory) Email id (alphanumeric, unique, special symbols(@,dot,_,-), enter)

Processing: User will enter the required details to get register for the event. All the user details will be stored in the data base. Further the notifications will be sent to his/her email id. Scenario1: Main line sequence 1. User: fills the details 2. System: System accepts and stores the details in a database. Scenario2: At step-2 of main line sequence 2a. enrolment number already registered. 2b. fill all the given fields.

R.3 Visitor: R.3.1 Register for events:

Description: This function facilitates the visitor to register to the events directly Precondition: Only non-csi members can register here. Input: Output: Message Your are successfully registered for the event. Notification will be sent to you via email. First Name (string, max char length 15,enter, mandatory ) Last Name (string, max char length 15, enter, mandatory) Enrolment no (max char length 20, alphanumeric , mandatory ,unique, select ) Gender (10, string, mandatory, select) D.O.B (15, Date-time, mandatory, select) Branch (50,string, mandatory, select) Semester (10, numeric, mandatory, select) Phone number(numeric, max length 10,enter, mandatory) Email id (alphanumeric, unique, special symbols(@,dot,_,-), enter)

Processing: Visitor will enter the required details to get register for the event. All the details will be stored in the data base. Further the notifications will be sent to his/her email id. Scenario1: Main line sequence 1. Visitor: fills the details 2. System: System accepts and stores the details in a database. Scenario2: At step-2 of main line sequence 2a. enrolment number already registered. 2b. fill all the given fields.