Requirements Engineering


Despite the pressures of ‘Internet time’ our clients understand that time spent understanding the business problem is a good investment.  They cannot afford to have poorly built, inappropriate or incomplete products or systems.  Commerce, industry, local and central government are increasingly interested in requirements engineering, an understanding of what they intend to build before they start building it.

Requirements engineering is primarily a communication activity, not a technical one.  We specialise in using both our experience in  communication and our technical skills to derive clear, comprehensive and unambiguous requirements, which we define as:

‘a specification of what should be implemented; descriptions of how the system should behave, or of a system property or attribute. They may be a constraint on the development process of a system.’

We tailor our standard practices to suit your project type, constraints and organizational culture.

Some ground-breaking projects work well with informal or ‘agile’ requirements engineering which involves a lot of rework.  Many projects work best with a more deliberate and structured approach.

We address three levels of requirements, which come from different sources at different project stages:

  1. Business requirements describe why the product or system is being built and identify the benefits.
  2. User requirements, which we usually capture in the form of use cases, describe the tasks or business processes a user will be able to perform with the product or system.
  3. Functional requirements describe the specific system behaviours that must be implemented. The functional requirements are the traditional “shall” statements found in a software requirements specification.

In a typical requirements engineering project we:

1.  Elicit

  • Define the business requirements
  • Get extensive user involvement and engagement
  • Focus on key user tasks
  • Define quality attributes

2.  Analyse

Prioritise requirements

3.  Specify

  • Produce printed or on-line specification
  • Store requirements in a Requirements Management tool.  We are experienced in using …




    RTM Workshop

    Vital Link

4.  Verify

Inspect Requirements Specifications

5.  Manage Requirements

Capture and control requirement changes

6.  Transition

Start to turn requirements into products and systems


SRS 2011

In 2011 I turned my notes on requirement gathering into a brief guide – SRS 2011 – for distribution to our clients.  An updated version – SRS 2013 – is in production.  We invite you to email and request a copy.


If you need clear, complete and unambiguous requirements, particularly in a changing and challenging environment we can help you with that.

Now that you know about our requirements engineering services give us a call on 07972 713333 or fill in the convenient contact form.