0% found this document useful (0 votes)
15 views

Effective Requirements Writing and Resume

Resume

Uploaded by

vinay25yadav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views

Effective Requirements Writing and Resume

Resume

Uploaded by

vinay25yadav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

How to write

Effective
Requirements -
Explained With
Examples

Diwakar Singh
Understand the Project
Context
Before you start writing requirements,
it's essential to have a thorough
understanding of the project's scope,
objectives, and constraints. Engage with
stakeholders, conduct interviews, and
review existing documentation to gather
essential information.

Example:
Project Name: Online Shopping Website

Objective: Develop a user-friendly online


shopping platform for our customers.
Use a Consistent
Structure
Having a consistent structure for your
requirements helps stakeholders easily
navigate and understand the information. A
widely used approach is the "SMART"
criteria, which stands for Specific,
Measurable, Achievable, Relevant, and
Time-bound.

Example:
Requirement ID: OSW-R001
Title: User Registration
Description: The system shall allow new
users to create an account with a valid email
address and password, providing access to
personalized features and order history.
Be Specific and
Unambiguous
Ensure that your requirements are clear,
precise, and unambiguous. Avoid vague
language and define the expected behavior,
inputs, outputs, and constraints explicitly.

Example:

Requirement ID: OSW-R002


Title: Product Search
Description: The system shall allow users to
search for products by name, category, and
price range. The search results should be
displayed within five seconds.
Include Functional and Non-
Functional Requirements
Functional requirements describe what the system
should do, while non-functional requirements
specify how the system should perform
(performance, security, usability, etc.).

Example:
Functional Requirement (FR):
Requirement ID: OSW-R003
Title: Add to Cart
Description: Users should be able to add items to
their shopping cart from the product details page.

Non-Functional Requirement (NFR):


Requirement ID: OSW-R004
Title: Response Time
Description: The system shall respond to user
actions within two seconds under normal load
conditions.
Use Use Cases or User Stories
For complex requirements, you can use use cases
or user stories to capture interactions between
users and the system. Use cases provide detailed
step-by-step interactions, while user stories are
simpler and focus on end-user needs.

Example (User Story):

As a registered user,
I want to be able to update my shipping address
So that I can receive my orders at the correct
location.
Prioritize Requirements
In some cases, not all requirements can be
implemented within the project constraints. Work with
stakeholders to prioritize requirements based on
business value and project constraints.

Example:
Priority: High
Requirement ID: OSW-R005
Title: Secure Payment Processing
Description: The system shall use SSL encryption to
ensure secure payment transactions.
Priority: Medium
Requirement ID: OSW-R006
Title: Wishlist Functionality
Description: Registered users shall be able to add
products to their wishlist for future reference.
Review and Validate Requirements
Before finalizing the requirements, conduct a thorough
review with stakeholders to ensure accuracy,
completeness, and alignment with the project's
objectives.

Example:
Review Meeting Notes (Extract):

Stakeholder A: Requirement OSW-R003 should


also allow users to specify the quantity of items to
be added to the cart.
Stakeholder B: For OSW-R005, make sure it
complies with PCI-DSS standards for payment
security.
Manage Changes and Version Control

Requirements may evolve throughout


the project lifecycle. Implement a change
management process and version
control to track modifications and
ensure everyone is working with the
latest requirements.
Thank You

You might also like