Requirement Analysis

What Are Requirements?

• Starting with a basic requirement definition, requirements in digital can
be categorized into two types:
• functional
• non-functional
• we’ll focus on these two types of requirements that we usually see in
digital products and services.
• other types, such as
• Legal
• technical requirements
 • depending on the context, the person in charge of handling requirements
documentation may need additional training in technical writing
information mapping.
What Are Functional Requirements?
• For a digital engagement, functional requirements relate to a product’s
functionality
• its capabilities
• Usability
• features, and operations
1. Functional requirements are clearly referenced as such in Functional
Requirements Documentation (FRD)
1. FRD provides a more in-depth elaboration of these requirements, which are gathered
as soon as a project kicks off and up until a project begins production.
2. Statement of Work (SOW) outlines the high-level goals and requirements
of the desired product
• requirements are not limited to the window of time before
production:
• change order documentation • warranty documentation ,etc.
• are useful forms of ongoing requirements documentation that occurs
throughout a project
• or even beyond the project!
• For as long as you work with a client, the documentation is
evergrowing and ever-evolving.
• Depending on the size and scope of a project, you might decide on a
milestone between the SOW and FRD.
• Some teams create Business Requirements Documentation (BRD) to
provide a formal midway sign-off—an expectation checkpoint—for all
parties.
• This presents the opportunity for the Project Manager to confirm the
team is heading in the right direction before getting too far down the
road with deliverables.
What Are Non-Functional Requirements?
• Non-functional requirements encompass anything not related to a
product’s functionality:
• its performance
• Stability
• Security
• technical specifications, to name justa few types of non-functional
requirements in the digital industry.
6 -Important Requirements Gathering Techniques
Why are requirements management tools
important
• In our real-world projects, we deal with far too many of those “he said,
she said” situations where malformed or vague requirements.
• end up tanking our projects business relationships.
• sometimes the task of requirements documentation falls to a project
manager or someone with limited technical proficiency and domain
knowledge.
• not forget that documenting requirements is simply a tedious task
• no one actually wants to spend their time creating (or reading) a 100-page print-
out of an Excel spreadsheet.
Why are requirements management tools
important
• “When budgets are thin, timelines are tight, and scope is creeping,
requirements documentation tends to be the first deliverable to go
and the last deliverable to be considered.”
• There a wealth of tools out there to make requirements
management simpler—easier to
• Track
• Test
• Analyze
• Visualize
 • and communicate to stakeholders.
What Is RM?
• Requirements management tools are any tools that help you
remove
• ambiguity
• Assumptions
• wishful thinking
• gray area
• interpretations—from a project’s requirements.
• As such, the end goal of requirements management (RM) is to
operate with clear, realistic, and agreed-upon requirements.
 • throughout the development process so you can easily test a
product or project to ensure it does what it’s supposed to do.

What Are Requirements Management Tools?

• The requirements management tools that you require
will be different depending on your project methodology and
goals.
• Likewise, your approach to requirements themselves will
vary depending on methodology.
• For example, some teams use another word for requirements such as
• “user stories”
• “product requirements”
 • “simply”
• “features”

Basic Requirements Tools

• For a very basic requirements management planning
• you might simply use a
• spreadsheet or a word document template to fill in your requirements documentation.
• Excel or Google Sheets and a word document are your most basic requirements tools, and for
some cases, they work just fine.

• However, they can become problematic.

• In this case, you rely heavily on individuals to update the documents
• it takes time and effort to ensure you’re working with the most recent version across teams.
 • Managing feedback in a central place becomes a challenge-
• you have to manage strings of emails and in-person feedback that must be
inputted manually into your documentation.

Complex Requirements Tools

• Complex requirement management planning, your tool might be an
entire software system for managing the relationships between
requirements-
• analyzing the impact of any changes
• managing approvals, and more.
Benefits of Requirement Management tool
Requirements Management Tools Selection Criteria
• Whatever you use, there are some main functions that any requirements
tool has to fulfill.
• Serve as a point of reference to document a project’s requirements
and implementation
• Serve as a blueprint to help stakeholders understand what to expect out of the project
• By and large, there’s a huge range of features offered in requirements
management tools
• including modules for product management
• portfolio management
• release management
• customer management.
 What to look for in RM- tool
• This includes the ability to define requirements, model relationships
between them-

This includes graphical tools and reports

Ultimately, being able to establish automatic relationships across requirements is
key in requirements management.
This is one of the major advantages of using requirements management software over a simple
spreadsheet.
• A good requirements software should include functionality for
interaction between users.
The basic integrations you should look for are integrations with software development tools (SW
development tools) word document, and spreadsheet tools
 Requirement Analysis and
Practice – ReqView tool
ReqView
• ReqView is a simple to use requirements management tool
• which you can capture structured requirements for a software or system product
and track traceability to design, tests and risks of the developed product.
• ReqView is the solution for small and medium size companies
• Medical
 • Aerospace
• Defense
• Automotive
• Electronics
• Automation
• ... industries saving a lot of efforts with documenting compliance with
industry standards.

ReqView
• Ease of Use - Capture well structured requirements and their relationships in a
familiar tabular view resembling MS Word and Excel.
• Flexibility - Manage requirements, tests, risks and other project artifacts in one
place using waterfall or agile process, or something in between.
• Traceability - Link requirements and other objects, browse requirements
traceability matrix and analyze impact of changes.
• No Server Needed .
• Offline Collaboration - Collaborate offline in your distributed team by storing the
project on a shared network drive or in your preferred Version Control System.
• Open File Format - Do not be afraid of vendor lock-in. ReqView project data are
human readable files with open file structure.
• Reasonable Price - Use the basic ReqView features for free or choose an annual
plan enabling advanced features and remote support.
ReqView Features
• User Defined Attributes
• Custom Traceability Links
• History Tracking
• Export to HTML, Word, CSV
• Import from Word and CSV
• Custom Multilevel
• Traceability Reports
• Offline Collaboration
Contents • Custom Attributes

• Install ReqView • Traceability Links

• Requirements Projects • Track Changes

• Review Documents • Compare Projects

• Edit Documents • Team Collaboration

• Keyboard Shortcuts • Google Drive Integration IMPORT

AND EXPORT
• Templates Import from MS Word
• Examples Import from MS Excel Export to
HTML Export to CSV Custom Export
• MANAGE INTEGRATION
REQUIREMENTS Command Line File
Data Format CSV
Roundtrip with DOORS
ReqIF Import from DOORS
ADMINISTRATION
License Server