Abstract
In this paper we argue that it is not self-evident how ‘requirements’ are defined, but that ‘requirements’ are enacted differently by differently situated actors, and that this has consequences in design practices. The purpose of the paper is to explore the consequences of prototyping practices in a local IT design project. The empirical material was gathered through the use of ethnographic methods, and analysed diffractively. Graphical user interface prototypes were tools for formulating business requirements in a business process analysis. Through a reading of a discussion which took place in a work meeting about the prototypes, we discuss how business requirements were enacted. This is discussed in relation to divergent and convergent approaches in IT design. One consequence was a risk that the prototyping process moved too fast to solutions, and another was the risk that the business process analysis method reproduced the dominant story of women's absence in IT design.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.