High level overview of the processes that make up the bulk of requirements management work.

By writing better requirements

From the article (by Scott Ambler):

UML 2 activity diagrams are typically used for business process modeling, for modeling the logic captured by a single  use case or usage scenario, or for modeling the detailed logic of a  business rule.  Although UML activity diagrams could potentially model the internal logic of a complex operation it would be far better to simply rewrite the operation so that it is simple enough that you don’t require an activity diagram. In many ways UML activity diagrams are the object-oriented equivalent of  flow charts and  data flow diagrams (DFDs) from structured development. 

Discussion of agile vs traditional requirements management

This article is an informed and wide ranging history of the profession/role of the business analyst.  Written by a developer for developers to help understand the role and how to work with them.

An introductory article about making sure you vesion control and maintain traceability over your requirements.

Requirements traceability is an important asect of good requirements management.  If you are new to requirements management or business analysis this is a good introduction to some good practices.

This link is to a series of blog posts on the V-model.  The V-model is a testing and validation framework for software development projects.

This article is useful for business analysts new to the software development world and highlights key quality gates in the development and implementation of software.  The articles focus on what a Business Analyst or Project Manager should know about the process.

The individual posts listed are

<font>Introduction</font>

<font>The value of testing</font>

<font>The V-Model and the development process</font>

<font>Verifying on the way into the development cycle</font>

<font>Testing and verifying on the way out of the development cycle</font>

<font>Extending the V-Model</font>

 

Identifies the assumptions most commonly made by business analysts.  Also provides high-level steps for how to avoid those assumptions

Good explanation of how to create a decision tree as a visual artifact when gathering requirements

Article starts with good justification for why requirements should be managed.  Then presents the different types of requirements, and checklists of 'stuff to do' for functional and non-functional requirements.