College of Computer Science & Engineering Department of Computer Science

Orientation Students Information System

.

.

.

.

.

.

.

.

.

.

OSIS
Software Requirements Specifications

Semester 011 Prepared by Majed Al-Sehli, 972049 Mohammad Al-Harbi, 972031 Prepared for Dr. Abdullah Al-Sukairi

Saturday, October 20, 2001

...................................8 REPORTS ..................................... 6 3.......................................................................................................................................1......... 13 3....2.................................1 PRODUCT FUNCTIONS ...................................................................................2 STUDENT INFORMATION ................. 1 1............3 STUDENT ATTENDANCE .....1...................4 PURPOSE .................................................................................................................. 7 3...........1..............2 MAINTAIN COURSE AND SECTION INFORMATION......... 2 OVERVIEW .............................1 1................1.....................................................6 SECTION INFORMATION........................................................................................1........................4 TEACHER INFORMATION ..2..... 3 2....................................... 9 3.......................................................... 5 2............2.....................................................3 SECURITY .................2 NONFUNCTIONAL REQUIREMENTS .......... 13 3............................... 5 2.................................................................... 4 2....2 1........................................................................... 13 1 ..... 3 2............................................................................... 13 3.............................3 1... OVERALL DESCRIPTION.................. 2 1......................... 3 2....................................................................................2 RECOVERY..................1........1..............................................................9 HISTORY .5 COURSE INFORMATION .......................................................................................................................1.............. 3 2. 11 3....1 AUTHORITIES AND AUTHENTICATION ..........................................2 SAMPLE STORYBOARDS .................................. 8 3........................................... INTRODUCTION ......... 6 3..................................7 EXAM INFORMATION .............................. SPECIFIC REQUIREMENTS.........................................................1 MAINTAIN ATTENDANCE INFORMATION.......2.................................. 6 3.... 3 2.....................................1 MAINTAIN STUDENTS ATTENDANCE .3 MAINTAIN SCORE INFORMATION ................................................................................ 9 3.... 12 3.......1 FUNCTIONAL REQUIREMENTS .................3 USER CHARACTERISTICS .............1 DEVELOPMENT PLATFORM .........................4 CONSTRAINTS ............................................................................................... 11 3......................................................................................................................... 2 ABBREVIATIONS............................................................................................................................................2.....4 GENERATE REPORTS .... 10 3....................................................................1.................................................................................2 SYSTEM ALLOCATING LETTER GRADES ................... 4 2.................................... 6 2...........................................................................................1....................................... 2 SCOPE ...... 5 2.......................................................1......................CONTENTS CONTENTS.............................................. 6 3....................................1.....................................................................1..............

2 Scope OSIS is to be designed and developed specifically for the OP. it will be possible for the OP to maintain up-to-date and accurate attendance. the Senior Project professor. OP OSIS DN Orientation Program. The OSIS has to be capable of maintaining students. and produce reports about them.1 Purpose This document contains the requirement specifications of OSIS (Orientation Students Information System) software package to be developed by Majed Al-Sehli and Mohammad Al-Harbi for the Deanship of Educational Services. 1. and teachers information. and the System Coordinator of the OP.1. exams scores. Using OSIS. OP is a rapidly developing orientation program in KFUPM. the customer Orientation Students Information System Denial grade 2 . Orientation Program (OP). The intended audience of this document is the designers. and letter grades for students. 1. INTRODUCTION 1. teacher-section assignments. It will be used to keep track of all the personal and academic information managed by the OP. courses. The design of OSIS will be based on an approved version of this document.3 Abbreviations Abbreviations used in this document are given below for reference.

The administrator enters the attendance information and saves it using the "section attendance" form in the system. Overall Description 2. This number is decided in the beginning of every semester and saved in the system configuration. It describes the product environment constraints and lists the functional and nonfunctional requirements of the OP. Course information can be changed using the same form. namely. Every number of lateness or penalties is counted as an absence. section number.1.1 Product functions 2. The administrator also enters the sections information.4 Overview The rest of this SRS document gives an explicit description of the OSIS. his absence is changed to “excused” and the administrator enters the excuse information through a special form in the system. 3 . credit hours. This is done through a special course form.1. days. number of exams.1. the course. If a student presents an official excuse for absence. The administrator assigns teachers to them using the same form. course number. attendance rules. the department. The system adds recorded absence.2 Maintain Course and Section Information The administrator enters the course information.1 Maintain Attendance information Each teacher takes attendance of his students and delivers the attendance sheet to the system administrator. and semester. 2. He can modify this information at any time through the same form. time. 2. namely. and semester.

the system generates a DN report. He can modify this information using the same form at any time. The system calculates averages and totals for each section and course.3 Maintain Score Information The administrator enters the major and final exams scores as soon as he obtains the marks either from the teachers or from the ITC. If a student exceeds this maximum number of absences. The administrator enters the cut-off points as the courses coordinators provide them and the system uses them to allocate letter grades to students. it generates a warning report. A special form in the system allows the administrator to enter the information. It also generates reports of students absences for sections and individuals. 2. number of exam. Exams scores are also reported to teachers and students.4 Generate Reports The system generates different kinds of reports. If a student approaches the maximum number of absences. 4 . which is set by course coordinator.1. This can be modified later using the same forms. student IDs and scores.1. The user can print any of the mentioned reports using a special report form.Another form is used to assign students to sections. 2. It generates weekly attendance sheets for each section listing enrolled students IDs and names. The form specifies the course.

logs into the OSIS and chooses section or student 2 Insert given exams scores 3 Generate the letter grades 8 Decide cut-off points for grades 4 System performs calculations 5 . 6 5 Admin.2. logs into the OSIS and chooses section or student 2 Insert given attendance data 3 Generate warning and DN reports 4 System performs calculations 2.2.2 System Allocating Letter Grades 1 Exams scores prepared by teachers or ITC 6 9 7 5 Admin.2 Sample Storyboards 2.1 Maintain Students Attendance 1 Teacher collects attendance data and passes it to the admin.2.

4 Constraints The configuration of the system should not be hard-coded.1. 2. and the cut-off points and weights for exams. 6 . delete and edit any data. Viewer: viewer users cannot add. OSIS configuration includes the number of exams for a specific course in a semester. there are two different types of users: Administrator: there is only one administrator of the system. Using OSIS does not require any special computer skills because it is required to be a web-based application that can be accessed over a local network using any web browser.3 User characteristics The users of OSIS are educated people with at least a bachelor degree. Namely.2. the number of lateness or penalties to be counted as an absence. He has the authority to add. Specific Requirements 3. and edit information. They can only view and search the database to obtain the needed information.1 Functional Requirements 3. Nevertheless. he shall have all the privileges that other users have. delete. Future changes in the OP should be easily accommodated. 3.1 Authorities and Authentication • The system shall provide different levels of access according to the authority of the user.

and e-mail. 7 . a student can be “regular” or “audit”. a student can be “active” or expelled with a “DN” grade. For status. type. ID number. For type. address. • The system shall maintain a status and a type for each student in every course per semester. Namely. 3. A list of enrolled students is provided at the beginning of each semester. The administrator and viewer shall be able to view students’ records for every semester.• The system shall provide user authentication by asking for a user name and a password to enforce authority levels and security. He must be a staff or faculty at KFUPM. phone number. the system shall check if the user is the administrator or a viewer.2 Student Information • The system shall maintain students’ personal information.1. When signing in. If a user forgets his password. student's name. status. father's name. the system should send it to his email. The administrator shall be able to create records for new students and edit any previous records. A new user can be added to the system only by applying to the administrator. The administrator shall be able to change the status and type.

8 . The administrator enters excuse information for later reference. • The system shall maintain student lateness information for each course. and whether it includes exams or not are recorded. The administrator shall enter the absence record as given by teachers for a single student or a whole section. The excuse reason. The administrator shall be able to edit absences at any time. The administrator and viewer shall be able to view lateness record for each section or individual student.1. specified by the course coordinator. The administrator and viewer shall be able to view absence records for each section or individual student.3. then the absence record of the student is incremented by one. The administrator shall be able to edit lateness at any time.3 Student Attendance • The system shall maintain student absence information for each course. The system shall add the number of lateness for each student. If the student provides an official excuse. date. The system shall add absences for each student and report warnings for excess absences as the administrator specifies for each course. If they add up to a number. the absence is not counted. The administrator enters the lateness record as given by teachers.

The administrator shall be able to enter a “penalty” record for a student in a specific lecture. maintain personal information. ID. For each semester. If they add up to a number. specified by the course coordinator. 9 . 3. This includes teacher's name. The administrator shall be able to edit a penalty at any time. then the absence record of the student is incremented by one. For each teacher. The administrator shall be able to add and modify teachers. mailbox. and notes.• The system shall maintain any penalty information for each student. as provided by the teacher. and e-mail. phone number. The system shall add the number of penalties for each student.1. 3. credit hours.5 Course Information • The system shall maintain courses information for each semester.4 Teacher Information • The system shall maintain teachers' information. number. The administrator and viewer shall be able to view the penalties recorded in each section and for each student.1. office location. maintain assigned sections information. Course information includes its name. The administrator and viewer shall be able to view teachers' personal information and academic information for each semester.

Each one teaches two classes of his partner’s section. For English courses. The administrator shall be able to add and modify a student’s enrollment record in a section. Number of lateness and penalties to be counted as an absence.6 Section Information • The system shall maintain all information regarding sections for every course in a semester. The registrar provides a list of all sections and enrolled students. there are four classes and two partner teachers. For each English section. 10 . Typing and word processing. specify the following: Number of exams.1. 3.For each course. include the following with their percentage in the total score: Oral exam. The administrator shall assign a teacher for a section. The administrator shall enter and modify section times. Number of absences to issue a warning. Number of absences to issue a DN grade.

Mean. The administrator shall be able to enter and edit exams’ marks for each student in every course.1. the system should generate the following: Bar chart reports of average scores in exams to be used to decide cut-off points for letter grades. 11 .1.8 Reports • The system shall generate reports that can be used by the dean. and students as needed. The administrator should enter the number of exams for a course with their weights. and note. total and letter grade statistics for each semester. For each course. teachers and times for every semester. Results of multiple-choice exams are given by the ITC as a text file. week in which the exam is to be held. Namely. exam 3.7 Exam Information • The system shall maintain all exams information for each student. teachers. as the coordinator of that course decides. The system shall calculate the total marks and averages. The system shall assign letter grades based on cut-off points given by coordinators and entered by the administrator. 3. number. weight.The administrator and viewer shall be able to view sections students.

Warning reports for excess absence in a course. Exams score by student with overall statistics.For each section. when expelled from a course. Exams scores and letter grades. 12 . the system should generate the following: A list of all students. which can be accessed and manipulated in the same manner as described above. lateness. Absence report for a whole section. List of assigned sections with time and population. ID and name (attendance sheet). and excused absences in each course for each semester. For each student. DN-grade notice.1. the system should generate the following: Personal and academic information. For each teacher. Total number of absences. 3.9 History • The system shall maintain all the information for every semester as history. penalties. the system should generate the following: Personal information and academic status.

or restart is proposed. the OSIS authenticates him.2 Recovery No checkpoint. Backups are to be taken regularly and reloading from backups will be done in case of corruption.2 Nonfunctional Requirements 3. 3. The front-end can run on any operating system that can be connected to the OP LAN and is capable of running a web browser. determines his level of authority.1 Development Platform The back-end shall run on Windows Server 2000© with SQL Server 2000©. User names and passwords are saved in a table in the database managed by the administrator using a special form.3.2.2. then affords privileged features. 3. recovery. When a user logs on. to enable users to change their passwords. The front-end code shall be implemented using Jscript.2. Windows© and Internet Explorer© are recommended.3 Security The system security shall be table-based. Password changing capability will be part of OSIS. Authorized persons on providing a “user name” and a “password” can log-on. 13 .

Sign up to vote on this title
UsefulNot useful