5 votes

Software Requirements Engineering

The definition of ‘functional requirement’ is that it essentially specifies something the system should do. The definition for a non-functional requirement is that it essentially specifies how the ...
Bharat Mane's user avatar
  • 6,775
5 votes

How to ask better questions as QA to business analyst regarding functional specs to add value?

As others have said, communicate the way the BA is most comfortable with. Some other suggestions: Start by confirming your understanding of the functional spec/feature behavior - I can't stress ...
Kate Paulk's user avatar
  • 31.5k
4 votes

How to ask better questions as QA to business analyst regarding functional specs to add value?

It's not an easy question and I am not sure it belongs in SQA, but have you tried to set up meetings and ask the questions face to face ? Many times a small demo or a few minutes of screen time can ...
Rsf's user avatar
  • 7,079
4 votes
Accepted

The third amigo problem when customer is unknown

This is an example of building a software system for the marketplace. In this case, you have many customers or users, each of which has its expectations for the system. However, someone must have ...
Thomas Owens's user avatar
  • 1,450
4 votes
Accepted

What are the ingredients for a successful Three Amigos meeting?

Make testing the focus For a given feature that you are discussing, as a group, go through what you plan for unit tests, integration tests and end-to-end tests. Talk about how you will do ...
Michael Durrant's user avatar
4 votes

How not to do chaos in software requirements from the beginning?

Ask more questions. Ask better questions. (Try Example Mapping, or other solutions listed in this question)
Mate Mrše's user avatar
  • 4,119
3 votes

What are the ingredients for a successful Three Amigos meeting?

One of the ways is Example Mapping. All you need is a pack of coloured cards and pens and preferably a table. Write the story on a yellow card and place it at the top of the table Write the ...
Mate Mrše's user avatar
  • 4,119
3 votes
Accepted

Proper way to form a functional requirement

To my understanding: As the developer, even you will not perform this action; you will still need to test running it as part of your unit tests. In the case of this action can not be performed due ...
Yu Zhang's user avatar
  • 9,942
3 votes

How should Software Testers improve the process of Requirements Analysis?

Review business and functional specifications on early phases. This should not take much time. Don't be afraid of asking questions and to look silly. After all this is your job to find bugs and bugs ...
Alexey R.'s user avatar
  • 11.6k
3 votes

How to ask better questions as QA to business analyst regarding functional specs to add value?

See if you can get some time with the BA to walk through questions. Maybe they comprehend better by seeing than by written description. If you aren't in the same office a quick skype (or what ever ...
CKlein's user avatar
  • 1,265
3 votes

What is the best practice to analyze the requirement as a tester?

It is not answerable. Answer is: "QA should devote as much time as needed to find out all inconsistencies in requirements, but don't waste anything beyond that". So you are back on square one. To ...
Peter M. - stands for Monica's user avatar
3 votes

What is the difference between SRS, RA, FRS, BRS documents?

The short-short answer - it depends. The longer version Despite the names and theoretical definitions, the differences in practice in my experience come down to how a particular organization chooses ...
Kate Paulk's user avatar
  • 31.5k
3 votes
Accepted

How not to do chaos in software requirements from the beginning?

I think this question is as a result of not following two of the most important testing principle: Early testing Early testing states that testing activity should begin as early as possible. This ...
PDHide's user avatar
  • 11.1k
2 votes

How can ISO 9000 and ISO 25000 Quality definition differ - parts included

The main difference it that requirements are what has been written down in the requirements documents, both the top level requirements document as supplied by the customer and in the derived ...
Steve Barnes's user avatar
2 votes

What is the best practice to analyze the requirement as a tester?

It’s better to catch the requirement ambiguities and fix them in the early development life cycle itself. Project functionality (What should be done and what should not be done). Software, Hardware ...
Shraddha's user avatar
2 votes

How to ask better questions as QA to business analyst regarding functional specs to add value?

First when you go through the Change request document, you read it carefully, inline it with current implementations and the raise queries to your BA with previous implementation and current change ...
Prasad_Joshi's user avatar
2 votes
Accepted

How should I document tests and requirements when third-party software is broken?

The short answer: you can't prevent regression in third party software. More detail: Third party software, as one of the comments mentioned, is outside your control. Since it's essential to your ...
Kate Paulk's user avatar
  • 31.5k
2 votes

How should Software Testers improve the process of Requirements Analysis?

You see that as a problem, I see that as normal development process in an Agile team. There is a reason why The Agile Manifesto says Welcome changing requirements, even late in development Like ...
Rsf's user avatar
  • 7,079
2 votes

What are the ingredients for a successful Three Amigos meeting?

I'd also add that seeing the story beforehand is a good way of making the Three Amigos session more likely to provide benefit. Thinking up questions and issues on the spot when you've only just seen ...
Moorpheus's user avatar
  • 265
1 vote

How should I document tests and requirements when third-party software is broken?

You can't really account for third party software being broken. It's outside of your control. But you should document it for several reasons: It might happen again and your documentation will give ...
newsn31's user avatar
  • 609
1 vote

What does QA need to take into consideration while checking that tasks are valid

Not answering the question directly, but using templates in tickets would help the author and you better understand what is expected and what is missing. It really depends on the tool you are using ...
Rsf's user avatar
  • 7,079
1 vote

What does QA need to take into consideration while checking that tasks are valid

That is the job of the whole team in agile process. Firstly all of people involved in development process sit together and come up with Definition of ready, which is basically a checklist for task/...
Prome's user avatar
  • 1,013
1 vote

How to ask better questions as QA to business analyst regarding functional specs to add value?

just to be clear, the function of testing is to verify the behavior of the entity under test. the role of QA probably should not be to design or engineer the product (that is unless the company only ...
fishtoo's user avatar
  • 11
1 vote

How to ask better questions as QA to business analyst regarding functional specs to add value?

So here I can see two possible issues: BA does actually understand your questions but they do not want to take responsibility since there might be some tricky points or areas. BA does not understand ...
Alexey R.'s user avatar
  • 11.6k
1 vote
Accepted

What percentage of total Requirements for a system are defect?

Assuming that you are asking if there is some kind of typical measure of how many requirements for a given system are in fact incorrect in some way, the simple answer is it depends. Is a requirement ...
Kate Paulk's user avatar
  • 31.5k
1 vote

How should Software Testers improve the process of Requirements Analysis?

As a QA Tester, you can take some time out before starting testing and using that for writing extensive use cases which will cover most of the scenarios. This will help you in later stages. However, ...
Rishikesh's user avatar
  • 885
1 vote

What is the best practice to analyze the requirement as a tester?

Ensure the requirements address the objective or its purpose. Ensure negative scenarios or conflicting workflows of the requirements. Define scope of the requirements. What is covered and what is out ...
Zeeshan S.'s user avatar
1 vote

What is the best practice to analyze the requirement as a tester?

When I read the word requirement my spline shivers. It is just an idea, probably a flawed one, it is definitely not required. What that blog describes is traditional waterfall, where the costs go up ...
Niels van Reijmersdal's user avatar
1 vote

What is the difference between SRS, RA, FRS, BRS documents?

It always boils down to the question of how much documentation do we actually need and when does it start to become waste. Waste is documentation no one ever reads or uses. I think a lot of this ...
Niels van Reijmersdal's user avatar
1 vote

What is the best practice to analyze the requirement as a tester?

Testers should: Write Test Cases based on the requirements Clarify any assumed requirements Begin Testing at the requirement phase Requirements should be: clear and specific with no uncertainty ...
Brian McCarthy's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible