COMP 3008 Chapter Notes - Chapter 10: Requirements Engineering, Interaction Design, Contextual Inquiry
Document Summary
Comp 3(cid:1004)(cid:1004)8 chapter (cid:1005)(cid:1004: two aims of the requirements activity, 1. Understand as much as possible about the users, their activities, and the context of that activity, so the system can support them in achieving their goals: 2. In practice, requirements evolve and develop as the stakeholders interact with designs and see what is possible and how certain facilities can help them: re(cid:395)ui(cid:396)e(cid:373)e(cid:374)ts a(cid:396)e (cid:374)ot eas(cid:455) to ide(cid:374)tif(cid:455). Ca(cid:374)(cid:374)ot (cid:271)e gathe(cid:396)ed/(cid:272)aptu(cid:396)ed (do(cid:374)"t e(cid:454)ist out the(cid:396)e a(cid:374)d we simply just need to pick them up) and cannot be elicited (clients/users know all the requirements and we just need to get them to tell us). Although customer must some idea of the requirements, they may not be articulated or complete (just an initial set). The physical environment: ex. how much lighting, noise, movement, what the user will be wearing (gloves not good for touch screen, 2. Do collaborators need to communicate across great distances: 3.