Experiences by Using AFFINE for Building Collaborative Applications for Online Communities

  • Mohamed Bourimi
  • Dogan Kesdogan
Part of the Lecture Notes in Computer Science book series (LNCS, volume 8029)


Continuous problems and deficits in developing complex and ever-changing (software) systems led to agile methods, e.g. Scrum. Nevertheless, the problem of considering a plethora of different functional as well as nonfunctional requirements (N/FRs) remains unsolved and gains in importance when engineering state-of-the-art software. The current tide of approaches aims at handling every single NFR by an individual process integrated into Scrum, yielding a process complexity which can not be handled properly. Scrum-based AFFINE was designed explicitly to provide an alternative solution to over-complex design- and development-processes and still considering all kinds of NFRs early enough in the process. In this paper, we discuss collected findings by using AFFINE in various projects dealing with the development of software for user-centered online communities towards some evidence of its suitability.


Agile Software Process Nonfunctional Requirements Engineering Security and Usability User Experience Scrum AFFINE 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Shneiderman, B., Plaisant, C.: Designing the User Interface: Strategies for Effective Human-Computer Interaction, 4th edn. Pearson Addison Wesley (2005)Google Scholar
  2. 2.
    Cranor, L., Garfinkel, S.: Security and Usability. O’Reilly Media, Inc. (2005)Google Scholar
  3. 3.
    Gross, T., Koch, M.: Computer-Supported Cooperative Workspace. Oldenburg (2007)Google Scholar
  4. 4.
    Bourimi, M., Barth, T., Haake, J.M., Ueberschär, B., Kesdogan, D.: AFFINE for enforcing earlier consideration of nFRs and human factors when building socio-technical systems following agile methodologies. In: Bernhaupt, R., Forbrig, P., Gulliksen, J., Lárusdóttir, M. (eds.) HCSE 2010. LNCS, vol. 6409, pp. 182–189. Springer, Heidelberg (2010)Google Scholar
  5. 5.
    Cremers, A.B., Alda, S.: Organizational requirements engineering (ch. 9) (2010), (last accessed, February 2013)
  6. 6.
    Schümmer, T.: A Pattern Approach for End-User Centered Groupware Development. Schriften zu Kooperations- und Mediensystemen - Band 3. JOSEF EUL VERLAG GmbH, Lohmar - Köln (August 2005)Google Scholar
  7. 7.
    Schwaber, K., Beedle, M.: Agile Software Development with Scrum, 1st edn. Prentice Hall PTR, Upper Saddle River (2001)Google Scholar
  8. 8.
    França, A.C.C., da Silva, F.Q.B., de Sousa Mariz, L.M.R.: An empirical study on the relationship between the use of agile practices and the success of scrum projects. In: Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement, ESEM 2010, pp. 37:1–37:4. ACM, New York (2010)Google Scholar
  9. 9.
    Li, J., Moe, N.B., Dybå, T.: Transition from a plan-driven process to scrum: a longitudinal case study on software quality. In: Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement, ESEM 2010, pp. 13:1–13:10. ACM, New York (2010)Google Scholar
  10. 10.
    Ambler, S.: Complex requirements on an agile project. Online (2008)Google Scholar
  11. 11.
    Salini, P., Kanmani, S.: Survey and analysis on security requirements engineering. Comput. Electr. Eng. 38(6), 1785–1797 (2012)CrossRefGoogle Scholar
  12. 12.
    McGraw, G.: Software security. IEEE Security and Privacy 2, 80–83 (2004)CrossRefGoogle Scholar
  13. 13.
    Beznosov, K., Kruchten, P.: Towards agile security assurance. In: Proceedings of the 2004 Workshop on New Security Paradigms, NSPW 2004, pp. 47–54. ACM, New York (2004)Google Scholar
  14. 14.
    Lee, J.C., Judge, T.K., McCrickard, D.S.: Evaluating extreme scenario-based design in a distributed agile team. In: CHI 2011 Extended Abstracts on Human Factors in Computing Systems, CHI EA 2011, pp. 863–877. ACM (2011)Google Scholar
  15. 15.
    Santen, T.: Security Engineering: Requirements Analysis, Specification, and Implementation. Habilitation, Fakultät Elektrotechnik und Informatik, Technische Universität Berlin (2006)Google Scholar
  16. 16.
    Ambler, S.: Beyond functional requirements on agile projects. Dr. Dobb’s Journal 33(10), 64–66+ (2008)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Mohamed Bourimi
    • 1
  • Dogan Kesdogan
    • 1
  1. 1.Information Systems InstituteUniversity of SiegenGermany

Personalised recommendations