Issues Dealing with Non-Functional Requirements across the Contractual Divide

Agreement on Non-Functional Requirements between customer and supplier is crucial to a successful IT solution delivery project. In an ideal world, stakeholders and architects cooperate to achieve their common goals in a win-win situation. In a commercial setting, however, one dominant feature often introduces powerful forces from outside the technical realm. That feature is the customer/supplier relationship, usually formalized in bidding rules or as a delivery contract. Formal customer/supplier relationships often place severe limitations on information exchange between stakeholders and architects. In this paper, we explore the effect of such limitations on the interaction of architectural design with the quantification of Non-Functional Requirements, and explore a number of avenues to deal with them.

[1]  Martin Glinz,et al.  Comparison of Requirements Hand-off, Analysis, and Negotiation: Case Study , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[2]  Joost Noppen,et al.  Imperfect Information in Software Design Processes , 2007 .

[3]  Agile Manifesto,et al.  Manifesto for Agile Software Development , 2001 .

[4]  Martin Glinz,et al.  A Risk-Based, Value-Oriented Approach to Quality Requirements , 2008, IEEE Software.

[5]  Tom Gilb,et al.  Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, And Software Engineering Using Planguage , 2005 .

[6]  Barry Boehm,et al.  A collaborative spiral software process model based on Theory W , 1994, Proceedings of the Third International Conference on the Software Process. Applying the Software Process.

[7]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

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

[9]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

[10]  Colin J. Neill,et al.  Uncertainty: A Meta-Property of Software , 2005, 29th Annual IEEE/NASA Software Engineering Workshop.

[11]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[12]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[13]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[14]  Barry W. Boehm,et al.  Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach , 1995, 1995 17th International Conference on Software Engineering.

[15]  Tony Gorschek,et al.  Handshaking with Implementation Proposals: Negotiating Requirements Understanding , 2010, IEEE Software.

[16]  Jeff Sutherland,et al.  Manifesto for Agile Software Development , 2013 .

[17]  Brad Novotny,et al.  Public works contracts, public supply contracts and public service contracts , 2014 .

[18]  Richard Berntsson Svensson,et al.  Managing quality requirements in software product development , 2009 .

[19]  Barbara Paech,et al.  Answering a Request for Proposal - Challenges and Proposed Solutions , 2012, REFSQ.

[20]  Björn Regnell,et al.  Supporting Roadmapping of Quality Requirements , 2008, IEEE Software.

[21]  Rick Kazman,et al.  Making Architecture Design Decisions: An Economic Approach , 2002 .