Requirements Engineering for Emergent Application Software

Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 141)

Abstract

The field of Requirements Engineering is arguably one of the most sensitive areas in the development of not only software but more importantly in the development of systems and organisational structures and processes supported by such systems. As service systems play an increasingly important role in today’s economy, the ability of software to respond to emergent real-world contexts becomes a key-enabling factor to developing new and unpredictable business models. This paper, which is partly based on the keynote lecture given by the author at ICEIS 2012, considers the field of emerged enterprise application software and critically examines the applicability of the methodology factors underpinning much of the practice in Requirements Engineering, to such systems.

Keywords

Requirements engineering Emergent software Service systems Teleological methodology 

References

  1. 1.
    Spohrer, J., Riecken, D.: Special section on service science. Comm. ACM 49, 31–90 (2006)CrossRefGoogle Scholar
  2. 2.
    ISTAG: Software Technolgies - The Missing Key Enabling Technology: Toward a Strategic Agenda for Software Technologies in Europe. ISTAG - Information Society Technologies Advisory Group, Brussels, Belgium (2012)Google Scholar
  3. 3.
    Cheng, B.H.C., Atlee, J.M.: Current and Future Research Directions in Requirements Engineering. In: Lyytinen, K., Loucopoulos, P., Mylopoulos, J., Robinson, B. (eds.) Design Requirements Engineering. LNBIP, vol. 14, pp. 11–43. Springer, Heidelberg (2009)Google Scholar
  4. 4.
    OMG (2003): UML Specifications. Object Management Group (2003)Google Scholar
  5. 5.
    Boehm, B.W.: A spiral model of software development and enhancement. Computer 21, 61–72 (1988)CrossRefGoogle Scholar
  6. 6.
    Gotel, O.C.Z., Finkelstein, C.W.: An analysis of the requirements traceability problem. In: Proceedings of the First International Conference on Requirements Engineering, pp. 94–101 (1994)Google Scholar
  7. 7.
    Ramesh, B., Jarke, M.: Toward reference models for requirements traceability. IEEE Trans. Software Eng. 27, 58–93 (2001)CrossRefGoogle Scholar
  8. 8.
    Rolland, C., Loucopoulos, P., Grosz, G., Nurcan, S.: A framework for generic patterns dedicated to the management of change in the electricity supply industry. In: International DEXA Conference (1998)Google Scholar
  9. 9.
    Kavakli, E., Loucopoulos, P., Filippidou, D.: Using Scenarios to Systematically Support Goal-Directed Elaboration for Information Systems Requirements. In: IEEE Symposium and Workshop on Engineering of Computer-Based Systems, pp. 308–314. IEEE Computer Society (1996)Google Scholar
  10. 10.
    Lalioti, V., Loucopoulos, P.: Visualisation of Conceptual Specifications. Information Systems 19, 291–309 (1994)CrossRefGoogle Scholar
  11. 11.
    Loucopoulos, P., Katsouli, E.: Modelling business rules in an office environment. SIGOIS Bulletin 13(2), 28–37 (1992)CrossRefGoogle Scholar
  12. 12.
    Tsalgatidou, A., Loucopoulos, P.: An object-oriented rule-based approach to the dynamic modelling of information systems. In: International Conference on Dynamic Modelling of Information Systems (1990)Google Scholar
  13. 13.
    Loucopoulos, P.: From information modelling to enterprise modelling. In: Brinkkemper, S., Lindencrona, E., Solvberg, A. (eds.) Information Systems Engineering: State of the Art and Research Themes, pp. 67–78. Springer (2000)Google Scholar
  14. 14.
    Kavakli, E., Loucopoulos, P.: Experiences with goal-oriented modelling of organisational change. IEEE Trans. Syst. Man and Cybern. - Part C 36, 221–235 (2006)CrossRefGoogle Scholar
  15. 15.
    Yu, E.S.K., Mylopoulos, J.: Why Goal Oriented Requirements Engineering. Department of Computer Science, University of Toronto (1998)Google Scholar
  16. 16.
    Hansen, S., Berente, N., Lyytinen, K.: Requirements in the 21st Century: Current Practice and Emerging Trends. In: Lyytinen, K., Loucopoulos, P., Mylopoulos, J., Robinson, B. (eds.) Design Requirements Engineering. LNBIP, vol. 14, pp. 44–87. Springer, Heidelberg (2009)Google Scholar
  17. 17.
    Lyytinen, K., Loucopoulos, P., Mylopoulos, J., Robinson, B. (eds.): Design Requirements Engineering. LNBIP, vol. 14. Springer, Heidelberg (2009)Google Scholar
  18. 18.
    Jarke, M., Loucopoulos, P., Lyytinen, K., Mylopoulos, J., Robinson, W.: The brave new world of design requirements. Information Systems 36, 992–1008 (2011)CrossRefGoogle Scholar
  19. 19.
    Brooks, F.J.: No silver bullet: essence and accidents of software engineering. IEEE Computer 20, 10–19 (1987)CrossRefGoogle Scholar
  20. 20.
    Brooks, F.P.: The Design of Design: Essays from a Computer Scientist. Addison-Wesley, New York (2010)Google Scholar
  21. 21.
    SEI: Ultra Large Scale Systems: The Software Challenge of the Future. Software Engineering Institute (2006)Google Scholar
  22. 22.
    Rittel, H.W.J., Webber, M.: Dilemmas in a General Theory of Planning. In: Cross, N. (ed.) Developments in Design Methodology, pp. 135–144. Wiley, Chichester (1984)Google Scholar
  23. 23.
    Jarke, M., Loucopoulos, P., Lyytinen, K., Mylopoulos, J.: The Brave New World of Design Requirements: Four Key Principles. In: Pernici, B. (ed.) CAiSE 2010. LNCS, vol. 6051, pp. 470–482. Springer, Heidelberg (2010)Google Scholar
  24. 24.
    Lawson, B.: How Designers Think: The Design Process Demystified. Butterworth, Cambridge (1990)Google Scholar
  25. 25.
    Eastman, C.M.: On the Analysis of Intuitive Design Processes. In: Moore, G.T. (ed.) Emerging Methods in Environmental Design and Planning. M.I.T Press, Cambridge (1970)Google Scholar
  26. 26.
    Hillier, B., Musgrove, J., O’Sullivan, P.: Knowledge and design. In: Cross, N. (ed.) Developments in Design Methodology, pp. 245–264. Wiley, New York, (1984)Google Scholar
  27. 27.
    OPEN-GROUP: SOA Reference Architecture. The Open Group http://www.opengroup.org/soa/source-book/soa/soa.htm (2009)
  28. 28.
    Armbrust, M., Stoica, I., Zaharia, M., Fox, A., Griffith, R., Joseph, A.D., Katz, R., Konwinski, A., Lee, G., Patterson, D., Rabkin, A.: A view of cloud computing. Commun. ACM 53, 50–58 (2010)CrossRefGoogle Scholar
  29. 29.
    Hagge, L., Lappe, K.: Patterns for the RE process. In: Proceedings of the 12th IEEE International Conference on Requirements Engineering, pp. 90–99 (2004)Google Scholar
  30. 30.
    Rapanotti, L., Hall, J.G., Jackson, M., Nuseibeh, B.: Architecture-driven problem decomposition. In: Proceedings of the 12th IEEE Internal Requirements Engineering Conference, pp. 80–89. IEEE Computer Society, Washington (2004)Google Scholar
  31. 31.
    Loucopoulos, P., Wan-Kadir, W.M.N.: BROOD: business rules-driven object oriented design. J. Database Manag. 19, 41–73 (2008)CrossRefGoogle Scholar
  32. 32.
    Heidari, F., Loucopoulos, P., Kedad, Z.: A Quality-Oriented Business Process Meta-Model. In: Barjis, J., Eldabi, T., Gupta, A. (eds.) EOMAS 2011. LNBIP, vol. 88, pp. 85–99. Springer, Heidelberg (2011)Google Scholar
  33. 33.
    Grefen, P., Ludwig, H., Dan, A., Angelov, S.: An analysis of web services support for dynamic business process outsourcing. Inf. Softw. Technol. 48, 1115–1134 (2006)CrossRefGoogle Scholar
  34. 34.
    Loucopoulos, P., Champion, R.E.M.: Knowledge-based support for requirements engineering. Inf. Softw. Technol. 31, 123–135 (1989)CrossRefGoogle Scholar
  35. 35.
    Loucopoulos, P., Champion, R.E.M.: Concept acquisition and analysis in requirements specifications. Software Engineering Journal 5, 116–124 (1990)CrossRefGoogle Scholar
  36. 36.
    Prekas, N., Loucopoulos, P., Rolland, C., Grosz, G., Semmak, F., Brash, D.: Developing Patterns as a Mechanism for Assisting the Management of Knowledge in the Context of Conducting Organisational Change. In: Bench-Capon, T.J.M., Soda, G., Tjoa, A.M. (eds.) DEXA 1999. LNCS, vol. 1677, pp. 110–122. Springer, Heidelberg (1999)Google Scholar
  37. 37.
    Seruca, I., Loucopoulos, P.: Towards a systematic approach to the capture of patterns within a business domain. The Journal of Systems & Software 67, 1–18 (2003)CrossRefGoogle Scholar
  38. 38.
    Loucopoulos, P.: The F3 (From Fuzzy to Formal) View on Requirements Engineering. Ingénierie des Systèmes d’Information 2, 639–655 (1995)Google Scholar
  39. 39.
    Al Balushi, T.H., Sampaio, P.R.F., Dabhi, D., Loucopoulos, P.: ElicitO: A Quality Ontology-Guided NFR Elicitation Tool. In: Sawyer, P., Heymans, P. (eds.) REFSQ 2007. LNCS, vol. 4542, pp. 306–319. Springer, Heidelberg (2007)Google Scholar
  40. 40.
    Loucopoulos, P., Kavakli, E.: Enterprise Modelling and the Teleological Approach to Requirements Engineering. Int. J. Intell. Coop. Info. Syst. 4, 45–79 (1995)CrossRefGoogle Scholar
  41. 41.
    Newell, A.: The knowledge level. Artif. Intell. 18, 87–127 (1982)CrossRefGoogle Scholar
  42. 42.
    Simon, H.A.: Models of Bounded Rationality. MIT Press, Cambridge (1982)Google Scholar
  43. 43.
    Louridas, P., Loucopoulos, P.: A generic model for reflective design. ACM Trans. Software Eng. Methodol. 9, 199–237 (2000)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  1. 1.Department of Informatics and TelematicsHarokopio University of AthensAthensGreece

Personalised recommendations