1. Donk, Lindenberg, Neerincx, Pemberton CHI20001 Specification Techniques

2. Donk, Lindenberg, Neerincx, Pemberton CHI20002 Overview  Introduction  What specifications can and can’t do  How and when to use specifications  Specifications in the design process  Different techniques, example  Conclusions

3. Donk, Lindenberg, Neerincx, Pemberton CHI20003 Introduction  specification means abstraction  different specification techniques stress different features  specifications can range from mock- up and natural language to formal methods

4. Donk, Lindenberg, Neerincx, Pemberton CHI20004 Benefits of specifications  identification of system properties  error and inconsistency detection  specifications can establish communication between designers and programmers  (formal) specifications can be used to create (interactive) prototypes

5. Donk, Lindenberg, Neerincx, Pemberton CHI20005 What specifications can’t do  guarantee a system is perfect  avoid miscommunication  7 myths and more

6. Donk, Lindenberg, Neerincx, Pemberton CHI20006 When to use specifications  complex systems (e.g. multi-agent systems, multimodal systems)  trustworthy systems (e.g. e-commerce)  not for complete systems

7. Donk, Lindenberg, Neerincx, Pemberton CHI20007 Role of specifications in design process  use formal specification linked to empirical methods for design and evaluation  specification techniques can be used throughout the entire design process  the design process used does not matter

8. Donk, Lindenberg, Neerincx, Pemberton CHI20008 Empirical Design Methods & Formal methods  Empirical methods (like usability engineering or the prototyping approach) have much attention for the user’s needs.  Specification techniques add attention for the system’s behaviour in critical situations (see benefits)

9. Donk, Lindenberg, Neerincx, Pemberton CHI20009 Usability Engineering empirical summative analysis design empirical formative analytical formative Assessment Specification implemen- tation flow of spec/assesstask/processflow of iteration

10. Donk, Lindenberg, Neerincx, Pemberton CHI200010 Prototyping approach (Pressman, 1997) requirements quick design prototype evaluation & refinement implementation

11. Donk, Lindenberg, Neerincx, Pemberton CHI200011 Which Specification Technique?  GOMS  GTA  Z  CSP ...

12. Donk, Lindenberg, Neerincx, Pemberton CHI200012 Different Techniques (I)  Goals, Operators, Methods and Selection (GOMS). Hierarchical description of the user’s goals and tasks  Groupware Task Analysis (GTA). Task modeling in environments where many people interact with a system

13. Donk, Lindenberg, Neerincx, Pemberton CHI200013 Different Techniques (II)  Z. Mathematical description of entities and their relations. Best fitted for the description of static properties of systems  CSP. Algebraic description of interacting, dynamic processes.

14. Donk, Lindenberg, Neerincx, Pemberton CHI200014 Example  game to play slide puzzles  specified by using natural language and CSP-alike

15. Donk, Lindenberg, Neerincx, Pemberton CHI200015 Which Specification Technique  the use of the specification in the design process determines the choice of technique  use combinations (e.g. Z or CSP combined with natural language)

16. Donk, Lindenberg, Neerincx, Pemberton CHI200016 Accessibility of Specification Techniques  the more formal/mathematical the specification technique the steeper the learning curve:  readability. Especially specification in for example Z can scare people of.  easy to write?

17. Donk, Lindenberg, Neerincx, Pemberton CHI200017 Conclusions  use formal methods complementary to empirical design methods  use formal methods for critical parts, i.e. parts that:  either must function properly,  or are likely to give trouble  the right technique at the right spot