Distributed cognition in the management of design requirements

15th Americas Conference on Information Systems 2009, AMCIS 2009

Volumn 3, Issue , 2009, Pages 1836-1845

  Hansen, Sean ^a   Lyytinen, Kalle ^a  

^a CASE WESTERN RESERVE UNIVERSITY   (United States)

Author keywords

Case study methodology; Distributed cognition; Requirements processes

Indexed keywords

DESIGN PROFESSIONALS; DESIGN REQUIREMENTS; DISTRIBUTED COGNITION; INFORMATION SYSTEMS DEVELOPMENT; MULTIPLE-CASE STUDY; REQUIREMENTS PROCESS; RESEARCH EFFORTS; SYSTEMS DEVELOPMENT;

INFORMATION SYSTEMS;

DESIGN;

EID: 84870854396     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (47)

1. Antón, A. & Potts, C. 1998. The use of goals to surface requirements for evolving systems. Proceedings of the 20th international conference on Software engineering: 157-166.
2. Aronson, J. 1994. A Pragmatic View of Thematic Analysis. The Qualitative Report, 2(1).
3. Aurum, A. and Wohlin, C. (2005). Requirements Engineering: Setting the Context, in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin (Eds.), Springer-Verlag, Berlin, Germany.
4. Berry, D. M., and Lawrence, B. (1998). Requirements Engineering, IEEE Software, 15, 2, 26-29.
5. Borgida, A., Greenspan, S., & Mylopoulos, J. (1985). Knowledge Representation as the Basis for Requirements Specifications. IEEE Computer, 18: 82-91
6. Boyatzis, R.E. 1998. Transforming Qualitative Information: Thematic Analysis and Code Development. Thousand Oaks, CA: Sage Publications, Inc.
7. Clark, A. 1997. Being There. Cambridge, MA: The MIT Press.
8. Crowston, K., and Kammerer, E.E. (1998). Coordination and Collective Mind in Software Requirements Development, IBM Systems Journal, 37, 2, 227-246.
9. Curtis, B., Krasner, H., & Iscoe, N. 1988. A field study of the software design process for large systems. Communications of the ACM, 31(11): 1268-1287.
10. Cybulski, J. 1998. Patterns in software requirements reuse. Paper presented at the Third Australian Conference on Requirements Engineering (ACRE'98), Geelong, Australia.
11. Damian, D.E., Eberlein, A., Shaw, M.L. G, and Gaines, B.R. (2003). An exploratory study of facilitation in distributed requirements engineering, Requirements Engineering, 8, 1, 23-41.
12. Eisenhardt, K.M. (1989). Building Theories from Case Study Research, Academy of Management Review, 14,4, 532-550.
13. Gotel, O., and Finkelstein, A. (1997). Extended requirements traceability: results of an industrial case study, Third IEEE International Symposium on Requirements Engineering IEEE Press, Annapolis, MD, USA, 169-178.
14. Grünbacher, P., and Braunsberger, P. (2003). Tool Support for Distributed Requirements Negotiation, Cooperative methods and tools for distributed software processes 56-66.
15. Guinan, P. J., Cooprider, J. G., & Faraj, S. 1998. Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach. Information Systems Research, 9(2): 101-125.
16. Halverson, C. A. 1995. Inside the Cognitive Workplace: New Technology and Air Traffic Control, Unpublished Dissertation, University of California-Sand Diego. Sand Diego, CA.
17. Hansen, S., Berente, N., and Lyytinen, K. (2009). Requirements in the 21st Century: Current Practice & Emerging Trends, in P. Loucopoulos, K. Lyytinen, J. Mylopoulos, and W. Robinson (Eds.), Design Requirements Engineering: A Ten-Year Perspective 14, Springer-Verlag, Heidelberg, Germany, 44-87.
18. Hickey, A.M., and Davis, A.M. (2004). A Unified Model of Requirements Elicitation, Journal of Management Information Systems, 20, 4, 65-84.
19. Hollan, J., Hutchins, E., & Kirsh, D. 2000. Distributed Cognition: Toward a New Foundation for Human-Computer Interaction Research. ACM Transactions on Computer-Human Interaction, 7(2): 174-196.
20. Hsia, P., Davis, A.M., & Kung, D.C. 1993. Status Report: Requirements Engineering. IEEE Software, 10, 75-79.
21. Hutchins, E. 1990. The technology of team navigation. In J. Galegher & R. Kraut & C. Egido (Eds.), Intellectual teamwork: social and technical bases of collaborative work. Hillsdale, NJ: Lawrence Erlbaum Assoc.
22. Hutchins, E. (1995a). Cognition in the Wild MIT Press, Cambridge, MA, USA.
23. Hutchins, E. 1995b. How a Cockpit Remembers Its Speed. Cognitive Science, 19: 265-288.
24. Hutchins, E., and Klausen, T. (2000). Distributed Cognition in an Airline Cockpit. In Cognition and Communication at Work, Y. Middleton (Ed.), Cambridge University Press, New York, NY, 15-34.
25. Hutchins, E. 2000. Distributed Cognition, International Encyclopedia of the Social & Behavioral Sciences: Elsevier, Ltd.
26. Jarke, M., and Pohl, K. (1994). Requirements engineering in 2001:(virtually) managing a changing reality, Software Engineering Journal, 9, 6, 257-266.
27. Kruchten, P. 2003. The Rational Unified Process: An Introduction (Third Edition ed.). Boston, MA: Pearson Education.
28. Lam, W., McDermid, T., & Vickers, A. 1997. Ten steps towards systematic requirements reuse. Paper presented at the Third IEEE International Symposium on Requirements Engineering, Annapolis, MD, USA.
29. Leffingwell, D., and Widrig, D. (1999). Managing Software Requirements: A Unified Approach Addison-Wesley Professional.
30. Levina, N. & Vaast, E. 2005. The Emergence of Boundary Spanning Competence in Practice: Implications for Implementation and Use of Information Systems. MIS Quarterly, 29(2): 335-363.
31. Lindquist, C. (2005). Fixing the Requirements Mess. CIO Magazine 52-60.
32. Lloyd, W.J., Rosson, M.B., and Arthur, J.D. (2002). Effectiveness of elicitation techniques in distributed requirements engineering, IEEE Joint International Conference on Requirements Engineering 311-318.
33. Norman, D. 1994. Things That Make Us Smart: Defending Human Attributes in the Age of the Machine. Cambridge, MA: Perseus Books.
34. Nuseibeh, B. & Easterbrook, S. 2000. Requirements engineering: a roadmap. Proceedings of the Conference on the future of Software Engineering: 35-46.
35. Ramesh, B., and Jarke, M. (2001). Toward reference models for requirements traceability, IEEE Transactions on Software Engineering, 27, 1, 58-93.
36. Rogers, Y. 1993. Coordinating Computer-Mediated Work. Computer Supported Cooperative Work, 1(4): 295-315.
37. Salomon, G. 1993. Distributed Cognitions: Psychological and Educational Considerations: Cambridge University Press.
38. Siddiqi, J., and Shekaran, M.C. (1996). Requirements Engineering: The Emerging Wisdom, IEEE Software, 13, 2, 15-19.
39. Sommerville, I. & Sawyer, P. 1997. Requirements Engineering: A Good Practice Guide: John Wiley & Sons, Inc. New York, NY, USA.
40. The Standish Group. (1995). The CHAOS Report West Yarmouth, MA.
41. Van Gelder, T. 1995. What Might Cognition Be, If Not Computation? The Journal of Philosophy, 92(7): 345-381.
42. van Lamsweerde, A. (2000). Requirements Engineering in the Year 00: A Research Perspective, Proceedings of the 22nd international conference on Software Engineering 5-19.
43. Vessey, I. & Sravanapudi, A. P. 1995. CASE tools as collaborative support technologies. Communications of the ACM, 38(1): 83-95.
44. Walz, D. B., Elam, J. J., & Curtis, B. 1993. Inside a Software Design Team: Knowledge Acquisition, Sharing, and Integration. Communications of the ACM, 36(10): 63-77.
45. Yin, R.K. (2003). Case Study Research: Design and Methods Thousand Oaks, CA: Sage Publications Inc
46. Zachman, J. 1997. Enterprise Architecture: The Issue of the Century. Database Programming and Design, 10(3): 44-53.
47. Zave, P. (1997). Classification of research efforts in requirements engineering, ACM Computing Surveys, 29, 4, 315-321.