Status of Non Functional Requirements Focused Practces and Their Impact on Project and Business Success

Abstract

Software applications are composed of functional requirements and non functional requirements. Functional requirements are demanded by every user and on the other hand the non functional requirements are handled in Adhoc nature due to inability of these requirements to provide necessary functionality. newlineIn ever changing dynamic environment with more focus on time to market and software quality, the survival of business unit is highly probabilistic. Imposition of such challenges is usually handled as solution strategies in business unit policies. But such policies are focused on handling functionality rather than non functional requirements. It had been due to limited work as available in literature related to empirical studies on non functional requirements and their contribution to business units. newlineThis thesis aims to carry the empirical studies including surveys, case studies and experimentations to achieve the below mentioned objectives: newlineand#61623; First, to empirically study the manner non functional requirements get attention of the software engineer during development of mobile apps like m-commerce apps in relation to functional apps. newlineand#61623; Second, to empirically analyze the contribution of non functional requirements in various project parameters like cost, time, project success etc. Such parameters are of prime interest as they determine survival of the firm in highly dynamic environment. The impact of non functional requirements on project success is determined by performing surveys and case studies individually and relative to each other. Sources for data collection include the industries, academics and the literature. newlineand#61623; Third, to empirically study the impact of non functional requirements on overall business success of both developing firm and software procuring firm. Project success may or may not lead to business success. newline newlineThe empirical analyses converged in the final understanding that the non functional requirements of the software are essential not only to software developing firm but also to firm procuring the