You are on page 1of 19

SOFTWARE REQUIREMENT SPECIFICATION

ON
ONLINE JOB CONSULTANCY

SUBMITTED TO-: SUBMITTED


BY-:
RAJEEV
RANJAN(0781563108)
.RAVI RANJAN(0791563108)
GAUTAM
KUMAR(0811563108)
IT-S9

Group No-49
CERTIFICATE
This is to certify that the project entitled “ONLINE JOB
CONSULTANCY” submitted is done by
Group No-49(IT-S9)
(Rajeev Ranjan(0781563108)
(Ravi Ranjan(0791563108)
(Gautam Kumar(0811563108)

is an authentic work carried out by him under my guidance.

Sign
ature
ACKNOWLEDGEMENT

The satisfaction that accompanies, that the successful completion of


any task would be incomplete without mentioning the name of the
person whose ceaseless cooperation made it possible, whose constant
guidance and encouragement crown all efforts with success.

We are grateful to _______________________ for the guidance,


inspiration and constructive suggestions that helped us in preparing
this project titled ONLINE JOB CONSULTANCY.
Contents:

1.Introduction
1.1 Purpose
1.2 Scope
1.3 Abbreviations
1.4 References
1.5 Overview
2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 Principle Actors
2.4 General constraints
3. Specific Requirements
3.1 Functional Requirements
3.2 Performance Requirements
3.3 Design Constraints
3.4 Screen Shots
4.Project Management And Testing Plan of
PIMS
4.1 Development process
4.2Hardware and Software Resources Required
4.3 Testing And quality plan
4.4 Risk management plan
4.5 Project Tracking.
ONLINE JOB CONSULTANCY
1.INTRODUCTION

1.1 PURPOSE

The main aim of the entire activity is to automate the process of day to
day activities of job updating, location of job, employee maintenance,
etc....
The limited time and resources have restricted us to incorporate, in this
project, only a main activities that are performed in a JOB consultancy
System, but utmost care has been taken to make the system efficient and
user friendly.
“ONLINE JOB CONSULTANCY” has been designed to computerize the
following functions that are performed by the system.

 registering new job available


 job location preference
 log-in and log-out Detail Functions
 total no vacancies
 job providing companies
 interview arrangement
 Statement of candidate Details
 job details
 Total number of candidates seeking job
 Individual candidate Report
 new companies in the market providing job opportunities
 There is the facility for password recovery, logout etc.

1.2 SCOPE

 During the past several decade personnel function has been


transformed from a relatively obscure record keeping staff to central
and top level management function.
 There are many factors that have influenced this transformation like
technological advances, professionalism, and general recognition of
human beings as most important resources.
 A computer based management system is designed to handle all the
primary
information required to calculate monthly statements. Separate
database is
maintained to handle all the details .
 This project intends to introduce more user friendliness in the various
activities such as record updation, registering new job opportunities,
candidate updation.
 The searching of record has been made quite simple as all the details
of the
candidate can be obtained by simply keying in the identification of
that candidate.
 Similarly, record maintenance and updation can also be accomplished
by using
the identification of the candidate with all the details being
automatically
generated. These details are also being promptly automatically
updated in the
master file thus keeping the record absolutely up-to-date.
 The main objective of the entire activity is to automate the process of
day to day
activities of JOB SEARCH like:
• new vacancies,
• Admission of a New Candidate,
• Arrangement of job according to candidate’s demand,
• Packages available.
• Online Cancellation.
• Email facility.
• Feedbacks

2. Overall Description
2.1 Product Perspective:
ONLINE JOB CONSLTANCY is aimed toward a person who is in a search
of job according to his profile/qualifications and expectations.
It also help the employers to get the right person to get their job done.
It is intended to be a stand-alone product and should not depend on the
availability of other software.It uses the web browser and thus is platform
independent.

2.2 Product Functions:


Advantage:
I have designed the given proposed system in the JSP to automate the
process of job consultancy.
This project is useful for the authorities which keep track of all the users
registered in a particular state.

Performance:
During past several decades, the records are supposed to be manually
handled for all activities. The manual handling of the record is time
consuming and highly prone to error. This project is fully computerized
and user
friendly even that any of the members can see the report and status of
the company.

Efficiency:
The basic need of this website is efficiency. The website should be
efficient so that whenever a new user submits his/her details the website
is updated automatically. This record will be useful for other users
instantly.

Control:
The complete control of the project is under the hands of authorized
person who has the password to access this project and illegal access is
not supposed to deal with.

Security:
Security is the main criteria for the proposed system. Since illegal access
may corrupt the database. So security has to be given in this project.

PROJECT CATEGORY:
This Project is coupled with material on how to use the various tool, sub
sets available in JSP, SERVLETS AND Microsoft Access.
The need of today’s software development is competence in a GUI based
front-end tool, which can connect to Relational Database engines. This
gives the programmer the opportunity to develop client server based
commercial applications.

2.3 Principal Actors:


 The two principal actors in job consultancy are “user” and “system”.
2.4 General Constraints:
 For full working job search requires Internet connection.

3 Specific Requirements
3.1 Functional Requirements:
We describe the functional requirements by giving various use cases.

Use cases related to Applicant:

Use Case 2: Login


Primary Actor: Applicant
Pre Condition: Nil

Main Scenario :
 Start the application. User prompted for login and password.
 User gives the login and password.
 System does authentication.
 Main screen is displayed.

Alternate Scenario :
 Authorization fails
• Prompt the user that he typed the wrong password
• Allow him to re-enter the password. Give him 3 chances.

Use Case 3: Change Password


Primary Actor: User
Pre Condition: User logged in

Main Scenario :
 User initiates the password change command.
 User is prompted for old password, new password and confirm new
password.
 User gives the old password, new password and confirm new
password.
 System does authentication.
 New password is registered with the system.

Alternate Scenario :
 Authorization fails
• Prompt the user that he typed the wrong password
• Allow him to re-enter the password. Give him 3 chances.
 New password and confirm new password do not match.
• Allow him to re-enter the attributes. Give 3 chances.

Use cases related to portfolios:

Use Case 4: Create Profile


Primary Actor: User
Pre Condition: nil.

Main Scenario:
 User initiates the “create profile” functionality.
 System asks the user for the portfolio details.

Alternate Scenario:
 Portfolio with the same name exists.
• System asks the user for a different name.

Use cases related toEmployer- :

Use Case 2: Login


Primary Actor: Employer
Pre Condition: Nil

Main Scenario :
 Start the application. User prompted for login and password.
 User gives the login and password.
 System does authentication.
 Main screen is displayed.

Alternate Scenario :
 Authorization fails
• Prompt the user that he typed the wrong password
• Allow him to re-enter the password. Give him 3 chances.

Use Case 3: Change Password


Primary Actor: User
Pre Condition: User logged in

Main Scenario :
 User initiates the password change command.
 User is prompted for old password, new password and confirm new
password.
 User gives the old password, new password and confirm new
password.
 System does authentication.
 New password is registered with the system.

Alternate Scenario :
 Authorization fails
• Prompt the user that he typed the wrong password
• Allow him to re-enter the password. Give him 3 chances.
 New password and confirm new password do not match.
• Allow him to re-enter the attributes. Give 3 chances.

Use cases related to portfolios:

Use Case 4: Create Profile


Primary Actor: User
Pre Condition: nil
Main Scenario:
 User initiates the “create profile” functionality.
 System asks the user for the portfolio details.

Alternate Scenario:
 Portfolio with the same name exists.
• System asks the user for a different name.
• User enters a different name.
• Empty portfolio gets created.

Use Case 4: Update Profile


Primary Actor: User
Pre Condition: User logged in.
Main Scenario:
 User initiates the “update profile” functionality.
 System asks the user for the portfolio details.

Sequence Diagrams
ER Diagram:
3.2 Performance Requirements:
 Better supported on Internet Exploler.

3.3 Design Constraints:


 Security: The files in which the information regarding securities and
portfolios
should be secured against malicious deformations.
 Fault Tolerance: Data should not become corrupted in case of system
crash or
power failure.

3.4 Screen Shots:


Project Management And Testing
Plan of ONLINE JOB CONSULTANCY
4.1 Hardware and Software resources required

The only hardware resource required is an internet connection. Following


are the main
software resources that are required:

4.3 Testing And Quality Plan


The quality control process for this project will consist of the
following:
 SRS and Architecture Review: The SRS and Architecture of
the project will be reviewed by a team including people
from outside.
 Design Review: Design document will be reviewed by the
project team.
 Unit Testing: Each programmer is responsible for Unit
Testing his module. The modules
Create/Delete/Rename/Edit Portfolio/Security. For some
modules, unit testing report will be produced.
 System Testing: Will be done according to the system test
plan, which will describe the testing strategy as well as list
all the test cases. The test plan will be reviwed.

4.4 Risk Management Plan

4.5 Project Tracking


As it is a small project, elaborate tracking is not necessary.
Following is project tracking plan:
 We will primarily track the schedule and tasks. This will be
done through weekly meetings and weekly status reports
(to be sent by email.)
 Status of the tasks achieved and missed will be reported
weekly.
 Effort tracking will be done informally, and if necessary re-
estimation will be done.
 Risks will be revisited monthly in the review meeting.
SOFTWARE & HARDWARE REQUIREMENTS

Component Requirement

Operating 1. SolarisTM10 on SPARC, x86, and x64 based systems,


system (OS) including support for whole root local and sparse root zones.
2. Solaris 9 on SPARC and x86 based systems.
3. Red Hat TM Enterprise Linux 5.0 Server, 32 and 64-bit
versions, all updates
4. Red Hat Enterprise Linux 3 and 4, all updates

Advanced Server (32 and 64-bit versions) and Enterprise


Server (32 and 64-bit versions)Windows

Windows 2000 Advanced Server, Data Centre Server version


SP4 on x86

Windows 2003 Standard (32 and 64–bit versions), Enterprise


(32 and 64–bit versions), Data Centre Server (32–bit version) on
x86 and x64 based systems

Windows XP Professional SP2 on x86 based systems

HP-UX 11i v1 (11.11 from uname), 64–bit on PA-RISC 2.0.


Access Manager 7.1 Patch 1 is not available for HP-UX.

Java 2 Standard J2SE platform 6.0, 5.0 Update 9 (HP-UX: 1.5.0.03), 1.4.2 Update 11, and
Edition (J2SE) 5.0 Update 12 (as of Java Enterprise System 5 update 1)
Component Requirement

Directory Access Manager Information Tree (configuration data store):


Server
• Sun Java System Directory Server Enterprise Edition 6.3
(requires Access Manager 7.1 Patch 2 or later)
• Sun Java System Directory Server Enterprise Edition 6.1
and 6.2 (requires Access Manager 7.1 Patch 1 or later)
• Sun Java System Directory Server 5.2 2005Q4 and 6.0

Access Manager Identity Repository (user data store):

• Sun Java System Directory Server Enterprise Edition 6.3


(requires Access Manager 7.1 Patch 2 or later)
• Sun Java System Directory Server Enterprise Edition 6.1
and 6.2 (requires Access Manager 7.1 Patch 1 or later)
• Sun Java System Directory Server 5.2 2005Q4 and 6.0

• Microsoft Active Directory

Web containers Sun Java System Web Server 7.0. On supported platform/OS combinations
you may elect to run the Web Server instance in a 64 bit JVM. Support
platforms: Solaris 9/SPARC, Solaris 10/SPARC, Solaris 10/AMD64, Red
Hat AS or ES 3.0/AMD64, Red Hat AS or ES 4.0/AMD64

Sun Java System Application Server Enterprise Edition 8.2

BEA Web Logic 8.1 SP4, and 9.2 for (Patch 1). Web Logic is not
supported with Access Manager for HP-UX.

IBM Web Sphere Application Server 5.1.1.6 and 6.1( for Patch 1). Web
Sphere is not supported with Access Manager for HP-UX.

RAM Basic testing: 512 Mbytes

Actual deployment: 1 Gbyte for threads, Access Manager SDK, HTTP


server, and other internals

Disk space 512 Mbytes for Access Manager and associated applications