CptS 322 - SRS: Development of Student Management System

This Software Requirements Specification (SRS) document outlines the requirements for the development of a student management system. The document begins with an introduction, defining the purpose, scope, definitions, and references. It then provides a general description of the product, including its perspective, functions, user characteristics, constraints, and assumptions. Specific requirements are detailed, covering user interfaces, hardware, software, and communications interfaces. Functional requirements such as registration and attendance management are described, along with use cases and class diagrams. Non-functional requirements, including performance, reliability, availability, security, maintainability, and portability, are also addressed. Design constraints, logical database requirements, and other requirements are included. The document incorporates analysis models such as sequence diagrams, data flow diagrams, and state-transition diagrams, along with a change management process and appendices containing a glossary and user interface examples. This SRS serves as a comprehensive guide for the development of the student management system, ensuring clarity and reducing potential errors during the development process. The system aims to streamline student information management and enhance organizational efficiency.

Software Requirements Specification Template
CptS 322—Software Engineering
9 February 2005
The following annotated template shall be used to complete the Software Requirements
Specification (SRS) assignment of WSU-TC CptS 322. The instructor must approve any
modifications to the overall structure of this document.
Template Usage:
Text contained within angle brackets (‘<’, ‘>’) shall be replaced by your project-specific
information and/or details. For example, <Project Name> will be replaced with either ‘Smart
Home’ or ‘Sensor Network’.
Italicized text is included to briefly annotate the purpose of each section within this template.
This text should not appear in the final version of your submitted SRS.
This cover page is not a part of the final template and should be removed before your SRS is
submitted.
Acknowledgements:
Sections of this document are based upon the IEEE Guide to Software Requirements
Specification (ANSI/IEEE Std. 830-1984). The SRS templates of Dr. Orest Pilskalns (WSU,
Vancover) and Jack Hagemeister (WSU, Pullman) have also be used as guides in developing this
template for the WSU-TC Spring 2005 CptS 322 course.
WSU-TC CptS 322 Software Requirements Specification Template

Development of Student Management System
for Willowbrook School
Software Requirements Specification
<Version>
<Date>
<Your Name>
Lead Software Engineer
Prepared for
WSU-TC CptS 322—Software Engineering Principles I
Instructor: A. David McKinnon, Ph.D.
Spring 2005

Development of Student Management System for Willowbrook School
Revision History
Date Description Author Comments
<date> Version 1.0 <Your Name> <First Revision>
Document Approval
The following Software Requirements Specification has been accepted and approved by the
following:
Signature Printed Name Title Date
<Your Name> Lead Software Eng.
A. David McKinnon Instructor, CptS 322
Software Requirements Specification Page ii

Development of Student Management System for Willowbrook School
Table of Contents
REVISION HISTORY................................................................................................................................................II
DOCUMENT APPROVAL........................................................................................................................................II
1. INTRODUCTION.....................................................................................................................................................1
1.1 PURPOSE...............................................................................................................................................................1
1.2 SCOPE...................................................................................................................................................................1
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS................................................................................................1
1.4 REFERENCES.........................................................................................................................................................1
1.5 OVERVIEW............................................................................................................................................................2
2. GENERAL DESCRIPTION....................................................................................................................................2
2.1 PRODUCT PERSPECTIVE........................................................................................................................................2
2.2 PRODUCT FUNCTIONS...........................................................................................................................................2
2.3 USER CHARACTERISTICS......................................................................................................................................2
2.4 GENERAL CONSTRAINTS.......................................................................................................................................2
2.5 ASSUMPTIONS AND DEPENDENCIES......................................................................................................................3
3. SPECIFIC REQUIREMENTS................................................................................................................................3
3.1.1 User Interfaces.............................................................................................................................................3
3.1.2 Hardware Interfaces....................................................................................................................................3
3.1.3 Software Interfaces.......................................................................................................................................3
3.1.4 Communications Interfaces..........................................................................................................................3
3.2 FUNCTIONAL REQUIREMENTS...............................................................................................................................3
3.2.1 Registration..................................................................................................................................................3
3.2.2 Attendance Management..............................................................................................................................4
3.3 USE CASES............................................................................................................................................................4
3.3.1 Use Case #1..................................................................................................................................................4
3.3.2 Use Case #2..................................................................................................................................................5
3.4 CLASSES / OBJECTS..............................................................................................................................................6
3.4.1 Schedule.......................................................................................................................................................6
3.4.1.1 Attributes...................................................................................................................................................6
3.4.1.2 Functions...................................................................................................................................................7
3.4.2 Student_attendance......................................................................................................................................7
3.4.1 Schedule.......................................................................................................................................................7
3.4.1.1 Attributes...................................................................................................................................................7
3.4.1.2 Functions...................................................................................................................................................7
3.5 NON-FUNCTIONAL REQUIREMENTS......................................................................................................................7
3.5.1 Performance.................................................................................................................................................7
3.5.2 Reliability.....................................................................................................................................................7
3.5.3 Availability...................................................................................................................................................7
3.5.4 Security.........................................................................................................................................................7
3.5.5 Maintainability.............................................................................................................................................7
3.5.6 Portability.....................................................................................................................................................7
3.6 INVERSE REQUIREMENTS......................................................................................................................................8
3.7 DESIGN CONSTRAINTS..........................................................................................................................................8
3.8 LOGICAL DATABASE REQUIREMENTS..................................................................................................................8
3.9 OTHER REQUIREMENTS........................................................................................................................................8
4. ANALYSIS MODELS..............................................................................................................................................9
4.1 SEQUENCE DIAGRAMS..........................................................................................................................................9
4.3 DATA FLOW DIAGRAMS (DFD).........................................................................................................................10
Software Requirements Specification Page iii

Development of Student Management System for Willowbrook School
4.2 STATE-TRANSITION DIAGRAMS (STD)..............................................................................................................11
5. CHANGE MANAGEMENT PROCESS..............................................................................................................11
BIBLIOGRAPHY.......................................................................................................................................................13
A. APPENDICES........................................................................................................................................................15
A.1 APPENDIX 1: GLOSSARY....................................................................................................................................15
A.2 APPENDIX 2: USER INTERFACE..........................................................................................................................16
A) HOME PAGE.........................................................................................................................................................16
B) STUDENT LOGIN..................................................................................................................................................17
C) Faculty Login......................................................................................................................................................18
Software Requirements Specification Page iv

Development of Student Management System for Willowbrook School
1. Introduction
The software requirement specification is created by the project manager for the development of
the information system and stating the main purpose, scope and limitation of the project. The
document is created for including the steps followed for the development of the information
system. A SDLC model is used for the development of the project and the requirement is
categorized into functional and nonfunctional requirements for the identification of the needs of
the information system. Different models such as class diagram, use case, Sequence Diagrams,
Data Flow Diagrams (DFD), and State-Transition Diagrams (STD) are used for designing the
information system.
1.1 Purpose
The main purpose of the software requirement specification document is to make the
requirement of the project clear and reduce the chances of errors during the development of the
information system. The audience of the SRS document are the stakeholders associated with the
project.
1.2 Scope
The software product required for the development of the information system is Microsoft Visual
Studio 2012, Microsoft Access 2013, etc.
Microsoft Visual Studio is used for building the interface of the information system with proper
validation that would restrict the user to input wrong information into the information system.
Microsoft Access is used for the development of the database of the information system and
store the details of the student and the courses inputted by the users.
The main purpose of the development of the information system is to allow the administrator to
manage the student information of the school and reduce the error in the management process for
increasing the efficiency of the organization.
With the implementation of the information system in the organization the overhead cost can be
reduced and the different level of users can use the system for getting the details such as the
student can access the information system for getting their time tables, exam schedules, teachers
can use it for tracking the record of a student and access the Couse materials, etc.
1.3 Definitions, Acronyms, and Abbreviations
For the development of the student management system the records of the student must be
handled and maintenance of the information manually is difficult (Nassif, Capretz & Ho, 2016).
The manual management of the information system can cause error and thus there is a
requirement for the up gradation of the current operation and develop the information system
according to the requirement of the organization.
1.4 References
David, F., & David, F. R. (2016). Strategic management: A competitive advantage approach,
concepts and cases
Software Requirements Specification Page 1

Development of Student Management System for Willowbrook School
Massacci, F., Paci, F., & Tedeschi, A. (2014). Assessing a requirements evolution approach:
Empirical studies in the air traffic management domain. Journal of Systems and Software,
95, 70-88.
Nassif, A. B., Capretz, L. F., & Ho, D. (2016). Enhancing use case points estimation method
using soft computing techniques. arXiv preprint arXiv:1612.01078.
1.5 Overview
For the development of the information system the functionality of the project should be
identified with the aim of the project. The targeted users should be identified before starting the
development of the information system and the constraints for the development should be
identified for removal of the risk and increasing the efficiency of the information system (David
& David, 2016). The requirement that is not clear should be assumed depending upon the
circumstances and the development process should never be stopped.
The SRS document is organized describing the specific requirement of the project followed by
the functional requirement and the nonfunctional requirements. The model used for the
development of the information system are also added in the document for making the
requirement clear for the software development team.
2. General Description
There are different factors affecting the development of the information system such as the
unavailability of the project team members and cost overrun. A risk analysis should be made and
a risk mitigation plan should be prepared for handling the risk arise during the development of
the information system.
2.1 Product Perspective
The main perspective of the final information system is to reduce the effort of the employees and
provide faster access of the information residing in the information in order to reduce the waiting
time.
2.2 Product Functions
The interface of the information system is kept simple and all the functionality are added for
aligning the business process with the information system and increasing the efficiency of the
organization.
2.3 User Characteristics
The users are required to register into the information system with all their details for using the
information system. The students and the faculty are categorized and different level of
permission are given on their accounts for using the information system.
2.4 General Constraints
Sudden change in the requirement can act as a constraint for the development of the project. A
change management plan is necessary for handling the change in the requirement of the project.
Software Requirements Specification Page 2

Development of Student Management System for Willowbrook School
2.5 Assumptions and Dependencies
It is assumed that the resources required for the development of the project would be available
during the course of development of the information system. The project is dependent on the
time and budget and it should be estimated properly (Massacci, Paci & Tedeschi, 2014). The
software and hardware should be available and the database should be developed according to
the requirement for the development of the project.
3. Specific Requirements
The requirement for the development of the information system are listed as follows:
 To create different group of users for viewing and accessing the information residing in
the information system.
 To be able to edit the information inputted by the different levels of users into the
information system
 To be able to generate report regarding the activity of the users
 To make the information system secure from unauthorized access
 To record the attendance of the students automatically and store the details
3.1.1 User Interfaces
 The user interface should be kept simple
 The requirement are analyzed for the generation of the report.
 Refer to appendices
3.1.2 Hardware Interfaces
Environment i3 6th generation
Configuration RAM – 4 Gb HDD – 500 Gb
Operating System Windows 8.1/ Windows 10
3.1.3 Software Interfaces
Front End Microsoft Visual Studio 2012
Front End PHP
Back End Microsoft Access 2015
Back End My SQL
3.1.4 Communications Interfaces
The central database of the information system can be accessed using a computer connected with
the local area network of the school.
3.2 Functional Requirements
The following functionality should be included for the development of the student management
system.
3.2.1 Registration
3.2.1.1 The registration of the student is important for inputting the details in the information
system.
Software Requirements Specification Page 3

Development of Student Management System for Willowbrook School
3.2.1.2 The name of the user, address, course name, qualification, contact number should be
inputted in the information system.
3.2.1.3 The validation of the information is important for increasing the consistency of the
information system.
3.2.1.4 A form should be given to the users that should be filled and validated for successfully
registration into the information system.
3.2.1.5 The details of the information system should be checked for reducing the errors occurring
in the information system and increasing the efficiency.
3.2.2 Attendance Management
3.2.2.1. The system should be able to track the attendance of the student and produce a bulletin
with the details of the attendance for the month.
3.2.2.2. The student should login into the information system from their college computers or
biometric devices for inputting their attendance.
3.2.2.3. The verification of the identity is important for inputting the attendance into the
information system.
3.2.2.4. The student should click on the login button or place their finger to input the attendance.
3.2.2.5. An error message should be displayed if the verification is not successful.
3.3 Use Cases
3.3.1 Use Case #1
Software Requirements Specification Page 4

Development of Student Management System for Willowbrook School
3.3.2 Use Case #2
Software Requirements Specification Page 5

Development of Student Management System for Willowbrook School
3.4 Classes / Objects
3.4.1 Schedule
3.4.1.1 Attributes
 Schedule_id
 Schedule_room_id
 Schedule_start_date
 Schedule_end_date
 Schedule_course_id
Software Requirements Specification Page 6

Development of Student Management System for Willowbrook School
 Schedule_Venue_id
3.4.1.2 Functions
 Student_schedule
 Rooms
 Courses
 Venue
3.4.2 Student_attendance
3.4.1 Schedule
3.4.1.1 Attributes
 attendance_id
 attendance_student_id
 attendance_date_id
3.4.1.2 Functions
 Student_schedule
3.5 Non-Functional Requirements
3.5.1 Performance
The information system can be used for tracking the records of the students and the updating the
information residing in the database information system. The response time of the system should
be minimum and the performance should not be down with the increase in the number of users.
3.5.2 Reliability
The remote connectivity to the centralized database is restricted for increasing the security of the
information system and the congestion in the network is reduced with the use of high bandwidth
cables.
3.5.3 Availability
The system should be available to all the users and authorized users should be able to use all the
functionality of the information system.
3.5.4 Security
Only authorized users and the administrator are allowed to assign permission and adding new
accounts. The accounts are password protected for securing it from unauthorized access.
3.5.5 Maintainability
The database needs to be periodically backed up for avoiding data loss.
3.5.6 Portability
The information system is developed in visual studio 2012 and is a web based application and
can run in any of the web browser such as chrome, Firefox, etc.
Software Requirements Specification Page 7

Development of Student Management System for Willowbrook School
3.6 Inverse Requirements
The boundary for the development of the information system should be identified for the
identification of the inverse requirement of the project. The system shall never be down because
it may cause a huge loss for the organization.
3.7 Design Constraints
The information system is used for the improvement of the security and the login option restricts
the unauthorized users to use the information system. The rights are given to the authorized users
and it is made to tolerate faults and reliable. A backup of the information system should be kept
for avoiding the loss of data.
3.8 Logical Database Requirements
Database is used for storing the student information and relational database is used for the
integration of the data.
3.9 Other Requirements
The other requirement used for the development of the information system is to secure the local
area network of the school campus for increasing the security of the information system.
Firewalls should be used for blocking the unknown IP address and secure the database should be
encrypted such that it cannot be accessed by the hackers for illegal use.
Software Requirements Specification Page 8

Development of Student Management System for Willowbrook School
4. Analysis Models
4.1 Sequence Diagrams
Software Requirements Specification Page 9

Development of Student Management System for Willowbrook School
4.3 Data Flow Diagrams (DFD)
Software Requirements Specification Page 10

Development of Student Management System for Willowbrook School
4.2 State-Transition Diagrams (STD)
5. Change Management Process
 Identification of the improvement that can be made for the development of the
information system
 Development of the business case for the inclusion of stakeholders in the development
process
 Creation of a road map for the implementation of the IT services
 Allocation of resources and data for the evaluation of the information.
Software Requirements Specification Page 11

Development of Student Management System for Willowbrook School
 Communicating with the stakeholders for the execution of the change in the business
process
 Monitoring and management of the constraints and dependencies
 Reviewing the changes for continuous improvement of the organization.
Software Requirements Specification Page 12

Development of Student Management System for Willowbrook School
Bibliography
Ameller, D., Ayala, C., Cabot, J., & Franch, X. (2013). Non-functional requirements in
architectural decision making. IEEE software, 30(2), 61-67.
Bahill, A. T., & Madni, A. M. (2017). Discovering system requirements. In Tradeoff Decisions
in System Design (pp. 373-457). Springer International Publishing.
Barai, G. R., Krishnan, S., & Venkatesh, B. (2015, October). Smart metering and functionalities
of smart meters in smart grid-a review. In Electrical Power and Energy Conference
(EPEC), 2015 IEEE (pp. 138-145). IEEE.
Bharamagoudar, S. R., Geeta, R. B., & Totad, S. G. (2013). Web based student information
management system. International Journal of Advanced Research in Computer and
Communication Engineering, 2(6), 2342-2348.
Buede, D. M., & Miller, W. D. (2016). The engineering design of systems: models and methods.
John Wiley & Sons.
Currie, K., McCallum, J., Murray, J., Scott, J., Strachan, E., Yates, L., & Wright, M. (2014).
Developing a national computerised absence monitoring and management system to
reduce nursing student attrition: Evaluation of staff and student perspectives. Nurse
education today, 34(5), 738-743.
David, F., & David, F. R. (2016). Strategic management: A competitive advantage approach,
concepts and cases.
Díaz, F. J., Schiavoni, M. A., Osorio, M. A., Amadeo, A. P., & Charnelli, M. E. (2015).
Integrating a learning management system with a student assignments digital repository:
a case study. International Journal of Continuing Engineering Education and Life Long
Learning, 25(2), 138-150.
Eichler, G., Erfurth, C., & Luke, K. H. (2014, June). Student Interaction Communities social
requirements reflected by a tool and system landscape. In Innovations for Community
Services (I4CS), 2014 14th International Conference on (pp. 47-54). IEEE.
Govaerts, S., Cao, Y., Vozniuk, A., Holzer, A., Zutin, D. G., Ruiz, E. S. C., ... & Tsourlidaki, E.
(2013, October). Towards an online lab portal for inquiry-based stem learning at school.
In International Conference on Web-Based Learning (pp. 244-253). Springer Berlin
Heidelberg.
Hansen, B. D., Wills, H. P., Kamps, D. M., & Greenwood, C. R. (2014). The effects of function-
based self-management interventions on student behavior. Journal of Emotional and
Behavioral Disorders, 22(3), 149-159.
Kim, C. J., Kim, J., Hong, T., Koo, C., Jeong, K., & Park, H. S. (2015). A program-level
management system for the life cycle environmental and economic assessment of
complex building projects. Environmental Impact Assessment Review, 54, 9-21.
Lisitsyna, L., Lyamin, A., & Skshidlevsky, A. (2014). Estimation of student functional state in
learning management system by heart rate variability method. Smart Digital Futures,
726-731.
Marlow, A. H., Lea, E. J., Mason, R. L., & Altmann, E. (2016). Nursing students' preferences for
professional experience placement: Investigation of 8 years of student placement
management system data. In NETNEP 2016, 6th International Nurse Education
Conference.
Software Requirements Specification Page 13

Development of Student Management System for Willowbrook School
Massacci, F., Paci, F., & Tedeschi, A. (2014). Assessing a requirements evolution approach:
Empirical studies in the air traffic management domain. Journal of Systems and Software,
95, 70-88.
Nassif, A. B., Capretz, L. F., & Ho, D. (2016). Enhancing use case points estimation method
using soft computing techniques. arXiv preprint arXiv:1612.01078.
Saulnier, B. (2015). The flipped classroom in systems analysis & design: Leveraging technology
to increase student engagement. Information Systems Education Journal, 13(4), 33.
Swink, M., Melnyk, S. A., Cooper, M. B., & Hartley, J. L. (2014). Managing Operations: Across
the Supply Chain (pp. 248-249). New York, NY: McGraw-Hill/Irwin.
Software Requirements Specification Page 14

Development of Student Management System for Willowbrook School
A. Appendices
A.1 Appendix 1: Glossary
DFD : Data Flow Diagram
ERD : Entity Relationship Diagram
SRS : Software Requirement Specification
SQL : Structured Query language
STD : State Transition Diagram
Software Requirements Specification Page 15

Development of Student Management System for Willowbrook School
A.2 Appendix 2: User Interface
A) Home Page
Software Requirements Specification Page 16

Development of Student Management System for Willowbrook School
B) Student Login
Software Requirements Specification Page 17

Development of Student Management System for Willowbrook School
C) Faculty Login
Software Requirements Specification Page 18