i.
Introduction
ii.
Scope of the model
iii. Product Perspective
iv. Use Case Diagram
v.
Class Diagram
vi. Activity Diagram
vii. Sequence Diagram
viii. State Diagram
ix. Deployment Diagram
x.
Collaboration Diagram
xi. Component Diagram
xii. Object Diagram
2
The primary purpose to develop this system is
to optimize the recruitment process for college.
Besides, the qualified applicants could be sort
by this system based on their qualifications and
company requirements. Based on the
applicant’s skills and areas of interest , the
company suitable or the company in which
he/she is going to place can be predicted.
Another purpose of the software is to facilitate
the student (in the college) and the company to
register and communicate with placement
office.
3
Campus Recruitment System enables the user to
have the typical recruitment facilities and features at
their disposal. It resolves the typical issue of manual
staffing processes and activities into a controlled
and closely monitored workflow in the architecture
of the application. The objective of this application is
to serve as a common meeting ground for
jobseekers and company, locally. This kind of
system is specifically designed for organization to
help in solving staffing problems and managing
human resource department activities at higher
degree of optimization.
4
In the “Campus Recruitment System ”, We will be having a user interface for the
admin, student and company .The user can log In to their account. Depending on the
user , the utilities will be decided. The student can login to their respective account
and can apply for the respective post available. If the user don’t have an account,
then he/she can create an account and can apply or the jobs. The company can
login to their account and can update the details of the jobs available. If the company
don’t have an account, the they can create and account and can update the job
details. Admin will already be having an ID and password. The admin will login and
manage the student and company’s activities. After the creation or the login of the
user, a successful message will be displayed to the user.
5
• A Use-Case Diagram for a Campus
Recruitment System represents the
various interactions and functionalities of
the system from the perspective of
different users or actors. Actors are
entities that interact with the system, and
use cases represent specific
functionalities or actions that the system
provides.
6
7
In software engineering, 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, operations (or methods),
and the relationships among
objects.
ADD A FOOTER
The class diagram is the main
building block of object-oriented
modelling. It is used for general
conceptual modelling of the
systematic of the application, and
for detailed modelling translating
the models into programming
code.
8
9
Activity diagrams are graphical representations of workflows of
stepwise activities and actions with support for choice, iteration and
concurrency. In the Unified Modeling Language, activity diagrams are
intended to model both computational and organizational processes
(i.e., workflows), as well as the data flows intersecting with the
related activities. Although activity diagrams primarily show the
overall flow of control, they can also include elements showing the
flow of data between activities through one or more data stores.
10
11
• A sequence diagram shows object interactions arranged in time sequence. It depicts the
objects and classes involved in the scenario and the sequence of messages exchanged
between the objects needed to carry out the functionality of the scenario. Sequence
diagrams are typically associated with use case realizations in the Logical View of the
system under development. Sequence diagrams are sometimes called event diagrams or
event scenarios.
• A sequence diagram shows, as parallel vertical lines (lifelines), different processes or
objects that live simultaneously, and as horizontal arrows, the messages exchanged
between them, in the order in which they occur. This allows the specification of simple
runtime scenarios in a graphical manner.
12
13
A state machine diagram is a type of diagram used in
computer science and related fields to describe the
behavior of systems. State diagrams require that the
system described is composed of a finite number of
states; sometimes, this is indeed the case, while at
other times this is a reasonable abstraction. Many
forms of state diagrams exist, which differ slightly and
have different semantics.
14
15
A deployment diagram in the Unified Modeling Language models the
physical deployment of artifacts on nodes. To describe a web site, for
example, a deployment diagram would show what hardware
components ("nodes") exist (e.g., a web server, an application server,
and a database server), what software components ("artifacts") run
on each node (e.g., web application, database), and how the different
pieces are connected (e.g. JDBC, REST, RMI).
The nodes appear as boxes, and the artifacts allocated to each node
appear as rectangles within the boxes. Nodes may have sub-nodes,
which appear as nested boxes. A single node in a deployment
diagram may conceptually represent multiple physical nodes, such as
a cluster of database servers.
16
17
A collaboration diagram, also known as a communication
diagram, is a visual representation that illustrates the interactions
and relationships between different objects or components within
a system. In the context of a Campus Recruitment System, a
collaboration diagram would depict how various elements, such
as users, entities, and processes, communicate and collaborate
to achieve specific functionalities.
ADD A FOOTER
18
19
A component diagram for a Campus Recruitment System
provides a visual representation of the system's high-level
architecture, illustrating the various components and their
interconnections. This diagram focuses on the modularization of
the system, showcasing the major software components and their
relationships.
20
21
An object diagram for a Campus Recruitment System provides a
static view of the system at a specific point in time, showing the
instances of classes and their relationships. It illustrates the
actual objects and their attributes, as well as the associations
between these objects.
22
23
Simran Singh - HU22CSEN0200035
Sravin Akshay- HU22CSEN0200025
Sujay - HU22CSEN0200021
Sarath Chandra - HU22CSEN0200034
Divyanshu Mahi - HU22CSEN0200189
Lohith - VU22CSEN0200036
24