Software Requirements
Specification
for
JOB RECRUITMENT SYSTEM
Version 1.0 approved
Prepared by D.LAKSHMAN,D.MALAKONDAIAH,D.HEMA HARIKA
KLUNIVERSITY
<date created>
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project>
Page ii
Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction ..............................................................................................................................1
1.1
1.2
1.3
1.4
1.5
Purpose ............................................................................................................................................ 1
Document Conventions.................................................................................................................... 1
Intended Audience and Reading Suggestions .................................................................................. 1
Product Scope .................................................................................................................................. 1
References........................................................................................................................................ 1
2. Overall Description ..................................................................................................................2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Product Perspective ......................................................................................................................... 2
Product Functions ............................................................................................................................ 2
User Classes and Characteristics ..................................................................................................... 3
Operating Environment.................................................................................................................... 3
Design and Implementation Constraints .......................................................................................... 4
User Documentation ........................................................................................................................ 4
Assumptions and Dependencies ...................................................................................................... 4
3. External Interface Requirements ...........................................................................................4
3.1
3.2
3.3
3.4
User Interfaces ................................................................................................................................. 5
Hardware Interfaces ......................................................................................................................... 5
Software Interfaces .......................................................................................................................... 5
Communications Interfaces ............................................................................................................. 5
4. System Features........................................................................................................................5
4.1 System Feature 1 .............................................................................................................................. 8
4.2 System Feature 2 (and so on) ........................................................................................................... 8
5. Other Nonfunctional Requirements .......................................................................................8
5.1
5.2
5.3
5.4
5.5
Performance Requirements .............................................................................................................. 9
Safety Requirements ...................................................................................................................... 10
Security Requirements ................................................................................................................... 10
Software Quality Attributes ........................................................................................................... 10
Business Rules ............................................................................................................................... 10
6. Other Requirements ..............................................................................................................10
Appendix A: Glossary..................................................................................................................10
Appendix B: Analysis Models .....................................................................................................10
Appendix C: To Be Determined List ..........................................................................................11
Revision History
Name
Date
Reason For Changes
Version
Software Requirements Specification for <Project>
Page 1
1. Introduction
1.1 Purpose
The recruitment and selection is the major function of the human resourcedepartment and recruitment
process is the first step towards creating the competitivestrength and the recruitment strategic advantage
for the organizations.Recruitment process involves a systematic procedure from sourcing the candidatesto
arranging and conducting the interviews and requires many resources and time.
1.2 Document Conventions
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
To structure the recruitment policy of company for different categories of employees.To analyze the
recruitment policy of the organization and to provide a systematicrecruitment process.It extends to the
whole organization. It covers corporate office, sites and worksappointments
1.5 References
This web application has been prepared on the basis of discussion with Teammembers and also taken
information from following websites,
Google.com
Wikipiedia.or
Software Requirements Specification for <Project>
Page 2
2. Overall Description
The following description gives the general factors that affect system and its requirements.
Candidate should finish his/her degree and should have proper certificate whileapplying for job and the
candidate should satisfy the eligibility criteria.
The resume should be in the form what that company specified while advertising.
The HR has the full permission to select or reject the candidate for interview.
If the candidate is selected for the particular job means all details about thecandidate will be added to the
company database and the modification can also bedone.
2.1 Product Perspective
HR and Candidate plays a major role in the recruitment process.
The necessary details of the candidate have to be submitted to the HR.
Verification has been done by the HR.
Selected candidate should be call to Interview.
HR intimates the selected candidate.
Finally Candidates accept or reject his offer letter
Software Requirements Specification for <Project>
Page 3
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
Use Cases:
1.
Notify Vacancy:
In this use-case the HR notify the vacancy details for the required job. If required job. If any vacancy
available means the appropriate notification need to bedone.2.
Fill Referral form:
Application form for the job will be filled by candidate in addition to theapplication form the resume for
the candidate also need to submit. Many candidateswill apply for the post from those lists of candidate HR
will do the short listing process according to their requirement of the post.
3. Interview Process:
Eligible candidate will be called for the interview process in interview process three steps will be carried
out that is Aptitude, Group Discussion (GD) andInterview.
4. Status:
After the interview process, HR list the selected candidates and gives offer letter to him/her. The candidate
accepts or rejects the offer letter to fill the vacancy
The Users are the candidates who should complete his/her degree with percentageabove 80).
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.>
Software Requirements Specification for <Project>
Page 4
2.5 Design and Implementation Constraints
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.>
2.7 Assumptions and Dependencies
The project is done on the basis of selection of candidates for the company
Every user should be comfortable working with computer and net browsing
.
He should be aware of the Recruitment System.
User must have comfortable knowledge of English language.
Software Requirements Specification for <Project>
Page 5
3. External Interface Requirements
3.1 User Interfaces
Our system will make use of the existing web browser such as Microsoft internetexplorer or Mozilla
3.2 Hardware Interfaces
Operating system: windows 9x or above, MAC or UNIX.
Pentium 2.0 GHz or higher
RAM: 256 Mb or more
Hard drive: 10 GB or more
3.3 Software Interfaces
Client on internet: Web Browser, Operating System (any)Web Server: WAS, Operating System (any)Data
Base Server: DB2, Operating System (any)
3.4 Communications Interfaces
The Recruitment System will be connected to the World Wide Web
4. System Features
Usability
Software Requirements Specification for <Project>
Page 6
The system shall allow the users to access the system form the internet usingHTML or its derivative
technologies. The system uses a web browser as aninterface.
Since all users are familiar with the general usage of browser, no specific training isrequired.
The system is user friendly and self-explanatory.
3.4 Reliability
The system has to be very reliable due to the importance of data and damagesincorrect or incomplete data
can do.
Availability
The system is available 100% for the user and is used 24 hours a day and 365 daysa year.The system shall
be operational 24 hours a day and 7 days a week.
Mean Time between Failures (MTBF)
The system will be developed in such a way that it may fail once in a year.
Mean Time to Repair (MTTR)
Even if the system is fails, the system will be recovered back up within an hour or less.
Accuracy
The accuracy of the system is limited by the accuracy of the speed at which theemployee of the library and
users of the library use of the system.
Access Reliability
The system shall provide 100% access reliability.
3.5PerformanceResponse Time
The splash page or information page should be able to be downloaded within aminute using a 56k modem.
The information is refreshed every two minutes. The systemshall respond to the member in not less than
two seconds from the time of the requestsubmittal. The system shall be allowed to take more time when
doing large processing jobs.
Software Requirements Specification for <Project>
Page 7
Throughput
The number of transactions is directly dependent on the number of users.
Capacity
The system is capable of handling 250 users a time.
3.6Supportability
The system designers shall take in to considerations the followingsupportability and technical limitations.
Internet Protocols
The system shall be comply with the TCP/IP protocol standards and shall designedaccordingly.
Maintenance
The maintenance of the system shall be done as per the maintenance contract.
Standards
The coding standards and naming conventions will be as per the Americanstandards.
3.7Design Constraints
The user should have sufficient knowledge of computers.
The users must know the English language, as the user interface will be
Provided in English.
Software Requirements Specification for <Project>
Page 8
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
This section describes in detail all the functional and non-functional requirements.
3.1 Use-Case Specifications1. Notify Vacancy
The HR head of a particular region shall inform details about the vacancy tocandidates.
Pre-Condition:
Vacancy must exist.
Post-Condition:
Details about the vacancy are informed.
2. Fill Referral Form
Software Requirements Specification for <Project>
Page 9
Online forms are filled by the Candidate .HR head process the filledforms .HR heads selects the list of
eligible candidates.
Pre-Condition:
Online form must exist. (All the mandatory fields should be filled by the candidate)
Post-Condition:
Forms filled are stored in a Information System for processing.The filled forms are sent to the HR. The HR
head produces the list of eligible candidates.
3. Interview Process
The Interviews are conducted by the HR head of the region that has thevacancy. The list of selected
candidates is obtained after the interview process.
Pre-condition:
Study the job description carefully and make sure your applicationand/or resume compliments what the
company is looking for. Plan what to wear to your interview.
Post-Condition:
if you get the job, go celebrate! Immediately send thank-youletter. Negotiate your salary when you are
offered the job. If you didn’t despair, just startagain.
3.Status
Candidate is informed about selection the job. Candidate accepts the joboffer to fill the vacancy. Or
Candidate rejects the offer letter. Candidate applicationis rejected.
Pre-Condition:
Candidate is selected for the job.
Post-Condition:
Candidate accepts or rejects the offer.
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 understand the intent and make suitable
design choices. Specify the timing relationships for real time systems. Make such requirements as
specific as possible. You may need to state performance requirements for individual functional
requirements or features.>
Software Requirements Specification for <Project>
Page 10
5.2 Safety Requirements
<Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well as
actions that must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>
5.3 Security Requirements
<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect the
product. Define any security or privacy certifications that must be satisfied.>
5.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.>
5.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.>
6. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>
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.>
Software Requirements Specification for <Project>
Page 11
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.>