Representing the Problem

Abstract

The previous chapter discussed dialogues for requirements, and processes for discovering them. This chapter focuses on how requirements are represented and recorded. Representation and requirements dialogues are, of course, closely linked. Representations become part of the conversation when we refer to and point at specifications and models during the process of analysis. Representations have been a somewhat neglected part of RE, although this problem has received increasing attention in several literatures (Muller, 1991). Requirements tend to be documented as lists of things that need to be implemented, such as functions or goals. However, requirements may be expressed in models as requirements specifications rather than just lists; alternatively, requirements may be embedded in a prototype design. Clearly lists, specifications, designs and prototypes all represent requirements in some manner; the question is, what are the merits of different types of requirements expression? This chapter addresses this question and looks at how different representations fit within the RE process.