An information systems design theory for integrated requirements and release management systems

Proceedings of the 42nd Annual Hawaii International Conference on System Sciences, HICSS

Volumn , Issue , 2009, Pages

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

^a UNIVERSITY OF JYVÄSKYLÄ   (Finland)

^b NONE

Author keywords

Global software development; Information systems design theory; Knowledge management; Release management; Requirements management; Software process improvement

Indexed keywords

DESIGN; INFORMATION SYSTEMS; KNOWLEDGE MANAGEMENT; PRODUCT DEVELOPMENT; PROJECT MANAGEMENT; REQUIREMENTS ENGINEERING; SOFTWARE DESIGN; SYSTEMS ANALYSIS;

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

MANAGEMENT INFORMATION SYSTEMS;

EID: 63349085495     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/HICSS.2009.66     Document Type: Conference Paper

References (55)

1. Adelson, B. and Soloway, E. (1985). The Role of Domain Experience in Software Design. IEEE Transactions on Software Engineering, 11(11), 1351-1360.
2. Akao, Y. (1990). An Introduction to Quality Function Deployment. In Akao, Y. (ed.), Quality Function Deployment. Integrating Customer Requirements into Product Design, Productivity Press, 3-24.
3. Argyris, C. and Schon, D.A. (1995). Organizational Learning II: Theory, Method, and Practice. Prentice Hall.
4. Van Aken, J. E. (2004). Management Research Based on the Paradigm of the Design Sciences: The Quest for Field-Tested and Grounded Technological Rules. Journal of Management Studies, 41(2), 219-246.
5. Aubert B. A., Vandenbosch B. and Mignerat M. (2003). Towards the Measurement of Process Integration. Proceedings of the Annual Conference of the Administrative Sciences Association of Canada. Halifax, Nova Scotia
6. Bosch, J. (2002). Maturity and Evolution in Software Product Lines:Approaches, Artefacts and Organization. Proceedings of the Second Software Product Line Conference (SPLC2). Springer Lecture Notes in Computer Science, 257-271.
7. Brown, S. L. and Eisenhardt, K.M. (1995). Product Development: Past Research, Present Findings, and Future Directions. Academy of Management Review, 20(2), 343-378.
8. Burchill, G. and Fine, C.H. (1997). Time versus Market Orientation in Product Concept Development: Empirically-based Theory Generation. Management Science, 43(4), 465-478.
9. Carlshamre P. (2002). Release Planning in Market-Driven Software Product Development: Provoking an Understanding. Requirements Engineering, 7, 139-151.
10. Carmel, E. and Agarwal, R. (2001). Tactical Approaches for Alleviating Distance in Global Software Development. IEEE Software, March/April, 22-29.
11. Carmel, E. and Agarwal, R. (2002). The Maturation of Offshore Sourcing of Information Technology Work. MIS Quarterly Executive, 1(2), 65-78.
12. Ciborra, C. (1996). The Platform Organization: Recombi-ning Strategies, Structures, and Surprises. Organization Science, 7(2), 103-118.
13. Curtis, B., Krasner, H. and Iscoe, N. (1988). A Field Study of the Software Design Process for Large Scale Systems. Communications of the ACM, 31(11), 1268-1287.
14. Daskalantonakis, M.K. (1992). A Practical View of Software Measurement and Implementation Experiences within Motorola. IEEE Transactions on Software Engineering, 18(11), 998-1010.
15. Davis, A. (1992). Software Requirements: Objects, Functions, and States. Prentice Hall, Eaglewood Cliffs, NJ.
16. El Sawy, O. (1998). Minding Your Own Business Processes: The BPR Learning Book. New York: McGraw-Hill.
17. Forselius, P. and Käkölä, T. (2009). An Information Systems Design Product Theory for Software Project Estimation and Measurement Systems. Proceedings of HICSS-42. IEEE.
18. Forsgren, P. and Daugulis, A. (1998). Requirements Engineering In Control Center Procurement Projects: Practical Experiences from the Power Industry. Proceedings of the 3rd International Conference on Requirements Engineering. IEEE.
19. Gilb, T. (1998). Principles of Software Engineering Management. Addison-Wesley, Reading, MA.
20. Greer, D. and Ruhe, G. (2004). Software Release Planning: an Evolutionary and Iterative Approach. Information and Software Technology, 46, 243-253.
21. Griffin, A.J. and Hauser, J.R. (1992). Patterns of Communication among Marketing, Engineering and Manufacturing, - a Comparison between Two New Product Teams. Management Science, 38(3), 360-372.
22. Grynberg, A. and Goldin, L. (2003). Product Management in Telecom Industry - Using Requirements Management Process. Proceedings of IEEE International Conference on Software: Science, Technology and Engineering (SwSTE '03).
23. Halbleib, H. (2004). Requirements Management. Information Systems Management 21(1), 8-14.
24. Herbsleb, J.D., Moitra, D. (2001). Guest Editors' Introduction:Global Software Development. IEEE Software,18(2),16-20.
25. Hevner, A.R., March, S.T., Park, J. and Ram, S. (2004). Design Science in Information Systems Research. MIS Quarterly, 28(1), 75-105.
26. Hrones, J.A. Jr., Jedrey, B.C. Jr. and Zaaf, D. (1992). Defining global requirements with distributed QFD. Digital Technical Journal, 5(4), 36-46. http://www.hpl.hp.com/hpjournal/dtj/vol5num4/vol5num4art3.pdf.
27. ISO (2005). ISO/IEC TR 19759. Software Engineering -Guide to the Software Engineering Body of Knowledge (SWEBOK). International Organization for Standardization, http://www.iso.org.
28. ISO (2006). ISO/IEC 14143 Information technology -Software measurement - Functional size measurement-Part 6. International Organization for Standardization, http://www.iso.org.
29. Jones, C. (2008). Applied Software Measurement, Third Edition. McGraw-Hill.
30. Kotonya, G. and Sommerville, I. (1998). Requirement Engineering: Processes and Techniques. John Wiley & Sons Ltd, England.
31. Käkölä, T. (2008). Best Practices for International eSourcing of Software Products and Services. Proceedings of HICSS-41. IEEE.
32. Käkölä, T., Dueñas, J. (Eds.) (2006). Software Product Lines: Research Issues in Engineering and Management. Springer.
33. Käkölä, T. and Koota, K. (1999). Dual Information Systems: Supporting Organizational Working and Learning by Making Organizational Memory Transparent. Journal of Organizational Computing and Electronic Commerce, 9(2&3), 205-232.
34. th International Conference on Information Systems, Paris (in press).
35. Lehtola, L. and Kauppinen, M. (2006). Suitability of Requirements Prioritization Methods for Market-driven Software Product Development. Software Process Improvement and Practise, 11(1), 7-19.
36. Van der Linden, F., Schmid, K. and Rommes, E. (2007). Software Product Lines in Action: The Best Industrial Practice in Product Line Engineering. Springer.
37. Markus, M. L., Majchrzak, A., and Gasser, L. (2002). A Design Theory for Systems That Support Emergent Knowledge Processes. MIS Quarterly, 26(3), 179-212.
38. McGrath, M.E. (2001). Product Strategy for High-Technology Companies: How to Achieve Growth, Competitive Advantage, and Increased Profits. Second Edition, New York, NY: McGraw-Hill.
39. Meyer, M.H. and Lopez, L. (1995). Technology Strategy in Software Products Company. The Journal of Product Innovation Management, 12(4), 294-306.
40. Meyer, M.H. and Selinger, R. (1998). Product Platforms in Software Development.Sloan Management Review,40(1),61-74.
41. O'Reilly, C.A. (1982). Variations in decision makers' use of information sources:The impact of quality and accessibility of information. Academy of Management Journal, 25(4), 756-771.
42. Perry, D.E., Staudenmayer, N.A. and Votta, L.G. (1994). People, Organizations, and Process Improvement. IEEE Software, 11(4), 36-45.
43. Pohl, K., Böckle, G. and Van der Linden, F. (2005). Software Product Line Engineering. Springer.
44. Ramasubbu, N., Krishnan, M. S., Kompalli, P. (2005). Leveraging Global Resources: A Process Maturity Framework for Managing Distributed Development.IEEE Software,22(3),80-86.
45. Regnell, B., Höst, M., Natt och Dag, J., Beremark, P. and Hjelm, T. (2001). An Industrial Case Study on Distributed Prioritization in Market-Driven Requirement Engineering for Packaged Software. Requirements Engineering, 6(1), 51-62.
46. Rautiainen, K., Lassenius, C., Vähäniitty, J, Pyhäjärvi, M. and Vanhanen, J. (2002). A Tentative Framework for Managing Software Product Development in Small Companies. Proceedings of the 35th Annual Hawaii International Conference on System Sciences (HICSS), 3409-3417.
47. Ruhe, G. and Saliu, M. O. (2005). The Art and Science of Software Release Planning. IEEE Software, 22(6), 47-53
48. Salo, A. and Käkölä, T. (2005). Groupware Support for Requirements Management in New Product Development. Journal of Organizational Computing and Electronic Commerce, 15(4), 253-284.
49. Van De Ven, A.H. (1986). Central Problems in the Management of Innovation. Management Science, 32, 590-607.
50. Walls, J. G., Widmeyer, G. R. and El Sawy, O. (1992). Building an Information System Design Theory for Vigilant EIS. Information Systems Research, 3(1), 36-59.
51. Walls, J.G., Widmayer, G.R. and El Sawy, O. (2004). Assessing Information System Design Theory in Perspective: How Useful was our 1992 Initial Rendition? Journal of Information Technology Theory and Application, 6(2), 44-58.
52. Wesselius, J. (2006). Strategic Scenario-Based Valuation of Product Line Roadmaps. In T. Käkölä & J.C. Dueñas (Eds.), Software Product Lines: Research Issues in Engineering and Management, Springer, 53-89.
53. nd edition. Microsoft Press, Washington.
54. Yin, R.K. (2003). Case Study Research: Design and Methods, third edition. Sage Publications.
55. Zhang, W., Mei, H. and Zhao, H. (2006). Feature-driven Requirement Dependency Analysis and High-level Software Design. Requirements Engineering, 11,:205-220.