Towards the Proper Integration of Extra-Functional Requirements

<body> <table width="100%"> <tr> <td align="center"> This page requires frames. <a href="http://dl.acs.org.au/index.php/ajis/article/viewPDFInterstitial/295/265">Click here</a> for the non-frames version. <p>Non-frames version <a href="http://dl.acs.org.au/index.php/ajis/article/viewPDFInterstitial/295/265">available</a>.</p> </td> </tr> </table> <h1>Towards the Proper Integration of Extra-Functional Requirements</h1> <h2><i>Hike Hochmuller</i></h2> <h3>Australasian Journal of Information Systems</h3> <h4>Abstract</h4> <div>In spite of the many achievements in software engineering, proper treatment of extra-functional requirements (also known as non-functional requirements) within the software development process is still a challenge to our discipline. The application of functionality-biased software development methodologies can lead to major contradictions in the joint modelling of functional and extra-functional requirements. Based on a thorough discussion on the nature of extra-functional requirements as well as on open issues in coping with them, this paper emphasizes the role of extra-functional requirements in the software development process. Particularly, a framework supporting the explicit integration of extra functional requirements into a conventional phase-driven process model is proposed and outlined.</div> </body>