Requirements Evolution is one of the main issues that affect development activities as well as system features (e.g., system dependability). Although researchers and practitioners recognise the importance of requirements evolution, research results and experience are still patchy. This points out a lack of methodologies that address requirements evolution. This thesis investigates the current u...

Software development teams are often geographically distributed from their customers and end users. This creates significant communication and coordination challenges that impact the effectiveness of requirements engineering. Travel costs, and the local availability of quality technical staff increase the demand for effective distributed software development teams. This research reports an empi...

Traditional approaches to requirements elicitation stress systematic and rational analysis and representation of organizational context and system requirements. This paper argues that the introduction of any computer-based system to an organization transforms the organization and changes the work patterns of the system’s users in the organization. These changes interact with the users’ values a...

There are many problems associated with requirements engineering, including problems in defining the system scope, problems in fostering understanding among the different communities affected by the development of a given system, and problems in dealing with the volatile nature of requirements. These problems may lead to poor requirements and the cancellation of system development, or else the ...

This paper examines the use of Bayesian Networks to tackle one of the tougher problems in requirements engineering, translating user requirements into system requirements. The approach taken is to model domain knowledge as Bayesian Network fragments that are glued together to form a complete view of the domain specific system requirements. User requirements are introduced as evidence and the pr...

0950-5849/$ see front matter 2012 Elsevier B.V. A http://dx.doi.org/10.1016/j.infsof.2012.07.011 ⇑ Corresponding author. E-mail addresses: [email protected] (S.T. Ac te.uam.es (J.W. Castro), [email protected] (N. Juristo). Context: To develop usable software we need to understand the users that will interact with the system. Personas is a HCI technique that gathers information about users in...

The guidelines for Requirements Management have been documented many times formally but the actual problems faced by the software industry are quite different. Through research it is found that most of the software projects fail before they are completed or if they do reach completion their quality is not up to the mark. The aim of this Research study is to identify the loopholes in the require...

Some systems failures are due to defects in manufacturing and design, however that there are a significant number of system failures which result from errors, omissions and inconsistencies in the system requirements. We thus need methods to support a ‘safe’ requirements engineering process whose objectives are to specify system requirements such that system states which compromise safety are av...

Requirements elicitation is widely regarded as the most challenging activity within the scope of requirements engineering. The activity concerns the understanding of problems that a system should address, which later leads to the identification of system requirements. As an abstract process, its effectiveness is greatly influenced by the credibility and suitability of the stakeholders involved....

This document presents the business requirement of Unified University Inventory System (UUIS) in Technology-independent manner. All attempts have been made in using mostly business terminology and business language while describing the requirements in this document. Very minimal and commonly understood Technical terminology is used. Use case approach is used in modeling the business requirement...