Student Attendance Management System

NOTE: This template is shareware downloaded from www.processimpact.com www.processimpact.com.. All shareware payments are donated to the Norm Kerth Benefit Fund to help a consultant who is disabled with a brain injury. Please visit http://www.processimpact.com/norm_kerth.html http://www.processimpact.com/norm_kerth.html to to make a shareware payment ($10 suggested). Thank you!

Software Requirements Requirements Specification for

Version 1.0 approved

Prepared y Arsene !wi"eyimana# $don %sengimana

<&o'>

<0(#)#*01+>

Copyright © 2016 by Arsene Twizeyimana

Software Requirements Software Requirements Specification for Page ii

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

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

2. Overall Description...................................................................... .................................... ........2 2.1 2.2 2.3 2.4 2.5 2.6 2.7

Product Product Perspectiv Perspective............ e........................... ............................. ............................. .............................. ............................. ............................................. ...............................2 Product Product Features...... Features..................... ............................. ............................. .............................. ............................. ............................. .......................................... ........................... 2 User Classes Classes and Characteris Characteristics..... tics.................... .............................. ............................. ............................. ............................................... ................................5 Operating Operating Environm Environment........ ent....................... ............................. ............................. .............................. ............................. ........................................... .............................6 Design Design and Implementa Implementation tion Constraints. Constraints............... ............................. .............................. ............................. ............................. .......................... ...........6 User Documenta Documentation... tion.................. ............................. ............................. .............................. ............................. ............................. ....................................... ........................ 6 Assumpti Assumptions ons and Dependenc Dependencies......... ies....................... ............................. .............................. ............................. ............................................ ..............................6

3. System Features............................................................. .................................. ................. ........ ................ .......7 3.1 3.2

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

4. External Interface Requirements......................................................... .............................. ...................... ............ ....7 4.1 4.2 4.3 4.4

User Interfaces.. Interfaces................. .............................. ............................. ............................. .............................. ............................. ............................. ............................. ................... ..... 7 Hardware Hardware Interfaces... Interfaces.................. ............................. ............................. .............................. ............................. ..................................................... .......................................8 Software Software Interfaces.. Interfaces................. .............................. ............................. ............................. .............................. ............................. ............................. ........................... ............ 8 Communic Communication ationss Interfaces... Interfaces.................. .............................. ............................. ............................. ............................. .......................................... ............................8

5. Other Nonfunctional Requirements.................................................... ............................ .......8 5.1 5.2 5.3 5.4

Performanc Performancee Requiremen Requirements......... ts....................... ............................. ............................. ............................. .............................. ............................. ....................... ......... 8 Safety Safety Requiremen Requirements......... ts........................ ............................. ............................. .............................. ............................. ............................. ............................. .................. .... 8 Security Security Requiremen Requirements........ ts...................... ............................. ............................. ............................. .............................. ............................. ............................. ................. ..9 Software Software Quality Quality Attribute Attributes.............. s............................. ............................. ............................. ............................. ............................. ................................ .................9

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

Revision History Name

Date

Reason for Changes

Version

Software Requirements Software Requirements Specification for Page 1

1.

Intr In trod odu uctio ction n

“Attendance Management System” is software developed for maintaining the attendance of the student on the daily basis in the University of Kigali (UoK) !he staff" who are handling the sub#ects" will be responsible to mar$ the attendance of the students %ach staff will be given with a separate username and password based on the sub#ect they handle An accurate report based on the student attendance is generated here !his system will also help in evaluating attendance eligibility criteria of a student !his chapter will cover the bac$ground of the study" problem statement" ob#ectives of the study" significance of the study and technology to be used

1.1

Purp Purpos osee

!his !his Attend Attendanc ancee Manag Managem ement ent &ist &ist Syste System m is inten intended ded to help help the lectu lecturer rerss and the head head of depart departme ment nt to truc$ truc$ and manag managee how student studentss attend attend the class class 't also also helps helps in genera generati ting ng the percentage of attendance uic$ly uic$ly Software Softwar e Requireme Requirements nts Specification Specification (SRS) for Attendance Attendance Management Management !he !he pur purpos pose of Syste System m document document is to describe describe the eternal eternal behavior behavior of the Attendance Attendance System System *euirem *euirements ents Specification defines and describes the operations" interfaces" performance" and uality assurance reuirements of the Attendance System !he document also describes the nonfunctional reuirements such as the user interfaces 't also describes the design constraints 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 reuirements for the software !he Software *euirements Specification (SRS) captures captures the complete complete software software reuirements reuirements for the system system"" or a portion of the system system 't is intended for the designers and developers.

1.2 1.2

Proj Projec ectt Scop Scopee

!his pro#ect is limited only on how the students attend the class and each module !his application will manage each student attendance in class And will limit for Uo$

1.3

Refer ferences


2.

Overal Overalll Desc Descri ript ption ion

2.1 2.1

Produ Product ct Persp Perspect ectiv ivee

+nline Student attendance system is a web application based system which will helps UoK to ma$e Attendance students and managing all necessaries information concern it online +nline Students attendance system has ,parts- administrator part" &ectures part and Student part %ach part has its own functions functions 2.2 Administrator

!his part is being used by users who have all privileges to access all information of +nline U!. Students attendance list system li$e /uman *esource !his part provides the option of ma$ing 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 !his part has the following Menus1. Home: !his menu shows all users general information on the system" and what0s reuired to

get into the system 2. Students !his lin$ helps the Admin to add new students and enable him or her to delete or edit the names of students 3. ourses

!his lin$ allows the admin to add and remove the courses according to the year of study and lecturer !. "ogout: %it the administrator administrator page and close your session" session" come bac$ to home page

1 c#ange password !his lin$ will help Administrator to change his2her password $. reports: !his lin$ will allow administrator to generate the general and daily report of the web

application


2.3 "ecturer

!his part is designed for the user which can be any lecturer who needs to ma$e the attendance of students A lecturer can see the following home page menus !o access its student3s first name and last name and password must be provided1. Home: !his menu shows all users general information on the system" and what0s reuired to get into

the system 2. "ogout:

%it the page and close the session" come bac$ to home page 3.

#ange password -

!his lin$ will help lecturer to change his2her password !. Ma%e Ma%e att atten enda danc ncee

!his will enable the lecturer to ma$e the attendance of students

2.! Student

!his part is designed designed for the students in order to allow them to chec$ their report of attendance !he students can see the following menus !o access their the attendance reports &. Home: !his menu shows all users general information on the system" and what0s reuired to get into

the system $. "ogout:

!his menu allows the student to uit the system and eit the page and close the session" come bac$ to home page 7.

#ange password -

!his lin$ will help the student to change his2her password '. Report

!his lin$ will allow the student to chec$ his or her report of attending report


2.2 2.2

Prod Produc uctt Feat Featur urees

2.3

User Classes Classes and Character Characteristic isticss


ame of a use case

escription

&ogin to the system

Administrator" or" Sta Staff" St Stude udent mu must gi give th their lo login an and pa password to perform all functionality of the system regarding them" if they don3t have them Admin have to register their accounts following certain condition

Attendance Attenda nce

!his is the action done by the lecturers


4hange password

!his is the ac action which helps every user to ch change his2her owner password any time time

4o 4ourses

!his action helps Administrator to add the courses in the system

5eneral report

!his function function helps administ administrator rator to generate the general report of the attendance

Student report

!his is where Admin made report on student

Student

!his !his functio function n helps helps the Student to chec$ the report of his or her attendance

2.4 2.4

Opera Operatin ting g En Envir vironm onment ent

2.4.1 HARDWARE REQUIREMENTS (Minimum Requirement)

2.4. 2.4.1 1

2.5



Minimum RAM: * 2GB or Above



Hard is%: *128 GB



+rocessor:* Intel Pentium 4(1.50 GHZ) or above

SOFT SOFTWA WARE RE REQUIREMENTS (minimum Requirement) 

,perating system: -indows



ront esign: VB.Net version 10.0, .NET framework 4.0



ront*/nd "anguage: 0isua 0isua basic



ac%*/nd: Oracle



ac%*/nd onnectiity: ADO.net

Design Design and Impl Implemen ementatio tation n Constrain Constraints ts

<$escribe any items or issues that will limit the options available to the developers. These might include) corporate or regulatory policies* hardware limitations +timing requirements, memory requirements* requirements* interfaces to other applications* specific technologies, tools, and databases to be used* parallel operations* language requirements* requirements* communications protocols* security considerations* design conventions or programming standards +for e-ample, if the customers organi"ation will be responsible for maintaining the delivered software.!


2.6 2.6

User User Docu Documen mentat tation ion

2.7

Assumpti Assumptions ons and Depende Dependencie nciess

3.

Syst System em Feat Featur ures es

3.1 3.1

Syst System em Feat Featur uree 1

<$ont really say 2System 3eature 4.5 State the feature name in #ust a few words.!

3.1.1

Descript Description ion and Priority Priority <rovide a short description of the feature and indicate whether it is of 6igh, 7edium, or Low priority. priority. 1ou 1ou could also include specific priority component ratings, such as benefit, penalty, cost, and ris' +each rated on a relative scale from a low of 4 to a high of 8.!

3.1.2

Stimulus Stimulus/Re /Respon sponse se Sequenc Sequences es
3.1.3

Function Functional al Requirem Requirements ents <0temi"e the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to e-ecute the use case. 0nclude how the product should respond to anticipated anticipated error conditions or invalid inputs. inputs. Requirements Requirements should be concise, complete, unambiguous, verifiable, and necessary. necessary. 9se 2T:$5 as a placeholder to indicate when necessary information is not yet available.! <;ach requirement should be uniquely identified with a sequence number or a meaningful tag of some 'ind.!

*%678-


*%679-

3.2 3.2

Syste System m Featur Featuree 2 (and (and so on) on)

4.

Extern External al Interf Interface ace Requir Requirem ement entss

4.1 4.1

User User In Inter terfa face cess

<$escribe the logical characteristics characteristics of each interface between the software product and the users. This may include sample screen images, any 90 standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions +e.g., help that will appear on every screen, 'eyboard shortcuts, error message display standards, and so on. $efine the software components for which a user interface is needed. $etails of the user interface design should be documented in a separate user interface specification.!

4.2 4.2

Hardw Hardware are Interf Interface acess

<$escribe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.!

4.3 4.3

Softw Software are In Inter terfac faces es

<$escribe the connections between this product and other specific software components +name and version, including databases, operating systems, tools, libraries, and integrated commercial components. 0dentify the data items or messages coming into the system and going out and describe the purpose of each. $escribe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. 0dentify data that will be shared across software components. 0f the data sharing mechanism must be implemented in a specific way +for e-ample, use of a global data area in a multitas'ing operating system, specify this as an implementation constraint.!

4.4 4.4

Commu Communi nicat cation ionss Interf Interface acess

<$escribe the requirements associated with any communications functions required by this product, including e/mail, e/mail, web browser, networ' server communications communications protocols, electronic forms, and so on. $efine any pertinent message formatting. 0dentify any communication standards that will be used, such as 3T or 6TT. Specify any communication security or encryption issues, data transfer rates, and synchroni"ation mechanisms.!


5.

Other Other Nonfun Nonfuncti ctiona onall Requir Requireme ements nts

5.1 5.1

Perfor Performan mance ce Requir Requireme ements nts

<0f there are performance requirements for the product under various circumstances, circumstances, state them here and e-plain their rationale, to help the developers understand the intent and ma'e suitable design choices. Specify the timing relationships for real time systems. 7a'e such requirements as specific as possible. 1ou may need to state performance requirements for individual functional requirements requirements or features.!

5.2 5.2

Safet Safety y Requi Requirem rement entss

5.3 5.3

Secur Security ity Requi Requirem remen ents ts

5.4 5.4

Softw Software are Qual Quality ity Attrib Attribute utess

6.

Othe Otherr Requ Requir irem emen ents ts

<$efine any other requirements not covered elsewhere in t he SRS. This might include database requirements, requirements, internationali"ation requirements, legal requirements, requirements, reuse ob#ectives for the pro#ect, and so on. (dd (dd any new sections that are pertinent pertinent to the pro#ect.!

Appendix A: Glossary <$efine all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. 1ou 1ou may wish to build a separate glossary that spans multiple pro#ects or the entire organi"ation, organi"ation, and #ust include terms specific to a single pro#ect in each SRS.!


Appendix B: Analysis Models S4S5/M ",- 6A7RAM


 ee 1


/ntity Reations#ip iagram


Appendix C: Issues List < This is a dynamic list of the open requirements requirements issues that remain to be resolved, including T:$s, pending decisions, information that is needed, conflicts awaiting resolution, and the li'e.!

Student Attendance Management System

Recommend Documents