AFFINE for Enforcing Earlier Consideration of NFRs and Human Factors When Building Socio-Technical Systems Following Agile Methodologies

  • Mohamed Bourimi
  • Thomas Barth
  • Joerg M. Haake
  • Bernd Ueberschär
  • Dogan Kesdogan
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6409)

Abstract

Nowadays, various user-centered and participatory design methodologies with different degree of agility are followed when building sophisticated socio-technical systems. Even when applying these methods, non-functional requirements (NFRs) are often considered too late in the development process and tension that may arise between users’ and developers’ needs remains mostly neglected. Furthermore, there is a conceptual lack of guidance and support for efficiently fulfilling NFRs in terms of software architecture in general. This paper aims at introducing the AFFINE framework simultaneously addressing these needs with (1) conceptually considering NFRs early in the development process, (2) explicitly balancing end-users’ with developers’ needs, and (3) a reference architecture providing support for NFRs. Constitutive requirements for AFFINE were gathered based on experiences from various projects on designing and implementing groupware systems.

References

  1. 1.
    Shneiderman, B., Plaisant, C.: Designing the User Interface: Strategies for Effective Human-Computer Interaction, 4th edn. Pearson Addison Wesley, London (2005)Google Scholar
  2. 2.
    Gross, T., Koch, M.: Computer-Supported Cooperative Workspace. Oldenburg, Bombay (2007)CrossRefGoogle Scholar
  3. 3.
    Chung, L., Nixon, B.A.: Dealing with non-functional requirements: three experimental studies of a process-oriented approach. In: ICSE 1995. ACM, New York (1995)Google Scholar
  4. 4.
    Jokela, T.: Assessment of user-centred design processes - lessons learnt and conclusions. In: Oivo, M., Komi-Sirviö, S. (eds.) PROFES 2002. LNCS, vol. 2559, pp. 232–246. Springer, Heidelberg (2002)CrossRefGoogle Scholar
  5. 5.
    Schümmer, T., Lukosch, S., Slagter, R.: Empowering end-users: A pattern-centered groupware development process. In: Fukś, H., Lukosch, S., Salgado, A.C. (eds.) CRIWG 2005. LNCS, vol. 3706, pp. 73–88. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  6. 6.
    Lieberman, H., Paterno, F., Wulf, V. (eds.): End User Development. Springer, Heidelberg (2006)Google Scholar
  7. 7.
    Highsmith, J.: Agile software development ecosystems. Addison-Wesley, Reading (2002)Google Scholar
  8. 8.
    Balzert, H.: Lehrbuch der Softwaretechnik, Basiskonzepte und Requirements Engineering,, 3rd edn. Spektrum (2008)Google Scholar
  9. 9.
    Haake, J.M., Schümmer, T., Haake, A., Bourimi, M., Landgraf, B.: Supporting flexible collaborative distance learning in the cure platform, vol. 1. IEEE Computer Society, Los Alamitos (2004)Google Scholar
  10. 10.
    Schümmer, T., Slagter, R.: The oregon software development process (2004)Google Scholar
  11. 11.
    Bourimi, M.: Collaborative design and tailoring of Web based learning environments in CURE. In: Dimitriadis, Y.A., Zigurs, I., Gómez-Sánchez, E. (eds.) CRIWG 2006. LNCS, vol. 4154, pp. 421–436. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  12. 12.
    Bourimi, M., Lukosch, S., Kühnel, F.: Leveraging visual tailoring and synchronous awareness in Web-based collaborative systems. In: Haake, J.M., Ochoa, S.F., Cechich, A. (eds.) CRIWG 2007. LNCS, vol. 4715, pp. 40–55. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  13. 13.
    Bourimi, M., Kühnel, F., Haake, J., Abou-Tair, D., Kesdogan, D.: Tailoring collaboration according privacy needs in real-identity collaborative systems. In: CRIWG (2009)Google Scholar
  14. 14.
    Ambler, S.W.: Beyond functional requirements on agile projects. Dr. Dobb’s Journal 33(10) (2008)Google Scholar
  15. 15.
    Huth, S.: Marktstudie probleme und fehler im requirements-engineering, www.sigs-datacom.de/wissen/artikel-fachzeitschriftel/artikelansicht.html?tx_mwjournals_pi1%5BshowUid%5D=2479 (accessed 2010)
  16. 16.
    Emam, K.E., Koru, A.G.: A replicated survey of it software project failures. IEEE Softw. 25(5) (2008)Google Scholar
  17. 17.
    Grudin, J.: Groupware and social dynamics: eight challenges for developers. Communications of the ACM 37(1) (1994)Google Scholar
  18. 18.
    Paech, B., Dutoit, A.H., Kerkow, D., Knethen, A.V.: Functional requirements, non-functional requirements, and architecture should not be separated. Technical report, Proceedings of the International Workshop on Requirements Engineering (2002)Google Scholar
  19. 19.
    Schwaber, K.: Scrum overview, http://codebetter.com/blogs/darrell.norton/pages/50339.aspx (accessed August 2010)
  20. 20.
    Erl, T.: Service-Oriented Architecture (SOA): Concepts, Technology, and Design. Prentice Hall PTR, Englewood Cliffs (2006)Google Scholar
  21. 21.
    Gu, Q., Lago, P.: A stakeholder-driven service life cycle model for SOA. In: IW- SOSWE 2007: 2nd International Workshop on Service Oriented Software Engineering. ACM, New York (2007)Google Scholar

Copyright information

© IFIP International Federation for Information Processing 2010

Authors and Affiliations

  • Mohamed Bourimi
    • 1
    • 2
  • Thomas Barth
    • 2
  • Joerg M. Haake
    • 1
  • Bernd Ueberschär
    • 3
  • Dogan Kesdogan
    • 2
  1. 1.Cooperative SystemsFernUniversität in HagenHagenGermany
  2. 2.IT SecurityUniversity of SiegenSiegenGermany
  3. 3.Leibniz Institute of Marine SciencesUniversity of KielKielGermany

Personalised recommendations