Vnrvjiet: Name of The Experiment: Name of The Laboratory: Experiment No: Date
Vnrvjiet: Name of The Experiment: Name of The Laboratory: Experiment No: Date
Vnrvjiet: Name of The Experiment: Name of The Laboratory: Experiment No: Date
PROBLEM STATEMENT:
1) This forms the first and foremost step in the processing of exam application. After the first
round of verification done by the system, the information is in turn forwarded to the Exam
Controller.
2) The application is then processed manually based on the report given by the system. The
system also provides the student the list of exam dates.
3) The controller will be provided with fees details to display the current status of application
to the student, which they can view in their online interface.
4) After all the necessary criteria has been met, the original information is added to the
database and the hall ticket is sent to the student
VNRVJIET Name of the Experiment:
Name of the Laboratory:
Experiment No: Date:
1.1 PURPOSE
If the entire process of Issue of Hall ticket is done in a manual manner then it would take several
days for the hall ticket to be issued to the student. Considering the fact that the students who paid
the fees for the examination and the details will be verified, an Automated System becomes
essential to meet this verification and issuing process. So, this system uses several programming and
database techniques to elucidate the work involved in this process. As this is a matter of National
Security, the system has been carefully verified and validated in order to satisfy it.
1.2 SCOPE
• The System provides an online interface to the user where they can fill in their personal details and
submit the necessary documents (may be by scanning).
• The controller concerned with the issue of hall ticket can use this system to reduce his workload
and process the application in a speedy manner.
• Provide a communication platform between the student and the controller.
• Students will come to know their status of application and the date in which they must subject
themselves for manual document verification.
VNRVJIET Name of the Experiment:
Name of the Laboratory:
Experiment No: Date:
1.4 REFERENCES
IEEE Software Requirement Specification format.
1.7 OVERVIEW
SRS has two sections: overall description and specific requirements - Overall Description will
describe major role of the system components and inter-connections. Specific Requirements will
describe roles & functions of the actors.
VNRVJIET Name of the Experiment:
Name of the Laboratory:
Experiment No: Date:
2.6 CONSTRAINTS
• The applicants require a computer/Mobile to submit their information.
• Although the security is given high importance, there is always a chance of intrusion in the web
world which requires constant monitoring.
• The user has to be careful while submitting the information.
USECASE DIAGRAM
The purpose of a use case diagram in UML is to demonstrate the different ways that a user might
interact with a system. Create a professional diagram for nearly any use case using our UML diagram
tool.
ACTIVITY DIAGRAM
An activity diagram is a special kind of state diagram. An activity diagram is like a flow chart, showing flow of
control from activity to activity. An activity is an ongoing nonatomic execution within a state machine
VNRVJIET Name of the Experiment:
Name of the Laboratory:
Experiment No: Date:
STATECHART DIAGRAM
A statechart diagram shows the state machine focusing on the flow of control from state to state.
Contents:
● Simple states and composite states.
● Transitions, including events and actions.
SEQUENCE DIAGRAM
● A sequence diagram is an interaction diagram that emphasizes time ordering of messages.
● A sequence diagram shows the objects participating in the interaction by their lifelines and the messages
that they exchange/ arranged in time sequence.
VNRVJIET Name of the Experiment:
Name of the Laboratory:
Experiment No: Date:
COLLABORATION DIAGRAM
A Collaboration diagram is an interaction diagram that emphasizes the structural organization of the objects
that send and receive messages called collaboration diagram.
COMPONENT DIAGRAM
A component diagram, also known as a UML component diagram, describes the organization and
wiring of the physical components in a system. Component diagrams are often drawn to help model
implementation details and double-check that every aspect of the system's required functions is
covered by planned development
VNRVJIET Name of the Experiment:
Name of the Laboratory:
Experiment No: Date:
DEPLOYMENT DIAGRAM
A deployment diagram is a UML diagram type that shows the execution architecture of a system,
including nodes such as hardware or software execution environments, and the middleware
connecting them.
PACKAGE DIAGRAM
Package diagrams are structural diagrams used to show the organization and arrangement of various
model elements in the form of packages. A package is a grouping of related UML elements
VNRVJIET Name of the Experiment:
Name of the Laboratory:
Experiment No: Date: