Issues dealing with non-functional requirements across the contractual divide

Proceedings of the 2012 Joint Working Conference on Software Architecture and 6th European Conference on Software Architecture, WICSA/ECSA 2012

Volumn , Issue , 2012, Pages 315-319

  Poort, Eltjo R ^a   Key, Andrew ^b   De With, Peter H N ^c   Van Vliet, Hans ^d  

^a Logica   (Netherlands)

^b Logica United Kingdom   (United Kingdom)

^c EINDHOVEN UNIVERSITY OF TECHNOLOGY   (Netherlands)

^d VU UNIVERSITY AMSTERDAM   (Netherlands)

Author keywords

IT Tendering; Non Functional Requirements; Project Management; Requirements Management; Software Architecture

Indexed keywords

COMMERCIAL SETTINGS; IDEAL WORLDS; INFORMATION EXCHANGES; IT SOLUTION; IT TENDERING; NON-FUNCTIONAL REQUIREMENTS; REQUIREMENTS MANAGEMENT; WIN-WIN;

ARCHITECTURAL DESIGN; PROJECT MANAGEMENT;

SOFTWARE ARCHITECTURE;

EID: 84870654883     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/WICSA-ECSA.212.52     Document Type: Conference Paper

References (26)

1. L. Chung, B. Nixon, E. S. Yu, and J. Mylopoulos, Non-Functional Requirements in Software Engineering. Kluwer Academic, 1999.
2. B. Paech, A. Detroit, D. Kerkow, and A. von Knethen, "Functional requirements, non-functional requirements, and architecture should not be separated - a position paper," ser. REFSQ, Essen, Germany, September 2002.
3. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, 2nd. ed. Addison Wesley, 2003.
4. T. Gilb, Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Newton, MA, USA: Butterworth- Heinemann, 2005.
5. B. Boehm and H. In, "Identifying Quality-Requirement Conflicts," IEEE Software, pp. 25-35, March 1996.
6. B. Boehm and P. Bose, "A collaborative spiral software process model based on Theory W," in Third International Conference on the Software Process, 'Applying the Software Process', 1994.
7. US Government, "Code of Federal Regulations, title 48: Federal Acquisition Regulation," National Archives and Records Administration, 2005.
8. European Commission, "Directive 2004/18/EC of the European Parliament and of the Council of 31 March 2004 on the coordination of procedures for the award of public works contracts, public supply contracts and public service contracts," Official Journal of the European Union, 2004.
9. "RACV Insurance Pty Ltd v. Unisys Australia Ltd," 2001, vSC 300.
10. R. Gram and B. Keulen, "Quick scan tunnelprojecten," Ministerie van Verkeer en Waterstaat - Rijkswaterstaat, 2010, referentie 10 008 R 012.
11. R. Kazman, J. Asundi, and M. Klein, "Making Architecture Design Decisions: An Economic Approach," SEI, Tech. Rep. CMU/SEI-2002-TR-035, 2002.
12. B. Regnell, R. Berntsson Svensson, and T. Olsson, "Supporting roadmapping of quality requirements," IEEE Software, vol. 25, pp. 42-47, March 2008.
13. R. Berntsson Svensson, "Managing quality requirements in software product development," Ph.D. dissertation, Department of Computer Science, Lund University, 2009.
14. D. A. Garvin, "What does "product quality" really mean?" MIT Sloan Management Review, vol. 26, pp. 25-43, Fall 1984.
15. B. Boehm, P. Bose, E. Horowitz, and M. J. Lee, "Software requirements negotiation and renegotiation aids: a Theory-W Based Spiral Approach," in 17th international conference on Software engineering (ICSE), 1995, pp. 243-253.
16. S. Fricker, T. Gorschek, C. Byman, and A. Schmidle, "Handshaking with implementation proposals: Negotiating requirements understanding," IEEE Software, vol. 27, no. 2, pp. 72-80, 2010.
17. P. Kruchten, The Rational Unified Process: An Introduction. Boston: Addison-Wesley, 1998.
18. G. Pitette, "Progressive acquisition and the RUP: Comparing and combining iterative processes for acquisition and software development," 2001.
19. B. Paech, R. Heinrich, G. Zorn-Pauli, A. Jung, and S. Tadjiky, "Answering a Request for Proposal - Challenges and Proposed Solutions," in Proceedings 18th International Working Conference Requirements Engineering: Foundation for Software Quality (REFSQ2012).
20. S. C. Mcconnell, Software Project Survival Guide (Pro - Best Practices). Microsoft Press, Nov. 1997.
21. P. A. Laplante and C. J. Neill, "Uncertainty: A meta-property of software," in 29th Annual IEEE/NASA Software Engineering Workshop, 2005, pp. 228-233.
22. J. Noppen, "Imperfect information in software design processes," Ph.D. dissertation, University of Twente, 2007.
23. Agile Alliance, "Manifesto for Agile Software Development," http://agilemanifesto.org, 2001.
24. A. M. Davis, Just Enough Requirements Management. Dorset House, 2005.
25. M. Glinz, "A Risk-Based, Value-Oriented Approach to Quality Requirements," IEEE Software, vol. 25, pp. 34-41, 2008.
26. S. Fricker and M. Glinz, "Comparison of requirements handoff, analysis, and negotiation: Case study," in 2010 18th IEEE International Requirements Engineering Conference, ser. RE '10. Washington, DC, USA: IEEE Computer Society, 2010, pp. 167-176.