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

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.

[1]  Ben Shneiderman,et al.  Designing the User Interface: Strategies for Effective Human-Computer Interaction , 1998 .

[2]  Barbara Paech,et al.  Functional requirements, non-functional requirements, and architecture should not be separated -A position paper , 2002 .

[3]  Patricia Lago,et al.  A stakeholder-driven service life cycle model for SOA , 2007, IW-SOSWE '07.

[4]  Stuart Anderson,et al.  Requirements Evolution from Process to Product Oriented Management , 2001, PROFES.

[5]  Khaled El Emam,et al.  A Replicated Survey of IT Software Project Failures , 2008, IEEE Software.

[6]  Glenn Cater,et al.  Service Oriented Architecture (SOA) , 2011, Encyclopedia of Information Assurance.

[7]  Stephan Lukosch,et al.  Leveraging Visual Tailoring and Synchronous Awareness in Web-Based Collaborative Systems , 2007, CRIWG.

[8]  Till Schümmer,et al.  The Oregon Software Development Process , 2004, XP.

[9]  Jim Highsmith,et al.  Agile Software Development Ecosystems , 2002 .

[10]  Timo Jokela.  Assessment of User-Centred Design Processes - Lessons Learnt and Conclusions , 2002, PROFES.

[11]  Lawrence Chung,et al.  Dealing with Non-Functional Requirements: Three Experimental Studies of a Process-Oriented Approach , 1995, 1995 17th International Conference on Software Engineering.

[12]  Helmut Balzert,et al.  Lehrbuch der Softwaretechnik - Basiskonzepte und Requirements Engineering, 3. Auflage , 2009, Lehrbücher der Informatik.

[13]  Jörg M. Haake,et al.  Tailoring Collaboration According Privacy Needs in Real-Identity Collaborative Systems , 2009, CRIWG.

[14]  Till Schümmer,et al.  Empowering End-Users: A Pattern-Centered Groupware Development Process , 2005, CRIWG.

[15]  Jonathan Grudin,et al.  Groupware and social dynamics: eight challenges for developers , 1994, CACM.

[16]  Jesus Favela,et al.  Groupware: Design, Implementation, and Use , 2003, Lecture Notes in Computer Science.

[17]  Mohamed Bourimi.  Collaborative Design and Tailoring of Web Based Learning Environments in CURE , 2006, CRIWG.

[18]  B. Schneirdeman,et al.  Designing the User Interface: Strategies for Effective Human-Computer Interaction , 1998 .

[19]  Jörg M. Haake,et al.  Supporting flexible collaborative distance learning in the CURE platform , 2004, 37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of the.