Requirements Management: the Swiss army knife approach

Submitted by: Bastiaan Deblieck on 17 July 2009

Comments: 0

OK let’s have a look at some other parts of the Swiss army knife. After the successful post about idea management it’s time to explain how to do requirements management … with the same application.


Requirements hell index


We got a test for you. Do any of the following statements apply to your analysis, development and/or test processes?
 

  • Do you copy your table of contents from your MS Word document to a spreadsheet to track the activities on the different parts of your requirements specification: stakeholders, priorities, cost, benefit, contact persons, remarks?
  • Do you need a formal way to know which functional requirements are not yet covered by system requirements?
  • Do you need to find system requirements that have no formal relation to user requirements?
  • Do you also have a hard time understanding the impact of a user requirement on one or more system requirements or vice versa?
  • The more statements above apply to you, the higher your ‘requirements hell index’. Here is a solution.


040 Requirements Management 1
 

The goal of a requirements management tool is to support the requirements management process.
 

  • Document
  • Analyze
  • Prioritize and agree
  • Controlling change or in other words: traceability
  • Communicate to relevant stakeholders


TenForce supports all your requirements management activities in a pragmatic but flexible way. TenForce does not impose a method or is not related to any vendor of development/configuration management solutions. It comes pre-configured with everything you need to manage the complex multi-dimensional jigsaw that requirements make up.

In addition TenForce allows you to manage centrally and dynamically actions issues, questions, actions, decisions, risks, meeting minutes … All this related to your requirements management process and accessible through one and the same application!
A hierarchical list of requirements with relevant attributes.

040 Requirements Management 2

Managing an “individual” requirement.

040 Requirements Management 3
 

  •  Overview: Your customized form to manage requirements information.
  •  Solution: Description of the expected solution.
  •  Links: Link to the system requirements that implement the user requirement.
  •  Child items: The sub-requirements of this main requirement.
  •  Comments: Allow free forum-like comments.
  •  Attachments: Attach documents, links, pictures, …
  •  History: Browse through all changes.

 
See how system requirements implement user requirements

040 Requirements Management 4
 
Moreover, we offer
 

  •  Excel-based reporting.
  •  Bi-directional link between user requirements & system requirements.

 
And on top of that you can link test cases to every requirement. Thus building an end to end requirement management and verification solution.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
  • Links to video content with 'rel="lightvideo"' in the <a> tag will appear in a Lightbox when clicked on.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
1 + 16 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.