Design for Excellence in the Context of Very Large-Scale Requirements Engineering

Sanja Aaramaa, Samuli Saukkonen, Jarkko Hyysalo, Jouni Similä, Pasi Kuvaja, Markku Oivo

2015

Abstract

The increasing complexity of software-intensive systems (SIS) has led to a completely new concept: Very Large-Scale Requirements Engineering (VLSRE), where the sheer number of requirements typically exceeds 10,000. Design for eXcellence (DfX) principles and their execution have been studied in different contexts for decades. However, DfX has not been in the focus of the Requirements Engineering (RE) process, and especially not in the VLSRE context. This paper addresses the DfX topic through an empirical study of the DfX RE-process and practices in a large global ICT organisation operating in the VLSRE mode. The result of this study is a conceptual framework that helps to overcome the challenges identified, leading towards changes in the operational procedures of the DfX RE-process, accommodating the requirements of very large-scale development. The piloting of the framework has been started in the case company, and initial feedback has been positive. The findings of this study offer new insights for scholars and practitioners.

References

  1. Abran, A., Moore, J. W., Bourque, P. and Dupuis, R. eds., 2004. SWEBOK: Guide to the software engineering body of knowledge. s.l. IEEE Computer Society.
  2. Aurum, A. and Wohlin, C., 2003. The fundamental nature of requirements engineering activities as a decision making process. Information and Software Technology, 45, pp. 945-954.
  3. Aurum, A. and Wohlin, C., 2007. A value-based approach in requirements engineering: Explaining some of the fundamental concepts. s.l., Springer. Berlin Heidelberg, pp. 109-115.
  4. Battin, R., Crocker, R., Kreidler, J. and Subramanian, K., 2001. Leveraging resources in global software development.
  5. Booker, J. D., 2003. Industrial practice in designing for quality. International Journal of Quality and Reliability Management, 20(3), pp. 288-303.
  6. Boothroyd, G. and Dewhurst, P., 1983. Design for assembly: A designer's handbook. Boothroyd Dewhurst Inc. Wakefield, Rhode Island.
  7. Bralla, J. G., 1996. Design for eXcellence. s.l. McGrawHill.
  8. Braun, P., 2003. Metamodel-based integration of tools. Helsinki, Finland, s.n.
  9. Cooper, J. S., 2004. Design analysis of PEMFC bipolar plates considering stack manufacturing and environmental impact. Journal of Power Sources, pp. 152-169.
  10. Dalgleish, G. F., Jared, G. E. M. and Swift, K. G., 2000. Design for assembly: Influencing the design process. Journal of Engineering Design, 11(1), pp. 17-29.
  11. De Hayes, D. W. and Robert, R. T., 1972. Guidelines for management. Business Horizons, 15(3), pp. 7-46.
  12. DeLain, L. and O'Meara, E., 2004. Building a business case for revenue management. Journal of Revenue & Pricing Management, 2, p. 368-377.
  13. Dodgson, M., Gann, D. and Salter, A., 2008. The management of technological innovation. Completely revised and updated. Oxford University Press. New York.
  14. Ebert, C. and De Neve, P., 2001. Surviving global software development. s.l., IEEE Software, pp. 62-69.
  15. Freeman, R., 1984. Strategic management: A stakeholder approach. Pitman. Boston, MA.
  16. Geer, D. and Ruhe, G., 2004. Software release planning: An evolutionary and iterative approach. Information and Software Technology, 46, pp. 243-253.
  17. Gorschek, T. and Wohlin, C., 2006. Requirements abstraction model. Requirements Engineering Journal, 11, pp. 79-101.
  18. Gray, B., 1989. Collaborating: Finding common ground for multiparty problems. Jossey-Bass. San Francisco.
  19. Gubrium, J. F. and Holstein, J. A., 2002. Handbook of interview research. Context & method. s.l. Sage Publications. Thousand Oaks.
  20. Hall, J. G., Jackson, M., Laney, R., Nuseibeh, B., and Rapanotti, L., 2002. Relating software requirements and architectures using problem frames. s.l., s.n.
  21. Healy, R. J., 1968. Design for security. s.l. Wiley.
  22. Heindl, M. and Biffl, S., 2006. Risk management with enhanced tracing of requirements rationale in highly distributed projects. ACM, New York, p. 20-26.
  23. Helo, P., 2004. Managing agility and productivity in the electronics industry. Industrial Management & Data Systems, 104(7), pp. 567-577.
  24. Hemmings, K. R., 1974. Commercial-vehicle cabs: Design for packaging, access and visibility. s.l., s.n., pp. 345-356.
  25. Herbsleb, J., Mockus, A., Finholt, T. and Grinter, R., 2001. An empirical study of global software development: Distance and speed. Toronto, Canada, s.n., pp. 81-90.
  26. Herbsleb, J. and Moitra, D., 2001. Global software development. s.l., s.n., pp. 16-20.
  27. Huang, G., 1996. Design for X: Concurrent engineering imperatives. Chapman and Hall. London, 1st edition.
  28. Hyysalo, J. et al., 2009. A new way to organise DFX in a large organization. Springer-Verlag. Oulu, Berlin, Heidelberg, pp. 274-288.
  29. Jacobson, I., Booch, F. and Rumbaugh, J., 1999. The unified software development process. AddisonWesley. Reading, MA.
  30. Kasanen, E., Lukka, K. and Siitonen, A., 1993. The constructive approach in management accounting research. Journal of Management Accounting Research, 5, p. 243-264.
  31. Kotonya, G. and Sommerville, I., 2003. Requirements engineering - Process and techniques. John Wiley & Sons Ltd. West Sussex.
  32. Krumenauer, F. Z., Matayoshi, C. T., da Silva, I. B., Filho, M. S., and Batalha, G. F., 2008. Concurrent engineering and DFMA approaches on the development of automotive panels and doors. Journal of Achievements in Materials and Manufacturing Engineering, 31(2), pp. 690-698.
  33. Lauesen, S., 2002. Software requirements - Styles and techniques. Addison-Wesley. London.
  34. Lee, H. L. and Billington, C., 1992. Managing supply chain inventory: Pitfalls and opportunities. Sloan Management Review, 33(3), pp. 65-73.
  35. Leffingwell, D. and Widrig, D., 2003. Managing software requirements: A use case approach. Pearson Education, Inc. Boston.
  36. Lehto, J., Härkönen, J., Haapasalo, H., Belt, P., Möttönen, M. and Kuvaja, P., 2011. Benefits of DfX in requirements engineering. Technology and Investment, 2(1), pp. 27-37.
  37. Lehtola, L., Kauppinen, M. and Kujala, S., 2004. Requirements prioritization challenges in practice. s.l., Springer , p. 497-508.
  38. Leuser, J. and Ott, D., 2010. Tackling semi-automatic trace recovery for large specifications. s.l., LNCS, pp. 203-217.
  39. Maciaszek, L., 2005. Requirements analysis and system design. Pearson Education. Harlow.
  40. Maltzman, R., Rembis, K. M., Donisi, M., Farley, M., Sanchez, R. C., and Ho, A. Y., 2005. Design for networks - Ultimate design for x. Bell Labs Technical Journal, 9(4), pp. pp. 5-23.
  41. Maznevski, M. and Chudoba, K., 2000. Bridging space over time: Global virtual team dynamics and effectiveness. Organization Science, 11(5), pp. 473- 492.
  42. McZara, J., Sarkani, S., Holzer, T. and Eveleigh, T., 2014. Software requirements prioritization and selection using linguistic tools and constraint solvers-A controlled experiment. Empirical Software Engineering, 8. Springer. US, pp. 1-41.
  43. Möttönen, M., Belt, P., Härkönen, J., Haapasalo, H. and Kuvaja, P., 2010. Applying design for sustainability in an ICT company. International Journal of Sustainable Economy, 2(2), pp. 180-193.
  44. Möttönen, M., Härkönen, J., Belt, P., Haapasalo, H. and Similä, J., 2009. Managerial view on design for manufacturing. Industrial Management and Data Systems, 109(6), pp. 859 - 872.
  45. Natt och Dag, J., Regnell, B., Gervasi, V. and Brinkkemper, S., 2005. A linguistic-engineering approach to large-scale requirements management. IEEE Software, Jan.-Feb., 22(1), pp. 32-39.
  46. Ngo-The, A. and Ruhe, G., 2005. Decision support in requirements engineering. In: Engineering and Managing Software Requirements. Springer. New York, NY, 1st edition. pp. 267-286.
  47. Nurmuliani, N., Zowghi, D. and Williams, S. P., 2006. Requirements volatility and its impact on change effort: Evidence-based research in software development projects. s.l., s.n.
  48. Paasivaara, M. and Lassenius, C., 2004. Collaboration practices in global inter-organizational software development projects. Software Process Improvement and Practice, 8, pp. 183-199.
  49. Potts, C., 1995. Invented requirements and imagined customers: Requirements engineering for off-the-shelf software. s.l., s.n.
  50. Pun, K., 2006. Determinants of environmentally responsible operations: A review. International Journal of Quality and Reliability Management, 23(3), pp. 279-297.
  51. Ramachandran, M., 2011. Software security engineering: Design and applications. Nova Science Publishers Inc. Commack, NY.
  52. Regnell, B., Svensson, R. and Wnuk, K., 2008. Can we beat the complexity of very large-scale requirements engineering? In: B. Paech & C. Rolland, eds. Requirements Engineering: Foundation for Software Quality. Springer. Heidelberg, pp. 123-128.
  53. Ruhe, G. and Saliu, M., 2005. The art and science of software release planning. Software, 22, pp. 47-53.
  54. Runeson, P. and Höst, M., 2009. Guidelines for conducting and reporting case study method in software engineering. Empirical Software Engineering, 14(22), pp. 131-164.
  55. Sabaliauskaite, G., Loconsole, A., Engström, E. U., Unterkalmsteiner, M., Regnell, B., Runeson, P. and Feldt, R., 2010. Challenges in aligning requirements engineering and verification in a large-scale industrial context. s.l., Springer, pp. 218-142.
  56. Shih-Wen, H., 2002. Concurrent design method for developing a new product. International Journal of Industrial Ergonomics, pp. 41-55.
  57. Sommerville, I. and Sawyer, P., 2004. Requirements engineering. A good practice guide. Wiley & Sons. Chichester, West Sussex.
  58. Stephen, J., Andriole, J. and Freeman, P., 1993. Software systems engineering - The case for a new discipline. Software Engineering Journal, p. 15.
  59. Strigini, L., 1996. Limiting the dangers of intuitive decision making. IEEE Software, 13, pp. 101-103.
  60. Svensson, R. B., Olsson, T. and Regnell, B., 2008. Introducing support for release planning of quality requirements - An industrial evaluation of the QUPER model. Washington, IEEE Computer Society, pp. 18-26.
  61. Tiikkaja, M., 2002. Experience report: Case: COTS SW component acquisition and management process, s.l.: Minttu project.
  62. van Lamsweerde, A., Darimont, R. and Letier, E., 1998. Managing conflicts in goal-driven requirements engineering. 24(11), pp. 908-926.
  63. Wiegers, K., 2003. Software requirements. Microsoft Press. Redmond (Washington), 2nd edition.
  64. Wnuk, K., Regnell, B. and Karlsson, L., 2009. What happened to our features? Visualization and understanding of scope change dynamics in a largescale industrial setting. Atlanta, GA, s.n., pp. 89-98.
  65. Wohlin, C. and Aurum, A., 2005. What is important when deciding to include software requirements in a project or release? International Symposium on Empirical Software Engineering, pp. 246-255.
  66. Xie, S. Q., Tu, P. L. and Zhou, Z. D., 2004. Internet-based DFX for rapid and economical tool/mould-making. International Journal of Advanced Manufacturing Technology, pp. 821-829.
  67. Xuan, X., Singh, A. D. and Chatterjee, A., 2006. Lifetime prediction and Design-for-Reliability of IC interconnections with electromigration induced degradation in the presence of manufacturing defects. Journal of Electronic Testing, 22(4-6), pp. 471-482.
Download


Paper Citation


in Harvard Style

Aaramaa S., Saukkonen S., Hyysalo J., Similä J., Kuvaja P. and Oivo M. (2015). Design for Excellence in the Context of Very Large-Scale Requirements Engineering . In Proceedings of the 10th International Conference on Software Engineering and Applications - Volume 1: ICSOFT-EA, (ICSOFT 2015) ISBN 978-989-758-114-4, pages 196-207. DOI: 10.5220/0005502101960207


in Bibtex Style

@conference{icsoft-ea15,
author={Sanja Aaramaa and Samuli Saukkonen and Jarkko Hyysalo and Jouni Similä and Pasi Kuvaja and Markku Oivo},
title={Design for Excellence in the Context of Very Large-Scale Requirements Engineering},
booktitle={Proceedings of the 10th International Conference on Software Engineering and Applications - Volume 1: ICSOFT-EA, (ICSOFT 2015)},
year={2015},
pages={196-207},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0005502101960207},
isbn={978-989-758-114-4},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 10th International Conference on Software Engineering and Applications - Volume 1: ICSOFT-EA, (ICSOFT 2015)
TI - Design for Excellence in the Context of Very Large-Scale Requirements Engineering
SN - 978-989-758-114-4
AU - Aaramaa S.
AU - Saukkonen S.
AU - Hyysalo J.
AU - Similä J.
AU - Kuvaja P.
AU - Oivo M.
PY - 2015
SP - 196
EP - 207
DO - 10.5220/0005502101960207