Software Requirements

Specification
For

Job portal

Prepared by :-

Sandeepa Garg(CS):- 0712610082

Ranjna Pal(CS):-0712610075

Anil kumar Yadav(CS):-0712610011

Anshuman (IT):-0712613005

Final year 2010-2011

Date by :-24th November2010

 .

1. Introduction
2. The project would help in effective and systematic record keeping that is
storing and retrieving of useful data. Project Job Portal includes all the aspect
of online career consultancies, company registration, priority based job
search, job application, resume display, resume update, priority resume
search, user credential maintenance, application short listing and display
innovative news
1.1 Purpose Objective:-

Computerized on Line Job Search System is developed to facilitate the

General administration system to manage the various information of the Job Seeker and Job
Provider and the processes involved in a placement company. So, that organization can access
accurate information quickly and easily as and when required, thereby improving its operational
efficiency & effectiveness

In today’s competitive environment, where everybody wants to be on the top, Information plays very
crucial role. As fast as information is accessed and processed, it can give good results. Today
Internet is the fast way of transferring Data and Information over wide area.

Computerized system helps to fulfill these goals. Computerization of the official works will help in
doing lot of manual work quickly. It will help in easy storage and access of all information, in short
period of time.

Specific Objective:-

Objective of doing this project is to enhance our knowledge in the field of E-com technology using
ASP.NET platform and C# as a language. Some of the client requirement and objectives of this site
is as under:-

 To increase the business of Client.

 To make it Global.
 To facilitate job search.

[Type text]
 .

 To facilitate company so that it can search for best candidates available.

 To help candidates to fetch a right job.
 To act as a middle men connecting Job seeker and Provider.
 User can search for different options available.
 User can do on-line resume posting etc.
 User can use search engine to look for different vacancies, facilities available etc.
 User can do apply for job on-line.
 User can download different forms etc.
So these are some of the objectives which we have to accomplish.

1.2 Document Conventions

Font – Arial
Font size- 11

1.3 Intended Audience and Reading Suggestions

This specification is for the developer and programmer.In this SRS we will learn how the
project work . The sequence of reading this project is from the introduction and then its
step so that we are already aware of the document font size and what is the order of the
specification.

1.4 Product Scope

The main Scope of study: -

1. It should contain all the information of Company and Vacancy which is registered in this site.
2. It should contain all the information of Job Seeker like Personal Detail, Professional Detail,
and Educational Detail etc.
3. It should process and evaluate jobs registered by companies.
4. It should contain information related to Job expiry or re registration.
5. It should inform both Job Seeker and Job Provider when the appropriate person is found for
a job.
6. It should maintain proper financial records.
7. It should have Administrator for scheduling administrative work of site

References –

[Type text]
 .

SITES REFERRED:-

1. http://www.google.com
2. http://www.monster.com
3. http://www.timesjob.com

BOOKS:-

 MSDN
 Microsoft .Net Framework-2005 ASP Application Development by Mike Snell and
Glenn Johnson.
 HTML 4 for Dummies by ED Tittel.
 SYSTEM ANALYSIS AND DESIGN by ELIAS M AWAD.
 SOFTWARE ENGINEERING by Rajib Mall.

2. Overall Description -
2.1 Product Perspective –

2.2 Product Functions-

Modules of project:

The project can be divided in to three main modules.

 Jobseeker module
 Employer module
 Administrator module

Module 1:

[Type text]
 .

Job Seeker module:-

 Job Seeker Registration

 Login for Job Seeker

 View User Information

 Post Resume

 View Post Resume

 Search Job

 Change Password

Module 2:

Administrator module:-

 Post News

 View Company Profile

 View Posted Jobs

 View User Profile

 View Post Resume

 View Apply Jobs

 View Feedback

 Change Password

Module 3:

Job Provider OR Employer module:-

 View Company Info

 Add Post Job

[Type text]
.

 View Post Job

 Change Password

 Search for eligible candidate

3. External Interface Requirements

3.1 User Interfaces
<Describe the logical characteristics of each interface between the software product and the
users. This may include sample screen images, any GUI standards or product family style
guides that are to be followed, screen layout constraints, standard buttons and functions
(e.g., help) that will appear on every screen, keyboard shortcuts, error message display
standards, and so on. Define the software components for which a user interface is needed.
Details of the user interface design should be documented in a separate user interface
specification.>

3.2 Hardware Interface

 Processor :Intel Pentium 4 CPU, 2.66GHz

 Memory

 RAM : 256 MB DDR

 Hard Disk : 40 GB SATA

 Mouse : Quantum

 Keyboard : Samsung (Multimedia Supported)

 Drive : CD-RW, Floppy drive

 Printer : HP-Laser printer

Hardware requirement for Implementation

[Type text]
.

 Processor:

 Minimum : 568 MHz Pentium Processor

 Memory:

 RAM : 64 MB

 Hard Disk : 4 GB

 Display : 1024 * 768, True Type Color-32 Bit

 Mouse : Any Normal Mouse.

 Keyboard : Any window Supported Keyboard.

 3.3 Software Interfaces:-


 Operating System : Windows XP Professional

 Front End : ASP.NET

 Back End : SQL Server-2005

 Glossary-

[Type text]
 .


Analysis Models:-

Breaking a problem into successively manageable parts for individual study.

Attribute:

A data item that characterizes an object.

Cost/Benefit Analysis:

The purpose of the comparing the projected savings and benefits to projected to costs to decide
whether the system change is justified.

Data Base:

A store of integrated data capable being directly addressed for multiple user; it is organized so
that various files can be accessed through a single referenced based on the relationship among
records in the file rather than the physical location.

DBMS:

The software that determines how data must be structured to produce the user’s view; and
maintain update the system.

Data Flow:

Moment of data in a systems from appoint of origin to specific destination indicated by a line and
arrow.

Data Security:

Protection of data from loss, disclosure, modification or destruction.

Data Structure:

Logically related set of data that can be decomposed into lower level data elements; a group of
data elements handled as a unit.

Design:

[Type text]
 .

Process of devolving the technical and operational specification of a candidate system for
implementation.

Feasibility Study:

A procedure that identifies describes and evaluates candidate systems and selects the best
system for implementation.

File:

Collection related records organized for a particular purpose also called a data set

Flow Chart:

A graphic picture of the logical steps and sequence involved in a procedure or a program.

Implementation:

In system development- a phase that focuses on user training, site preparation and file conversion
for installing a candidate system.

Normalization:

A process of replacing a given file with its logical equivalent; the object is true derive
sample file with no redundant elements.

Operating System:

In data base machine based software that facilitates the availability information or reports through
the DBMS.

Password:

Identity authenticator a key that allow access to a program system or procedure.

Pert:

A flow system model used to manipulate various values as a basis for determining the critical
path to interpret this relationship and to relate them back to the real world as a control technique.

Record:

A collection of aggregates or related item of data treated as a unit.

[Type text]
 .

Source code:

A procedure or format that allow enhancement on a software package.

System:

A regular or orderly arrangement of components or parts in a connected and interrelated series or

whole; a group of components necessary to some operation.

System Design:

Detailed concentration on the technical and other specification that will make the new system
operational.

[Type text]
.

2. Overall Description
2.1 Product Perspective
<Describe the context and origin of the product being specified in this SRS. For example,
state whether this product is a follow-on member of a product family, a replacement for
certain existing systems, or a new, self-contained product. If the SRS defines a component
of a larger system, relate the requirements of the larger system to the functionality of this
software and identify interfaces between the two. A simple diagram that shows the major
components of the overall system, subsystem interconnections, and external interfaces can
be helpful.>

2.2 Product Functions

<Summarize the major functions the product must perform or must let the user perform.
Details will be provided in Section 3, so only a high level summary (such as a bullet list) is
needed here. Organize the functions to make them understandable to any reader of the
SRS. A picture of the major groups of related requirements and how they relate, such as a
top level data flow diagram or object class diagram, is often effective.>

2.3 User Classes and Characteristics

<Identify the various user classes that you anticipate will use this product. User classes may
be differentiated based on frequency of use, subset of product functions used, technical
expertise, security or privilege levels, educational level, or experience. Describe the
pertinent characteristics of each user class. Certain requirements may pertain only to certain
user classes. Distinguish the most important user classes for this product from those who
are less important to satisfy.>

2.4 Operating Environment

<Describe the environment in which the software will operate, including the hardware
platform, operating system and versions, and any other software components or applications
with which it must peacefully coexist.>

2.5 Design and Implementation Constraints

<Describe any items or issues that will limit the options available to the developers. These
might include: corporate or regulatory policies; hardware limitations (timing requirements,
memory requirements); interfaces to other applications; specific technologies, tools, and

[Type text]
.

databases to be used; parallel operations; language requirements; communications

protocols; security considerations; design conventions or programming standards (for
example, if the customer’s organization will be responsible for maintaining the delivered
software).>

2.6 User Documentation

<List the user documentation components (such as user manuals, on-line help, and
tutorials) that will be delivered along with the software. Identify any known user
documentation delivery formats or standards.>

4. System Features
[Type text]
.

<This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section
by use case, mode of operation, user class, object class, functional hierarchy, or
combinations of these, whatever makes the most logical sense for your product.>

4.1 System Feature 1

<Don’t really say “System Feature 1.” State the feature name in just a few words.>
4.1.1 Description and Priority
<Provide a short description of the feature and indicate whether it is of High, Medium,
or Low priority. You could also include specific priority component ratings,
such as benefit, penalty, cost, and risk (each rated on a relative scale from a
low of 1 to a high of 9).>
4.1.2 Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the behavior
defined for this feature. These will correspond to the dialog elements
associated with use cases.>
4.1.3 Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These are
the software capabilities that must be present in order for the user to carry out
the services provided by the feature, or to execute the use case. Include how
the product should respond to anticipated error conditions or invalid inputs.
Requirements should be concise, complete, unambiguous, verifiable, and
necessary. Use “TBD” as a placeholder to indicate when necessary
information is not yet available.>
<Each requirement should be uniquely identified with a sequence number or a
meaningful tag of some kind.>
REQ-1:
REQ-2:

4.2 System Feature 2 (and so on)

5. Other Nonfunctional Requirements

5.1 Performance Requirements

<If there are performance requirements for the product under various circumstances, state
them here and explain their rationale, to help the developers

[Type text]
.

[Type text]
.

[Type text]
.

[Type text]
.

[Type text]
.

[Type text]
.

[Type text]
.

[Type text]
.

[Type text]
.

[Type text]
.

[Type text]