Recent Requirements Engineering research, recognises that successful system development relies upon the ability to model and understand the intentional structure of the organisational and business environment within which an IS is intended to operate. The importance of establishing and maintaining explicit links between information systems requirements and business goals is further emphasised b...

Consensus building is essential in aligning multiple stakeholder viewpoints which are commonly emerging during the process of requirements elicitation, analysis and validation [15]. In fact, agreement among diverse groups of stakeholders is deemed prerequisite to establishing project cooperation and collaboration. While individuals frequently rank the importance of their personal goals over the...

Contribution structures offer a way to model the network of people who have participated in the requirements engineering process. They further provide the opportunity to extend conventional forms of artifactbased requirements traceability with the traceability of contributing personnel. In this paper, we describe a case study that investigated the modelling and use of contribution structures in...

In this paper we argue that the industrial development of interactive systems has to recognise the social dimension of work if these systems are to fully meet the real needs of their users. Under current approaches this depends on whether an individual requirements engineer implicitly applies a user-centred approach, recognises the importance of cooperation and is sufficiently sympathetic and i...

The Goal Based Requirements Analysis Tool (GBRAT) is designed to support goal-based requirements analysis. The tool provides procedural support for the identi cation, elaboration, re nement and organization of goals to specify the requirements for software based information systems. GBRAT employs interactive Web browser technology to support the collaborative nature of requirements engineering.

Requirements Engineering is considered as one of the most critical phases of a software development project. Low-quality requirements are a major reason for the failure of a project. Consequently, techniques are needed that help to improve the support of stakeholders in the development of requirements models as well as in the process of deciding about the corresponding release plans. In this pa...

We propose two stages for data warehouse requirements engineering (i) an ‘early information’ part where the information relevant to decision making is discovered, and (ii) a ‘late’ part where this information is structured as facts and dimensions. Our focus is on the former. Early information data warehouse requirements engineering starts with targets defined as pairs of the form where A...

Interviews with IS developers suggest that requirements analysis is rarely perceived as a cooperative activity. Instead it is often seen as a process of extracting requirements from passive clients (as terms such as “requirements capture” and “requirements engineering” imply). A more cooperative approach which recognises requirements analysis as a negotiative process between analyst(s) and clie...

Data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile collection of data to provide the strategic information to the decision makers. Most of the data ware house project fails to meet the business requirements and business goals because of the improper requirement engineering phase. Building a data warehouse is a very challenging task. Data warehouse development can us...