[SRS] Collecting known requirements in the ReqView
Closed this issue · 3 comments
Description
SRS stands for Software requirements specification.
Requirements gathering is also part of my role as a tester.
In most cases we do not have requirements and we have to develop them, that is also my role.
In this task, I will gather interesting links and information about creating a Software requirements specification.
Research is wider because first we have to consider if we mean Software requirements specification or something else, due to the fact that we do not have developed processes yet.
The difference between a Requirement and a Specification
Requirements They outline "what" the software must do. They outline the software from the end-user , business and stakeholder perspective.
Questions:
-
What scope does the SRS should cover in Handsontable?
-
How we can gather requirements?
Article about gathering req.
Software Requirements Gathering Techniques: A Formula For Success
- GitHub issue board
- discussion with support team, product owner, devs team.
- what customers use it for? We have a summary.
- Into which categories we divide the requirements? With which we should start? Main division - functional & nonfunctional.
Summary with comparision.
Arcticles & tutorials:
Your Guide to Writing a Software Requirements Specification (SRS) Document
Lifecycle of requirement
How to organize Requirements as a Business Analyst
Best practices and simple guide
Chores
- Research - tutorials, nomenclature.
- Implementation in phases.
Tools for managing requirements and test cases
- Reqview
- TestRail?
Reqview was chosen to describe requirements.
I am changing the title due to the fact that the essence of this issue is the grouping of requirements.