IET~DAVV STUDY MATERIALS SRS.docx

IET DAVV STUDY MATERIAL
Software Requirement Specification
Guided By: Submitted By:
Dr. G.L.Prajapati Lokesh Nargesh(19I7029)
Madhur Jatiya(19I7030
Rani Ahire(20C7084)
Department of Computer Engineering / Information Technology
Institute of Engineering & Technology
Devi Ahilya Vishwavidyalaya, Indore(M.P.)
(www.iet.dauniv.ac.in)
11- 2022

Table of Contents
Table of Contents..................................................................................................................................... ii
1. Introduction........................................................................................................................................ 1
1.1 Purpose.............................................................................................................................................. 1
1.2 Document Conventions..................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions................................................................................. 1
1.4 Product Scope.................................................................................................................................... 1
1.5 References.......................................................................................................................................... 1
2. Overall Description............................................................................................................................. 1
2.1 Product Perspective............................................................................................................................1
2.2 Product Functions..............................................................................................................................2
2.3 User Classes and Characteristics..................................................................................................... 2
2.4 Operating Environment.....................................................................................................................2
2.5 Design and Implementation Constraints......................................................................................... 2
2.6 User Documentation.......................................................................................................................... 2
2.7 Assumptions and Dependencies....................................................................................................... 2
3. External Interface Requirements...................................................................................................... 3
3.1 User Interfaces.................................................................................................................................. 3
3.2 Hardware Interfaces........................................................................................................................ 3
3.3 Software Interfaces........................................................................................................................... 3
3.4 Communications Interfaces............................................................................................................. 3
4. System Features.................................................................................................................................. 3
4.1 System Feature 1............................................................................................................................. 4

4.2 System Feature 2 (and so on)......................................................................................................... 4
5. Other Nonfunctional Requirements................................................................................................ 4
5.1 Performance Requirements............................................................................................................ 4
5.2 Safety Requirements........................................................................................................................ 4
5.3 Security Requirements.................................................................................................................... 5
5.4 Software Quality Attributes............................................................................................................ 5
5.5 Business Rules.................................................................................................................................. 5
6. Other Requirements......................................................................................................................... 5
Appendix A: Glossary.............................................................................................................................. 5
Appendix B: Analysis Models................................................................................................................ 5
Appendix C: To Be Determined List..................................................................................................... 5

1. Introduction
1.1 Purpose
IET-DAVV Study material is a website that provides the notes, previous year's question papers, syllabus,
e-books and other course study material to the student of iet anyone can access the data upload on the
website can also upload the study material or his/her branch to help the upcoming new students in IET.
1.2 Document Conventions
The font we are working with Time New Roman size (20) for Headings and size(16) for usual details.
The text format we are following is Time New Roman size (14) for heading and description. This
application does not requires any special tool for performing any operation, this application can be easily
run in any smart phone.
1.3 Intended Audience and Reading Suggestions
This documents will capture all stackholders prefrences , different conflict and their resolution. Also , it
could be used by potential developers, design engineer , tester ,project managers e.t.c. This project has
been implemented under the guidance of college professor. This project is useful for students and the
mostly the new coming in IET.
1.4 Product Scope
The problem faced by many of the student that of study material that they cannot arrange or doesn’t know
about the exam pattern and lectures that they have missed. In many of the colleges the newly admitted
student feels alone and hesitate about asking the syllabus and other study related things. This website may
be very helpful for the newly admitted students that they can easily prepares themself for exams.
1.5 References
1. LittleHelp (http://littlehelp3.epizy.com/index.php)
2. LetsPrep! (https://letsprep.co.in/)
3. RGPV Notes(https://www.rgpvnotes.in/btech/grading-system-old/notes/)
4. NPTEL (https://nptel.ac.in/courses,)
5. SaiVidhya(https://saividya.ac.in/study-material-cse.html

2. Overall Description
Study material generally assists the students to enhance their learning process. This encourages students
to learn new concepts that significantly enhance their knowledge. This may provide a proper pathway for
the students to prepare for the exams and mid sem test(MST). This makes the students fearless from the
exams and about the notes.
The basic idea involved in here is that each item has to be in sequential form in database that the subject
related to the branch.The first step is in developing an object oriented design methodology for computer
applications as well as for database system is the use of UML (Unified Modelling Language) as a
standard notation for the modeling of real world objects. UML was conceived as a language for modeling
software. UML is also considered an industry standard modeling language with a rich graphical notation,
and comprehensive set of diagrams and elements. The list of notations includes use case diagrams, class
diagrams, and interaction diagrams describe sequences of events, package diagrams, activity diagrams,
state diagrams. It is used to specify, visualize, modify, construct and document the artifacts of an object-
oriented software-intensive system.
2.1 Product Perspective
2.2 Product Functions
This website are helpful for IET-DAVV Student if I was a first year student it is very useful for me I was
study material 1 semester. It is impactful of the work on real life/ end-user just because if I was student so
it helpful I was using this website for better reach.

2.3 User Classes and Characteristics
There are two user classes in IET-DAVV Study material website :- User ,Admin
User
Users are students, All the students can use this website for finding study material for their Branch and
Semester. The user would check every semester and branch for 1st sem to 8th sem user is a student this is
a major factor users can select the semester and branch. Enter the semester and the branch user can click
the search button and find the best results for him/her User input is required for making the successful
reservation.
Admin
IET Study Material Website team (Admin) is the administrative stakeholder of the software-intensive
system. Admin can able to update the information about the website. See reports, and check the
information of the user, and also the provided data is fully valid and true.
2.4 Operating Environment
2.4.1 Server Side :
Processor: Intel® Xeon® processor 3500 series
HDD: Minimum 500GB Disk Space
RAM: Minimum 16GB
OS: Windows 8.1, Linux
Database: SQL Server 2014 (SQL14)
2.4.2 Client side (minimum requirements):
Processor: Intel Dual Core
HDD: Minimum 80GB Disk Space
RAM: Minimum 1GB
OS: Windows 8, Linux.

2.5 Design and Implementation Constraints
The application will use Java, DBMS, html5, css3, JavaScript, as main web technologies. HTTP and FTP
protocols are used as communication protocols. FTP is used to upload the web application in live domain
and the client can access it via HTTP protocol. Several types of validations make this web application a
secured one and SQL Injections can also be prevented.
2.6 User Documentation
There will be no user manuals, online helps or tutorials as it is made as simple as web beginners can also
use it easily with best web GUI functionality.
2.7 Assumptions and Dependencies
The requirements for the user interface is developed under the assumption that user interface is a subsystem
of existing system for Study Matrial website which keeps and processes information about study materials
and also users can select the semester and branch to find material.

3. External Interface Requirements
3.1 User Interfaces
Website have very simple user interface for good experience. Developer name and photos are present in
the top of the home page and all the contributers name and their respective profiles with photos are
present in the remaining page.
3.2 Hardware Interfaces
Laptop with 8 GB RAM and 320 GB Storage:
Laptop or a PC is required with minimum 4 GB of RAM and 320 GB of storage with Operating System
windows 8 or higher, And RAM 4 GB to use the software efficiently.
Smartphone with minimum 4 GB RAM and 32 GB Storage:
A Smartphone is needed to execute the Application to check whether the development is going right or
not. We can use Emulator also but for speed we have to use Physical Android Phone so that our
Application executes fast.
Smartphone with minimum 4 GB RAM and 32 GB Storage:
A Smartphone is needed to execute the website to download and check whether the development is going
right or not. We can use Emulator also but for speed we have to use Physical Android Phone so that our
website executes fast.
3.3 Software Interfaces
<Describe the connections between this product and other specific software components (name and
version), including databases, operating systems, tools, libraries, and integrated commercial components.
Identify the data items or messages coming into the system and going out and describe the purpose of
each. Describe the services needed and the nature of communications. Refer to documents that describe
detailed application programming interface protocols. Identify data that will be shared across software
components. If the data sharing mechanism must be implemented in a specific way (for example, use of a
global data area in a multitasking operating system), specify this as an implementation constraint.>

3.4 Communications Interfaces
Communications Interfaces are the interface that belongs to any communications functions that are
required and are used in our software. Communication standards and Network server communications
protocols: HTTP, HTTPS, or FTP.

4. System Features
4.1 System Feature 1
4.1.1 Description and Priority
Our Website are flexible for all devices like ps, laptops, tables, even supported in smart
phones(android or ios devices).Response time of Website is very high due to this it can bhi run fast with
even average internet quality.
4.1.2 Stimulus/Response Sequences
4.1.3 Functional Requirements
Home Page was very simple and good looking. In the top of the website navigation bar present which
contains options of home, study material, developers, contributors, about and contact us etc. Developers'
and Contributors names and their respective profiles with photos are present in the remaining page.

5. Other Nonfunctional Requirements
5.1 Performance Requirements
● Our Website are flexible for all devices like ps, laptops, tables, even supported in smart
phones(android or ios devices).
● Response time of Website is very high due to this it can bhi run fast with even average internet
quality.
5.2 Safety Requirements
There is no any special need of safety requirement for the user but for the developer It is suggested that
the Data Stored on the Server should be encrypted with any algorithm, so that no any hacker or thief can
able to stole the Data.
5.3 Security Requirements
The Application is Fully Secured in the terms of login credentials there are many conditions which has
been applied to the User Authentication Activity, No any fraud user can able to Login into the
Application. Only those User can able to access the Application who has the Authentication to the
Application. Or the User which has been created by the Admin can only able to Login into the
Application.
5.4 Software Quality Attributes
Availability:
This attribute is indicative as to whether an application will execute the tasks it is assigned to perform.
Availability also includes certain concepts that relate to software security, performance, integrity,
reliability, dependability, and confidentiality. In addition, top-notch availability indicates that a software-
driven system will repair any operating faults so that service outage periods would not exceed a specific
time value.
Performance:

This attribute pertains to the ability of a software-driven system to conform to timing requirements. From
a testing point of view, it implies that Software Testing engineers must check whether the system
responds to various events within defined time limits. These events may occur in the form of clock
events, process interruptions, messages, and requests from different users, and others.
Testability:
Software testability indicates how well a software-driven system allows Software Testing professionals to
conduct tests in line with predefined criteria. This attribute also assesses the ease with which Software
Quality Assurance engineers can develop test criteria for a said system and its various components.
Engineers can assess the testability of a system by using various techniques such as encapsulation,
interfaces, patterns, low coupling, and more.
Usability:
Every software-driven system is designed for ease of use to accomplish certain tasks. The attribute of
usability denotes the ease with which users are able to execute tasks on the system; it also indicates the
kind of user support provided by the system. The most wellknown principle for this property is KISS
(Keep It Simple Stupid). In addition, Software Quality Assurance engineers must test software to check
whether it supports different accessibility types of control for people with disabilities. Usability has a
critical and longstanding bearing on the commercial fortunes of a software application or package.
Functionality:
This attribute determines the conformity of a software-driven system with actual requirements and
specifications. Most Software Testing professionals view this attribute as crucial and a foremost
requirement of a modern application, and would therefore advocate the performance of tests that assess
the desired functionality of a system in the initial stages of Software Testing initiatives.
5.5 Business Rules
Business Rules A business rule is anything that captures and implements business policies and practices.
A rule can enforce business policy, make a decision, or infer new data from existing data.This includes
the rules and regulations that the System users should abide by. This includes the cost of the project and
the discount offers provided. The users should avoid illegal rules and protocols. Neither admin nor
member should cross the rules and regulations.

6. Other Requirements
There are different categories of users namely Admin, Users etc. Depending upon the category of user the
access rights are decided. It means if the user is anadministrator then he can be able to modify the
data,delete, append etc. All other users except the Admin only have the rights to retrieve the information
about database.
Appendix A : Analysis Models
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-
transition diagrams, or entity-relationship diagrams.>
Appendix C: To Be Determined List

IET~DAVV STUDY MATERIALS SRS.docx

More Related Content

Similar to IET~DAVV STUDY MATERIALS SRS.docx

More from Madhur Jatiya

Recently uploaded

IET~DAVV STUDY MATERIALS SRS.docx