srs exam suite report
Post on 09-Sep-2014
116 Views
Preview:
TRANSCRIPT
SOFTWARE REQUIREMENT SPECIFICATIONS
1
1. INTRODUCTION
Now a days, for any school or selection we need to correct Many number of
objective type questions papers. manually correcting the answer sheets is not better in this fast
Communication world. So we need to move on a special Type of approach which will make our
job is easier. Let us try online exam for faster, better, accurate way of accessing , and updating
the data. I assure that the given project can be simulated or can be Extended to conduct online
exams.
1.1. Purpose
This Desktop Application provides facility to conduct Examination.It saves time as it allows
number of students to give the exam at a time and displays the results as the test gets over, so
no need to wait for the result. It is automatically generated by the database.
User can register, login and give the test with his specific id, and can see the results as well.
Now a days, for any school or selection we need to correct
Many number of objective type questions papers. manually correcting the answer sheets is
not better in this fast Communication world. So we need to move on a special Type of
approach which will make our job is easier.
Let us try online exam for faster, better, accurate way of accessing , and updating the data.
I assure that the given project can be simulated or can be Extended to conduct online exams.
1.2. Scope
Scope of this project is very broad in terms of other manually taking exams.Few of them
are:-
_ This can be used in educational institutions as well as in corporateworld.
_ Can be used anywhere any time as it is a Desktop application(user Location doesn’t matter).
_ No restriction that examiner has to be present when the candidate takes the test.
2
1.3. Glossary
JRE- Java Runtime Environment
GUI - Graphical User Interface.
JDBC - JavaDataBase Connection.
RAM - Random Access Memory
ES - Examsuite.
OS - Operating System
DB - Databases
1.4.References
This desktop application has been prepared on the basis of discussion with team
members,faculty members and also taken information from following books and websites .
www.google.com
www.wikipedia.org
www.alexa.com Fundamental of Software Engineering By Rajiv Mall
Software Engineering : A practitioner’s approach Ed. By Pressman, Roger
Software Engineering Seventh Edition Ian Summerville
Software Engineering Ed.2 by Jalota & Pankaj.
Schaum’s Series, “Software Engineering”
1.5. Overview
The next chapter, the Overall Description section, of this document gives an overview of
the functionality of the product. It describes the informal requirements and issued to establish a
context for the technical requirements specification in the next chapter.The third chapter,
Requirements Specification section, of this document is written primarily for the developers and
describes in technical terms the details of the functionality of the product. Both sections of the
document describe the same software product in its entirety, but are intended for different
audiences and thus use different language.
3
2.OVERALL DESCRIPTION
This section of the SRS will describe the general factors that affect the product and its
requirements. This section does not state specific requirements. Instead, it provides a background
for those requirements, which are defined in detail in Section 3 of the SRS, and makes them
easier to understand
2.1. Product Perspective
The proposed Language Skill Exam System is an Exam System.
The test created for taking test has following stages
Login
Test
Result
Login:-
There is a quality login window because this is more secure than other login forms as in a normal
login window there are multiple logins available so that more than one person can access to test
with there individual login .But in this project there is only one login id i.e. administrator id and
Password by which a person enter the site. Hence it is more secure and reliable than previously
used on-line test simulators.
Test:
Test page is the most creative and important page in this project. It consists of 2 modules
namely:
Subject selection
Utilities
Subject selection:-
From the given choices the candidate can select his field (like C, C++ and JAVA etc) for
taking on with the test.
Utilities:-
It includes:-
4
Skip and come back to the question afterwards if needed.
Gives the result percentage and the candidate is elgible for that test or not..
2.2. Product Function
There are two different users who will be using this product:
University chancellor who will be acting as the administrator.
Students who will be accessing the ES
The features that are available to the Administrator are:
The administrator has the full fledged rights over the ES.
Can create/delete an accounts
Can hide any kind of features from the both of users.
Insert/delete/edit the information of available on ES.
Can access all the accounts of the faculty students.
The features available to the Students are:
Can view the different categories of Test available in their account.
Can view their marks.
Can view their percentage in the subject.
Can view the various reading material.
Can view and modify its profile but can modify it to some limited range.
5
2.2.1 Use Case Diagrams for Productive Function
LEVEL 1: Skeleton Structure
6
Login0.1
Main System
0.3
Database Connection
0.2
User System
Result
LEVEL 2:
Data Base
LEVEL 3:
Database
2.2.1
7
AddEmployee
DeleteEmployee
EditEmplyee
Sing upusers
Exam Results
Exam
System
Password /User name
2.3.USER CHARACTERISTICS
There are various kinds of users for the product. Usually web products are visited by
various users for different reasons.
The users include :
Students who will be using the above features by accessing the ES through the GUI.
Examiner who will prepare& load database into the software.
8
2.4. CONSTRAINTS
The whole implementation is done three modules. The first one is login,second one is
insertion to database model.and the third one is system design.Administrator and the second is
Examinee.
Module I
In this model if student entered as new user then ,he has to provide a details like
username ,password ,date of birth.If the student had account already then he will enter through
his user name and password.
Module II:-
The general theme behind a database is to handle information as an integrated whole. A database
is a collection of interrelated data stored with minimum redundancy to serve many users quickly
and effectively. After designing the input and output, the analyst must concentrate on database
design or how data should be organized around user requirements. The general objective is to
make information access, easy quick, inexpensive and flexible for other users.
Module III:
output form design: Computer output is the most important and direct source of information to
the user. Efficient, intelligible output design should improve the system relationship with the user
and help in decision-making. The outputs provide in the system are the softcopy report available
for printing. Printouts should be designed around the output requirement of the user. The output
devices to consider depend on the factor such as compatibility of the device with the system,
response time requirement and number of copies needed.
Input form design: Input Design is the process of converting user originated computer based
format. Inaccurate input data are the most common cause of errors in data processing .Errors
entered by data entry operators can be controlled by input design. The goal of designing input
data is to make data entry as easy, logical and free from errors as far as possible. In this system,
the input screens are developed according to the user requirement
9
MENU TREE
10
Module ILogin
Module IISign Up
Module IIIExam
Module IVResult
Registered User Registration Questions Result published
Main ModuleSystem
2.5 ASSUMPTIONS AND DEPENDENCIES
Full working of exam suite is dependent on the availability of Java Run Time Environment.
2.5.1 Assumptions:
In general it has been assumed that the user has complete knowledge of the system that means
user is not a naïve user. Any data entered by him/her will be valid. To make the software as user
friendly as possible but at the same time keeping in minds user requirements.
PC should be Windows 9X/NT/WorkStation or Windows 2000 with latest service pack.
2.5.2. Dependencies:
It depends that the one should follow the international standards for the generating the User ID &
should fill the related information in the proper format.
11
3. SPECIFIC REQIUREMENTS
3.1. External Interface Requirements
3.1.1. User Interfaces
Application will be accessed through a graphical user interface. The interface would be viewed
best using 800 x 600 pixels resolution. The software would be fully compatible with Microsoft
Windows. . No user would be able to access any part of the application without logging on to the
system.
3.1.2. Hardware Interfaces
Processor : Intel Pentium IV 2.4 GHZ or above
Clock speed : 500 MHZ
System bus : 32 bits
RAM : 256MB of RAM
HDD : 40 GB or higher
Monitor : SVGA COLOR
Keyboard : 108Keys
Mouse : 2 button mouse
3.1.3. Software Interfaces
OS : MS WINDOWS XP SP2
Environment : Java Runtime Environment 1.5
Front end : Core Java J2SDK1.5
Back end : Microsoft Access 2003
12
3.2 FUNCTIONAL REQUIREMENTS
This section gives the list of Functional and nonfunctional requirements which are
applicable to the Exam System. Functional requirements are nothing but the services provided by
the system to its end users.
There are three sub modules in this phase.
Candidate module.
Examiner module.
Administrator module.
The functionality of each module is as follows.
Candidate module: The candidate will logon to the software and take his examination. He can
also check his previous examinations marks and his details. The candidate will get result
immediately after the completion of the examination.
Examiner module: The database is prepared & loaded into the software. Selection for
examination can be done language wise by the examiner. The results will be displayed
immediately after completion of the examination.
Administrator module: The administrator collects all the results after successful completion of
the examination and sends to the head quarters as and when required.
13
3.3 OTHER NONFUNCTIONAL REQUIREMENTS
3.3.1. Performance Requirements
Some Performance requirements identified is listed below:
The database shall be able to accommodate a minimum of 10,000 records of students.
The software shall support use of multiple users at a time.
Password Management
Regular Database Archiving
There are no other specific performance requirements that will affect development.
3.3.2. Safety Requirements
The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.
3.3.3 Security Requirements
Some of the factors that are identified to protect the software from accidental or malicious
access, use, modification, destruction, or disclosure are described below.
Keep specific log or history data sets
Assign certain functions to different modules
Restrict communications between some areas of the program
Check data integrity for critical variables
Later version of the software will incorporate encryption techniques in the user/license
authentication process. Communication needs to be restricted when the application is validating
the user or license.
14
3.4 DESIGN CONSTRAINTS
Should anyone wish to work on further development of DRAGON WAR knowledge in any
of the following programming languages is required:
JAVA
MS Access
SQL
15
top related