Requirements Determination


The goal of this course is to discover, analyse and document the functional and non-functional requirements that a software system should satisfy. The focus is on determining those features that a system should offer to its actors and stakeholders. The core process is to create an unambiguous requirements document that contains all the technical details that are needed by analysts and designers.

The course consists of three main stages; the first stage entails scoping the problem and finding an initial set of requirements and features. The second stage involves analyzing these requirements for inconsistencies, conflicts and missing requirements. The main objective is to resolve these problems before starting with stage 3, which is concerned with describing and documenting requirements that other stakeholders (such as analysts, designers and users) can understand and use. The percentage theory/practice is 70/30.

This course is based on a number of years of practical experience with requirements determination in real projects combined with use of modern and improved requirements capture techniques. In particular, we incorporate use case technology into the course as a special case. For complex systems we must ensures that they do not become unmaintainable, which is what we have experienced in projects.

What do you learn?

  • Scoping large complex systems
  • A structured and defined approach to requirements discovery
  • Interviewing techniques and improved stakeholder communication
  • How to incorporate other approaches into the model, for example use cases

What previous Delegates have said about the Course

  • "Good, step-by step approach"
  • "Modern and highly useful methods"
  • "Exceeded my expectations"


Click here for course contents




We assume that the student is a senior analyst or designer and has extensive knowledge of at least one systems methodology (for example, OMT, Yourdon, Jackson, UML). Furthermore, the student must have experience with real-life application development.

Who should attend?

Analysts, novice requirements analysts, product managers and other professionals who are involved in 'upstream' system development activities. This course is not suitable for junior designers or developers.

Course form

The percentage theory/exercises is 70:30. The student learns a number of interviewing techniques in order to learn how to elicit requirements during the role playing sessions.


Requirements Determination

Fill in your personal details