Beruflich Dokumente
Kultur Dokumente
Specification
for
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for Online Job Portal
Page ii
Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics....................................................................................................2
2.4 Operating Environment..................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies.....................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6
Revision History
Name Date Reason For Changes Version
Software Requirements Specification for Online Job Portal Page 1
1. Introduction
1.1 Purpose
The project helps in proper management and coordination of the records and information. The
project will be able to give the report so that management can make decisions on the basis of
these reports. Computerized Online Job Search System is developed to facilitate the General
Administrative system to manage the various information of the Job Seeker and Job Provider and
the processes involved in a Placement company. So that, the organization can access accurate
information quickly and easily as and when required, thereby improving its operational efficiency
and effectiveness
.
In today’s competitive environment, where everybody is on the top, Information plays very crucial
role. As fast as information is accessed and processed, it can give good result. Today is a fast
way of transferring Data and Information over wide area, hence we have used internet as a way
for exchanging information. Computerized Systems 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. This way convenience will prevail both for the
Job Seeker and the Job Provider.
1.2 Document Conventions
A feasibility study is conducted to select the best system that meets performance requirement.
This entails an identification description, an evaluation of candidate system and the selection of
best system for the job. The system required performance is defined by a statement of
constraints, the identification of specific system objective and a description of outputs.
3.Improve-information-level benefits
-It provides better information in the stipulated space and time for decision-making.
4.Time-saving-benefits
-It saves lots of time and provides the same result in a far lesser period of time.
Software Requirements Specification for Online Job Portal Page 2
1.3 Intended Audience and Reading Suggestions
<Describe the different types of reader that the document is intended for, such as developers,
project managers, marketing staff, users, testers, and documentation writers. Describe what the
rest of this SRS contains and how it is organized. Suggest a sequence for reading the document,
beginning with the overview sections and proceeding through the sections that are most pertinent
to each reader type.>
1.4 Product Scope
The Scope of the Online Job Portal includes the following key points:
- It should contain all the information about Company and Vacancy which is in this site.
1.5 References
INTERNET
[1] Catherine Ricardo, Iona College New Rochelle, New York, Database Systems
Principles, Design, and Implementation, New York: Maxwell Macmillan, 1990.
[2] Jeffery L. Whitten, Lonnie D. Bentley, Kevin C. Dittman, Purdue University, West
Lafayette, IN, Systems Analysis and Design Methods, 6th edition, New York: McGraw-
Hill/Irwin, 2004.
2. Overall Description
2.1 Product Perspective
The web pages (Html/J2EE) are presented to provide the user interface on staff client
side. The communication between customer and server is provided through HTTP/HTTPS
protocols.
On the server side, web server WASCE is used and database DB2 is used for storing
information
1. Job Employer
2. Job Administrator
Viewing members.
Emailing
Add Country
Add State
Add City
Edit/Delete Recruiter
View Reports
3. Employee Section
Registration
Upload Video/ Audio Resumes - giving an extra edge to the deserving candidates
References/Video References
Advance search by keywords, location, job title, skill, industry, company, profile
Interest list for Jobs and the option of posting resumes to the entire list in one go
Option of having Personal Web Page (Profile Builder) - The professional details could be
filled through simple designed form. Upload images, scanned salary slips, academic
records, experience certificate, passport copy etc., with a link and it could be accessed
online from anywhere with feature of differential access.
Option of taking Industry endorsed tests for better employability and put them on the
personal web page along with the resume
Confidentiality feature to define privacy level eg block current employer from accessing
profile.
3.1 User Classes and Characteristics
There are four categories of users accessing this system. We will differentiate these users on the
basis of their roles and access rights.
Employee: Employee means job seeker who is interested to have a job. They must have
their login account on this portal.
Employer: Employer means job provider who is interested to find employees. They also
must have their login account on this portal.
Job Portal Administrator: The person, who is responsible for the management,
maintenance and administration of this portal.
Visitors: The person who is just visiting this portal. He or She can just only search
available jobs. He or She can neither apply for jobs nor post jobs.
3.2 Operating Environment
• Supports all web browsers like Mozilla Firefox, Google Chrome, Internet Explorer
3.3 Design and Implementation Constraints
1. Any person is allowed to create his/her login account and register himself/herself on this portal.
2. Only registered persons can apply for jobs. The persons who don’t have any account on this
portal can only see the posted jobs.
3. Any company can’t post their job on this portal that is not registered to this portal.
4. No one have rights to change the information of someone else account on this portal.
5. No file except PDF and doc format can be uploaded on this portal.
6. Once an employee apply for a job. He can’t apply again for this job. (Because he has already
applied for this job).
7. No one can maintain and manage this portal except the administrator of this portal.
8. Any user who likes to register him/her on this portal must have an email address (like yahoo,
hotmail, Gmail or etc.). Because alert messages will be sent to that mail box.
3.4 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.>
3.5 Assumptions and Dependencies
Website Administrator: There should be at least one website administrator who can
manage and maintain this website.
Server based software: The software will be installed on server. So it will be client
independent i.e. software needs not to be installed on each client machine.
Software on client end: The only software needed on the client end is the web browser.
If a client doesn’t have a web browser he can’t get benefit from this job portal.
Internet based: As this software is an internet based i.e. the organization or any
employee that is going to use this job portal, must have an internet connection.
4. External Interface Requirements
4.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
Software Requirements Specification for Online Job Portal Page 7
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.>
4.2 Hardware Interfaces
The selection of hardware is very important in the existence and proper working of any software.
In the selection of hardware, the size and the capacity requirements are also important. The job
portal can be efficiently run on Pentium system with at least 128MB RAM and Hard disk drive
having 20GB. Floppy disk drive of 1.44MB and 14 inch Samsung color monitor suits the
information system operation.(A Printer is required for hard copy output).
4.3 Software Interfaces
One of the most difficult tasks is that, the selection of the software, once system requirement is
known is determining whether a particular software package fits the requirements. After initial
selection further security is needed to determine the desirability of particular software compared
with other candidates. This section first summarizes the application requirement question and
then suggests more detailed comparisons.
•Other Tools & Technologies -------- Java (JDK), Servlets (JSDK), JSPl
4.4 Communications Interfaces
<Describe the requirements associated with any communications functions required by this
product, including e-mail, web browser, network server communications protocols, electronic
forms, and so on. Define any pertinent message formatting. Identify any communication
standards that will be used, such as FTP or HTTP. Specify any communication security or
encryption issues, data transfer rates, and synchronization mechanisms.>
5. System Features
<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.>
5.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.>
REQ-1:
REQ-2:
Software Requirements Specification for Online Job Portal Page 9
5.2 System Feature 2 (and so on)
6. Other Nonfunctional Requirements
6.1 Performance Requirements
Server Side
Client Side
The system is a web based application clients are requiring using modern web browser
such as Mozilla Firefox 1.5, Internet Explorer 6 and Enable cookies.
• 1GB RAM
• 512MB RAM
6.2 Safety Requirements
6.3 Security Requirements
All users should be properly authenticated before allowed entry into the system
Authentication will be based on a E-mail address, and a password. All activities on the system
must be logged.
6.4 Software Quality Attributes
<Specify any additional quality characteristics for the product that will be important to either the
customers or the developers. Some to consider are: adaptability, availability, correctness,
flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability,
and usability. Write these to be specific, quantitative, and verifiable when possible. At the least,
clarify the relative preferences for various attributes, such as ease of use over ease of learning.>
6.5 Business Rules
<List any operating principles about the product, such as which individuals or roles can perform
which functions under specific circumstances. These are not functional requirements in
themselves, but they may imply certain functional requirements to enforce the rules.>
7. Other Requirements
The user must be agreed with all the term and conditions that have provided by the
System Administrator, local authority and Should Obey to the all International standards and
Protocols.
7.1Licensing Requirements
The usage is restricted to only O.J.P. Neil Beato who is developing the Online Job Portal System
and signs the maintenance contract.
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>
Appendix B: Analysis Models
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>
Appendix C: To Be Determined List
<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they
can be tracked to closure.>