The main agenda of Requirements Engineering (RE) is the development of tools, techniques and languages for the elicitation, specification, negotiation, and validation of software requirements. However, this development has traditionally been focused on functional requirements (FRs), rather than non-functional requirements (NFRs). Consequently, NFR approaches developed over the years have been fragmental and there is a lack of clear understanding of the positions of these approaches in the RE process. This paper provides a systematic classification and analysis of 89 NFR approaches.

Background: IT Service Management (ITSM) is the set of processes that allow planning, organizing, directing and controlling the provisioning of IT services. Among the concerns of ITSM, namely within the service level management process, are the requirements for services availability, performance, accuracy, capacity and security, which are specified in terms of service-level agreements (SLA). Research problems: SLA definition and monitoring are open issues within the ITSM domain. In this research plan we are going to focus on three specific problems in this context: (1) SLAs in the context of ITSM are informally specified in natural language; (2) SLAs specifications are not grounded on models of ITSM processes; (3) SLAs compliance verification in IT services is not performed at the same level of abstraction as service design. Research goals: Our main goals on this research work are to mitigate the above problems by proposing a model-based approach to IT services SLA specification and compliance verification. The specification part will be accomplished by proposing a SLA language- a domain specific language (DSL) for defining quality attributes as non functional requirements (NFRs) in the context of ITSM. Its metamodel will be an extension of the meta-model of the adopted process modeling language. As

Due to the enormous pressure towards deploying software as fast as possible, functional requirements have been the main focus of software development process at the expense of implementing non-functional requirements (NFRs) such as performance and security. Thus, in practice, NFRs have been observed to be frequently neglected or forgotten in the software development process. However, NFRs is an important concept in requirements engineering which plays an essential role in the success or the failure of systems. NFRs introduce quality characteristics, but they also represent constraints under which the system must operate. So, the chances of success for the software system are maximized when NFRs are modeled since the initial phases of the development process. This article reviews the NFR concepts, relates them to the overall software development process and identifies new areas of further work. Keywords. Requirements engineering, Non-functional requirements, Software development process.

This research investigates the relevance of project scope management and organizational change management in the context of IT deployment projects in which new IT artifacts are introduced in organizations. Scope management refers to the management of project content, whereas organizational change management refers to communicating, justifying and leading the change delivered by the project to the organization receiving the new IT artifacts. Deployment refers to the process of “taking the artifacts into use”, involving both emergent and planned changes. This research provides new insights for both aspiring and current deployment project managers who need to understand better the characteristics of deployment projects, the motivations of project managers, and the most important success factors of deployment projects as those differ from software development projects and from other types of projects.

Abstract—Test-first development requires tests before implementation and provides fast feedback after implementation. However, this development method emphasizes functional testing rather than non-functional testing. Furthermore, it does not provide any approach to handle requirements trade-off problems even requirements conflicts are inevitable during software development. Thus, in this research we design a Requirement Trade-off Analysis Framework (RTAF) to automatically explore conflicts between requirements. This framework allows developers to define functional and non-functional requirements, set the properties of each requirement, and specify the critical design point of the system. In our approach, a critical design point may be implemented by several designs. By evaluating the satisfaction degrees of all requirements with respective to the possible designs, RTAF will determine the best design according to the critical method of different designs. This research will introduce a process to apply RTAF. A sorting example is developed to describe our framework and process. This approach is implemented on the basis of JUnit and JUnitPerf. Keywords—Test-first development, requirements conflicts, trade-off analysis 1.