Professional Documents
Culture Documents
Version 1.0
Version History
Version Date Changes Made Done By Remarks
No
Introduction:
This proposed system provides the automation of Examination module. The Exam branch
content automates and facilitates the examination procedures. This program has the
features like Distribution and weightage of marks, Attendance requirements, Minimum
academic requirements, Award of class Lateral entry students etc.,
This section mainly briefs about who is the customer and what is customer business and the
problems customer is facing in the existing business. It also gives information on business aspects
considered for automation, goals of the project.
Target audience
Colleges examination cell,examination branch of a university.
About Customer
Provide details about the customer business and the problems customer is experiencing in
the existing business, which led him for going for this automation project.
Project Objectives
Provide details about goals of the project or things to be achieved by implementing this project in
customer business.
Scope
Identify the areas considered for automation in customer business as part of this project and areas
not considered.
Definitions
Term Definition
ATM Automatic Teller Machine
References
Provide information about documents, discussions, telecons and standards referred in creating this
requirements document
Assumptions
List the assumptions taken while preparing this requirements document
Environment
This section provides information about environment required to implement and operate this
application. It also identifies the minimum knowledge required for the users to operate the software
created as part of this project
Implementation environment
Hardware Environment
Identify the configuration of server required to host this application, in terms of processor capacity,
RAM, LAN card speed, Router, HDD capacity.....
Software Environment
Identify the software required to implement the application developed in terms of operating system,
front end, browsers, drivers, database….
User characteristics
List the minimum knowledge and skill the users need to have to operate this application
Functional Requirements
This section will list all the functional requirements of the application being developed and their
operating specification
Requirements lookup table
S.no Requirement Requirement name Source Stable Priority Need Verifiable
ID (Customer/vendor) Y/N Y/N
User
User
Requirement ID RTA_UC_01
Title Registration
Description Student should register before logging in to the account for feed
back.
Actor Student
Input Student details
Behavior Takes the student details required for login.
Takes username and password
Output Registered successfully.
Pre condition NA
Post condition NA
Exceptions If any of the fields are left ,fill the fill in the field exception raised.
Use case diagram
Registration
User
Special instructions NA
Requirement ID RTA_UC_02
Title Login
Description User has to login before applying for the required action. This is
also applicable to the Administrator for verifying the applications of
the users.
Actor Administrator/User
Input Username and password
Behavior Verifies the username and password
If valid logins to the home page.
Output Login successful.
Pre condition NA
Post condition NA
Exceptions If either username or password is invalid, error exception is raised.
Use case diagram
Login
Administrator/
User
Special instructions NA
Requirement ID RTA_UC_03
Title Logout
Description User and Administrator logs out after accomplishment of the
required task
Actor Administrator/User
Input Username and password
Behavior Logout of the respective page of the User and Administrator.
Output Logout successful.
Pre condition NA
Post condition NA
Exceptions NA
Use case diagram
Logout
Administrator/
User
Special instructions NA
Requirement ID RTA_UR_04
Title License Registration
Description User applies for the License.
Actor User
Input User’s personal details.
Behavior User applies for the Driving License.
Output Application sent.
Pre condition NA
Post condition NA
Exceptions User has to fill all the details provided in the application, if not Fill
all the fields exception is raised.
Use case diagram
Special instructions NA
Requirement ID RTA_UR_05
Title Vehicle Registration
Description User applies for the Vehicle Registration.
Actor User
Input User’s personal and Vehicle details.
Behavior User applies for the Registration of the vehicle.
Output Application sent.
Pre condition NA
Post condition NA
Exceptions User has to fill all the details provided in the application, if not Fill
all the fields exception is raised.
Use case diagram
Special instructions NA
Requirement ID RTA_UR_06
Title Registration fee
Description User pays Registration fee of the Vehicle and Driving License.
Actor User
Input Online payment.
Behavior User pays registration fee online using debit card.
Output Registration Payment success.
Pre condition NA
Post condition NA
Exceptions User has to enter the correct Debit card number in order to make
the payment successful, if not exception is raised.
Use case diagram
Special instructions NA
Requirement ID RTA_UR_07
Title Road Tax Payment
Description User pays road tax in order to get the permission to drive on road.
Actor User
Input Online Tax payment.
Behavior User pays Tax online using his/her debit card.
Output Tax Payment success.
Pre condition NA
Post condition NA
Exceptions User has to enter the correct Debit card number in order to make
the tax payment successful, if not exception is raised.
Use case diagram
Special instructions NA