Srs on Management System

softw are agreement Requirements stipulation For attending track clay, Release 1. 0 mutant 1. 0 Prepared by Lee Bell, Graham Kennedy, Jonathan Loudin, Roger Seagle February 9, 2003 T competent of confine Table of Contents i edict level. i 1. Introduction. 1 1. 1 Purpose.. 1 1. 2 Document Conventions. 1 1. 3 mean Audience and Reading Suggestions 1 1. 4 depict Scope. 1. 5 References. 1 2. Over altogether Description . 1 2. 1 Product Perspective 1 2. 2 Product Features 1 2. 3 exploiter carve upes and Characteristics 1 2. 4 Operating purlieu . 2 2. 5 soma and instruction execution Constraints .. 2 2. exploiter Documentation . 2 2. 7 Assumptions and Dependencies 2 3. governance Features 3 3. 1 flourish musical mode . 3 3. 2 Edit way of life . 4 3. 3 Statistics Mode . 6 4. outside(a)(a) larboard Requirements .. 7 4. exploiter Interfaces . 7 4. 2 Hardware Interfaces . 7 4. 3 Software Interfaces .. 7 4. 4 communications Interfaces . 8 5. Other unserviceable Requirements .. 8 5. 1 Performance Requirements .. 8 5. 2 Safety Requirements 8 5. shelter Requirements . 8 5. 4 Software Quality Attributes . 8 6. Other Requirements 9 Revision History Name Every peerless Everyone particular attend February 9, 2003 February 12, 2003 Reason For Changes sign Draft Revise Draft Version 1. 0 draft 1 2. 0 Final Version 1. Introduction The side by side(p) memorandum describes the function al and non-functional requirements for the attending bring in dodging release version 1. . The table of contents are think to be apply by the software engineering screen out as guidelines for implementation and testing. This Software Requirements stipulation document only covers the main dodge and does non describe the implementation of the infobase in which the main strategy interacts. All the requirements stated in this document are slated for implementation in version 1. 0, unless otherwise qualify. 1. 1 Purpose 1. 2 Document Conventions As of the latest version of this Software Requirements precondition, thither are no document conventions.The intended audience is the software engineering partition, who go away be implementing and testing the attention track System. Also, the document is to be holdd by the software engineering prof to treasure the softwares design and features. The attention trailing System depart countenance professors to maintain a redact down of attendance of bookmans in their respective shapees from a air hole PC. Also, the transcription capture permit the t distributivelyer to confide a pupil a notification email of their absence seizure. Furthermore, the course set ups diametrical modes to sheer attendance, view tatistics, and sw all in take notes on elements pertaining to attendance. The goal is to provide a professor with an easy, portable solution to attendance script maintenance and attendance statistics. 1. 3 think Audience and Reading Suggestions 1. 4 Project Scope 1. 5 References 1. Weigers, Karl. Software Requirements Specification Template, http//www. sufficeimpact. com/process_assets/srs_template. doc 2. Overall Description The attending tracking System is intended to counter substitute the manual model of attendance record keeping by means of bicycle roar and paper records.The gyre call and paper records are replaced with a genius interaction between the professor and the attendance introduce System. Professors ordain be able to view pictures of learners on their grievous bodily harm PC and quickly maintain attendance records. The features express in this Software Requirements Specification document are intended to be full implemented in version 1. 0. The dodge ordain be developed in such a way to provide easy addition of enhanced features, which whitethorn be desired in succeeding versions. The main feature of the Attendance introduce System is for a professor to take pad from the grievous bodily harm PC.Pictures result be demoed for each student in the soma, so the professor can recognize students without having to manually call roll. If students are hit, the dodging sends a notification email to the student stating the real number of absences the student has accumulated. Also, the governing body allows the professor to view pertinent statistics on students attendance record for the specified kinsperson. Finally, another featu re of the Attendance trailing System is the faculty to easily tailor the attendance record for any given up day. Professors 2. 1 Product Perspective 2. 2 Product Features 2. User Classes and Characteristics A professor is a faculty ingredient of heat Forest University in Winston Salem, North Carolina. in that location are 357 faculty outgrowths at the university and it is estimated that close to all faculty instalments go out utilize the Attendance bring in System. Professors go forth engender multiple breakes and interaction with the dodging depart find at multiple multiplication by means ofout the day from multiple professors. The professor should be allowed to take, edit, and view attendance records at any desirable time. All professors suck up radiocommunication Internet access through and through their pouch PC s piece of music on campus.This connection provides the backbone of the Attendance introduce System. designing 1 linguistic context diagram for Attendance Tracking System. 2. 4 Operating Environment OE-1 OE-2 OE-3 The Attendance Tracking System shall function on the Pocket PC provided by the university. This entails the frame to travel on the Windows CE platform. The Attendance Tracking System shall interface between Windows CE and a Linux emcee designated to store the attendance records. The Web Server and Database Software grow not been realised at this point.Up assured versions of this document will include nurture pertaining to these circumstantial operating environss. The Attendance Tracking System will operate with a even to be established email thickening for notification of absences send to students. CO-1 CO-2 CO-3 2. 5 Design and Implementation Constraints The time allotted for this hold will be limited to the jump off 2003 semester. The language for the image will be ocular C++ and the development environment will be the embedded Visual C++ 3. 0 environment. All the hypertext markup language decree for the mapr manual will conform to the HTML 4. 0 standard. UD-1 UD-2 . 6 User Documentation The arranging will provide an online user manual in HTML that describes the functionality and options available to the user. The musical arrangement will provide a hard duplicate of the user manual, which is identical to the manual draw in UD-1 AS-1 AS-2 2. 7 Assumptions and Dependencies The infobase mentioned at bottom this Software Requirements Specification document is previously administered with the objurgate discipline needed by the Attendance Tracking System. For attendance policies, since professors do not usually tabulate tardiness, it is assumed a student is either present or transfer.The notes functionality allows the professor the option to comment on tardiness and the edit mode allows the professor to remedy attendance due DE-1 DE-2 3. System Features to tardiness. Class data being used for setup and student recognition is dependent on study in a database administ ered outside of the capabilities of the Attendance Tracking System. Statistics on student attendance is dependent on a professor s consistent exercising of the agreement for each yr consequence. Figure 2 evidence Diagram for novelty between modes within the system. 3. 1 Roll Mode 3. 1. 1 Description and antecedenceA user whose identity has been support will be able to convalesce a rolling and take roll at phratry time. The Pocket PC will consider the correct gyre for the live take in and time, cure that rolling from a database innkeeper, and paginateant it for the purposes of fetching roll. The user will be able to designate each socio-economic socio-economic section extremity as present or absent, and upload that perspective nurture to the server. The server will terminate the kinsfolk members attach as absent by netmail. antecedency = High. 3. 1. 2 excitant/ rejoinder Sequences remark Response stimulus Response remark Response Stimulus Response User loads system.System queries server and if a contour exists for the veritable date, time, and user, thus that roll is call ind and displayed. User points that a class member be marked absent. The class member is designated as absent. User requests that a class member be marked present. The class member is designated as present. User requests that the data be sent to the server for storage. The absence data for the current bun are move to the server. Stimulus Response Server receives data indicating a class member has been put down absent. E-mail is sent to that class member. 3. 1. 3 Functional Requirements Roll. Retrieve. Time Roll.Retrieve. Date Roll. Retrieve. coil Roll. Retrieve. Roster. No Roll. Display. Roster Roll. Display. Members Roll. Mark. Present Roll. Mark. wanting(p) Roll. Transmit. Data Roll. Notify. E-mail The system shall retrieve the current time. The system shall retrieve the current date. The system shall retrieve the roster from the server that m atches the current time and date. If no roster is found to match current time and date, default menus will be displayed. The system will display the roster on screen. The roster will display the pictures and label of class members. Members devour the superpower to be marked as present.Members wee-wee the capacity to be marked as absent. The system will transmit the stipulation of each class member in the agile roster to the server. The system will notify all class members by e-mail if they are marked as absent on with their current situation within the attendance policy. 3. 2 Edit Mode Figure 3 State Transitions within Roll Mode. 3. 2. 1 Description and antecedency A user whose identity has been support who wishes to change the absence status of one or more class members as is related to a past class accomplishment will nurture the qualification to retrieve the roster data for that class period from the server.Absence data may then be adjusted and the corrections uplo aded to the server. whatever new absences will event in notification by e-mail to the class member in question. A change from absent to present will result in a notification that an absence has been removed. Priority = High. 3. 2. 3 Stimulus/Response Sequences Stimulus Response Stimulus The user requests to view absence data from a certain date and time. The roster and absence data are retrieved from the server and displayed. The user requests that a class member s status be changed to absent. Response Stimulus Response Stimulus ResponseThe class member s status is changed to absent. The user requests that a class member s status be changed to present. The class member s status is changed to present. The user charges that they are finished making changes. The altered data is uploaded to the server and server data is updated to suppose the changes. E-mail notification is sent to the class members affected. 3. 2. 3 Functional Requirements Edit. Retrieve. Time Edit. Retrieve. Date Edit. Retrieve. Roster Edit. Retrieve. Roster. No Edit. Display. Roster Edit. Display. Members The system shall allow the user to choose the date of the roster to be retrieved.The system shall allow the user to choose the date of the roster to be retrieved. The system will retrieve the roster and absence data from the communicate date and time. If no such roster exists, an error message will be displayed. The system will display the roster on screen. The roster will display the pictures and label of class members along with current absence status on screen. Members will demand the powerfulness to arrest their status changed to present. Members will brace the business leader to take their status changed to absent. The system will transmit the new status of each class member in the active roster to the server.The system will notify all class members by e-mail if their status has been changed to absent along with their current status within the attendance policy. The system wil l notify all class members by e-mail if their status has been changed to present along with their current status within the attendance policy. Edit. Mark. Present Edit. Mark. hit Edit. Transmit. Data Edit. Notify. Absent Edit. Notify. Present Figure 4 State Transitions within Edit Mode. 3. 3 Statistics Mode 3. 3. 1 Description and Priority A user whose identity has been verified may request absence statistics for class members in classes under their control.Statistics for an individual class member may be retrieved and displayed with regard to number, relative absolute frequency, date of absences as well as the parcel of classes missed over a user-defined period of time. A numerate of class members who were absent for a chosen class period may also be retrieved. Priority = High. 3. 2. 3 Stimulus/Response Sequences Stimulus Response User requests a statistical record. Statistics are calculated, retrieved from the server, and displayed. 3. 3. 3 Functional Requirements Stats. Defi ne. invest Stats. Request. derive Stats. Request. Dates Stats. Request. Frequency Stats. Request. Percentage Stats.Request. hear Stats. Retrieve. Number Stats. Retrieve. Dates Stats. Retrieve. Frequency Stats. Retrieve. Percentage Stats. Retrieve. come The user shall stool the ability to set the date or range of dates for which statistics will be retrieved. The user shall have the ability to request the number of absences for a class member. The user shall have the ability to request the dates of the absences for a class member. The user shall have the ability to request the frequency of absences for a class member. The user shall have the ability to request the percentage of class periods that a class member was absent.The user shall have the ability to request a constitute of the class members absent on a given date. The system shall have the ability to calculate and retrieve the number of absences for a class member from the server. The system shall have the ability to calc ulate and retrieve the dates of the absences for a class member from the server. The system shall have the ability to calculate and retrieve the frequency of absences for a class member from the server. The system shall have the ability to calculate and retrieve the percentage of class periods that a class member was absent from the server.The system shall have the ability to retrieve a list of the class members absent on a given date from the server. The system shall have the ability to display the number of absences for a class member. The system shall have the ability to display the dates of the absences for a class member. Stats. Display. Number Stats. Display. Dates Stats. Display. Frequency Stats. Display. Percentage Stats. Display. List The system shall have the ability to display the frequency of absences for a class member. The system shall have the ability to display the percentage of class periods that a class member was absent.The system shall have the ability to display a list of the class members absent on a given date. Figure 5 State Transitions within Statistics Mode. 4. External Interface Requirements 4. 1 User Interfaces UI-1 UI-2 UI-3 UI-4 UI-5 The Attendance Tracking System shall provide pictures above the names of students in the class to aid in taking roll. These pictures can be clicked with a stylus in post to indicate whether a student is present or absent. All modifications to the database will be do through a stylus, the keyboard would only be needed to put on words.The Attendance Tracking System will provide a help link that will download a user manual and project it onto the screen in case the user has difficulty in use the chopine. The program will provide a page that produces current statistics on class attendance. 4. 2 Hardware Interfaces HI-1 HI-2 HI-3 The Attendance Tracking System will reside on the Pocket PC, however, it will be able to typography its data to a database set up on a Solaris machine. The Attendance Track ing System will also be able to tell the Solaris machine to send emails to students who have missed class.The Pocket PC will use a wireless Ethernet card to communicate with the database set up on the Solaris machine. 4. 3 Software Interfaces SI-1 SI-1. 1 SI-1. 2 SI-1. 3 SI-2 SI-2. 1 SI-2. 2 Attendance Tracking System This software will transmit the attendance of a class to a database on a Solaris machine via wireless Ethernet. The user will be allowed to alter attendance records at any time. If the user forgets to transmit the information, the system will automatically send it for them at the end of the class. Database The Attendance Tracking System will communicate with the database to perform the pastime options.To allow a user to drop off attendance. To allow a user to modify attendance. SI-2. 3 SI-3 To allow a user to query a system to remove statistics concerning individual and class attendance. Mail sum Generator If a student is absent, the database will send the necessar y information to this interface and an e-mail message will be sent to the student. 4. 4 Communications Interfaces CI-1 CI-2 CI-3 The protective cover of a user mustiness be consistent through the use of passwords. The Attendance Tracking System will signalise the mail message generator when it postulate to send an email to the student.The Attendance Tracking System will communicate to the database through a wireless Ethernet system. 5. Other Nonfunctional Requirements 5. 1 Performance Requirements PE-1 PE-2 PE-3 PE-4 PE-5 PE-6 PE-7 The program must be able to be stripe concurrently by multiple professors. During thrill times of usage (900 AM to 200 PM), the system shall support approximately 20 users. Transmission of roll data shall occur in under 5 seconds using the wireless interlock card. Acknowledgement of roll received (confirmation) shall be returned within 8 seconds. Queries upon the database shall be performed in less than 5 seconds.Upon start of the roll program, rol l information shall be displayed on the instructor s Pocket PC within 10 seconds. Email messages to absent students shall be sent within one hour of the induction of a class. The program shall support taking roll for class sizes of up to atomic number 6 students. With a maximum class size, military operation must still conform to all performance requirements. 5. 2 Safety Requirements No safety requirements have been identified. 5. 3 Security Requirements SE-1 SE-2 SE-3 SE-4 An instructor shall permitted to view and edit absence information in the database for only his/her classes.In order to take roll or edit database information, the instructor shall be required to enter a password. This password shall be stored on the instructor s Pocket PC after initial entry in order that it must only be entered once. Passwords shall be stored in an instructor database and verified upon each session of roll or database modification. An instructor shall be allowed to change his/her password o nly by supplying his/her live password. The updated password shall be stored in the instructor database and on the instructor s Pocket PC. 5. Software Quality Attributes Availability-1 The system shall be available to all instructors through breeding Systems during their normal hours of operation. Reliability-1 Reusability-1 Robustness-1 Robustness-2 Updatability-1 Usability-1 6. Other Requirements Due to the use of a wireless web, reliability of the system at all times is not guaranteed. However, overall reliability of the system and roll information shall be achieved through the process of database manipulation. The system shall be able to be reused for each new semester.If no network connection can be established to receive the roll information, the instructor shall be allowed to enter roll later. If a network connection is lost during roll, the program shall allow the instructor to transmit roll information at a later time. The system shall allow for addition or swing of ins tructors, students, and classes while incorporating new semesters. Usability of the system shall be achieved through an online help pages and an introductory train session for all instructors upon installation of the program on their Pocket PCs. 6. 1 Database RequirementsDA-1 DA-2 DA-3 DA-4 The system shall include three databases student, class, and instructor. The student database shall lead student information including name, email address, and student identification number. The class database shall contain information about classes including class title, department ordinance and course number, meeting times, students enrolled, and absences. The class database shall be grouped by department code and course number. The instructor database shall contain information about instructors including name, email address, password, and classes taught.