lOMoARcPSD|39659544

Software Requirement
Specification

For

<Naukri.Com>
Prepared by <Yug Rohra>

<Lovely Professional University>

<Reg No:-12317117>

<submitted To:-Shivani Sharma>

 lOMoARcPSD|23499314

TABLE OF CONTENTS

1. Introduction............................................................................................................................3
1. Purpose .3
2. Document Conventions .3
3. Intended Audience and Reading Suggestions .4
4. Definitions, abbreviations .4
1. Definitions .4
2. Abbreviations .5
1.5 Project Scope .7
2. Overall Description................................................................................................................8

2.1 Product Perspective .8

2.2 Product Features .9
2.3 User Classes and Characteristics .10
2.4 Operating Environment .10
2.5 Design and Implementation Constraints .1
2.6Assumptions and Dependencies .12
3. Specific Requirements.........................................................................................................12
3.1 Functional Requirements .12
4. External Interface Requirements.......................................................................................18 .18
.18
1. User Interfaces
.18
2. Hardware Interfaces
.18
The application must run on any OS. Ex. Windows, Mac, android.
4.3 Software Interfaces
.19
.19
5. Other Nonfunctional Requirements...................................................................................19 .19

1. Performance Requirements
2. Safety Requirements
3. Security Requirements
6. Other Requirements............................................................................................................20

`
Hath rh: p:Wks and Comgcnsr+tJou Ca+gany z'zs off':Plug.So, fry IT+c ‹ou<'crsr+thou stJnouudcd by
kirn. h: nstJccd it '”E'rcz Jf'vc u zi: net Jookfzg tér z job. yon look tar n Job. Yoz zi: canstzJttJ\'
I.Est nf Aezonş-ins / Abbrevlntìons
 SRS DOCUMENT

1 A DeBntżtooq .Srroaş'azs aoö Aëbrey1attons:-

1.5.1 Wuctton& Reqnlceinenls

Performance

8offn bre Quedó Attrtbwtes

• FmpIpx•idzsii o1'ñdnmbzmooi xwipwm ilaul s

Browse

hlgn ing I n

• Maintenance of w'zbslte
£E2MorŒn ouMr*qobemeoæ

Scree' Słăe Red iúcemenł

Non-Functional Requirements
Non-functional requirements are essential aspects of
a system that describe how it should behave, rather
than what it should do. For a website like Naukri.com,
which is a job search platform, several non-functional
requirements are critical to ensure its effectiveness,
efficiency, security, and user satisfaction. Here are
some non-functional requirements that could apply to
Naukri.com:
1.Performance:
1. Response Time: The website should load
within a reasonable timeframe, typically a few
seconds, to ensure a smooth user experience.
2. Scalability: The platform should be able to
handle a large number of concurrent users
without significant degradation in
performance.
3. Throughput: Ability to handle a large number
of job postings, searches, and user
interactions simultaneously without crashing
or slowing down.
2.Reliability:
1. Availability: Naukri.com should be available
24/7 except during scheduled maintenance
windows.
2. Fault Tolerance: The platform should be
resilient to failures, ensuring that even if one
component fails, the system as a whole
remains operational.
3. Backup and Recovery: Regular backups of
user data should be taken to ensure quick
recovery in case of data loss or corruption.
3.ecurity:
1. Data Security: User data (both personal and
professional) should be encrypted and stored
securely to prevent unauthorized access or data
breaches.
2. Authentication and Authorization: Proper
mechanisms should be in place to authenticate
users and grant them appropriate access levels to
the system's functionalities.
3. Protection Against Common Attacks: Implement
measures such as Cross-Site Scripting (XSS)
prevention, SQL injection prevention, and CSRF
(Cross-Site Request Forgery) protection to
safeguard against common web attacks.
4.Usability:
1. Accessibility: The website should be accessible to
users with disabilities, complying with accessibility
standards such as WCAG (Web Content
Accessibility Guidelines).
2. User Interface Consistency: Consistent layout,
design elements, and navigation throughout the
website to enhance user experience and ease of
use.
3. Multilingual Support: Support for multiple
languages to cater to a diverse user base.
5.Scalability:
1. Horizontal and Vertical Scalability: Ability to scale
both by adding more servers (horizontal) or
enhancing existing servers (vertical) to handle
increased load.
6.Maintainability:

•Modularity: The system should be modularized to

facilitate easier maintenance and future enhancements.
•Documentation: Comprehensive documentation for
developers and administrators to understand the system
architecture, APIs, and configurations.
7.Regulatory Compliance:

•Data Privacy Regulations: Compliance with relevant

data protection regulations such as GDPR (General Data
Protection Regulation) or local data privacy laws.
•Job Posting Regulations: Adherence to labor laws and
regulations regarding job postings and recruitment
processes in relevant jurisdictions.
These are just some examples of non-functional
requirements for Naukri.com. The specific requirements may
vary based on factors such as the target audience, business
goals, and regulatory environment.