System Features: 1.1.database - Storage

1.
System Features
1.1. Database – Storage
1.1.1. Description and Priority
Proposed Database is intended to store, retrieve, update, and
manipulate information related to university which include
 Profile of both users
 Student details
 My account
 Test results
1.1.2. Stimulus / Response Sequences
Responses for Administrator: The administrator can Login and
Logout. When the Administrator Logs into the Online Exam
system. The system will check for validity of login .If the Login and
password are valid, the response to this action is the administrator will
be able to modify, view, add, deleting and all other functions that can
be performed on the database.
Examination:
First of all the user/examinee gets a valid identification number (same
as
the roll no for a normal examination).The user can log on with this
identification no. and can take up the examination. After logging in the
user
can see various options and can choose the option from the menu.
1.2. Functional Requirements
This section gives the list of Functional and non functional

requirements which are applicable to the Online Exam
1
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.
3.2.1 Interface Requirements
This section describes how the software interfaces with other software
products or users for input or output.
3.2.1.1 User Interface
Application will be accessed through a Browser Interface. The interface

would be viewed best using 1024 x 768 and 800 x 600 pixels
resolution
setting. The software would be fully compatible with Microsoft Internet
2
Explorer for version 6 and above. No user would be able to access any
part of
the application without logging on to the system.
2. Non Functional Requirements

4.1. User Interfaces
Application will be accessed through a Browser Interface. The interface
would be viewed best using 1024 x 768 and 800 x 600 pixels
resolution
setting. The software would be fully compatible with Microsoft Internet
Explorer for version 6 and above. No user would be able to access any
part of
the application without logging on to the system.
4.2. Hardware Interfaces

Server Side:
 Operating System: Windows 9x/xp ,Windows ME
 Processor: Pentium 3.0 GHz or higher
 RAM: 256 Mb or more
 Hard Drive: 10 GB or more
Client side:
 Operating System: Windows 9x or above, MAC or UNIX.
 Processor: Pentium III or 2.0 GHz or higher.
 RAM: 256 Mb or more
4.3. Software Interfaces
Client Side : .HTML, Web Browser, Windows XP/2000/Vista

Web Server: .HTML, Windows XP/2000/Vista
4.4. Communications Interfaces
The Customer must connect to the Internet to access the
3
Website:
 Dialup Modem of 52 kbps
 Broadband Internet
 Dialup or Broadband Connection with a Internet Provider.
5.Other Nonfunctional
Requirements
5.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.
There are no other specific performance requirements that will affect
development
5.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.
5.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.
4
Communication needs to be restricted when the application is
validating the user or license. (i.e., using https).
5.4. Software Quality Attributes

The Quality of the System is maintained in such a way so that it
can be very user friendly to all the users.
The software quality attributes are assumed as under:
1)Accurate and hence reliable.
2) Secured.
3) Fast speed.
4) Compatibility.

System Features: 1.1.database - Storage

Uploaded by

Copyright:

Available Formats

System Features: 1.1.database - Storage

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Features: 1.1.database - Storage

Uploaded by

Copyright:

Available Formats

1.

1.2. Functional Requirements

This section gives the list of Functional and non functional

3.2.1 Interface Requirements

3.2.1.1 User Interface

Application will be accessed through a Browser Interface. The interface

2. Non Functional Requirements

4.2. Hardware Interfaces

4.3. Software Interfaces

Client Side : .HTML, Web Browser, Windows XP/2000/Vista

4.4. Communications Interfaces

The Customer must connect to the Internet to access the

5.1. Performance Requirements

5.2. Safety Requirements

5.3. Security Requirements

5.4. Software Quality Attributes

You might also like