Software R equirements Specification for
Page 1
Software Requirements Specification For
STUDENT INFORMATION SYSTEM (SIS) Version 1.0
Prepared by :Abhijeet Pradhan(ca160759) Madhusmita Das(170719007) Esha Dandapat(ca160746) Debi Prasanna Mohanty(ca160752)
Submitted to: Dr. Ramakrusha swain
SILICON INSTITUTE OF TECHNOLOGY DATE : 17.07.2018
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
Page 2
Table of Contents Table of Contents Revision History 1. Introduction 1.1 1.2 1.3 1.4 1.5
ii ii 1
Purpose1 Document Conventions 1 Intended Audience and Reading Suggestions Product Scope 1 References 1
1
2. Overall Description 2.1 2.2 2.3 2.4 2.5 2.6 2.7
2
Product Perspective 2 Product Functions 2 User Classes and Characteristics2 Operating Environment 2 Design and Implementation Constraints 2 User Documentation 2 Assumptions and Dependencies 3
3. External Interface Requirements 3.1 3.2 3.3 3.4
User Interfaces 3 Hardware Interfaces 3 Software Interfaces 3 Communications Interfaces
3
4. System Features 4.1 4.2
System Feature 1 4 System Feature 2 (and so on)
4 4
5. Other Nonfunctional Requirements 5.1 5.2 5.3 5.4 5.5
Performance Requirements Safety Requirements 5 Security Requirements 5 Software Quality Attributes Business Rules 5
3
4
4
5
6. Other Requirements Appendix A: Glossary Appendix B: Analysis Models Appendix C: To Be Determined List
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
5 5 5 6
Software Requirements Specification for
Page 3
Revision History Name Group :4
Date 24.07.18
Reason For Changes
Version
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
1.
Page 4
Introduction
MAD-E(SIS) w hose software requirements are specified in this document, including the version number -1.The student management system can handle all the details about a student. The details include college details , course details , student personal details ,academic details etc., the student management system is an automated version of manual student management system.
1.1
Purpose
The SRS document contains the complete software requirements for the online student information management system and describes the design decisions , architectural design and the detailed design needed to implement the system. It provides the visibility in the design and provides information needed for software support. It is a new reliable student management system with a great customer support.
1.2
Document Conventions
SRS : Software Requirement Specification SIS : Student Information System Font style(header and content) : Times Server : refer to the host machine Client : refers to the user of SIS
2.
Intended Audience and Reading Suggestions This document is created for the instructor of ‘OOAD’ for his review.
2.1
Product Scope ● ● ● ● ● ● ● ● ● ●
Provide a secure LOGIN environment (username and password for login) Provide username and password when student has taken admission Access to site anytime/anywhere Student can view their personal details Check fees and other details anytime/anywhere (fee management) Check academic details (attendance, results, notices) Check library details(book availability) Booking a book View return date of book Online fee payment
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
2.2
Page 5
References ● IEEE 830-1998 standard for writing SRS document.
3.
Overall Description
3.1
Product Perspective
3.2
Product Functions ● ● ● ● ●
LOGIN & HOMEPAGE PERSONAL DETAILS ACADEMIC DETAILS LIBRARY BOOK INFO FEE PAYMENT
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
3.3
Page 6
User Classes and Characteristics ● Students
3.4
Operating Environment ● ● ● ● ●
3.5
Hardware : Pentium IV processor or later Technology : Microsoft .net with SQL Server Language : C++,C OS/Platforms : windows 7 or later IE 7.0 or later with flash player
Design and Implementation Constraints ● The information of all students, Fees and library must be stored in a database that is accessible by the website. ● MS SQL Server will be used as SQL engine and database. ● The student information System is running 24 hours a day. ● Users may access SIS from any computer that has Internet browsing capabilities and an Internet connection. ● Users must have their correct usernames and passwords to enter into their online accounts and do actions. ● 3 months, 4 members, cost – 150000
3.6
User Documentation
This software package will come with a user’s guide to it’s interface actions. The details of the design Analysis , Design and Test cases of this software package will be delivered along with this software.
3.7
Assumptions and Dependencies
There are no assumptions made.
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
Page 7
4.
External Interface Requirements
4.1
User Interfaces Web-based Interface
4.2
Hardware Interfaces Pentium IV processor or later
4.3
Software Interfaces Windows 7 or later
4.4
Communications Interfaces
HTTP protocol with SSL (HTTPS)
5.
System Features(Functional Requirements)
5.1
System Feature 1
6.
● ●
6.1
Display LOGIN screen with below details ● Collect User Id and Password & authenticate After password validation, ● Allow user to enter the system & display the HOMEPAGE containing below info ● Menu options for all System Feature
System Feature 2
●
6.2
If user selects View Profile option from Homepage ● Display the details like (sname, sid, dateOfBirth, gender, email, address, mobile number) ● User should be able to update details of email and mobile number
System Feature 3
●
When user selects VIEW ACADEMIC DETAIL
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
●
6.3
Page 8
The page must show options to check attendance, Results, Notices and give Feedback ● Users selects respective options to check all the details
System Feature 4
●
6.4
When users selects the “Library Book Info ” option ● User should be displayed all the books he has taken from library along with received and return date ● When users Selects the ‘Booking Option’ then ▪ User should provide the book name, bookid, or book author ● The availability of the book will be shown(if available or not) ● Then he can book the book.
5 System Feature 5
●
When User selects the “Fee Management” option, ● Users should be able to view all the account information at once.(i.e. Canteen, cafeteria, hostel, etc)
●
When users select ‘Fee payment option’ ● User should be able to pay the desirable amount from the total amount. ● There should be various payment options like (internet banking, Debit/Credit card) ● If payment fails due to low balance or other technical error repayment/retry option should be there. ▪ When user select ‘print receipt’ option ● User Should get the print of payment done with all transaction details like amount paid, bill no, Date of payment and Reason of payment, mode of payment.
7.
Other Nonfunctional Requirements
7.1
1 Error handling
●
SIS product shall handle expected and unexpected errors in ways that prevent loss in information and long downtime period.
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
7.2
Page 9
5.2 Performance Requirements ● Responses to view information shall take no longer than 5 seconds to appear on the screen
7.3
5.3 Security Requirements ● Highly secured payment gateway for online fee payment ● Login page should be highly secured and login details must be encrypted ● System will use secured database
5.4 Safety
7.4
Requirements
● System use shall not cause any harm to human users.
7.5
5.5 Software Quality Attributes ●
Reliability Related ● System should have high reliability in critical modules like view personal details, view academic details, fee payment and other major processes
●
Maintainability Related ●
●
Reusability related ●
7.6
System should be highly maintainable: Good technical documents, Proper commenting inside programs, Coding standards & guidelines must be followed
Modules should have reusable functions
5.5 Business Rules ● No s uch business rule
8.
Other Requirements
Appendix A: Glossary SIS : Student Information system
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
Page 10
Appendix B: Analysis Models D ata flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams
Appendix C: To Be Determined List
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.