I'm still thinking about the BABOK. It seems like requirements are the "nouns"--they are a description of an end state. For example, there might be these requirements in an incident management implementation:

• count the number of issues tracked
• send all user requests to the Service Desk
• categorize incidents by service catalog service

Each of these requirements describes the end state. Project management is then a function that transforms the current state to a desired state, for example:

Today I've been reading through the BABOK to learn more about documenting requirements. (One of the BABOK disciplines is called "Requirements Elicitation" and another one is called "Requirements Analysis & Documentation," so it seems like a good place to start :) We need to document requirements for an upcoming ITSM tool upgrade.

IT Service Management depends heavily on the effective operation of project management and business analysis. Hopefully on the site we will be talking about project management and business analysis--at least enough so that Universities can get pointers on how to become more effective at project management and requirements gathering.

"Slideshare" is a web site that lets people share slide presentations with one another. Recently the "Better Projects" blog linked to two Slideshare presentations, about Scrum and about the BABOK (Business Analyst Body of Knowledge) v2.