Checklist for generating requirements

From WikID

This article is part of the Bachelor design guide; the original version can be found at page 98.

Contents 1 What is a checklist for generating requirements? 1.1 The stakeholders 1.2 Aspects involved product design 1.3 Product process tree 2 When can you use a checklist for generating requirements? 3 How to use a checklist for generating requirements? 3.1 Starting points 3.2 Expected outcome 3.3 Possible procedure 4 Tips and concerns 5 Literature 6 References

What is a checklist for generating requirements?

Checklists for generating requirements are lists with questions that you can ask yourself when creating a design specification (also known as a list of requirements). Checklists ensure a systematic approach to the creation of the programme of requirements. The most important thing is not to forget a particular requirement, meaning that we have to arrive at a complete collection of requirements. A programme of requirements can be created by taking into account three points of view:

1. The stakeholders
2. The aspects involved
3. The product lifecycle.

These different points of view can be taken into account when generating requirements, and some provide explicit, clear-cut checklist (for example, Pugh^[1]). Other points of view, for example the process tree, is not by definition a checklist, however, it helps the generation of requirements in the same way.

The stakeholders

The aims and preferences of people set the requirements for a new product. Who are the people affected by the new product, what interests do they have, what do they decide on, and what information can they provide? Important stakeholders are the company, its (future) customers, suppliers, transport companies, wholesale and retail trade, consumer organizations, and legislator. An example of a checklist to distinguish relevant stakeholders can be found in Design Methods: Seeds of Human Futures^[2].

Aspects involved product design

There are checklists of aspects which usually play a role in the assessment of a product. By aspects we mean such general issues such as perfomance, environment, maintenance, aesthetics and appearance, materials, and packaging amongst others. Such check­lists have been drafted by Hubka and Eder^[3], Pahl and Beitz^[4], and Pugh^[1].

Product process tree

The process tree of a product provides for a third viewpoint to arrive at a complete specification. Between origination and disposal a product goes through several processes, such as manufacturing, assembly, distribution, installation, operation, maintenance, use, re-use and disposal. Each of these processes brings certain requirements and wishes for the new product. One becomes aware of these requirements by making a process tree.

When can you use a checklist for generating requirements?

Checklist are useful when devising a first list of requirements, at the end of the analysis stage of the design process.

How to use a checklist for generating requirements?

Starting points

The starting points of using checklists is the information found in the analysis the design problem, the context of the design problem etc.

Expected outcome

The outcome of using checlist for generating requirements is a first list with requirements, which contains redundant require­ments.

Possible procedure

1. Search for the appropriate checklist
2. Use the checklist to generate as many requirements as possible.
3. Work systematically through the checklist. Do not skip any of the points on the checklist.
4. Follow the procedure listed in design specification.

Tips and concerns

• Use more than one checklist; checklist complement each other.
• More practical guidelines for developing design requirements can be found in the book Engineering design methods^[5]

Literature

• N. Roozenburg and E. Eekels (1995) Product Design: Fundamentals and Methods, Lemma, Utrecht.
• J.C. Jones (1982) Design Methods: Seeds of Human Futures, Wiley, Chichester.
• V. Hubka en W.E. Eder (1988) Theory of Technical Systems: A Total Concept Theory for Engineering Design, Springer, Berlijn.
• G. Pahl en W. Beitz (1984) Engineering Design: A Systematic Approach, Design Council, London.
• S. Pugh (1990) Total Design: Integrated Methods for Succesful Product Engineering, Addison Wesley, Wokingham.

References

1. ↑ ^{1.0 1.1} S. Pugh (1990) Total Design: Integrated Methods for Succesful Product Engineering, Addison Wesley, Wokingham.
2. ↑ J.C. Jones (1982) Design Methods: Seeds of Human Futures, Wiley, Chichester.
3. ↑ V. Hubka en W.E. Eder (1988) Theory of Technical Systems: A Total Concept Theory for Engineering Design, Springer, Berlijn.
4. ↑ G. Pahl en W. Beitz (1984) Engineering Design: A Systematic Approach, Design Council, London.
5. ↑ N. Cross (1989) Engineering Design Methods, Wiley, Chichester.