Software Requirements Specification (SRS) For

Programmatic  Invoice

Table of Contents

1.  Introduction
1.1  Purpose
1.2  Scope
1.3  Definitions, Acronyms, and Abbreviations
1.4  References
1.5  Overview

2.  The Overall Description

2.1  Product Perspective
2.1.1 System Interfaces
2.1.2 Interfaces
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
2.1.5 Communications Interfaces
2.1.6 Memory Constraints
2.1.7 Operations
2.1.8 Site Adaptation Requirements
2.2  Product Functions
2.3  User Characteristics
2.4  Constraints
2.5 Assumptions and Dependencies
2.6 Apportioning of Requirement

3.  Specific Requirements

3.1 External interfaces Requirements 
          3.1.1  User Interface :
• Index Page
• Admin Login Screen
• Student Register Screen
• Admin Home Page
• Question Details (CRUD) Screen
• All Student Result Screen
• All Questions Screen
• Quiz Interface
• Score Of Student
            3.1.2 Hardware Interfaces
           3.1.3 Software Interfaces 
           3.1.4 Communications Interfaces
 
3.2 Software Product Features 
           3.2.1 project Information Maintenance            
•           Validity Checks 
•           Error Handling/ Response to Abnormal situations
•           Sequencing Information
3.2.2 Admin Info Maintenance
•          Validity Checks
•           Sequencing Information
•           Error Handling/ Response to Abnormal situations 
3.2.3 Quiz  Info Maintenance
•          Validity Checks
•           Sequencing Information
•           Error Handling/ Response to Abnormal situations 

3.3 Performance Requirements

 3.4 Design Constraints

 3.5 Software System Attributes

           3.5.1 Security 

           3.5.2 Maintainability 

           3.5.3 Portability

 3.6 Logical Database Requirements

 3.7 Other Requirement

1.  Introduction  
1.1  Purpose  
This project is developed to manage the examination process in University and Schools. Using
this , Teachers can easily manage the information of students and they can set paper easily
compared to normal process and students will find this interface more ineractive and easy to
use. 

The main purpose of this quiz management system project is developing a system that solves
the problem of managing student records in files for the teachers. 

This project will enhance teachers productivity and the information will be much more
maintainable.Because we can see the data of all students in just a single click. And chances of
loosing the records will fall down to a great extent because data is stored safely in a database
that is located in some safe server.

This quiz management system automates the examination process and make the process of
conducting exams easy.

1.2  Scope 

• The application is designed to maintain data related to the Students exams,

• Managing the questions asked in exam
• Detail information about the questions and results.
• Detail information about Students Result
• Generation of Marksheet

1.3  Definitions, Acronyms, and Abbreviations

• CRUD-Create,read,update,delete
1.4  References  
 
• www.geeksforgeeks.com
• www.javatpoints.com
• www.tutorialpoint.com

CLASS NOTES
• Java  programming 
• Software Engineering
• Algorithm Design and Analysis

1.5  Overview  
The rest of this SRS document describes the various system requirements, interfaces,
features and functionalities in detail.
2.  The Overall Description  
The system will be responsible for storing details of products, employees & customers. In which
product details will incorporate unique su code, name & retail price. Presence of unique su code
will enable ease in updating, deleting along with fetching details of the required product. 

Moreover, employee details will comprise a registration as well as a login page. Which will
enable new employees to register themselves and at the same time  pre-registered employees
will be able to login using a dedicated id and a password. Registered employees will be
equipped with an authority to fetch & modify the details of a product during the sale. This will
ultimately avert unauthorised individuals from accessing the software. Hence creating a secure
environment.

Customer details will be stored along with billing so as to keep a track on transaction history.
These details could be documented during the phase of billing. Customer details will consist of
Name, Mobile no., E-mail,Date/Time of the purchase along with bill number and total amount
,Bill no,and employee id. This will help workers in future to generate adequate discounts while
generating a bill.

2.1  Product Perspective

The need for software is felt, as the earlier system is manual thus requiring lot of
paperwork and making it difficult to keep track of all the previous
Qusetiions,Results and the updates done in questions.
The system will give the advantage of eliminating paperwork and in turn errors
caused by manual result making and it is a complete solution that helps you create
quiz, calculate scores, manage students records, manage changes done in exam
at different time ,provide security and even more.

2.1.1 System Interfaces

                 None
2.1.2 User Interfaces:
The application will have a user-friendly and menu based interface.
 Following screens will be provided:-
• Index Screen:- This screen is responsible for showing the options to login as
admin or to register as a student.
• Admin Login Screen:- This screen is responsible for requesting the admin to
enter  email and password. And also to verify the entered credentials from the
past records.
• Student Register Screen:- This screen is responsible for requesting the student
to register for exams and also update their information in records.
• Admin Home Page:- Responsible for showing all different options a admin have.
• Question Details (CRUD)  Screen:- Responsible to  Add, Delete, Update
questions present in the database
• All Student Result Screen:- Responsible for showing results of all students.
• All Questions Screen:- Responsible For Showing all questions that will be there
 in quiz.
• Quiz Interface:- Interface that will show questions and stores the marks and
updates marks.
• Student Score Screen:- Interface responsible for showing the marks scored in
quiz.

2.1.3 Hardware Interfaces

Processor Pentium 500 MHz
RAM  2 GB 
Hard Drive 4 GB Disk Drive Space(Available)

2.1.4 Software Interfaces

Database MYSQL

API JAVA JDK 16

Other Tool And Technology Java (JDK), Swings,AWT,MSWord
IDE used are NetBeans.
2.1.5 Communications Interfaces
• None

2.1.6 Memory Constraints

• At least 2 GB RAM and 4 GB space on the hard disk will be required for running
the application. 

2.1.7 Operations
• This product release will not cover any automated housekeeping aspects of the 
Database. The DBA at the client site will be responsible for manually deleting
old/non required data.Database backup and recovery will also have to be
handled by DBA. 

2.1.8 Site Adaptation Requirements

• The terminals at client sites will have to support the hardware and software
interface specified in above sections. 
2.2  Product Functions 
The system will only allow  authentic users to access the software. Based upon the intention the
user will be directed towards their desired destination. Depending upon the roles he/she will be
able to access specific modules of the system.
 • A summary of the major functions that the software will perform:
• A Login facility for enabling only authorised access to the system.
• Students are rendered with an option to Register themselves.
• Admin can Delete, Update, Create,Delete the questions. 
• Students can generate a marksheet along with an automated totalization of the marks.
• admin can make appropriate changes in the questions and results of students.
 
2.3  User Characteristics
• Educational level: Basic understanding of English language.
• Technical expertise: Should be comfortable using general-purpose applications
on a computer.
2.4  Constraints
• MySQL is used to define rules to allow or restrict what values can be stored in
columns. The purpose of inducing constraints is to enforce the integrity of a
database. MySQL is used to limit the type of data that can be inserted into a
table.

• Due to limited features of DBMS being used, performance tuning features will
not be applied to the queries and thus the system may become slow with the
increase in number of records being stored.

• Due to limited features of DBMS being used, database auditing will also be
provided.

• Admin at the college will have to implement a security policy to safeguard the
student related information from being modified by unauthorized users (by means
of gaining access to the backend database).
2.5 Assumptions and Dependencies
 
• Total Marks generated cannot be blank.
• Once quiz is attempted and then question changed then marks of old test will not be
modified.

2.6 Apportioning of Requirements

• Not Required

3.  Specific Requirements  

 
3.1 External Interfaces
   3.1.1 User Interface
   The following screens will be provided:

Index Page:
This will be the first page that will be projected. It will allow users to select either they are
student or admin and accodingly will redirect to the appropriate page.

Admin Login Screen:

This will also be one of the second screens that would be projected. This will include
various fields such as 
• UserName              
• Password                                

Also some buttons will be available 

• back button:- This will erase all the details written by the user and go back to
index page.

• Submit button:- This will store submit the data and match it with the admin
information.

Student Register Screen:

As the name suggests this screen is evidently responsible to handle  erroneous
information entered. This will include various fields such as 
• Full Name
• Roll Number           
• Father Name  
• Mother name              
• Phone Number    
• Email          
• Gender              
• 10th
• 12th             
• Graduation
• Address            
Also some buttons will be available 
• Back button:- This will erase all the details written by the user and redirect to
index page.
• Save And Next button:- This will store the data in SQL, to the table named
’Student’.

Admin Home Page:

The mother of all screens which allows admin to direct towards various screens such as
CRUD Details, All Student Result,All Questions screens. This screen will include
following buttons:-

•  Add New Question :-  this will add new question in database.
•  Update Queston :- this will update existing question from database.
• Delete Question :- this will direct towards deleting question from database
• All Student Result :-this will direct towards All Students result.
•  All Questions:- This will direct towards the all questions screen.
 
•

Question Details (CRUD) Screen:

 This screen helps the admin to modify the qusetions. This screen involves
fields for question details like:-

•  Question Id
•  Question
• Option1
• Option2
• Option3
• Option4
• Answer

More some buttons are also present in this screen

• ADD:- Responsible to add questions

• DELETE :- Responsible to delete questions
• Update;-Responsible to update questions

All Student Result Screen:

• This screen will show the result of all students who have attempted the quiz.

All Questions Screen:

This screen will show the whole list of question which are there in quiz.

Quiz Interface:
This screen shows the main feature of application and shows quiz.
• Question
• Options
• Timer
There are two buttons: Next,Submit and by next we will go to next question and by
clicking on submit we will submit the exam.

Score Of Student:

This screen will show the score of student in the quiz.

3.2 Software Product Features

3.2.1 Project Information Maintenance 
Description
This application will enable admin to create quiz .Modify questions ,maintain
results,questions in previous tests,information of students and their respective
institutes. Student Will answers questions of quiz obtain marks and then those
marks will be stored in database alonmg with student information for further use.  
Validity Checks 
 • Only admin with role Data Entry Operator will be authorised to access the admin
home page module. 
• Uid (E-mail) and password field while logging in cannot be blank.
• Student name and contact no. and roll number cannot be blank.
• Question id and name will be unique for every question.
• Student details using 10th and 12th and university cannot be blank.
 
  Sequencing Information
• Only admin with role Data Entry Operator will be authorised to access the result
information.
  Error Handling/ Response to Abnormal situatio ns
•  If any of the above validations/sequencing flow does not hold true, appropriate
error messages will be prompted to the user for doing the needful.

 3.2.2 Admin Information Maintenance

Description
Admin will login through admin login screen and then he can access
admin home page and set the exam and modify exam time to time and maintain
results of students.
  
 Validity Checks 
• Only admin with role Data Entry Operator will be authorised to access the admin
home page module. 
• Uid (E-mail) and password field while logging in cannot be blank.

 Sequencing Information 
• Registered admin  will be equipped with an authority to fetch & modify the details of a
students and questions. Unauthorised individuals will not be allowed to access the
database and hence cannot manipulate it.Admin can generate results also.

 Error Handling/ Response to Abnormal situations

•  If any of the above validations/sequencing flow does not hold true, appropriate
error messages will be prompted to the user for doing the needful.

3.2.3 Quiz Info Maintenance

Description
Student needs to first register for the exam and then we save it in database.And
then they will proceed for the mcq and save their answers.Then they will get marks
according to their performance in the test.
Validity Checks
• Student name and roll number cannot be blank.
• Phone number,10th and 12the marks should not be blank as well as name of the
university.
  Sequencing Information
• Presence of unique roll number will enable ease in updating, deleting along with fetching
details of the required product.
  Error Handling/ Response to Abnormal situations 
•  If any of the above validations/sequencing flow does not hold true, appropriate
error messages will be prompted to the user for doing the needful.

3.3 Performance Requirements

• None

3.4 Design Constraints

• None

3.5 Software System Attributes

3.5.1 Security
The application will be password protected. Admin will have to enter correct email,
password in order to access the application.

3.5.2 Maintainability
The application will be designed in a maintainable manner. It will be easy to incorporate
new requirements in the individual modules.
3.5.3 Portability
The application will be easily portable on any operating system, i.e., windows, linux or mac-os.

3.6 Logical Database Requirements 

• Students : Name, father name,mother name,tenth university name,tenth
percentage,tenth passing year,twelfth university name,twelfth percentage,twelfth
passing year,Graduation university name,Graduation percentage,Graduation
passing year,marks,DOB, Email, Mobile_Number, Gender, Address, Roll
Number.
• Questions : Questionno,Question,Option1,Option2,Option3,Option4,Answer

Class Diagram for DataBase

3.7 Other Requirements
•    none