What Counts as Software Process? Negotiating the Boundary of Software Work Through Artifacts and Conversation
- 17 October 2009
- journal article
- Published by Springer Science and Business Media LLC in Computer Supported Cooperative Work (CSCW)
- Vol. 18 (5-6), 401-443
- https://doi.org/10.1007/s10606-009-9100-4
Abstract
No abstract availableKeywords
This publication has 14 references indexed in Scilit:
- Boundary Negotiating Artifacts: Unbinding the Routine of Boundary Objects and Embracing Chaos in Collaborative WorkComputer Supported Cooperative Work (CSCW), 2007
- Organizational routines as a unit of analysisIndustrial and Corporate Change, 2005
- Software process development and enactment: concepts and definitionsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Software processPublished by Association for Computing Machinery (ACM) ,2000
- A reappraisal of structured analysisACM Transactions on Information Systems, 1993
- A rational design process: How and why to fake itIEEE Transactions on Software Engineering, 1986
- The Powers of AssociationSociological Review, 1984
- Software Engineering EconomicsIEEE Transactions on Software Engineering, 1984
- Agency, StructurePublished by Bloomsbury Academic ,1979
- Outline of a Theory of PracticePublished by Cambridge University Press (CUP) ,1977