Project Overview and Scope

Transcription

1 Project Overview and Scope MISSION What problem does this project address? Historically, students tend to skip class. This system aids instructors in tracking the attendance of their students. It will give instructors a central location to track the attendance of all of their students in all of their classes. It will eliminate the time spent tracing back through papers. This program will be useful for many years to come. The problem is that instructors do not take roll because it can be time consuming and unorganized. With this system, hopefully instructors will begin taking roll and holding students accountable for attendance. In former ways of taking roll, one student could "cover" for another by signing the roll for him. With the security of this system, that will be eliminated. This will benefit students, instructors, and the university as a whole. What is the goal of this project? This project will produce a program for instructors to track attendance and print reports related to attendance. What are some key features that define the product? This system creates functionality for creating, editing, deleting, searching, categorizing, browsing, tallying, and recording on student's attendance. This automates all attendance operations and ensures that instructors will always have access to reports containing information that is automatically up-to-date. This system will have a user-friendly interface, engineered for the most computer illiterate instructors. The website engine will be secure and only allow instructors with the proper permissions to edit, delete, or browse the database. This will prevent cheating or the submission of false information. This will prevent students from entering false data, also. What makes this product different from others? This system will be more accurate and easily accessible. In the long run it will be cheaper and waste less paper. Less valuable time will be wasted. This system will have much better maintainability, accuracy, manageability and security. This system will not allow for students to sign another student s name.

2 SCOPE What is the scope of this project? We will build this attendance tracking program for instructors and professors inspired by Dr. Shaw s requirements. What are the high-level assumptions or ground rules for the project? We assume that the user takes responsibility for entering the data needed into the database. What are we not going to do? We are not going to enter the data into the database. The user is responsible for entering the courses he or she teaches and the rosters associated with each course. Is this project part of a larger effort? STATUS This project is starting for Dr. Shaw to develop a more advanced attendance tracking system in the future. What is the status of this project? What the system includes is functional. However, there are some navigation issues that need to be implemented in order for the system to be more user friendly. These issues were outside the scope of this project. APPLICABILITY Who should use this product? This product is aimed at teachers, instructors, and professors who wish to easily and efficiently track attendance of students and have easy access to attendance reports.

3 USE CASES PART ONE ACTORS: INSTRUCTOR 1. Register as a new user 2. User identifies his/herself 3. Edit user profile 4. View user profile 5. User adds a class 6. User chooses a class from his/her list of classes 7. User adds a student 8. User takes role 9. User views reports 10. User logs out USES CASES PART TWO UC-01: REGISTER AS A NEW Summary: Users need to register themselves in order to use this web application. Priority: Essential. Goal: To register the user into the database, so that he/she can use the application. Use frequency: Once per user. 1. Visit login page 2. Click to register as new user 3. Enter identifying information: first name, last name, , password, and department 4. Submit form If the address is already in use, the system will give you a message stating the address is already in use, and suggest trying another address. UC-02: IDENTIFIES HIS/HERSELF Summary: Users need to identify themselves to the application/database in order to use the application. Priority: Essential. Goal: To register the user into the database, so that he/she can use the application. Use frequency: Once per use. Prerequisite: User must be registered with the application. 1. Visit login page

4 2. Enter user name 3. Enter correct password 4. Click login button If any field is incorrect or left blank, the system will return a message stating that login failed. UC-03: VIEW PROFILE Summary: Users should be able to view the information stored in their profile. Priority: Non-Essential. Goal: To allow user to view his/her information stored in the database. Use frequency: Rare. Prerequisite: User must be logged into the system. 1. User clicks to view profile 2. The information is displayed on the screen If the user wished to change any of the information, he/she has the option to edit the profile (See UC-04). UC-04: EDIT PROFILE Summary: Users should be able to edit the information stored in their profile. Priority: Non-Essential. Goal: To edit or change the user s information stored in the database. Use frequency: Rare. Prerequisite: User must be logged into the system. 1. User clicks to edit profile 2. User edits the information he/she wishes to change 3. Click to submit 4. System edits the information in the database If the user leaves a portion blank, the system will display a message asking the user to enter the information. UC-05: INSTRUCTOR ADDS A CLASS Summary: Users should be able to add a course in which he/she is teaching in order to take attendance for that class. Priority: Essential. Goal: To add a course so that the instructor can enter students and take attendance. Use frequency: Once for each class the instructor teaches. Prerequisite: User must be logged into the system. 1. User clicks to add a course 2. User enters the required information: department, class, section, and time 3. Click to submit

5 4. System edits the information in the database If the user leaves a field blank, the system will display a message asking him/her to enter the correct information and re-submit the request. If the user enters information for a class that he/she has already registered, the system will not allow the course to be registered twice and inform the user of the duplication. UC-06: INSTRUCTOR CHOOSES A CLASS FROM HIS/HER LIST OF CLASSES Summary: In order to add students and take attendance for the class, the instructor should choose which class he/she would like to edit. Priority: Essential. Goal: To choose which class the instructor is going edit. Use frequency: Often. Prerequisite: User must be logged into the system, and the course must be registered in the database. 1. User clicks to view courses 2. User clicks the course he/she wishes to select If the course is not in the users list of courses, then it is not registered in the database. The user should then click to add a course (See UC-05). UC-07: INSTRUCTOR ADDS A STUDENT Summary: In order to take attendance, the instructor needs the class roster of each class. He will enter each student enrolled in the course into the system, in order to track attendance. Priority: Essential. Goal: To enter information for each student enrolled in each course into the database. Use frequency: Once for each student in each class. Prerequisite: User must be logged into the system, and the course must be registered in the database. 1. User clicks the course he/she wishes to add students to. 2. User clicks to add a student. 3. User enters required student information: first name, last name, and address. 4. User clicks to submit. If the student is already registered in the course, the system will display a message that states that to the user. UC-08: INSTRUCTOR TAKES ROLE Summary: The instructor will use this application to take attendance in class. He/she will mark the students that are present and leave the absent students unmarked. Priority: Essential

6 Goal: To allow instructor to easily take attendance during class and store the information in the database. Use frequency: Once for every day of every class. Prerequisite: User must be logged into the system, the course must be registered in the database, and all students must be added to the course roster. 1. User clicks the course he/she wishes to take attendance for. 2. User selects each student who is present at the time of role. 3. User clicks to submit. If a student is not on the role, then the instructor can add a student. (See UC-07) UC-09: INSTRUCTOR VIEWS REPORT Summary: The instructor can use this application to view the information stored in the database. This will allow him/her to see reports on student s attendance. Priority: Essential. Goal: To allow instructor to view student attendance information. Use frequency: Somewhat Often. Prerequisite: User must be logged into the system, the course must be registered in the database, and attendance should have been taken at least one day. 1. User chooses to view reports 2. User choose from his/her list of courses 3. User chooses the students he/she wishes to view absence report on. 4. The system displays information requested. If the student has not been absent, then information will display. UC-10: LOGS OUT Summary: Once the user has finished using the application for the time being, he/she will log out so that no one else can access their account. Priority: Essential. Goal: To provide security over users account. Use frequency: Once for each log in. Prerequisite: User must be logged into the system. 1. User chooses to logout from the menu. If the user is not logged in, then he/she can not logout.

7 Entity Relationship Diagram (ERD) Professors teach Classes take have Attendance Roster attend Students compose

8 Interface Design LOGIN PAGE This is the first screen the instructor sees when the user wants to enter the site. The user interacts with the screen by inputting their user name and password. They then select the Login button to try and enter. The program validates the information and either allows the user to enter further or denies entry into the site. If you want the site to remember your user name and password you can select the Remember Me checkbox.

9 REGISTRATION PAGE If the instructor does not have an account then the user must register with the LSU Attendance Tracking System. They must fill out all the required fields and submit the information before becoming registered.

10 CLASSES PAGE Once the instructor has entered the system then he/she will be able to select their class and see the all the students in the class. If the user has not registered his/her respective classes then the user must select the Add Class button to register..

11 CLASS REGISTRATION PAGE If the instructor has not registered their classes then the user must fill all the fields and select the Submit button. Then you may be able to select the Back to go back to the previous page. The instructor could also use the navigation bar to move around the site.

12 REPORTS PAGE The reports page allows the instructor to select a particular class and student and view that particular student s attendance. This will generate a report in a data grid showing the specific dates that the student was absent.

13 ROSTER PAGE When the instructor clicks on their specific class then this page is loaded. It loads a roster of all the students in that specific class. Then the instructor checks the checkbox under Present if that student is present.

14 ADD STUDENT PAGE This page is for the instructor to add a student to his/her class. The instructor will fill out all three fields and then click the submit button to add a new student to the roster. NAVIGATION BAR The navigation bar allows the user to navigate through the site easily and efficiently. The Home hyperlink lets the user return to the home page. The Login hyperlink allows the user navigate to the login page. The Classes hyperlink lets the user go to the class page. Lastly, the Reports hyperlink allows the user to view the reports page.

15 Matrices USE CASES x DATABASE DESIGN REGISTER AS A NEW IDENTIFIES HIS/HERSELF EDIT PROFILE ** VIEW PROFILE ** ADDS A CLASS CHOOSES A CLASS ADDS A STUDENT TAKES ROLE VIEWS REPORT LOGS OUT ATTENDANCE CLASSES PROFESSORS ROSTER STUDENTS Create pid, firstname, last name, , password, and department Read , password Update Firstname, lastname, , password, and department Read firstname, lastname, , department Create , date, classnum/secnum Read , date, classnum/secnum Create classnum/secnum, time, pid Read classnum/secnum, time, pid Read pid, firstname, lastname Read classnum/secnum, Create classnum/secnum, Read classnum/secnum, Read , lname, sname Create fname, lname, Read , lname, fname

16 USE CASES x INTERFACE DESIGN REGISTER AS A NEW IDENTIFIES HIMSELF EDIT PROFILE ** VIEW PROFILE** ADDS A CLASS CHOOSES A CLASS ADDS A CLASS TAKES ROLE VIEWS REPORT LOGS OUT LOGIN REGIS- TRATION CLASSES CLASS REGISTRATION REPORTS ROSTER NAVIGATION BAR ADD STUDENT

17 USE CASES x MANUAL REGISTER AS A NEW IDENTIFIES HIMSELF EDIT PROFILE** VIEW PROFILE** ADDS A CLASS CHOOSES A CLASS ADDS A STUDENT TAKES ROLL VIEWS REPORTS LOGS OUT SYSTEM OVERVIEW LOGGING ON SYSTEM MENU CHANGING ID AND PASSWORD ** EIT SYSTEM CLASSES SECTION REPORT SECTION QUERIES ** Indicates a portion of the user manual that has not been implemented into our current web application.

18 DATABASE DESIGN x INTERFACE DESIGN LOGIN REGIST- RATION CLASSES CLASS REGISTRATION ADD STUDENTS ROSTER REPORTS NAVIGATION BAR ATTENDANCE CLASSES PROFESSORS I I O date I I O classnum/ secnum classnum/ secnum pid O I time O I pid firstname I O lastname I O department I I password I I I O O I I I O ROSTER classnum/ secnum O O STUDENTS I O O lname I O O fname I O O

19 INTERFACE DESIGN x MANUAL SYSTEM OVERVIEW LOGGING ON SYSTEM MENU CHANGING ID AND PASSWORD CLASSES SECTION REPORTS SECTION QUERIES LOGIN REGISTRATION CLASSES CLASS REGISTRATION REPORTS ROSTER NAVIGATION BAR ADD STUDENT ** Indicates a portion of the user manual that has not been implemented into our current web application.