Beruflich Dokumente
Kultur Dokumente
REGISTRATION
SYSTEM
ACKNOWLEDGEMT
TABLE OF
CONTENTS
Table of contents:
S.n
o
Content
Page no
PROBLEM STATEMENT
14
1
2
DOMAIN MODEL AND UML CLASS DIAGRAM
IDENTIFYING CONCEPUTAL
AND DOMAIN MODEL
UML CLASS DIAGRAM
CLASS
INTERACTION DIAGRAM
SEQUENCE DIAGRAM
COMMUNICATION DIAGRAM
LAYER
23
25
29
31
35
38
42
50
59
LIST OF FIGURES
LIST OF FIGURES:
Fig.no Name of the figure
Page no
15
Fig2.2
Fig2.3
Fig2.4
Fig2.5
Fig2.6
Fig2.7
Fig2.8
Fig2.9
Fig3.1
Fig3.2
Fig4.1
Fig4.2
Fig5.1
Fig5.2
Fig6.1
17
18
18
19
19
20
20
21
24
26
30
31
38
41
43
Fig9.1
Fig9.2
Fig9.3
Fig9.4
Fig9.5
Fig9.6
60
61
61
62
62
63
LIST OF TABLES
LIST OF TABLES:
Table
no
Table
3.1
Table
7.1(a)
(b)
Table
7.2(a)
(b)
Page no
23
46
48
PROBLEM
STATEMENT
EX.NO:1
DEVELOPING PROBLEM STATEMENT
AIM:
To write a problem statement on exam registration system .
PROBLEM ANALYSIS :
The exam registration is an application in which applicant can register themselves for the
exam. The details of the students who have registered for the examination will be stored in a
database and will be maintained. The registered details can then be verified for any fraudulent
or duplication and can be removed if found so. The database which is verified can be used to
issue hall tickets and other necessary materials to the eligible students.
PROBLEM STATEMENT
Exam registration system is used in the effective dispatch of registration from to all of
the students this system adopts a comprehensive approach to minimize the manual work and
schedule resources, time in cogent manner the core of the system is to get the online
registration from (with details such as name , reg.no , etc.,) filled by the student whose
statement is verified for it is genuineness by the exam registration system with respect to the
already existing information in the database. This forms the first and fore most 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, the application is then processed manually based on the
report given by the system also provided the student list of exam dates.
The process of students accessing the registration application and applying for the
examination by filling out the form with proper details and then the authorities verify those
details given for truth and correctness are sequenced through steps
a. The students access exam registration application.
b. They fill out the form with correct and eligible details.
c. They complete the payment process.
d. The authorities verify or check the details.
10
CONTENT
1. Introduction
2. Objective
3. Overview
4. Purpose
5. Scope
6. Functionality
7. Usability
8. Performance
9. Reliability
1. INTRODUCTION
Exam Registration application is an interface between the student and the authority
responsible for the Exams. It aims at improving the efficiency in the registration of exams and
reduces the complexities involved in it to the maximum possible extent.
2. OBJECTIVE
The main objective of Exam Registration System is to make applicants register
themselves and apply for the exam. Exam Registration system provides easy interface to all
the users to apply for the exam easily.
3. OVERVIEW
The overview of the project is to design an exam registration tool for the registration
process which makes the work easy for the applicant as well as well as the authorities of
Exam. Authorities of the exam can keep track of and maintain the database of the registered
applicants for the exam.
4. PURPOSE
The purpose of exam registration system is to register for the exam in an easier way and
to maintain register details in an effective manner.
5. SCOPE
11
The scope of this Exam registration process is to provide easy interface to the applicants
where they can fill their details and the authorities maintain those details in an easy and
effective way.
6. FUNCTIONALITY
The main functionality of registration system is to make the registration and database for
it to be maintained in an efficient manner.
7. USABILITY
User interface makes the exam registration system to be useful . That is the system will
help the applicant to register easily and helps the authorities
to maintain the details
effectively. The system should be user friendly.
8. PERFORMANCE
It describes the capability of the system to perform the registration process of the
applicant without any error and performing it efficiently.
9. RELIABILITY
The exam registration system should be able serve the applicant with correct information
and day-to-day update of information.
FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system. That is the
services that are provided to the applicant who apply for the Exam.
UML DIAGRAMS
The following UML diagrams describe the process involved in the online recruitment
system
a. Use case diagram
b. Class diagram
c. Sequence diagram
d. Collaboration diagram
e. State chart diagram
f. Activity diagram
g. Package diagram
12
13
RESULT:
Thus the problem statement has been written and studied successfully.
14
DEVELOPING
USECASES&
USECASE
MODELING
15
EX.NO:2
DEVELOPING USECASE AND USECASEDIAGRAM
AIM:
To develop the use case and use case diagram for the exam registration system.
16
DESCRIPTION:
Scope : Exam registration system.
Level : User goal.
Primary actor : Candidate , Admin.
Stakeholders and Preconditions :
--Candidate : Wants to register for exam , enters the detail , quick access , some guidance.
--Admin : Wants to store details , allocate seats , performs verification .
Preconditions: Admin is identified as authenticated.
Success Guarantee : Candidate enters their personal details . Admin verifies the detail and
asks for the payment . Payment is done and the admin allocates the seat and hall ticket
number.
Main success scenario :
Candidate
arrives
to
the
registration
17
form
and
enters
the
The candidate enters their detail and selects the exam which he wants to write.
The candidate enter the verification detail like +2 mark sheet no , degree
certificate no .
The details will be stored in the database.
The candidate can make payment in different modes like using credit card , debit
card , net banking .
The required amount will be entered and the submit button is clicked for the
payment.
18
19
20
Fig
2.6
Verification use
case diagram
21
22
23
RESULT:
Thus the developing of use cases and use case model has been developedsuccessfully.
24
DOMAIN MODEL
&UML CLASS
DIAGRAM
25
EX.NO:3(a)
CONCEPTUALCLASSES AND DOMAIN MODEL
AIM:
To identify the conceptual classes and to develop the domain model.
CATEGORY LIST:
Business transaction
Transaction line item
Product or service to added
Role of People
Place of Transaction
Place of service
Noteworthy events
Physical objects
Catalogs
Other collaborating systems
Records
Financial instruments
Schedule manual document
Banking ,Payment ,
Candidate record
Payment ,each candidate records
Payment , hall ticket
Candidate ,admin
Online
Online
Authorization ,login with in schedule date
Hall ticket
Exam catalog
DB ,Bank
Fees proof/hall ticket
cash, credit/debit/Net banking
Enable with in last date of registration
Tabel 3.1 Category list
26
DOMAIN MODEL:
RESULT:
Thus the category list has been generated and the domain model has been identified.
27
EX.NO:3(b)
UML CLASS DIAGRAM
AIM:
To develop the UML class diagram for exam registration system.
CLASS DIAGRAM:
A class diagram in the unified modeling language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. It is represented using a rectangle with
three compartments. Top compartment have the class name, middle compartment the
attributes and the button compartment with operations.
28
CLASS DIAGRAM:
The candidate class contains the attribute of name and mail id and the method as
login().
This class has the association with admin . It contains the Personal information of the
candidate and the exam he/she selected.
FEES DETAILS:
The fees details class has the attribute of amount and method as View Details() and
Exit().
The payment class is associated with the fees details class. The payment class has
associationswith Credit card , Debit card and Net banking classes.
PAYMENT :
The payment class has the association with the Credit card , Debit card and net
banking .
The amount is the attribute with the payment class.Payment _made() is the function.
29
FEES PROOF:
The fees proof class has the attribute of Receipt number and the method as print() and
save().
The fees proof class is associated with Credit card , Debit card and Net banking.
ADMIN:
The admin class has the attribute Candidate information and method as Save()
and Discard().
The admin has the association with the fees details and the application generated
classes . If the payment is completed then the hall ticket will be generated .
APPLICATION GENERATION:
The application generation class has the attribute Application number and
method as Get hall ticket().
It is associated with the Admin and Candidate class . The hall ticket generated
will be received by the candidate and he / she can save or print the hall ticket.
RESULT:
Thus the class diagram for exam registration has been developed successfully.
30
INTERACTION
DIAGRAM
31
EX.NO:4(a)
SEQUENCEDIAGRAM
AIM:
To develop a sequence diagram for exam registration system .
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is
constructed by a Message Sequence Chart. There are two dimensions.
1. Vertical dimension - represent time.
2. Horizontal dimension - represent different objects.
It's basically used for the purpose of security or safety. It contains user, database for the
authentication status is verified from the database. The candidate will fill out the form with
correct and eligible details.
They complete the payment process for Exam Registration. The authorities check or
verify the details. After all verification the exam registration database is finalized. After filling
the application and verification submit the form and store the database finally in the exam
registration system.
The candidate selects the exam and enters their detail in the online registration form.
Then the candidate selects the payment mode like Credit card , Debit card and Net
banking.
If the payment is not completed then it goes for repayment and after completion of the
payment the application will be generated.
The details of exam is viewed by the candidate.
32
SEQUENCE DIAGRAM:
Object1 : Candidate
Object3 : Payment
Object5 : Admin
1 : Selects exam()
2 : Enter details()
3 : Verification()
5 : Select payment()
6 : Payment()
7 : Denied()
8 : Repayment/payment completion()
9 : Generate application()
10 : Hall ticket()
Fig 4.1
RESULT:
Thus the sequence diagram for exam registration system has been developed
successfully.
33
EX.NO:4(b)
COMMUNICATION DIAGRAM
AIM:
To develop the communication diagram for exam registration system .
COMMUNICATION DIAGRAM:
Fig 4.2
The communication diagram of exam registration system starts with the candidate .
The candidate selects the exam and he / she enters the detail in apply online
form.
The verification details will be send to the admin it verifies and stores the
candidate details.
34
The candidate moves to the payment option .The payment can be of Credit card ,
Debit card , Net banking.
when the payment denied the candidate moves for the repayment.
When the payment is completed then the application will be generated it contains
the candidate details and the exam details.
RESULT:
Thus the communication diagram for exam registration has been developed
successfully.
35
36
EX.NO:5(a)
STATE CHART DIAGRAM
AIM:
To develop the state chart diagram for exam registration system .
Fig 5.1
The state chart diagram starts with the main screen the candidate will enter into
the registration form he / she enters the necessary details.
The candidate moves to the payment option he /she enters the amount and waits
for the payment completion.
The Admin performs the application generation and the hall ticket will be
viewed by the candidate through the main screen.
If the payment doesnt complete it moves to the end state.
37
RESULT:
Thus the state chart diagram for exam registration has been developed
successfully.
38
UML ACTIVITY
DIAGRAM
39
EX.NO:5(b)
ACTIVITY DIAGRAM
AIM:
To develop the activity diagram for exam registration system .
ACTIVITY DIAGRAM:
An activity diagram is a variation or special case of a state machine in which the states or
activity representing the performance of operation and transitions are triggered by the
completion of operation. The purpose is to provide view of close and what is going on inside
a use case or among several classes. An activity is shown as rounded box containing the name
of operation.
DESCRIPTION:
The activity diagram of exam registration system starts with the online
registration form.
The candidate can enter their details in the registration form.
If the payment is completed, then the application will be generated.
If the payment is not completed then it goes to end.
After the completion if payment,the candidate details and the exam details
will be generated.
The candidate can print or save the generated form.
Then it goes to the end state.
40
ACTIVITY DIAGRAM:
Candidate details
Payment
Application generation
Generated examdetails
Print / Save
Fig 5.2
41
RESULT:
Thus the Activity diagram for exam registration has been developed successfully.
42
LOGICAL
ARCHITECTURE
&UML PACKAGE
DIAGRAM
43
EX.NO:6
LOGICAL ARCHITECTURE AND UML PACKAGE
DIAGRAM
AIM:
To develop the logical architecture and package diagram for exam
registration system .
LOGICAL ARCHITECTURE:
Fig 6.1
44
PACKAGE DIAGRAM:
A package diagram in the unified modeling language depicts the dependencies between the
packages that make up a model. It provides a way to group the elements. There are three types
of layers in package diagram. They are
User interface layer
Domain layer
User interface layer consists of swing and web. This layer describes how the
candidates login to the application form.
Domain layer shows the activities that are performed inside the exam registration
system. All the activities of candidate and admin are performed in this layer .
Technical service layer The sourcing and updating the details are performed in this
layer.
45
RESULT:
Thus the logical architecture and package diagram for exam registration has been
developed successfully.
46
DEVELOP AND
TEST TECHNICAL
SERVICE LAYER
47
EX.NO:7
DEVELOP AND TEST OF TECHNICAL LAYER
AIM:
To develop and test the technical layer of the exam registration
system.
TABLE:
STEP 1: Create an empty table
Tabel 7.1(a)
48
Tabel 7.1(b)
Tabel 7.2(a)
49
Tabel 7.2(b)
RESULT:
Thus the development and testing of technical service layer has been made successfully.
50
DEVELOP AND
TEST DOMAIN
OBJECT LAYER
EX.NO:8
51
CODING:
import java.uti.Vector;
}
Application generation:
import java.util.Vector;
52
/* {src_lang=Java}*/
Application generation:
import java.util.Vector;
}
public class Applicationggeneration {
/* {src_lang=Java}*/
53
import java.util.Vector;
import java.util.Vector;
54
import java.util.Vector;
}
import java.util.Vector;
}
import java.util.Vector;
55
}
import java.util.Vector;
}
import java.util.Vector;
56
import java.util.Vector;
}
import java.util.Vector;
57
}
import java.util.Vector;
}
import java.util.Vector;
58
59
RESULT:
Thus the development and testing of code has been made successfully.
60
EX.NO:9
DEVELOP AND TEST USER INTERFACE LAYER
AIM:
To develop and test the code of user interface layer of exam registration system.
Fig 9.1
PAYMENT FORM:
61
Fig 9.2
MODE OF PAYMENT:
Fig 9.3
NET BANKING MODE OF PAYMENT:
62
Fig 9.4
PAYMENT SUCCESSFUL:
Fig 9.5
GENERATED APPLICATION FORM:
63
Fig 9.6
64
RESULT:
Thus the development and testing the code of user interface layer has been made successfully.
65