Collecting and Analyzing Requirements

Every ITSM framework and standard references the need to meet "customer requirements". Unfortunately, there is less attention paid to the process of collecting and managing those requirements.

I am happy to report that the ITIL Service Design book contains some good high level guidance on "Requirements Engineering" (Section 5.1). Requirements Engineering is defined as

"the approach by which sufficient rigor is introduced into
the process of understanding and documenting business
and user requirements and ensuring traceability of changes
to each requirement."

The section goes on to to describe a Requirements Catalog for documenting and managing changes to requirements. It also describes techniques and tools for gathering, analyzing and validating requirements with customers.

ITIL defines three levels of requirements: Functional, Management and Operational and Usability.

The Service Design book is particularly good for those who do not have a background in the Software Development Life Cycle (SDLC). I would highly recommend it to everyone involved in process design, implementation and operational management.


Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

How Does ITIL Help in the Management of the SDLC?

The Difference between Change and Release Management

Search This Blog