Software Requirements Specification for Attendance Management System, Schemes and Mind Maps of Computer science

Download Software Requirements Specification for Attendance Management System and more Schemes and Mind Maps Computer science in PDF only on Docsity!

Software Requirements

Specification

For

Student Attendance system

Version 0.

Prepared by

Al Amin Ashik 193-35-

MD Rabiul Awal Shuvo 193-35-

Department of Software Engineering

Software Requirements Specification for Attendance Management System

Page ii Table of Contents Table of Contents...........................................................................................................................ii

1. Introduction

Problem Definition

The Attendance Tracking Management System takes input as student’s detail, no. of lectures attended no of practical conducted no. of lectures conducted etc. The contents are intended to be utilized by the engineering class as guidelines for implementation and testing. At the end of the particular semester the system would provide with defaulters list which would help the respective teacher incharge to take particular action.

1.1 Purpose

The following document describes the functional and non-functional requirements for the Attendance Tracking System release version 1.0. The contents are intended to be utilized by the engineering class as guidelines for implementation and testing. This Software Requirements Specification document only covers the main system and does not describe the implementation of the database in which the main system interacts. All the requirements stated in this document are slated for implementation in version 1.0, unless otherwise specified.

1.2 Document Conventions

This subsection contains definitions of all the terms, acronyms, and abbreviations used in the document. Terms and concepts from the application domain are defined  DIU – Daffodil International University  SRS – System Requirement Specification  SDLC – Software Development Life Cycle  UI – User Interface

1.3 Intended Audience and Reading Suggestions

The intended audience is the engineering class, who will be implementing and testing the Attendance Management System. Also, the document is to be utilized by the engineering professor to evaluate the software’s design and features.

1.4 Product Scope..................................................................................................................

The Attendance Management System will allow the teacher incharge to maintain a record of attendance of students in their respective classes from a PC. Also, the system will permit the teacher incharge to maintain all the essential details regarding a particular student. Furthermore, the program provides different modes to edit attendance, view statistics, and take notes on elements pertaining to attendance. The goal is to provide a professor with an easy, portable solution to attendance record maintenance and attendance statistics.

1.5 References........................................................................................................................

IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications. IEEE Computer Society, 1998.

2. Overall Description..................................................................................................................

2.1 Product Perspective..........................................................................................................

The Attendance Management System is intended to replace the manual model of attendance record keeping by means of roll call and paper records. The roll call and paper records are replaced with a single interaction between the professor and the Attendance Management System. Professors will be able to view details regarding attendance of individual students on their PC and quickly maintain attendance records. The features expressed in this Software Requirements Specification document are intended to be fully implemented in version 0.1. The system will be developed in such a way to provide easy addition of enhanced features, which may be desired in subsequent versions.

2.2 Product Functions............................................................................................................

The main feature of the Attendance Management System is that it keeps a record of all essentials details of each individual student. At the end of a specified period this system creates a defaulters list as well as the non-defaulters list. Attendance Percentage of each student in every subject would be displayed in this list Also, the system allows the professor to view pertinent statistics on student’s attendance record for the specified class. Finally, another feature of Attendance Management System is its flexibility and ease of use.

2.3 User Classes and Characteristics......................................................................................

Professors A professor is a faculty member of Daffodil International University. There are n number of faculty members at the university and it is estimated that almost all faculty members will utilize the Attendance Management System. Professors will have multiple classes and interaction with the system will occur at multiple times throughout the day from multiple professors. The professor should be allowed to take, edit, and view attendance records at any desirable time. All professors have Internet access through their PC’ s. This provides the backbone of the Attendance Management System.

2.7 Assumptions and Dependencies

AS-1: The database mentioned within this Software Requirements Specification document is previously administered with the correct information needed by the Attendance Management System. AS-2: For attendance policies, since professors do not usually tabulate tardiness, it is assumed a student is either present or absent. The system also assumes that detail regarding each student would be made correctly. DE-1: Class data being used for setup and student recognition is dependent on information in a database administered outside of the capabilities of the Attendance Management System. DE-2: Statistics on student attendance is dependent on a professor’ s consistent utilization of the system for each class period.

3. External Interface Requirements

3.1 User Interfaces

UI-1: The Attendance Management System shall provide details of students in the class to aid in taking roll. UI-2: These details can be clicked with a mouse in order to view a particular student’s attendance record. UI-3: All modifications to the database will be done through a keyboard. UI-4: Application will be accessed through a Browser Interface. The interface would be viewed best using 1024 x768 and 800 x 600 pixels resolution setting. UI-5: The program will provide a page that produces current statistics on class attendance

3.2 Hardware Interfaces

Server Side : H1: Operating System: Windows 7/xp/vista, Windows ME H2: Processor: Pentium 3.0 GHz or higher H3: RAM: 512Mb or more H4: Hard Drive: 128 Mb or more Client side: H5: Operating System: Windows 7 or above, MAC or UNIX. H6: Processor: Pentium III or 2.0 GHz or higher. H7: RAM: 512 Mb or more

3.3 Software Interfaces SI-1: Attendance Management System SI-1.1: This software will transmit the attendance of a class to a database on a machine via Internet. SI-1.2: The user will be allowed to modify attendance records at any time. SI-1.3: If the user forgets to transmit the information, the system will automatically send it for them at the end of the class. SI-2: Database The Attendance Management System will communicate with the database to perform the following options. SI-2.1: To allow a user to enter attendance. SI-2.2: To allow a user to modify attendance. SI-2.3: To allow a user to query a system to gain statistics concerning individual and class attendance.

3.4 Communications Interfaces

CI-1: The security of a user must be consistent through the use of passwords. CI-2: The Attendance Management System will communicate to the database through Internet.

The Use case diagram is a collection of diagram and text together that make action on goal of a process.

4.3 Use case diagram elements:

The use case diagram consists of six graphics elements that represent whole system:  Systems  Actors  Use cases  Association  Dependencies  generalization The Relationships between and among the actors and the use case of Attendance System:

 Admin Entry: Use case of Admin are Manage attendance, Manage Teachers, Manage

Students Attendance, Manage Login, Manage Users.

 System User Entity: Use case of System User are Manage Attendance, Manage

Teachers, Manage Students Attendance.

 Teachers Entity: Use Cases if Teachers are Mark Attendance, Search Students, View

Students Profile.

 Students Entity: Use Cases of Students are View Attendance, Request for Attendance,

Attendance Reports. Course management: Admin can view the course which is offering by college and can manage the courses and can add new courses that college wishes to offer. And Teachers Also Add Course and Students. Student Management: Teacher and Admin can view the student information. Attendance Management: View the attendance of students and manage the attendance details.

If user type is employee, then, have full access to view, add a new record and make changes in attendance record if any.  Select the section and other related information in the attendance form.  “update” the attendance to save the record in the database.  View the attendance record of students. Course management: Users can view the courses that are offering by the college. When user type is Teacher, it will have access only to limited features of the system and in this case only can view the courses.  The employee selects the course.  All courses that are offered by the college would be displayed to the employee.

5. System Features.......................................................................................................................

The attendance system has been built to eliminate the time and effort wasted in taking attendances in schools and colleges. It also greatly reduces the amount of paper resources needed in attendance data management

5.1 System Feature.................................................................................................................

5.1.1 Description and Priority This is a web base application. It’s built to be used for school/college faculty so that they may take student attendance on their phones or computer.

1. System Administrator
2. Faculty
3. Teacher 4.Students 5.1.2 Stimulus/Response Sequences The list of operations that the system will provide are-
4. An authenticated registration/login/logout option
5. Faculty have access to create a course and added the course teacher and students

Description Admin as well as members can view the entire details of the students or members who are registered. Stakeholder s Admin, Teacher FR-06 Post Events and Notice Description Admin as well as members can post or create any type events and notice that is related to these alumni. All the members of this alumni can see every event and notice. Stakeholder s Admin, Teacher FR-07 Check Attendance Description Students can check only their own attendance records Stakeholder s Admin, Teachers, Students FR-08 Generate Report Description Teachers and student can download their generated report in pdf format. Stakeholder s Teachers, Students

6.2 Performance Requirements

PE-1: The program must be able to be run concurrently by multiple professors. During peak times of usage (9:00 AM to 2:00 PM). PE-2: Transmission of roll data shall occur in under 5 seconds. PE-3: Acknowledgement of roll received (confirmation) shall be returned within 8 seconds. PE-4: Queries upon the database shall be performed in less than 5 seconds. PE-5: Upon start of the roll program, roll information shall be displayed on the instructor’ s Pocket PC within 10 seconds. PE-6: Email messages to absent students shall be sent within one hour of the conclusion of a class. PE-7: The program shall support taking roll for class sizes of up to 100 students. With a maximum class size, performance must still conform to all performance requirements.

6.3 Safety Requirements........................................................................................................

System would be protected by a password. As it is connected via LAN and MAN an antivirus has been installed on system for its safety purpose

6.4 Security Requirements.....................................................................................................

SE-1: An instructor shall permit to view and edit absence information in the database for only his/her classes. SE-2: 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 PC after initial entry in order that it must only be entered once. SE-3: Passwords shall be stored in an instructor database and verified upon each session of roll or database modification. SE-4: An instructor shall be allowed to change his/her password only by supplying his/her existing password. The updated password shall be stored in the instructor database and on the instructor’s PC_._

6.5 Software Quality Attributes.............................................................................................

Availability-1: The system shall be available to all instructors through Information Systems during their normal hours of operation. Reliability-1: Due to the use of a wireless network, 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. Reusability-1: The system shall be able to be reused for each new semester. Robustness-1: If no network connection can be established to receive the roll information, the Instructor shall be allowed to enter roll later. Robustness-2: If a network connection is lost during roll, the program shall allow the instructor to transmit roll information at a later time. Updatability-1: The system shall allow for addition or deletion of instructors, students, and classes while incorporating new semesters. Usability-1: Usability of the system shall be achieved through an online help page and an introductory training session for all instructors upon installation of the program on their Pocket PCs.