A Practical Estimation Method for Complex RE

Adoption of the most suitable requirements engineering (RE) process and selection of the most appropriate RE techniques for a given project are challenging issues for industry. In order to alleviate the problems, a framework for RE process development (FRERE) was developed based on our research in the last six years. The overall architecture of the framework and a brief case study are presented in the paper. The framework addresses several core issues of the RE process: engineering issues, domain issues, characteristics of the software project, and issues of conformity to software process standards. FRERE consists of three parts: (1) The RE process knowledge base (REPKB) which contains RE process knowledge, (2) methodologies which provide guidance to develop a customized software process model in an iterative way; and (3) assessment models which provide information about the suitability of the newly developed RE process model for the software project under development.

In global software development (GSD), teams from different geographies are involved in software development activities from requirement till management phase. There are many potential benefits associated with GSD environment such as development cost, round the clock development, accessibility to better skilled people and many others. Although, organizations are achieving the benefits of GSD but its challenging nature such as cultural and language differences, trust relationship, coordination and communication is introducing numerous challenges that cannot be ignored. These challenges are significantly influencing requirement engineering (RE) process in GSD. One of the reasons behind challenging nature of RE in GSD is varying situational contexts such as social, communication and cultural contexts, language, human, technical and management related contexts. This necessitate for a comprehensive framework that demonstrates the perspective of situational contexts. This study aims to review the existing situational RE frameworks, highlights the reported situational contexts and provide future research directions. The literature revealed that the situational contexts are commonly related to twelve categories that include stakeholders, organization, requirements, project, management, risk, culture, standard, task, communication, technique and methods, and innovation. The situational contexts related to these categories show the main standpoint of situational software development in GSD. These situational contexts are significant for improving competencies of the team members while performing RE process in GSD environment. This study also draws attention towards some imperative research directions for further studies in line of situational software engineering.

Requirements engineering (RE) process improvement methods typically work with explicit process models describing activities and document flow between the stakeholders involved, and with explicit document definitions. In complex, multi-project contexts, however, the RE process is better characterized as intertwining of design, negotiation, and sense-making. In the first part of This work, we present the concepts of a workshop-based RE process improvement technique suitable for a multi-project context. In the second part, we show the experiences made in an industrial case study conducted with Nokia smart traffic products. The major innovations of our approach are: (i) instead of a process model, an information model is created, which focuses solely on the responsibilities of stakeholders with regard to the major documents; (ii) instead of document details, only the major point of view of the documents is defined.

This paper identifies the essential components of a requirements engineering (RE) process and provides alternatives to the requirements analyst when deciding on a particular set of RE methods. Existing methods of choosing RE techniques are discussed, and a new technique is proposed specifically for choosing RE techniques for projects with critical time-to-market projects. The components of the essential RE process as well as many other insights into the practice of RE were identified by examining the current literature and by analyzing the data from 25 completed surveys concerning the area of RE. The survey data provides insight into the state of the practice in requirements engineering.

The aim of this tutorial is to explain in an accessible manner the psychology of people in the context of misunderstandings, politics and social issues that affect software development. It focuses on user-stakeholder interaction techniques for analysis and interpretation of human behaviour, and how psychological knowledge can be used to improve the requirements engineering (RE) process as well as interpreting the implications of human motivations and values for requirements and software systems architecture. Soft issues, such as politics and people's feelings, are often cited as problems in the RE process and as key causes of system failure. It is clear from the RE literature that understanding user beliefs and values is vital for the success of software development. The London Ambulance service is a canonical example of system failure caused, in part, by inadequate understanding of ambulance crews' motivations, values of self esteem and autonomy, and the emotional reaction to lack of involvement in the requirements process, leading to technology failure.

The first argument presented is that if we have a clear understanding of the objectives of the requirements engineering (RE) process then we can identify what techniques we need. No single method or technique will be sufficient. The second argument is that a key objective of the RE process is to specify a system which will ultimately be successful. Three common types of failure are examined: process failure, expectation failure and interaction failure. The third argument is that if the causes of each type of failure can be described then we will be able to identify what techniques are needed to help us avoid failure. The five common causes are described: the requirements engineering process itself, human communication within requirements, knowledge development, documentation of requirements and management. A discussion of each cause is followed by a list of the RE techniques needed. The paper concludes with a 'wish list' of seventy requirements for RE techniques, and a brief discussion of the strengths and weaknesses of the RE community in meeting those requirements.

Requirements Engineering (RE) is a critical process in Software Engineering (SE) activities. RE helps stakeholders to manage requirements appropriately before dedicated requirements are used to design and implement software. The first stage in RE process is known as requirements elicitation whereby during elicitation, stakeholders will perform a set of activities to permit understanding in problem domain for respected scenario and hence proposing a set of established requirements in developing software. In elicitation, stakeholders need to collaborate and communicate in order to produce unambiguous requirements and create mutual agreement for software design and development. This can produce desired solution for all stakeholders. Soft issue is one of non-technical requirements that can associate with social presence, social interaction elements such as comfort, connectedness and motivation. This requirements need to be emphasized during RE process especially for a system that is categorized in Computer- Supported Collaboration Working (CSCW) domain. Users need CSCW domain system to carry out virtual communication, knowledge sharing via system's features. The aim of this paper is to carry out a preliminary study on RE process and requirements elicitation activities by identifying whether soft issues have been engaged in existing requirements elicitation process. Another aim is to compare stakeholders' roles based on selected articles. The method to investigate requirements elicitation process is done by identifying existing elicitation processes as well as involvement of stakeholders' collaboration during elicitation. According to the study, the comparison of existing requirements elicitation processes and comparison of job roles have been produced as a result in this paper.

Software development requires intensive communication between the requirements engineers and software stakeholders, particularly during the Requirements Engineering (RE) phase. Therefore, the individuals' culture might influence both the RE process and the result. Our aims are to investigate the extend of cultural influences on the RE process, and to analyze how the RE process can be adapted to take into account cultural aspects. The model we present is based on Hofstede's cultural theory. The model was applied on a pilot case study in the context of the conservative Saudi Arabian culture. The results reveal 6 RE aspects and 10 cultural factors that have a large impact on the RE practice.

Requirements Engineering (RE) has established itself as a software engineering discipline during the past decades. While researchers have been investigating the RE discipline with a plethora of empirical studies, attempts to systematically derive an empirically-based theory in context of the RE discipline have just recently been started. However, such a theory is needed if we are to define and motivate guidance in performing high quality RE research and practice. We aim at providing an empirical and valid foundation for a theory of RE, which helps software engineers establish effective and efficient RE processes. We designed a survey instrument and theory that has now been replicated in 10 countries world-wide. We evaluate the propositions of the theory with bootstrapped confidence intervals and derive potential explanations for the propositions. We report on the underlying theory and the full results obtained from the replication studies with participants from 228 organisations. Our results represent a substantial step forward towards developing an empirically-based theory of RE giving insights into current practices with RE processes. The results reveal, for example, that there are no strong differences between organisations in different countries and regions, that interviews, facilitated meetings and prototyping are the most used elicitation techniques, that requirements are often documented textually, that traces between requirements and code or design documents is common, requirements specifications themselves are rarely changed and that requirements engineering (process) improvement endeavours are mostly intrinsically motivated. Our study establishes a theory that can be used as starting point for many further studies for more detailed investigations. Practitioners can use the results as theory-supported guidance on selecting suitable RE methods and techniques.

Because requirements engineering (RE) problems are widely acknowledged as having a major impact on the effectiveness of the software development process, Sommerville et al. have developed a requirements maturity model. However, research has shown that the measurement process within Sommerville's model is ambiguous, and implementation of his requirements maturity model leads to confusion. Hence, the objective of our research is to propose a new RE maturity measurement framework (REMMF) based on Sommerville's model and to provide initial validation of REMMF. The main purpose of proposing REMMF is to allow us to more effectively measure the maturity of the RE processes being used within organisations and to assist practitioners in measuring the maturity of their RE processes. In order to evaluate REMMF, two organisations implemented the measurement framework within their IT divisions, provided us with an assessment of their requirements process and gave feedback on the REMMF measurement process. The results show that our measurement framework is clear, easy to use and provides an entry point through which the practitioners can effectively judge the strengths and weakness of their RE processes. When an organisation knows where it is, it can more effectively plan for improvement.

Developing software when team members are located in widely distributed geographic locations poses many challenges for developers, particularly during the requirements engineering (RE) phase. Using a case study of a large software development project with users located in the UK and software developers from an international software house based in New Zealand, the paper argues that while global RE using electronic communication media may be desirable in achieving economy of resources, social and cultural aspects of RE need to be considered so that lasting relationships with clients may be formed, and RE activities achieved. The main impediments to the process of RE during global software development are communication resulting from differences in shared meanings and context associated with the following: distribution of the clients and the development team; distribution of the development team; cultural differences between the clients and the development team; and cultural differences among the development team.

Requirements Engineering (RE) discipline deals with elicitation, analysis, specification, validation and management of requirements. Several ontology-driven approaches have been proposed to improve these RE activities. However, the requirements engineering community still lacks a comprehensive understanding on how ontologies are used in RE process. The objective of this work is to explore how ontologies are employed in requirements engineering, aiming to identify the main phases addressed, the languages that have been used, the types of existing contributions, as well as the requirements modeling styles have been used and the benefits of using ontology in RE. We conducted a systematic literature review to identify the primary studies on the use of ontologies in RE, following a pre-defined review protocol. Sixty-six papers were selected, covering the five main RE process phases. Moreover, we have identified thirteen ontology-related languages. Furthermore, twenty-six empirical studies have been identified which provided evidence of five group of benefits. The main findings of this review are: (1) there are empirical evidences to state that ontologies benefit RE activities in both academy and industry settings, helping to reduce ambiguity, inconsistency and incompleteness of requirements; (2) the vast majority of papers do not meet all RE phases; (3) nearly half of the papers use W3C recommended languages; (4) the majority of contributions are supported by a tool; and (5) there is a great diversity of requirements modeling styles supported by ontologies.

Usability and requirements engineering both provide means for discovering, analyzing, and fulfilling users' needs. In practice, it is difficult to manage and control user-centered design and system development processes separately. Based on a case study conducted in two software product companies, we have aimed to understand the role of usability specialists in the requirements engineering (RE) process. Our findings indicate that usability is still often seen as user interface design instead of a more comprehensive characteristic of a software product. Therefore, usability specialists had difficulties participating in early RE activities. To integrate usability as a natural part of the RE process, the usability teams have started to organize training in their companies. The main purpose of the training is to ensure that usability is not relying solely on the work of specialists but becomes a common responsibility for the whole product development organization.

Requirements engineering (RE) deals with the software requirements elicitation, validation and verification processes and implementation of elicited requirements. The RE process, for value-based software (VBS) development, is one of the highly complex and non-linear processes which mainly depends on the key stakeholders. VBS systems are extremely different from traditional systems due to their association with financial streams. There is a need of value-based RE practices. Stakeholders' analysis plays a vital role in the selection of critical stakeholders for RE phase in VBS development. Different stakeholders' identification and quantification (SIQ) approaches are presented by researchers in order to identify and quantify the stakeholders. The existing approaches are not uniform in terms of process activities and different stakeholders' attributes. Non-uniformity results in higher time consumption and higher complexity. The existing SIQ approaches are not suitable for current value-based RE practices. Hence, this research presents an intelligent decision support system for the VBS SIQP using stakeholder metrics and fuzzy logic. The data is finally divided into three clusters in order to select the highly prioritized stakeholders for VBS systems.

A most favorable Requirement Engineering process is considered to be subject of situational characteristics of Software Requirement Engineering settings. These characteristics are related to organizations, project, process, requirements, stakeholders etc. However, list of situational factors affecting the Requirement Engineering process during Global Software Development is presently not available. The lack of such study is challenging as it not only restrain the ability to improve Requirement Engineering process, but also it can undermine the competence of Requirement Engineering team to determine the core constraints and characteristics of developing software. To address this scarcity, we have merged a considerable related research into an initial list of situational factors that affect the Requirement Engineering Process during Global Software Development. We have performed Systematic Literature Review for situational factors identification. To carry on data merging, we have used thorough data coding techniques adopted from Grounded Theory. The initial list of situational factors consists of 37 factors, which is the sound initial reference list for Requirement Engineering process definition in Global Software Development environment. The outcome of this study symbolizes a significant contribution to the Requirement Engineering body of knowledge.