Abstract
Formalised systems development methods are used in systems development as a means to express and communicate knowledge about the systems/software development process (Ågerfalk and Fitzgerald 2006). Since methods are social constructs, they embed various assumptions about people and systems development as a social practice (Introna and Whitley 1997; Russo and Stolterman 2000). Essentially, methods encapsulate knowledge of good design practice so that developers can be more effective, efficient and confident in their work. Nonetheless, it is a well-known fact that many software organisations do not use methods (Iivari and Maansaari 1998; Nandhakumar and Avison 1999) and, when methods are used, they are not used straight out of the box but are tailored to suit the particular development situation (Fitzgerald et al. 2003). This tension between the method ‘as documented’ and the method ‘in use’ has been described as a ‘method usage tension’ between ‘method-in-concept’ and ‘method-in-action’ (Lings and Lundell 2004).
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
Ethnomethodologists refer to this property of human behaviour as ‘accountability’ (Garfinkel 1967; Dourish 2001; Eriksén 2002); people require an account of the truth or usefulness of something in order to accept it as valid. According to ethnomethodologist Harold Garfinkel (1967), actions that are accountable are ‘visibly-rational-and-reportable-for-all-practical-purposes’.
- 2.
According to sociologist Max Weber, social action is that human behaviour to which the actor attaches meaning and which takes into account the behaviour of others, and thereby is oriented in its course (Weber 1978).
- 3.
Max Weber introduced the notion of an ‘ideal type’ as an analytic abstraction. Ideal types do not exist as such in real life, but are created so as to facilitate discussion. We use the term here to emphasise that a formalised method, expressed in a method description, never exists as such as a method-in-action. Rather, the method-in-action is an appropriation of an ideal typical formalised method to a particular context. At the same time, a formalised method is usually an ideal type created as an abstraction of existing ‘good practice’ (Ågerfalk and Åhlgren 1999).
- 4.
Versatile Information and Business Analysis.
- 5.
Material actions are actions that produce material results, such as painting a wall, while communicative actions result in social obligations, such as a promise to paint a wall in the future. The latter thus corresponds to what Searle (1969) termed ‘speech act’.
- 6.
Issue Based Information Systems.
- 7.
REpresentation and MAintenance of Process knowledge.
- 8.
We acknowledge contributions of Dr. Fredrik Karlsson to this section.
References
Ågerfalk PJ (2004) Grounding through operationalization: constructing tangible theory in IS research. Paper presented at the 12th European conference on information systems (ECIS 2004), Turku, Finland
Ågerfalk PJ (2006) Towards better understanding of agile values in global software development. In: Krogstie J, Halpin TA, Proper HA (eds) Proceedings of the workshop on exploring modeling methods for systems analysis and design (EMMSAD ’06), held in conjunction with the 18th conference on advanced information systems (CAiSE ’06), Luxembourg, Luxembourg. Namur University Press, Namur, pp 375–382
Ågerfalk PJ, Åhlgren K (1999) Modelling the rationale of methods. In: Khosrowpour M (ed) Managing information technology resources in organizations in the next millennium. Proceedings of the 10th information resources management association international conference. IDEA Group, Hershey, PA, pp 184–190
Ågerfalk P, Fitzgerald B (2006) Exploring the concept of method rationale: a conceptual tool for method tailoring. In: Siau K (ed) Advanced topics in database research, vol 5. IGI, Hershey, PA
Ågerfalk PJ, Goldkuhl G (2001) Business action and information modelling: the task of the new millennium. In: Rossi M, Siau K (eds) Information modeling in the new millennium. Idea Group, Hershey, PA, pp 110–136
Ågerfalk PJ, Wistrand K (2003) Systems development method rationale: a conceptual framework for analysis. Paper presented at the 5th international conference on enterprise information systems (ICEIS 2003), 23–26 April 2003, Angers, France
Ågerfalk PJ, Goldkuhl G, Fitzgerald B, Bannon L (2006) Reflecting on action in language, organisations and information systems. Eur J Inform Syst 15(1):4–8
Argyris C, Schön D (1978) Organisational learning: a theory of action perspective. Jossey-Bass, San Francisco, CA
Beck K (2000) Extreme programming explained. Embrace change. Addison-Wesley, Boston, MA, p 190
Boar BH (1984) Application prototyping: a requirements definition strategy for the 80s. Wiley, New York, NY
Carroll JM (1994) Making use a design representation. Comm ACM 37(12):29–35
Cato J (2001) User-centred web design. Addison Wesley, Harlow
Chakraborty S, Sarker S, Sarker S (2010) An exploration into the process of requirements elicitation: a grounded approach. J Assoc Inform Syst 11(4):212–249
Checkland PB (1981) Systems thinking, systems practice. Wiley, New York, NY
Conklin J, Begeman ML (1988) gIBIS: a hypertext tool for exploratory policy discussion. ACM Trans Office Inform Syst 6(4):303–331
Conklin EJ, Yakemovic KB (1991) A process-oriented approach to design rationale. Hum Comput Interact 6:357–394
Conklin J, Selvin A, Shum SB, Sierhuis M (2003) Facilitated hypertext for collective sensemaking: 15 years on from gIBIS. In: Weigand H, Goldkuhl G, de Moor A (eds) Proceedings of the 8th international working conference on the language-action perspective on communication modelling (LAP 2003). Tilburg University, Tilburg, pp 1–22
Constantine LL (1996) Usage-centered design for embedded systems: essential models. In: Proceedings of the embedded systems conference ’96. Miller Freeman, San Francisco, CA
Constantine LL, Lockwood LAD (1999) Software for use. A practical guide to the models and methods of usage-centered design. ACM Press, New York, p 579
Coughlan J, Lycett M, Macredie RD (2003) Communication issues in requirements elicitation: a content analysis of stakeholders experiences. Inform Software Tech 45(8):525–537
Dourish P (2001) Where the action is: the foundations of embodied interaction. MIT Press, Cambridge
Eriksén S (2002) Designing for accountability. In: Proceedings of the second Nordic conference on human-computer interaction (NordiCHI 2002). ACM Press, New York, NY, pp 177–186
Fitzgerald B, Russo NL, Stolterman E (2002) Information systems development: methods in action. McGraw-Hill, Berkshire
Fitzgerald B, Russo NL, O’Kane T (2003) Software development method tailoring at Motorola. Comm ACM 46(4):65–70
Garfinkel H (1967) Studies in ethnomethodology. Polity Press, Cambridge
Glinz M, Fricker S (2013) On shared understanding in software engineering. In Proceedings of GI conference on software engineering, Aachen, Germany, 2013. GI lecture notes in informatics, vol 213, pp 19–35
Goldkuhl G (1999) The grounding of usable knowledge: an inquiry in the epistemology of action knowledge. Linköping University, Linköping. CMTO Research Papers 1999:03
Goldkuhl G, Lind M, Seigerroth U (1998) Method integration: the need for a learning perspective. IEE Proc Software 145(4):113–118
Gould JD, Lewis C (1985) Designing for usability: key principles and what designers think. Comm ACM 28(3):300–311
Hall RR (2001) Prototyping for usability of new technology. Int J Hum Comput Stud 55(4):485–501
Higgins JM (1995) Storyboard your way to success. Train Dev 49(6):13–18
Holmström J, Sawyer S (2011) Requirements engineering blinders: exploring information systems developers’ black-boxing of the emergent character of requirements. Eur J Inform Syst 20:34–47
Hughes J, Reviron E (1996) Selection and evaluation of information system development methodologies: the gap between the theory and practice. In: Jayaratna N, Fitzgerald B (eds) Lessons learned from the use of methodologies (proceedings of the 4th conference on information system methodologies). British Computer Society, London, pp 309–319
Iivari J, Maansaari J (1998) The usage of systems development methods: are we stuck to old practice? Inform Software Tech 40(9):501–510
Introna LD, Whitley EA (1997) Against method-ism: exploring the limits of method. Inform Tech People 10(1):31–45
Karlsson F (2013) Longitudinal use of method rationale in method configuration: an exploratory study. Eur J Inform Syst 22:690–710
Karlsson F, Ågerfalk PJ (2004) Method configuration: adapting to situational characteristics while creating reusable assets. Inform Software Tech 46:619–633
Karlsson F, Ågerfalk PJ (2009a) Exploring agile values in method configuration. Eur J Inform Syst 18(4):300–316
Karlsson F, Ågerfalk PJ (2009b) Towards structured flexibility in information systems development: devising a method for method configuration. J Database Manag 20(3):51–75
Karlsson F, Ågerfalk PJ (2012) MC Sandbox: devising a tool for method-user-centered method configuration. Inform Software Tech 54(5):501–516
Kerth NL (2001) Project retrospectives: a handbook for team reviews. Dorset House, New York, NY, p 268
Klein H, Hirschheim R (2001) Choosing between competing design ideals in information systems development. Inform Syst Front 3(1):75–90
Lapouchnian A (2005) Goal-oriented requirements engineering: an overview of the current research. Department of Computer Science, University of Toronto, Toronto, p 30
Lings B, Lundell B (2004) Method-in-action and method-in-tool: some implications for CASE. Paper presented at the 6th international conference on enterprise information systems (ICEIS 2004)
Lyytinen K, Robey D (1999) Learning failure in information systems development. Inform Syst J 9:85–101
MacLean A, Young RM, Bellotti VME, Moran TP (1991) Questions, options, and criteria: elements of design space analysis. Hum Comput Interact 6(3/4):201–250
Maiden NAM, Gizikis A, Robertson S (2004) Provoking creativity: imagine what your requirements could be like. IEEE Software 21(5):68–75
Malcolm E (2001) Requirements acquisition for rapid applications development. Inform Manag 39:101–107
Nandhakumar J, Avison DE (1999) The fiction of methodological development: a field study of information systems development. Inform Tech People 12(2):176–191
Naumann JD, Jenkins AM (1982) Prototyping: the new paradigm for systems development. MIS Q 6(3):29–44
Nguyen L, Swatman PA (2000) Complementary use of ad hoc and post hoc design rationale for creating and organising process knowledge. In: Proceedings of HICSS 2000
Nickols FW (1993) Prototyping: systems development in record time. J Syst Manag 44(9):26–30
Nonaka I (1994) A dynamic theory of organizational knowledge creation. Organ Sci 5(1):14–37
Oinas-Kukkonen H (1996) Method rationale in method engineering and use. In: Brinkkemper S, Lyytinen K, Welke RJ (eds) Method engineering. Principles of method construction and too support. Proceedings of IFIP TC8, WG8.1/8.2 working conference on method engineering, Atlanta, USA, 26–28 August 1996. Chapman & Hall, London, pp 87–93
OMG (2010) OMG Unified Modeling Language™ (OMG UML), superstructure. Version 2.3, OMG document formal/2010-05-05
Parnas DL, Clements PC (1986) A rational design process: how and why to fake it. IEEE Trans Software Eng 12(2):251–257
Polanyi M (1958) Personal knowledge: towards a post-critical philosophy. Routledge & K. Paul, Chicago
Ramesh B, Dhar V (1992) Supporting systems development by capturing deliberations during requirements engineering. IEEE Trans Software Eng 18(6):498–510
Rettig M (1994) Prototyping for tiny fingers. Comm ACM 37(4):21–28
Riemenschneider CK, Hardgrave BC, Davis FD (2002) Explaining software developer acceptance of methodologies: a comparison of five theoretical models. IEEE Trans Software Eng 28(12):1135–1145
Rolland C, Prakash N, Benjamen A (1999) A multi-model view of process modelling. Requir Eng 4(4):169–187
Rooksby J, Sommerville I, Pidd M (2006) A hybrid approach to upstream requirements: IBIS and cognitive mapping, chapter 6. In: Dutoit AH, McCall R, Mistrik I, Paech, B (eds) Rationale management in software engineering. Springer, Berlin, pp 137–154
Rossi M, Ramesh B, Lyytinen K, Tolvanen J-P (2004) Managing evolutionary method engineering by method rationale. J Assoc Inform Syst 5(9):356–391
Russo NL, Stolterman E (2000) Exploring the assumptions underlying information systems methodologies: their impact on past, present and future ISM research. Inform Tech People 13(4):313–327
Schön D (1983) The reflective practitioner. Basic Books Inc., New York, NY
Searle JR (1969) Speech acts: an essay in the philosophy of language. Cambridge University Press, Cambridge
Stolterman E (1992) How system designers think about design and methods: some reflections based on an interview study. Scand J Inform Syst 4:137–150
Stolterman E, Russo NL (1997) The paradox of information systems methods: public and private rationality. Paper presented at the British Computer Society 5th annual conference on methodologies, Lancaster, UK
Tolvanen J-P (1998) Incremental method engineering with modeling tools. Dissertation, Jyväskylä studies in computer science, economics and statistics, vol 47, University of Jyväskylä, Finland, p 301
van Slooten K, Hodes B (1996) Characterizing IS development projects, In: Brinkkemper S, Lyytinen K, Welke R (eds) Proceedings of IFIP TC8 working conference on method engineering: principles of method construction and tool support. Chapman & Hall, London, pp 29–44
Weber M (1978) Economy and society. University of California Press, Berkeley, CA (originally published in 1922 in German)
Wistrand K (2009) Method rationale revealed: communication of knowledge in systems development methods. Doctoral dissertation. Örebro University. Intellecta Infolog, V. Frölunda: Sweden. ISBN 978-91-7668-659-1
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Henderson-Sellers, B., Ralyté, J., Ågerfalk, P.J., Rossi, M. (2014). Method Engineering as a Social Practice. In: Situational Method Engineering. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-41467-1_3
Download citation
DOI: https://doi.org/10.1007/978-3-642-41467-1_3
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-41466-4
Online ISBN: 978-3-642-41467-1
eBook Packages: Computer ScienceComputer Science (R0)