Article provides an overview of twelve rules for writing good requirements. Each rule has its own page (linked from this one).

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. 

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

By writing better requirements

rather a database than an article. useful, however!

The Business Analysts Handbook has been launched by myself and a handful of friends and colleagues. From it's homepage; "This is a wiki for busness analysts to post thir knowledge. It is designed to be an evolving repository of knowledge for and about business analysts, or BAs." This site can be viewed as a business analysts body of knowledge, although rather that a formal and rigidly version controlled document such as PMIs PMBOK (or the proposed BABOK) my hope is that the wiki format will enable a broader contribution from practitioners and be a (cliché warning) live document, that evolves as the knowledge base grows.

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

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.

Burndown is a technique used in Scrum projects for tracking the progress within or across sprints. It is an exciting way to track how a team is progressing against a deadline - and we can apply it to any form of project-status. In this article, we will apply it to documenting business processes.

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.