Free Subscription

Requirements.com is trusted by leaders and experienced professionals across the world. Start your subscription today, for free.

More Articles and Posts

Packaging Requirements... do they matter?

Packaging Requirements... do they matter?

You and your team have worked so hard making sure you understand your customer's needs, the market opportunities, or the problems you're trying to solve.  Then you spent countless hours developing, testing, and marketing your...
Software Prototyping instead of Requirements Gathering?

Software Prototyping instead of Requirements Gathering?

Are requirements gathering practices a thing of the past?  How can teams deliver software that meet the expectations of the customer without clearly documenting requirements? In this article,  Meredith Aourtemanche, executive aeditor...
User Interface and Report Business Needs

User Interface and Report Business Needs

Part 6 of Dan Tasker’s Requirements in Context series discusses detailed business needs for a user interface (UI) or report, and capturing those needs as detailed requirements in a spreadsheet-based template for user interface.
High-Level Requirement DOs and DON’Ts

High-Level Requirement DOs and DON’Ts

Part 4 of Dan Tasker’s Requirements in Context series provides guidelines for what a business analyst should and shouldn’t include in a high-level requirement (HLR). It begins by comparing a formal HLR ‘shall’ statement to...

No content

A problem occurred while loading content.

New ways of working can actually accelerate your team’s productivity

The past several months have changed the business world, for better and for worse, perhaps for years to come. Many advantages are born out of disruption, for example, the world experiencing cleaner skies for a change.  There are other positive changes taking place...

2020-06-29

User Interface and Report Business Needs

Part 6 of Dan Tasker’s Requirements in Context series discusses detailed business needs for a user interface (UI) or report, and capturing those needs as detailed requirements in a spreadsheet-based template for user interface.

2020-06-12

High-Level Requirement DOs and DON’Ts

Part 4 of Dan Tasker’s Requirements in Context series provides guidelines for what a business analyst should and shouldn’t include in a high-level requirement (HLR). It begins by comparing a formal HLR ‘shall’ statement to a user story. What is similar about them is that...

2020-06-12

Skills for Requirements Elicitation

Requirements elicitation is one of three main disciplines of Requirements Engineering, complemented by requirements modeling and requirements management. A key success factor for professional Requirements Engineering - and especially for requirements elicitation - are good soft skills. During...

2020-05-16

Scope-based High-Level Requirements

Part 3 of Dan Tasker’s Requirements in Context series continues to look at high-level requirements, narrowing the context to that of a project charted to deliver an IT-bases solution. It discusses how scope statements that identify functional capabilities are a good source of HLRs.

2020-04-13

5 INCOSE Guidelines That Every Requirement Engineer Should Know

The International Council on Systems Engineering (INCOSE) outlines a number of guidelines for writing better requirements, 44 to be exact. From avoiding universal quantifiers, superfluous infinitives, and open-ended clauses, to maintaining consistency throughout the document - the INCOSE...

2020-04-16

Learn About Requirements

What is Requirements Traceability?

What is Requirements Traceability?

Requirements traceability refers to the capability of a requirements management process or tool which enables the process participant or tool user to follow the life of a requirement both forwards and backwards.  It also refers the the...
What are Product Requirements?

What are Product Requirements?

To meet the new challenges - today’s companies will have to change their strategies and to increase the customer experience - in order to get a better chance of succeeding in the future. Finding and maintaining a balance between operations,...
Requirements Glossary from A to Z

Requirements Glossary from A to Z

A Glossary documents the terms which are specific to a given domain, project, or endeavor.  Whether your project is large or small, a glossary of terms will ensure your entire team and your team's stakeholders are on the same page and...

No content

A problem occurred while loading content.

Join the Conversation at Requirements.com

Requirements Staff commented on What is Requirements Traceability?

@Boris - I think you're right. This requirements traceability article definitely needs some refreshing. We'll need to find somebody willing to do so.

janeman commented on User Interface and Report Business Needs

This looks good

Boris commented on What is Requirements Traceability?

Because we (manufacturers of traceability tools) are criticized in the article, I would like to comment on this: The most recent source in the article is from 2009... it is perhaps a bit outdated. We have actually done something since then ... and continue to work.

Here is a customer statement as proof:

“The elimination of manual effort, especially the manual maintenance of Excel matrices, is a great relief; YAKINDU Traceability helps us to work 70% more efficiently and clearly structured in our projects ... The use of this professional software tool was very well received by the OEMs (and strengthened the relationship of trust)”

Take a look yourself: http://itemis.com/traceability

Stan commented on Agile Requirements Engineering: An Empirical Analysis and Evidence from a Tertiary Education Context

A nice and very important contribution. We totally agree that Requirements Engineering is indispensable in all – even in agile project settings! In our certification schemes we provide an insight how to elicit, document and manage requirements in agile projects. Our syllabus and handbook is available at no charge and for download from: https://www.ireb.org/de/cpre/re-agile/

Boris commented on What is Requirements Traceability?

Regarding the section about "Requirements Traceability Best Practices":

I'm missing one point: Be benfitial! With well managed traceabiltiy data, it is so easy to provide reports that help both managers and engineers in their daily work. Here's a rough illustration and an emperical prove for this point: https://www.itemis.com/en/yakindu/traceability/documentation/user-guide/benefits_of_requirements_traceability#benefits_of_requirements_traceability

Adrian M. commented on Context is Everything... When It Comes to Requirements

Great article series on requirements! Thank you Dan for your insights.

Requirements Staff commented on What is Requirements Prioritization?

Once an analyst has chosen the method(s) by which to select which requirements have highest priority, she should turn to her colleagues and other stakeholders for input to ensure that everyone is in agreement regarding the emphases of the project. She should also ensure that they understand and agree on the method(s) by which the requirements will be prioritized.

Requirements Staff commented on What is Requirements Prioritization?

When it comes to the process of assigning a requirement’s priority, any requirement may be prioritized at any point in its lifecycle, according to BABOK. But regardless of when it is done, before a requirement can be prioritized, an analyst must consider what is most important from a business standpoint. There are a number of possible business considerations , including value, cost, risk, difficulty of implementation, likelihood of success, stakeholder agreement and urgency, each of which is described in more detail below. Often, a combination of these methods is used when considering the business need; rarely is one alone used in a vacuum.