Student Attendance Management System 5p3p3z

Version 1.0 approved

Prepared by Arsene Twizeyimana/ Odon Nsengimana

<08/4/2016>

Copyright © 2016 by Arsene Twizeyimana

Software Requirements Specification for Page ii

Table of Contents Table of Contents...........................................................................................................................ii Revision History.............................................................................................................................ii 1. Introduction..............................................................................................................................1 1.1 1.2 1.3

Purpose.......................................................................................................................................1 Project Scope..............................................................................................................................1 References..................................................................................................................................1

2.1 2.2 2.3 2.4 2.5 2.6 2.7

Product Perspective....................................................................................................................2 Product Features.........................................................................................................................2 Classes and Characteristics................................................................................................5 Operating Environment..............................................................................................................6 Design and Implementation Constraints.....................................................................................6 Documentation...................................................................................................................6 Assumptions and Dependencies.................................................................................................6

3.1 3.2

System Feature 1........................................................................................................................7 System Feature 2 (and so on).....................................................................................................7

4.1 4.2 4.3 4.4

Interfaces............................................................................................................................7 Hardware Interfaces...................................................................................................................8 Software Interfaces.....................................................................................................................8 Communications Interfaces........................................................................................................8

5.1 5.2 5.3 5.4

Performance Requirements.........................................................................................................8 Safety Requirements...................................................................................................................8 Security Requirements................................................................................................................9 Software Quality Attributes........................................................................................................9

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

3. System Features.......................................................................................................................7 4. External Interface Requirements...........................................................................................7

5. Other Nonfunctional Requirements.......................................................................................8

6. Other Requirements................................................................................................................9 Appendix A: Glossary....................................................................................................................9 Appendix B: Analysis Models.....................................................................................................10 Appendix C: Issues List...............................................................................................................13

Revision History Name

Date

Reason for Changes

Version

Software Requirements Specification for <Students Management System> Page 1

1.

Introduction

“Attendance Management System” is software developed for maintaining the attendance of the student on the daily basis in the University of Kigali (UoK). The staff, who are handling the subjects, will be responsible to mark the attendance of the students. Each staff will be given with a separate name and based on the subject they handle. An accurate report based on the student attendance is generated here. This system will also help in evaluating attendance eligibility criteria of a student. This chapter will cover the background of the study, problem statement, objectives of the study, significance of the study and technology to be used.

1.1

Purpose

This Attendance Management List System is intended to help the lecturers and the head of department to truck and manage how students attend the class. It also helps in generating the percentage of attendance quickly. The purpose of Software Requirements Specification (SRS) for Attendance Management System document is to describe the external behavior of the Attendance System. Requirements Specification defines and describes the operations, interfaces, performance, and quality assurance requirements of the Attendance System. The document also describes the nonfunctional requirements such as the interfaces. It also describes the design constraints that are to be considered when the system is to be designed, and other factors necessary to provide a complete and comprehensive description of the requirements for the software. The Software Requirements Specification (SRS) captures the complete software requirements for the system, or a portion of the system. It is intended for the designers and developers.

1.2

Project Scope

This project is limited only on how the students attend the class and each module. This application will manage each student attendance in class. And will limit for Uok.

1.3

References


2.

Overall Description

2.1

Product Perspective

Online Student attendance system is a web application based system which will helps UoK to make Attendance students and managing all necessaries information concern it online. Online Students attendance system has 3parts: part, Lectures part and Student part. Each part has its own functions. 2.2 This part is being used by s who have all privileges to access all information of Online UTB Students attendance list system like Human Resource. This part provides the option of making the search on the database according to the first and last names of student, lectures and the name of course, by editing adding or delete. This part has the following Menus: 1. Home: This menu shows all s general information on the system, and what`s required to get into the system. 2. Students This link helps the to add new students and enable him or her to delete or edit the names of students 3. Courses This link allows the to add and remove the courses according to the year of study and lecturer. 4. : Exit the page and close your session, come back to home page. 5. change : This link will help to change his/her . 6. reports: This link will allow to generate the general and daily report of the web application.


2.3 Lecturer This part is designed for the which can be any lecturer who needs to make the attendance of students. A lecturer can see the following home page menus. To access its student’s first name and last name and must be provided: 1. Home: This menu shows all s general information on the system, and what`s required to get into the system. 2. : Exit the page and close the session, come back to home page 3. Change :

This link will help lecturer to change his/her . 4. Make attendance This will enable the lecturer to make the attendance of students

2.4 Student This part is designed for the students in order to allow them to check their report of attendance. The students can see the following menus. To access their the attendance reports 5. Home: This menu shows all s general information on the system, and what`s required to get into the system. 6. : This menu allows the student to quit the system and exit the page and close the session, come back to home page 7. Change :

This link will help the student to change his/her . 8. Report This link will allow the student to check his or her report of attending report


2.2

Product Features

<Summarize the major features the product contains or the significant functions that it performs or lets the perform. Details will be provided in Section 3, so only a high level summary is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or a class diagram, is often effective.>

2.3

Classes and Characteristics


Name of a use case

Description

to the system

, Staff, Student must give their and to perform all functionality of the system regarding them, if they don’t have them have to their s following certain condition.

Attendance

This is the action done by the lecturers


Change

This is the action which helps every to change his/her owner any time.

Courses

This action helps to add the courses in the system

General report

This function helps to generate the general report of the attendance

Student report

This is where made report on student.

Student

This function helps the Student to check the report of his or her attendance.

2.4

Operating Environment

2.4.1 HARDWARE REQUIREMENTS (Minimum Requirement)  Minimum RAM: -2GB or Above  Hard Disk: -128 GB  Processor:-Intel Pentium 4(1.50 GHZ) or above 2.4.1

SOFTWARE REQUIREMENTS (minimum Requirement)  Operating system: Windows  Front Design: VB.Net version 10.0, .NET framework 4.0  Front-End Language: Visual basic  Back-End: Oracle  Back-End Connectivity:ADO.net

2.5

Design and Implementation Constraints


2.6

Documentation

2.7

Assumptions and Dependencies

3.

System Features

3.1

System Feature 1

3.1.1

Description and Priority

3.1.2

Stimulus/Response Sequences

3.1.3

Functional Requirements <Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind.>

REQ-1:


REQ-2:

3.2

System Feature 2 (and so on)

4.

External Interface Requirements

4.1

Interfaces

4.2

Hardware Interfaces

4.3

Software Interfaces

4.4

Communications Interfaces


5.

Other Nonfunctional Requirements

5.1

Performance Requirements

5.2

Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. Define any safety certifications that must be satisfied.>

5.3

Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.>

5.4

Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.>

6.

Other Requirements

Appendix A: Glossary


Appendix B: Analysis Models SYSTEM FLOW DIAGRAM


DFD level 1


Entity Relationship Diagram


Appendix C: Issues List < This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

Student Attendance Management System 5p3p3z

Overview 5o1f4z

More details 6z3438

Related Documents c2h70

Student Attendance Management System 5p3p3z

Student Attendance Management System 5p3p3z

Student Attendance Management System 5p3p3z

Student Attendance Management System 5p3p3z

Student Attendance Management System_erdiagram 5rge

Attendance Management System m423w

More Documents from "Odon Nsengimana" 41lx

Student Attendance Management System 5p3p3z

2005 - Pe104 - Fundamentals Of Rhythm 412w37

Respuesta Examen 142b27

Diseno De Sismica 3d.pdf 5x2ev