1. Team # 2 Members: Sowmya Krishnaswamy Hakan Terzioglu Manu Mehan Jerome Tunaya

2. Project Overview  Provide a secure login and logout system which will be used by tutors, students and administrators in the Minority Engineering and Computer Science department.  This product will keep a track of what has been done in the tutorial center and give a useful feedback that will be used in the future for requests of additional funding for this tutorial program.

3. Requirements Specific requirements Efficient way to keep track of all of the students who receive help. The software will compute the duration of time that is spent by student or tutor in the center. A need for the administrators of the lab to quickly figure out certain statistics such as the average number of visitors to the lab, average time spent in the lab, and the area of study that the student receives help in is needed.

4. Requirements (cont.) Specific requirements System will avoid login of a student/tutor before he logout in a given day. In other words there will not be duplication of login. The system will give error messages in the case of invalid inputs. The system will give options to students for self- study or tutorial. If self-study is chosen, self-study register is flagged and there will be no evaluation of the tutor. (that space becomes gray, no edit). If the tutorial is chosen, the system will provide levels for tutor evaluation.

5. Requirements (cont.) Specific requirements The system will provide the opportunity to change the password for tutors. The initial password for the tutors is specified by the administrator and when the tutor login the system for the first time, he will be forced to change his password. The system will determine the duration of time spent in the center as three hours if the tutor or the student forgets to logout.

6. Requirements (cont.) Specific requirements The administrator shall be able to reset all the data stored in the system. The system will provide a confirmation message box if the administrator clicks the clear box. The system shall provide graphical representation of the statistical data which is stored in the database.

7. Requirements (cont.) Functional requirements The data will be checked if it is in the specified format or it is in the database. Then two types of error messages can be generated: The one that tells the input is not in the proper format and the one that there is no match to the entered input in the database.

8. Requirements (cont.) Functional requirements For the output data, there is a simple subtraction function which calculates the difference between logout and login time. The result will be the duration of study in the tutorial center.

9. Requirements (cont.) Interface Requirements Input data items Student ID User name for the tutor Password for the tutor Password for the admin Output data items Duration of time Error messages in the case of invalid data input

10. Requirements (cont.) Interface Requirements(cont.) Format of the input and output data items Student ID must be a nine digit number User name for the tutor is a string of 6-8 characters Password for the tutor must be at least 5 characters long and should include only letters and numbers. Password for the admin must be at least 5 characters long and should include only letters and numbers.

11. Requirements (cont.) Interface Requirements(cont.) Accuracy of the data There is no accuracy requirement for the input data but the duration of time spent in the tutorial center must be captured accurately. The frequency of the data received and sent The data is received when a student or tutor comes to the tutorial center and wants to login the system. So there is no specific frequency of the data. It depends on the number of students and tutors entering to the center in a given interval.

12. Requirements (cont.) Physical Environment Requirements: The software will run on J2SE, which is the abbreviation of Java 2 Platform, Standard Edition. The code developers will use this software in their own PCs at home. They may also work in lab 257 in Engineering building I since the computers in that lab have that software.

13. Requirements (cont.) Physical Environment Requirements: The code developers will make changes in the code to their local copies of the software. So there would be a main copy of the code and the modification to that code is done after inspection to that problem by the whole group. The main copy will be kept in a different folder by all of the members of the group.

14. Requirements (cont.) Users and Human Factors Requirements: Our system will support three types of users.(students, tutors and administrator.) Since the software will be designed in a user friendly manner, a high level of skill in computer usage is not necessary for the users.

15. Requirements (cont.) Users and Human Factors Requirements The users will not require any special accommodations, every user will be assumed to have enough physical property to use the system. ( for example we will not provide large fonts for possible users with eye problems)

16. Requirements (cont.) Documentation Requirements: The system will store statistical data and the administrator will have access to it. The data will be classified according to their occurrence of date i.e. the data that were formed in January for example would be saved in the folder January. The system will provide graphical representation of the statistics. The administrator will be able to print them or observe online.

17. Requirements (cont.) Data Requirements: No data calculations will be performed. There is a simple time difference computation within the system which gives the duration of the time spent in the tutorial center by either the student of the tutor. The student ID which the students enter when they login the system and the user name, password which the tutors enter when they login the system must be retained.

18. Requirements (cont.) Security Requirements: The one who may abuse this system are tutors since they may be employed or not according to the evaluation results. So a tutor may enter the system by finding the student ID s (since there is no password required for the students) and may give high evaluation points to him. The client did not want us to recover this problem so there will be no security requirement. The code developers may deal with this problem if the group would decide to overcome this bottleneck.

19. Requirements (cont.) Quality Assurance Requirements: The software must be reliable if the user enter a valid input. ( the format of the inputs is specified above) The system should give some predefined error messages if the input data is not valid. Test cases must be run in the software developed to assure high quality.

20. Requirements (cont.) Quality Assurance Requirements: The client also should test before the deliverance of the product. No maintenance will be supplied after the client accepts the product. The documentation is so important in this manner because the maintenance can be performed by the technical staff of the tutorial center if the project is fully documented.

21. The Proposed System: Users and Modes of Operation The proposed system will be computer program that will be active at all times the lab is open. It will consist of many features that will make the overall log sheet concept that is previously used ancient. It will provide a secure login and logout method used by students, tutors, and administrators.

22. Users and Modes of Operation Students Login process- The first screen that the student will come across is the main option screen, which consists of logging in as a student, tutor, or administrator. Once the student chooses the proper option, they will be brought to another screen asking for their login identity, a password and the area of study to they need assistance with. After filling out these questions the student will than exit the system by clicking on the login button.

23. Users and Modes of Operation Students(cont.) Logout process Once the student is ready to leave the lab, they will be asked to enter the system again. They will asked to fill out an evaluation which consists of the tutor’s name that they received help from and a rating box to check off. The student can than properly log out of the system by clicking on the logout button.

24. Users and Modes of Operation Tutors Login process- The first screen that the tutor will come across is the main option screen, which consists of logging in as a student, tutor, or administrator. Once the tutor chooses the appropriate option, they will be brought to another screen asking for their login identity and a password. The tutor can than exit the system by clicking on the login button.

25. Users and Modes of Operation Tutors Logout process- Once the tutor is ready to leave the lab, they will be asked to enter the system again. They will be asked to logout properly so the system can record this logout time.

26. Users and Modes of Operation Administrators Login process The first screen that the administrator will come across is the main option screen, which consists of logging in as a student, tutor, or administrator. Once the administrator chooses the appropriate option, they will be brought to another screen asking for their login identity and a password.

27. Users and Modes of Operation Administrators Modifying process- After logging into the system, the administrator has the option to modify and view many forms of information. They can choose to add or remove tutor’s names and passwords. They can also choose to print out of view certain information about the student’s and tutor’s activity in the lab.

28. Users and Modes of Operation Administrators Logout process Once the administrator is ready to leave the system, they will be asked to properly logout by clicking on the logout button.

29. The Proposed System: Operational Scenarios Typical Scenario 1 The student sits down at the login system and prepares to log in. They are asked to enter their student identity number as well as a corresponding password. However, the password they enter is incorrect. The system will than let the student know that the password was invalid by a popup message saying “Invalid Password.”

30. The Proposed System: Operational Scenarios Typical Scenario 2- The student sits down at the login system and prepares to log in.They are asked to enter their student identity number as well as a corresponding password. They successfully log into the system and begin to fill out the proper information required from them. The student than receives help from the tutor and prepares to leave the lab. They are than asked to enter the system to properly log out. The student than fills out the evaluation sheet properly and logs out by clicking on the logout button. The login and logout times are properly recorded by the system.

31. The Proposed System: Operational Scenarios Typical Scenario 3- The administrator sits down at the login system and prepares to log in. They are asked to enter their identity and the corresponding password. They successfully log into the system and begin to modify and view tutor information. They choose to add a new tutor to the system. By clicking on the add new tutor button and filling out the tutor’s name and password for the specific tutor, they are able to accomplish this task quickly and efficiently. The administrator than logs out of the system by clicking the logout button.

32. The Proposed System: Operational Scenarios Atypical Scenario 1 The student sits down at the login system and prepares to log in. They are asked to enter their student identity number as well as a corresponding password. They successfully log into the system and begin to fill out the proper information required from them. The student than receives help from the tutor and prepares to leave the lab. They are than asked to enter the system to properly log out. However, the student forgets to log out properly and does not record a log out time. The system will than default the visit of the student to a time of three hours.

33. The Proposed System: Operational Scenarios Atypical Scenario 2- The tutor sits down at the login system and prepares to log in. They are asked to enter their identity number as well as a corresponding password. They successfully log into the system by clicking on the login button. They are than required to enter the system to properly log out. The student than fills out the evaluation sheet properly and logs out by clicking on the logout button. However, the tutor forgets to log out properly and does not record a log out time. The system will than default the tutor’s work time to three hours.

34. The Proposed System: Operational Scenarios Atypical Scenario 3 The administrator sits down at the login system and prepares to log in. They are asked to enter their identity and the corresponding password. They successfully log into the system and begin to modify and view tutor information. They choose to add a new tutor to the system. By clicking on the add new tutor button and filling out the tutor’s name and password for the specific tutor, they are able to accomplish this task quickly and efficiently. However, the specific tutor has already been previously added to the system. The administrator will than get a message saying “User Already Exists” letting the administrator know that the specific tutor is already in the system. The administrator can than log out of the system properly.

35. Future Modifications Graphical representation of the statistical data may be evaluated. The system can be modified to be more secure.

36. Conclusion This project is intended to keep a track of studies handled in tutorial center of Minority Engineering and Computer Science department. The data obtained from the system will be used as proof of progress in the center and it can be also used for additional funding requests.