Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Analysis Report
ON
MeNTORS
An Online Recruitment Portal
Submitted By
Abhishek Kulkarni (111A1045)
Gauri Limaye (111A1046)
Nishant Makhija (111A1047)
Guided By
Prof. Masooda Modak
INDEX
S.NO
TITLE
.
1.
Problem Definition
2.
Requirement Analysis
3.
4.
Analysis Phase
5.
Design Phase
6.
Future Aspects
7.
References
PROBLEM DEFINITION
The website is an ecommerce website called MeNTORS. MeNTORS is the
provider of Talent Banking, e-Recruitment and Applicant Tracking Solutions, with
particular strengths in Talent Attraction and Candidate Experience. Recruitment
Management Solutions from PeopleBank.com delivers significant reductions in time
spent on the recruitment process, direct and indirect costs incurred, and at the same time
increases the quality of candidates you are seeing. By improving companys online
Employer Branding and managing all the applicants of corresponding company through
one portal, no matter where they came from, you get to see the best talent faster. As
unique Talent Bank of a company grows, you become less dependent on expensive
advertising campaigns and recruitment agencies and cost per hire and time to hire are
reduced significantly.
REQUIREMENT ANALYSIS
NEED
When you look at bringing your recruitment processes online you will probably be
surprised at just how many products are out there. There are a range of important
questions you will want to ask to find your perfect partner. Who delivers the best results
and the best value? Who provides all the features to meet all of your needs? Who has the
track record in providing the service and stability to support you many years into the
future? MENTORS provides with such solutions.
MAJOR OBJECTIVES
The main objectives of developing the Online Recruitment Website are as given below: 1. To provide recruiters with talent bank.
2. To provide the environment for online assessment of candidates with career
profiles, CV parsing and online aptitude tests.
3. To provide candidates with knowledge of available employers and jobs.
1.
1.1
Introduction
Purpose
Scope
Initial functional requirements will be: Browsing through the website to see the available candidates and jobs.
Adequate searching mechanisms for easy and quick access to particular
company.
Regular updates to registered candidates about new jobs.
Maintaining database of regular candidates and customers of different
needs.
Adequate payment mechanism and gateway for all popular credit cards,
cheques and other relevant payment options
Initial non functional requirements will be: 24 X 7 availability
Better component design to get better performance at peak time
1.3
References
Technologies to be used
Programming languages:
HTML, XML: Hyper Text Markup Language and Extensible markup
Language are the predominant markup languages for web pages. It
provides a means to describe the structure of text-based information in a
document and to supplement that text with interactive forms, embedded
images, and other objects.
PHP: A server side scripting language used for database connectivity.
2.
2.1
Overall Description
Product perspective
The website for recruitment is aimed towards the companies who want to
reach out to the maximum eligible candidates who can provide potential services
to the company. This project envisages bridging the gap between the recruiters
and the candidates. It should be user-friendly, quick to learn and reliable
software for the above purpose. It is intended to be a stand-alone product and
should not depend on the availability of other software. It should run on both
UNIX and Windows based platform Product functions
User: Administrator
Functions: The Administrator is the super user and has complete control over all
the activities that can be performed. The application notifies the administrator of
all new registrations by companies and candidates, and the administrator can then
approve or reject them. The administrator also maintains record of candidate
profiles with results of aptitude tests. The administrator can also view and delete
entries in the guestbook.
User: Recruiters
Functions: Recruiters will have their own portals through which they can see
registered candidates for their recruitment process.
User: Candidates
Functions: Candidate will register on the site and login on candidate portal.
Candidates will be provided with the facility of CV Parsing. Candidates will be
look for companies in which they are interested. Candidates will appear for
aptitude test of corresponding companies. They will be notified about results and
further process on their account login.
Product perspective :This software is totally self contained and works relatively as efficient as other packages
related to the subject. It provides simple database rather than complex ones for high
requirements and it provides good and easy graphical user interface to both new nave as
well as experienced users of the computers.
System Interfaces:Interface:
The software provides good graphical interface for the front end of the database and a
good informative interface for the rear end
Hardware Interface :The system should have these hardware requirements :
The processor should be at least Pentium 3 or above
The processor speed should be greater than 400Mhz
The video device should support graphics
Ram should be or greater than 120 mb
Software Interfaces :The software requires the support of the following softwares for the database and other
requirements
PHP ,JDK and html editor for web interface
MySQL for database
Server(windows 2000,apache or xampp)
Remote CPanel
FileZilla for FTP
Operations :The operations required by the users are:
Customers : Do shopping, Reserve products
Merchants: Bid their products, Manage transport facility and look after
the payment method
2.2
User characteristics
The user should be familiar with the Recruitment related terminology like
Aptitude test/CV/Transaction etc.
The user should be familiar with the Internet.
2.3
Constraints
Limited to HTTP/HTTPS.
No multilingual support
FEASIBILITY STUDY
Feasibility study is the process of determination of whether or not a project
is worth doing. Feasibility studies are undertaken within tight time constraints and
normally culminate in a written and oral feasibility report. I have taken two weeks in
feasibility study with my co-developer. The contents and recommendations of this
feasibility study helped us as a sound basis for deciding how to proceed the project. It
helped in taking decisions such as which software to use, hardware combinations, etc.
Technical Feasibility
Economical Feasibility
Operational Feasibility
1. Technical Feasibility
Technical feasibility determines whether the work for the project can be done
with the existing equipment, software technology and available personnel. Technical
feasibility is concerned with specifying equipment and software that will satisfy the user
requirement.
This project is feasible on technical remarks also, as the proposed system is
more beneficiary in terms of having a sound proof system with new technical
components installed on the system. The proposed system can run on any machines
supporting Windows and Internet services and works on the best software and hardware
that had been used while designing the system so it would be feasible in all technical
terms of feasibility.
2. Economical Feasibility
Economical feasibility determines whether there are sufficient benefits in
creating to make the cost acceptable, or is the cost of the system too high. As this
signifies cost benefit analysis and savings. On the behalf of the cost-benefit analysis, the
proposed system is feasible and is economical regarding its pre-assumed cost for making
a system.
We classified the costs of website according to the phase in which they
occur. As we know that the system development costs are usually one-time costs that will
not recur after the project has been completed.
3. Operational Feasibility
Operational feasibility criteria measure the urgency of the problem or the
acceptability of a solution .
2.4
Given below is an overall picture of the system, as depicted in the above use-case
diagrams:
1. System:
Database Management: Control the database and keep track of all records of
customers and employee details.
Contact and Giving Permission to Corporates: Contact with the vendors and give
permission to sell their product under the site after testing the products quality.
View all details: View the details of all employees and control the whole site.
Advertising the Site: Responsible for making advertisements for the site.
Regulating Payments: Keep track of all the payment transactions made by the
customers and update the payment information.
Consulting with Banks: Responsible for contacting the banks for the validation of
the a/c number provided by the customer while purchasing and make the transaction
from the given a/c.
2. Customers:
Choosing and comparing products: Can view all available products and can
compare them and make a choice for purchasing products.
Giving Feedback to Customer Care: Can give feedback to the 24X7 Customer Care
Service center about their impression for the site and services.
3. Shop Owner:
Taking Permission from Administrator: Vendors must take permission from the
Administrator for selling their products under the site. Administrator will test
products quality according to its market price to permit vendor for selling purpose.
4. Customer Care:
3.
3.1
Specific Requirements
This section of the SRS should contain all the software requirements to a level of
detail sufficient to enable designers to design a system to satisfy those
requirements, and testers to test that the system satisfies those requirements.
When using use-case modeling, these requirements are captured in the use cases
and the applicable supplementary specifications. If use-case modeling is not
used, the outline for supplementary specifications may be inserted directly into
this section.
Use-Case Reports
In use-case modeling, the use cases often define the majority of the functional
requirements of the system, along with some non-functional requirements. For
each use case in the above use-case model or subset thereof, refer to or enclose
the use-case report in this section. Make sure that each requirement is clearly
labeled.
3.2
Supplementary Requirements
3.3
4.
Supporting Information
The supporting information makes the SRS easier to use. It includes: a) Table of
contents, b) Index, c) Appendices. These may include use-case storyboards or
user-interface prototypes. When appendices are included, the SRS should
explicitly state whether or not the appendices are to be considered part of the
requirements.
Future Developments :
DESIGN PHASE
In the design phase the architecture is established. This phase starts with the
requirement document delivered by the requirement phase and maps the requirements
into an architecture. The architecture defines the components, their interfaces and
behaviors. The deliverable design document is the architecture. The design document
describes a plan to implement the requirements. This phase represents the ``how'' phase.
Details on computer programming languages and environments, machines, packages,
application architecture, distributed architecture layering, memory size, platform,
algorithms, data structures, global type definitions, interfaces, and many other
engineering details are established. The design may include the usage of existing
components.
Architecture
The architecture defines the components, interfaces, and behaviors of the system.
The components are the building blocks for the system. These components may be built
from scratch or re-used from an existing component library. The components refine and
capture the meaning of details from the requirement document. The components are
composed with other components using their interfaces. An interface forms a common
boundary of two components. The interface is the architectural surface where
independent components meet and communicate with each other. Over the interface,
components interact and affect each other. The interface defines a behavior where one
component responds to the stimuli of another component's actions.
ACTIVITY DIAGRAM
CLASS DIAGRAM
REFERENCES
1. HTML5 and CSS 3.0 www.w3schools.com/html/html5_intro.asp
2. MySQL Documentation http://dev.mysql.com/doc/
3. SMTP Configuration www.serversmtp.com/en/smtp-configuration
4. Bootstrap Blog http://blog.getbootstrap.com/
5. HTML Table Export http://ngiriraj.com/
6. File Upload http://www.w3schools.com/php/php_file_upload.asp
7. Impact of E-recruitment R. Naveed www.mnmk.ro/documents/2013-01/4-18-113.pdf
8. E-recruitment An HR perspective P. Dhamija
http://www.researchersworld.com/vol3/issue3/vol3_issue3_2/Paper_05.pdf