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

By writing better requirements

Article by Suzanne Robertson about how to approach writing requirements when you are under constraints that prevent you from completing them.  Good article, very stimulating discussion in the comments.

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. 

…Is another man’s treasure. There are many different ways to document requirements when developing software. And there is a proliferation of requirements documents - MRD, PRD, SRS, FRS and design documents. Everyone has a perspective on what each document represents, and each person on the team has a unique perspective on what questions the document answers.

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.

The article is written in the context of implementing knowledge management strategies and it talks about a quality approach to project execution and requirements management.

This includes the importance of reconciling the details with the strategic direction when documentaing and managing corporate knowledge.

This is a useful article for anyone getting involved in the development of Knowledge Management systems or Business Process systems and Repositories.

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>