Small-Scale Classification Schemes: A Field Study of Requirements Engineering

dc.contributor.authorHertzum, Morten
dc.date.accessioned2020-06-06T09:06:56Z
dc.date.available2020-06-06T09:06:56Z
dc.date.issued2004
dc.date.issued2004
dc.description.abstractSmall-scale classification schemes are used extensively in the coordination of cooperative work. This study investigates the creation and use of a classification scheme for handling the system requirements during the redevelopment of a nation-wide information system. This requirements classification inherited a lot of its structure from the existing system and rendered requirements that transcended the framework laid out by the existing system almost invisible. As a result, the requirements classification became a defining element of the requirements-engineering process, though its main effects remained largely implicit. The requirements classification contributed to constraining the requirements-engineering process by supporting the software engineers in maintaining some level of control over the process. This way, the requirements classification provided the software engineers with an important means of discretely balancing the contractual aspect of requirements engineering against facilitating the users in an open-ended search for their system requirements. The requirements classification is analysed in terms of the complementary concepts of boundary objects and coordination mechanisms. While coordination mechanisms focus on how classification schemes enable cooperation among people pursuing a common goal, boundary objects embrace the implicit consequences of classification schemes in situations involving conflicting goals. Moreover, the requirements specification focused on functional requirements and provided little information about why these requirements were considered relevant. This stands in contrast to the discussions at the project meetings where the software engineers made frequent use of both abstract goal descriptions and concrete examples to make sense of the requirements. This difference between the written requirements specification and the oral discussions at the meetings may help explain software engineers' general preference for people, rather than documents, as their information sources.de
dc.identifier.doi10.1023/B:COSU.0000014877.66402.43
dc.identifier.pissn1573-7551
dc.identifier.urihttp://dx.doi.org/10.1023/B:COSU.0000014877.66402.43
dc.identifier.urihttps://dl.eusset.eu/handle/20.500.12015/3648
dc.publisherSpringer
dc.relation.ispartofComputer Supported Cooperative Work (CSCW): Vol. 13, No. 1
dc.relation.ispartofseriesComputer Supported Cooperative Work (CSCW)
dc.subjectclassification schemes
dc.subjectconceptual design
dc.subjectcooperative work
dc.subjectcoordination
dc.subjectrequirements engineering
dc.subjectrequirements specification
dc.subjectsmall-scale classification
dc.titleSmall-Scale Classification Schemes: A Field Study of Requirements Engineeringde
dc.typeText/Journal Article
gi.citation.endPage61
gi.citation.startPage35
gi.citations.count11
gi.citations.elementFederico Cabitza, Carla Simone (2013): Computational Coordination Mechanisms: A tale of a struggle for flexibility, In: Computer Supported Cooperative Work (CSCW) 4-6(22), doi:10.1007/s10606-013-9187-5
gi.citations.elementMorten Hertzum (2008): On the Process of Software Design: Sources of Complexity and Reasons for Muddling through, In: Lecture Notes in Computer Science, doi:10.1007/978-3-540-92698-6_29
gi.citations.elementTangni C. Dahl-Jørgensen, Elena Parmiggiani (2023): Caseworkers’ participation in procurement: Infrastructuring Child Welfare Services in Norway, In: Computer Supported Cooperative Work (CSCW) 4(32), doi:10.1007/s10606-023-09469-4
gi.citations.elementSusan Gasson (2005): The Dynamics of Sensemaking, Knowledge, and Expertise in Collaborative, Boundary-Spanning Design, In: Journal of Computer-Mediated Communication 4(10), doi:10.1111/j.1083-6101.2005.tb00277.x
gi.citations.elementNasir Mehmood Minhas, Shahla Majeed, Ziaul Qayyum, Muhammad Aasem (2011): Controlled vocabulary based software requirements classification, In: 2011 Malaysian Conference in Software Engineering, doi:10.1109/mysec.2011.6140639
gi.citations.elementRebekka Wohlrab, Eric Knauss, Patrizio Pelliccione (2020): Why and how to balance alignment and diversity of requirements engineering practices in automotive, In: Journal of Systems and Software, doi:10.1016/j.jss.2019.110516
gi.citations.elementRashidah Kasauli, Rebekka Wohlrab, Eric Knauss, Jan-Philipp Steghöfer, Jennifer Horkoff, Salome Maro (2020): Charting Coordination Needs in Large-Scale Agile Organisations with Boundary Objects and Methodological Islands, In: Proceedings of the International Conference on Software and System Processes, doi:10.1145/3379177.3388897
gi.citations.elementSabine Mas (2015): Caractéristiques de schémas de classification personnels des documents administratifs électroniques : éléments d’analyse et de discussion, In: Documentation et bibliothèques 1(55), doi:10.7202/1029047ar
gi.citations.elementMaria Teresa Borges Tiago, João Pedro Almeida Couto, Flávio Gomes Tiago, António Cabral Vieira (2007): Knowledge management, In: Management Research News 2(30), doi:10.1108/01409170710722946
gi.citations.element(2009): Proposition of a Faceted Classification Model to Support Corporate Information Organization and Digital Records Management, In: 2009 42nd Hawaii International Conference on System Sciences, doi:10.1109/hicss.2009.359
gi.citations.elementMiroslaw Staron, Ludwik Kuzniarz (2005): Properties of Stereotypes from the Perspective of Their Role in Designs, In: Lecture Notes in Computer Science, doi:10.1007/11557432_15

Files