Blog

Test model and requirement management

In prior posts, I have discussed test models as a package of test scenarios. Each scenario has specific requirements. The development of software for the telecommunications industry deals with large systems like OSS/BSS, and requirements creation is the initial phase of the project.
11 November 2014
QA consulting
Quality assurance
The article by Julia Ilyushenkova
Head of Telco and Web applications testing department

In prior posts, I have discussed test models as a package of test scenarios. Each scenario has specific requirements. The development of software for the telecommunications industry deals with large systems like OSS/BSS, and requirements creation is the initial phase of the project.

This phase is critical, as requirements errors can result in wasted time and increased cost. Analysis shows that the later readjustment phase can consume 30 to 40 percent of the total effort expended on a software development project.

Researchers have even indicated that about 50 percent of the bugs can be caused by requirements errors; thus, requirements errors may lead to between 70 to 85 percent of all project readjustment costs.

As you can see in Figure 1, the correction of requirements defects can cost up to 110 times more if found in operation than it would if the same defect had been discovered during the requirements definition phase.

Figure 1. Requirements cost to correct a requirement defect depending on when it is discovered. Source: M.P.Singh and Rajnish Vyas

We as QA consultants advise that two main parts of the requirements creation phase should be separated – into requirements development and requirements management.

Figure 2. Difference between requirements development and requirement management.

The requirements development phase aims to collect information, make analysis, review and approve requirement. As a rule, it results in documents package creation. These are documents about image and product borders, software requirement specifications, data vocabulary and a corresponding analysis model.

The review and approval of this package defines the base requirements version (i.e. the agreement between developers and customers). The requirements management stage includes all actions supporting integrity, accuracy and timeliness of renovation of the agreement on requirements during the project.

Management of requirements includes:

  • Management of changes for the base version of requirements;
  • Maintenance of project plans actuality according to changing requirements;
  • Management of versions of separate requirements and the documentation of requirements;
  • Control of a condition of requirements in the base version; and
  • Management of logic connections between separate requirements and other materials with the project.

The best practices and characteristics for requirements management are as follows:

  • Completeness – Each requirement should completely describe the functionality that will be implemented in the software. In other words, it should contain all information necessary for developers to create the fragment of functionality.
  • Correctness – Each requirement should describe the desirable functionality precisely. Connections (links) with sources of requirements is necessary for correctness.
  • Practicability – Possibility to implement each requirement under certain conditions and restrictions imposed by the system and operating environment. Here it is needed to provide interaction of developers with experts in marketing and analysts the ability for extraction of all requirements.
  • Necessity – Each requirement should reflect what is really necessary for users or necessary to meet external system requirements or standards.
  • Setting of priorities – Setting of priorities is necessary to cope effectively with budget reduction, infringement of terms, loss of personnel, or the addition of new requirements in the course of development.
  • Clarity – All readers of requirements should interpret them the same. All special and potentially confusing terms should be provided in a glossary.
  • Verifiability – Requirement management helps to identify the incomplete, not agreed upon, impracticable or ambiguous requirements.

More Posts

gaming-qa
24 August 2023,
by a1qa
4 min read
Ready, steady, test: How QA drives seamless gaming experiences
Why is QA pivotal for delivering unmatched player experiences? How to level up video game quality? Find the answers in the article.
Cybersecurity testing
Functional testing
Localization testing
Performance testing
Quality assurance
Test automation
Usability testing
alina
25 July 2023,
by a1qa
4 min read
Interview with Alina Karachun, Account director at a1qa: unearthing the power of a true IT leader
Read the interview with Alina Karachun, Account director at a1qa, about the importance of creativity and feedback for executives and their teams, what is ethical leadership, and many more.
Interviews
Quality assurance
why-do-bugs-get-missed
17 April 2023,
by a1qa
4 min read
Why do bugs get missed? Learn the problems and tips to avoid them
Still, finding overlooked bugs after the app goes live? Let’s find out why this happens and how to fix it.
Quality assurance
Test automation
a1qa-articles
31 January 2023,
by a1qa
5 min read
Best of 2022 by executives: 8 most visited a1qa blog posts
Let’s look back and revisit the most visited a1qa articles of 2022!
Quality assurance
Test automation
qa-trends
12 January 2023,
by a1qa
4 min read
The future of software testing: top 4 impactful trends that will dominate in 2023
Consider the major industry trends for the upcoming year to know how to improve current QA strategies and stay ahead of the curve.
QA trends
Quality assurance
Test automation
test-automation
7 December 2022,
by Dileep Marway
3 min read
Release at pace with test automation: What, why, and how to measure success?
An automation-first approach is key to enhancing testing capabilities and increasing overall operational efficiency. However, I would suggest justifying its implementation, so that it can deliver the promised value.
Quality assurance
Test automation
what-is-a-culture-of-happiness
2 December 2022,
by Dileep Marway
3 min read
What is a сulture of happiness for a QA company?
Great culture drives employee engagement and satisfaction, contributes to an impressive work output, and improves organisational performance. But how do we build a culture of happiness? In this blog, I will share more on the answer to this.
Quality assurance
agile-qa
30 November 2022,
by Dileep Marway
3 min read
Agile QA – what is needed for greater flexibility and speed?
What should your QA team focus on to become truly agile, enable quality at speed, and contribute to lasting performance improvement? In addition to introducing test automation, I suggest considering shared responsibility for software soundness.
Agile
Quality assurance
interview-with-dileep
28 November 2022,
by a1qa
9 min read
Interview with Dileep Marway on a series of articles “Agility and speed: Supercharging your business strategies with QA”
We cooperated with the VP of Engineering and Quality at SHL to present you with a series of his blog posts on: culture of happiness, test automation, and Agile-driven QA. Happy reading!
Agile
Quality assurance
Software lifecycle QA
Test automation

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.