An information systems design product theory for the class of integrated requirements and release management systems

Journal of Software Maintenance and Evolution

Volumn 23, Issue 6, 2011, Pages 443-463

  Käkölä, Timo ^a   Koivulahti Ojala, Mervi ^a   Liimatainen, Jani ^b  

^a UNIVERSITY OF JYVÄSKYLÄ   (Finland)

^b ACCENTURE   (United States)

Author keywords

global software product development; information systems design theory; knowledge management; release management; requirements management; software process improvement

Indexed keywords

INFORMATION SYSTEMS DESIGN THEORY; RELEASE MANAGEMENT; REQUIREMENTS MANAGEMENT; SOFTWARE PROCESS IMPROVEMENT; SOFTWARE PRODUCT DEVELOPMENT;

COMPUTER SOFTWARE MAINTENANCE; GROUPWARE; INDUSTRY; INFORMATION SYSTEMS; KNOWLEDGE MANAGEMENT; MANAGEMENT; MANAGEMENT INFORMATION SYSTEMS; PRODUCT DESIGN; PRODUCT DEVELOPMENT; SYSTEMS ANALYSIS;

SOFTWARE DESIGN;

EID: 80053188440     PISSN: 1532060X     EISSN: 15320618     Source Type: Journal    
DOI: 10.1002/smr.492     Document Type: Article

References (58)

1. Brown SL, Eisenhardt KM,. Product development: Past research, present findings, and future directions. Academy of Management Review 1995; 20 (2): 343-378.
2. Meyer MH, Selinger R,. Product platforms in software development. Sloan Management Review 1998; 40 (1): 61-74.
3. Carmel E, Agarwal R,. Tactical approaches for alleviating distance in global software development. IEEE Software 2001; 18 (2): 22-29. (Pubitemid 32293336)
4. Herbsleb JD, Moitra D,. Guest editors' introduction: Global software development. IEEE Software 2001; 18 (2): 16-20.
5. Ramasubbu N, Krishnan MS, Kompalli P,. Leveraging global resources: A process maturity framework for managing distributed development. IEEE Software 2005; 22 (3): 80-86. (Pubitemid 40889812)
6. Käkölä T, Dueñas J, (eds.). Software Product Lines: Research Issues in Engineering and Management. Springer: Berlin, 2006.
7. Pohl K, Böckle G, Van der Linden F,. Software Product Line Engineering: Foundations, Principles, and Techniques. Springer: Berlin, 2005.
8. Van der Linden F, Schmid K, Rommes E,. Software Product Lines in Action: The Best Industrial Practice in Product Line Engineering. Springer: Berlin, 2007.
9. Carmel E, Agarwal R,. The maturation of offshore sourcing of information technology work. MIS Quarterly Executive 2002; 1 (2): 65-78.
10. Käkölä T,. Best practices for international eSourcing of software products and services. Proceedings of 41st Hawaii International Conference on Systems Sciences (HICSS-41). IEEE: New York NY, 2008.
11. Adelson B, Soloway E,. The role of domain experience in software design. IEEE Transactions on Software Engineering 1985; 11 (11): 1351-1360. (Pubitemid 16539522)
12. Grynberg A, Goldin L,. Product management in Telecom Industry-Using requirements management process. Proceedings IEEE International Conference on Software: Science, Technology and Engineering (SwSTE'03), Los Alamitos, CA, U.S.A. IEEE Computer Society, 2003.
13. Halbleib H,. Requirements management. Information Systems Management 2004; 21 (1): 8-14. (Pubitemid 37538974)
14. Hrones JA Jr, Jedrey BC Jr, Zaaf D,. Defining global requirements with distributed QFD. Digital Technical Journal 1992; 5 (4): 36-46. Available at: http://www.hpl.hp.com/hpjournal/dtj/vol5num4/vol5num4art3.pdf. [15 January 2010 ].
15. Regnell B, Höst M, Nattoch Dag J, Beremark P, Hjelm T,. An industrial case study on distributed prioritization in market-driven requirement engineering for packaged software. Requirements Engineering 2001; 6 (1): 51-62.
16. Salo A, Käkölä T,. Groupware support for requirements management in new product development. Journal of Organizational Computing and Electronic Commerce 2005; 15 (4): 253-284. (Pubitemid 43471310)
17. Akao Y,. An introduction to quality function deployment. Quality Function Deployment: Integrating Customer Requirements into Product Design, Akao Y, (ed.). Productivity Press, 1990; 3-24.
18. Burchill G, Fine CH,. Time versus market orientation in product concept development: Empirically-based theory generation. Management Science 1997; 43 (4): 465-478. (Pubitemid 127569851)
19. Griffin AJ, Hauser JR,. Patterns of communication among marketing, engineering and manufacturing-A comparison between two new product teams. Management Science 1992; 38 (3): 360-372.
20. Curtis B, Krasner H, Iscoe N,. A field study of the software design process for large scale systems. Communications of the ACM 1988; 31 (11): 1268-1287.
21. Ciborra C,. The platform organization: Recombining strategies, structures, and surprises. Organization Science 1996; 7 (2): 103-118.
22. Wesselius J,. Strategic scenario-based valuation of product line roadmaps. Software Product Lines: Research Issues in Engineering and Management, Käkölä T, Dueñas JC, (eds.). Springer: Berlin, 2006; 53-89.
23. Käkölä T, Taalas A,. Validating the information systems design theory for dual information systems. Proceedings of the 29th International Conference on Information Systems (ICIS). Association for Information Systems: Paris, 2008. Available at: http://www.aisnet.org [15 January 2010 ].
24. Forselius P, Käkölä T,. An information systems design product theory for software project estimation and measurement systems. Proceedings of 42nd Hawaii International Conference on Systems Sciences (HICSS-42). IEEE: New York NY, 2009.
25. ISO. Information technology-Software measurement-Functional size measurement-Part 6. ISO/IEC 14143, International Organization for Standardization, 2006. Available at: http://www.iso.org [15 January 2010 ].
26. Van De Ven AH,. Central problems in the management of innovation. Management Science 1986; 32 (5): 590-607.
27. Hevner AR, March ST, Park J, Ram S,. Design science in information systems research. MIS Quarterly 2004; 28 (1): 75-105.
28. Markus ML, Majchrzak A, Gasser L,. A design theory for systems that support emergent knowledge processes. MIS Quarterly 2002; 26 (3): 179-212.
29. Van Aken JE,. Management research based on the paradigm of the design sciences: The quest for field-tested and grounded technological rules. Journal of Management Studies 2004; 41 (2): 219-246. (Pubitemid 38284437)
30. Walls JG, Widmeyer GR, El Sawy O,. Building an information system design theory for vigilant EIS. Information Systems Research 1992; 3 (1): 36-59.
31. Walls JG, Widmeyer GR, El Sawy O,. Assessing information system design theory in perspective: How useful was our 1992 initial rendition? Journal of Information Technology Theory and Application 2004; 6 (2): 44-58.
32. Walsh KR, Dickey MH,. Structured modeling group support systems: A product design theory. Information and Management 2003; 41 (5): 655-667.
33. Software engineering-Guide to the software engineering body of knowledge (SWEBOK). ISO. ISO/IEC TR 19759, International Organization for Standardization, 2005. Available at: http://www.iso.org [15 January 2010 ].
34. Rautiainen K, Lassenius C, Vähäniitty J, Pyhäjärvi M, Vanhanen J,. A tentative framework for managing software product development in small companies. Proceedings of 35th Hawaii International Conference on System Sciences (HICSS-35), 2002; 3409-3417.
35. Yin RK,. Case Study Research: Design and Methods (3rd edn). Sage Publications: Beverley Hills CA, 2003.
36. Koivulahti-Ojala M, Käkölä T,. Framework for evaluating the version management capabilities of a class of UML modeling tools from the viewpoint of multi-site, multi-partner product line organizations. Proceedings of the 43rd Hawaii International Conference on Systems Sciences (HICSS-43). IEEE: New York NY, 2010.
37. Argyris C, Schon DA,. Organizational Learning II: Theory, Method, and Practice. Prentice-Hall: Englewood Cliffs NJ, 1995.
38. Perry DE, Staudenmayer NA, Votta LG,. People, organizations, and process improvement. IEEE Software 1994; 11 (4): 36-45.
39. Bosch J,. Maturity and evolution in software product lines: Approaches, artefacts and organization. Proceedings of the Second Software Product Line Conference (SPLC2) (Lecture Notes in Computer Science). Springer: Berlin, 2002; 257-271.
40. McGrath ME,. Product Strategy for High-Technology Companies: How to Achieve Growth, Competitive Advantage, and Increased Profits (2nd edn). McGraw-Hill: New York NY, 2001.
41. Meyer MH, Lopez L,. Technology strategy in software products company. The Journal of Product Innovation Management 1995; 12 (4): 294-306.
42. Carlshamre P,. Release planning in market-driven software product development: Provoking an understanding. Requirements Engineering 2002; 7 (3): 139-151.
43. Ruhe G, Saliu MO,. The art and science of software release planning. IEEE Software 2005; 22 (6): 47-53. (Pubitemid 41709724)
44. Gilb T,. Principles of Software Engineering Management. Addison-Wesley: Reading MA, 1998.
45. Greer D, Ruhe G,. Software release planning: An evolutionary and iterative approach. Information and Software Technology 2004; 46 (4): 243-253.
46. Momoh J, Ruhe G,. Release planning process improvement-An industrial case study. Software Process: Improvement and Practice 2006; 11 (3): 295-307. (Pubitemid 44023480)
47. Kotonya G, Sommerville I,. Requirement Engineering: Processes and Techniques. Wiley: England, 1998.
48. Davis A,. Software Requirements: Objects, Functions, and States. Prentice-Hall: Eaglewood-Cliffs NJ, 1992.
49. Forsgren P, Daugulis A,. Requirements engineering in Control Center Procurement Projects: Practical experiences from the power industry. Proceedings of the 3rd International Conference on Requirements Engineering. IEEE: New York NY, 1998.
50. Käkölä T, Koota K,. Dual information systems: Supporting organizational working and learning by making organizational memory transparent. Journal of Organizational Computing and Electronic Commerce 1999; 9 (2 and 3): 205-232.
51. Bundschuh M, Dekkers C,. The IT Measurement Compendium: Estimating and Benchmarking Success with Functional Size Measurement. Springer: Berlin, 2008.
52. Daskalantonakis MK,. A practical view of software measurement and implementation experiences within Motorola. IEEE Transactions on Software Engineering 1992; 18 (11): 998-1010.
53. Jones C,. Applied Software Measurement (3rd edn). McGraw-Hill: New York NY, 2008.
54. Wiegers KE,. Software Requirements: Practical Techniques for Gathering and Managing Requirements (2nd edn). Microsoft Press: Washington, 2003.
55. O'Reilly CA,. Variations in decision makers' use of information sources: The impact of quality and accessibility of information. Academy of Management Journal 1982; 25 (4): 756-771.
56. Aubert BA, Vandenbosch B, Mignerat M,. Towards the measurement of process integration. Proceedings of the Annual Conference of the Administrative Sciences Association of Canada, Halifax, NS, 2003.
57. Zhang W, Mei H, Zhao H,. Feature-driven requirement dependency analysis and high-level software design. Requirements Engineering 2006; 11 (3): 205-220. (Pubitemid 43881237)
58. Lehtola L, Kauppinen M,. Suitability of requirements prioritization methods for market-driven software product development. Software Process Improvement and Practice 2006; 11 (1): 7-19.