SOFTWARE ENGINEERING

 OBJECT ORIENTED DESIGN PROCESS(5 STAGES) FOR

TRAINING AND PLACEMENT

MANAGEMENT SYSTEM
As object-oriented system is made up of interacting objects
that maintain their own local state and provide operations on
that state. The representation of the state is private and cannot
be accessed directly from outside the objects. Object –oriented
design processes involve designing object classes and the
relationship between these classes.

To develop a system design for training and placement

management system from concept to detailed, object-
oriented design, there are five things that we need to do:

1) Understand and define the context and the

Modes of use of the system.
2) Design the system architecture.
3) Identify the principal objects in the system.
4) Develop design models.
5) Specify objects interface.
The training and placement management system creates
student and company databases. This module allows
students to update parts of bio data and invite companies
for placements. Student list can be retrieved from the
database of the management software on the basis of the
selection criteria of the company.

Training and placement management module

additionally manages interview schedules, student list
announcements, records of various training and
placement activities and the like. This module
of education ERP solutions can assign login rights to the
department staff.

The placement officer is responsible for updating the

placement related information like eligible criteria for a
particular company, arriving date for the company which
is coming for recruitment, the list of students who are
eligible for attending the recruitment process. The list of
student who got placed in a company and the placement
officer can access the student information from the
student database for selecting the eligible candidates list
for placements. He also can send notifications to
students regarding any information.
1. SYSTEM CONTEX AND MODELS OF
USE

The first stage in any software design process is to

develop an understanding of the relationships between
the software that is being designed and its external
environment.
The system context and model of system use represent
two complementary models of the relationships between
a system and its environment.

a) The system context is a static model that describes the

other system in that environment.

b) The model of the system use is a dynamic model that

describes how the system actually interacts with its
environment.
The context model of a system may be represented as

Training and placement management system data flow

diagram is often used as a preliminary step to create an
overview of the Training and placement without going
into great detail, which we can later b elaborated .it
normally consists of overall application dataflow and
processes of the training and placement process. It
contains all of the user flow and their entities such all the
flow of college, company, Applicant, job, Training,
placement, Qualification.

USECASE DIAGRAM FOR TRAINING AND

PLACEMENT MANAGEMENT SYSTEM

The use-case description helps to identify objects and

operation in the system.
 This Use-case diagram is a graphic depiction of the
interactions among the elements of Training and
Placement Management System.

It represents the methodology used in system analysis to

identify, clarify, and organize system requirements of
Training and placement Management system.

The main actors of Training Placement Management

System in this use case Diagram are: Super Admin,
System User, College Mates, who perform the different
type of use cases such as Training, Manage Placement,
Manage Job, Manage Jobseeker, Manage Application,
Manage Company, Manage Users and Full Training and
Placement Management System Operations.

The relationships between and among the actors and the

use cases of Training and Placement Management
System:
 Super Admin Entity: Use cases of Super Admin are
Training, Manage Placement, Manage Job, Manage
Company, Manage Users and Full Training and
Placement Manage System Operations
 System User Entity: Use cases of System User are
Training, Manage Placement, Manage Job, Manage
Applicant, Manage Company, Manage Qualification

 College Mates Entity: Use cases of College Mates are

Post Jobs, Search Candidates, Select Candidates, send
Emails

 Student Entity: Use cases of Student are Search jobs,

apply for jobs, view applications status , view results

2. ARCHITECTURAL DESIGN

Once the interactions between the software system that is

being designed and the system’s environment have been
defined, we can use this information as a basis for
designing the system architecture
Training and placement (OTAP) system provides the
modules like
 Student
 Admin
 Company
A. STUDENT MODULE: In this module, creation of
student input records about academic career from
SSLC, HSC and all semester with facilities to modify
the records and viewing changed records. The Student
views the company details and verifies particular
company details and provides valid details for
registration.
 B. COMPANY MODULE: The Company enrolls
themselves and they register their profile and their
will marquee in the main page till their drive and view
the student’s details and update their details. Login
Company, registration, students details view.

C. ADMIN MODULE: The admin is the placement

officer who views the student’s details and company
details and posts the selected students list. Sending
email to student for complete list of information for
particular campus. Indication of hall ticket issued to
candidates through mail. Login, View company
details, View selected students details, sending mail.

3. OBJECT IDENTIFICATION

By this stage in the design process, we should have some

ideas about the essential objects in the system that we are
designing. Training and Placement Management System
Object Identification describes the structure of a training
and placement management system classes, their
attributes, operations, and the relationships among
objects.
Classes of Training and Placement Management
System
 Training Class : Manage all the operations of
Training
 Placement Class : Manages all the operations of
placement
 Job Class : Manages all the operations of job
 Jobseeker Class : Manages all the operations of
Jobseeker
 Applicant Class : Manages all the operations of
Applicant
 Company Class : Manages all the operations of
Company

Training Placement

training_id placement_id
training_student_id placement_college_id
training_registration placement_student_id
training_name placement_type
training_type placement_description
training_year
training_description addPlacement()
addTraining() editPlacement()
editTraining() deletePlacement()
saveTraining() searchPlacement()
 Job Jobseeker
job_id job_seeker_id
job_name job_seeker_name
job_type job_seeker_mobile
job_salary job_seeker_email
job_vacancy job_seeker_address
job_description
addJob() addJobskeer()
editJob() editJobskeer()
deleteJob() searchJobskeer()

Applicant Company
applicant_id company_id
applicant_name company_name
applicant_mobile company_type
applicant_email company_description
applicant_password company_address

addApplicant() addCompany()
editApplicant() editCompany()
deleteApplicant() deleteCompany()
saveApplicant()
4. DESIGN MODELS

Design models show the objects or object classes in a

system and, where appropriate, the relationships between
these entities. Design models essentially are the design.
They are the bridge between the requirements for the
system and system implementation. This means that there
are conflicting requirements on these models.

The model that we discuss in this section is:

a. Sequence models
b. State machine models

a. Sequence models:
This is the UML sequence diagram of training and
Placement Management system which shows the
interaction between the objects of Company,
Qualification, Training, Jobseeker, and Job. The
instance of class objects involved in this UML
sequence Diagram of Training and Placement
Management system are as follows:
Company object
Qualification object
Training object
Jobseeker object
Job Object
 Admin will be able to login in their account using their
credentials. After login user can manage all the operations
on Training, Company, Qualification, Job, and Jobseeker.
All the pages such as Qualification, Job, and Jobseeker are
secure and user can access this page after login. The
diagram helps demonstrate how the login page works in a
Training and Placement Management system. The objects
interact over the course of the sequence, and user will not
be able to access this page without verifying their identity.

b. State machine models:

It shows how individual objects change their state in
response to events. These are represented in the
UML using state chart diagram. State machine
models are dynamic models.
  Admin user can search jobseeker, view
description of a selected jobseeker, add
jobseeker, update and delete information after
placement.
 Its shows the flow of editing, adding, updating
and selection of student in company.
 All objects in Training and placement system are
interlinked
 It shows the full description and flow of
placement, application, training, job, and
jobseeker.
Training and Placement Management System
Component diagram: It shows components, provided and
required interfaces, ports, and relationships between the
qualification, company, applicant, job and training. This type
of diagrams is used in component based development to
describe systems with service-oriented architecture. Training
and Placement Management System UML component
diagram, describes the organization and wiring of the
physical components in a system.
Components of UML Component Diagram of Training
and Placement Management System:
Qualification Component
Company Component
Applicant Component
Job component
Training Component
5. OBJECT INTERFAC SPECIFICATION

An important part of any design process is the

specification of the interfaces between the components in
the design. We need to specify interfaces so that objects
and sub-systems can be designed parallel. Once an
interface has been specified, the developers of other
objects may assume that interface will be implemented.

Utilities according to specific user

1. Admin:-
- Admin has the supreme power of the application.
- Admin provides approval for student and
corporate registration.
- Admin is responsible for maintaining the whole
system.
- Use search engine for searching any data about
student with various filter parameters.
- Admin can delete any profile.
- Admin can send mail to student and company.
2. Student:-
- Student of the college is the user of this
application.
 - New student needs to sing up with basic details.
- Reregistered student can login using unique
username and password.
- Student can submit resume and update profile
information.
- Student can download their profile as PDF
format.
3. Company:-
- To communicate with Placement Officer,
company needs to signup.
- After approved by placement Officer Company
can search the all of the students’ information.
- Company can mail to placement officer
4. Common:-
- Everyone can see some common pages e.g.
statistics.jsp, home.jsp etc.
- Every registered user can change their password
and upload new profile picture.
Object interface design is concerned with specifying the
detail of the interface to an object or to a group of object.
This means defining the signatures and semantics of the
services that are provided by the object or by a group of
objects. Interfaces can be specified in the UML using same
notation as in object identification design. However, there is
no attribute section, and UML stereotype<interface> should
included in the name part.