Requirements engineering for web-based information systems

This chapter overviews the existing methods of requirements analysis as prescribed by some of the best-known web-development methods. It also discusses the pre-eminent importance of stakeholder analysis, identification of stakeholder views and concerns, and the processes governing elicitation of web systems requirements. The chapter finally derives a model of concern-driven requirements evolution from several case studies undertaken in the area of web-enabled employee service systems.

Promoting and supporting requirements engineering creativity

Requirements Engineering (RE) is a commencing phase in the systems development life cycle and concerned with understanding and specifying the customer's requirements. RE has been recognized as a complex cognitive problem solving process which takes place in an unstructured and poorly understood problem .context. A recent understanding describes the RE process as inherently creative, involving cycles of incremental building followed by insight-driven econceptualization .of the problem space. This chapter relates this new understanding to various creative process models described in the creativity and psychology of problem solving literature.

A review of current attempts to support problem solving in RE using
various design rationale approaches suggests., that their common major
wealmess lies in the lack of support for the creative and insight-driven problem solving process in RE. In addressing this weakness, the chapter suggests a new approach to promoting and supporting RE creativity using design rationale. The suggested approach involves the ad hoc recording of rationale to support the creative exploration complemented by a post hoc conceptual characterization of the problem space to support insight driven reconceptualization.

Managing the requirements engineering process

Process management is a crucial issue in developing information or computer systems. Theories of software development process management suggest that the process should be supported and managed based on what the process really is. However, our learning from an action research study reveals that the requirements engineering (RE) process differs significantly from that which the current literature tends to describe. The process is not a systematic, smooth and incremental evolution of the requirements model, but involves occasional simplification and restructuring of the requirements model. This revised understanding of the RE process suggests a new challenge to both the academic and industrial communities, demanding new process management approaches. In this paper, we present our understanding of the RE process and its implications for process management.

Managing the requirements engineering process

Process management is a crucial issue in developing information or computer systems. Theories of software development process management suggest that the process should be supported and managed based on what the process really is. However, our learning from an action research study reveals that the requirements engineering (RE) process differs significantly from what the current literature tends to describe. The process is not a systematic, smooth and incremental evolution of the requirements model, but involves occasional simplification and restructuring of the requirements model. This revised understanding of the RE process suggests a new challenge to both the academic and industrial communities, demanding new process management approaches. In this paper, we present our understanding of the RE process and its implications for process management.

Understanding problem solving in requirements engineering : debating creativity with IS practitioners

RE is well-recognised as a creative problem solving activity by the systems development community. However, while substantial research has been conducted and knowledge gained about creativity in the general psychology of problem solving, creativity as it applies to RE remains a relatively unexplored area - one that has neither been comprehensively studied, nor highly recognised, as a research topic of importance. This paper attempts to address the above mentioned gap by presenting findings from a recent focus group study of creativity in RE as perceived by a group of RE practitioners. We provide a conceptual framework for understanding creativity in RE, which may be of use to requirements engineers attempting to enable more creative approaches and results, as well as adding to the existing, limited body of research in this area.

Issues in IT service-oriented requirements engineering

Corporate information technology (IT) management is increasingly service-oriented, offering continuous evaluation and improvement of application, communication, delivery and support services to internal and external customers. Service-oriented requirements engineering (SoRE) plays a significant role in identifying and specifying service requirements, formally defined through service-level agreements (SLAs). However, the new frameworks and approaches emerging to guide these developments have not yet addressed how requirements for such services can be effectively developed, nor identified the diverse issues involved. We report a case study of a web services team development of requirements for an internal Service Desk service. The study revealed five main issues of concern when developing service provider requirements: service roles, responsibilities and accountability; service performance metrics; resolution of conflicting stakeholder service requirements; customer acceptance of service change; and service provider team structure. This study suggests that in the new IT services era, new techniques and approaches are needed for eliciting and determining provider and customer requirements that involve key stakeholder groups equitably and more closely negotiate the sometimes-conflicting provider and customer needs.

Understanding requirements engineering process: a challenge for practice and education

Reviews of the state of the professional practice in Requirements Engineering (RE) stress that the RE process is both complex and hard to describe, and suggest there is a significant difference between competent and "approved" practice. "Approved" practice is reflected by (in all likelihood, in fact, has its genesis in) RE education, so that the knowledge and skills taught to students do not match the knowledge and skills required and applied by competent practitioners.

A new understanding of the RE process has emerged from our recent study. RE is revealed as inherently creative, involving cycles of building and major reconstruction of the models developed, significantly different from the systematic and smoothly incremental process generally described in the literature. The process is better characterised as highly creative, opportunistic and insight driven. This mismatch between approved and actual practice provides a challenge to RE education - RE requires insight and creativity as well as technical knowledge. Traditional learning models applied to RE focus, however, on notation and prescribed processes acquired through repetition. We argue that traditional learning models fail to support the learning required for RE and propose both a new model based on cognitive flexibility and a framework for RE education to support this model.

The slow wheels of requirements engineering research: responding to the challenge of societal change

Despite the significant Requirements Engineering (RE) research efforts over the past decade the research--industry gap still remains persistent.
Recent attempts by the RE research community to address this issue include cumulative knowledge studies to describe the current state of RE research and the establishment of a new conference dedicated to the comparative evaluation of RE.
This paper reports the state of RE research from 2001 to 2005. A taxonomy of RE literature is presented and a conceptual framework for
understanding the current state of RE is also described. The ensuing analysis shows that during the period 2001-2005 there was only an incremental development of RE research without any radical theoretical contributions to its body of knowledge. The paper also poses a challenge for the RE research community to respond to the dramatic changes in the
social and business world.

Using protocol analysis to explore the creative requirements engineering process

Protocol analysis is an empirical method applied by researchers in cognitive psychology and behavioural analysis. Protocol analysis can be used to collect, document and analyse thought processes by an individual problem solver. In general, research subjects are asked to think aloud when performing a given task. Their verbal reports are transcribed and represent a sequence of their thoughts and cognitive activities. These verbal reports are analysed to identify relevant segments of cognitive behaviours by the research subjects. The analysis results may be cross-examined (or validated through retrospective interviews with the research subjects). This paper offers a critical analysis of this research method, its approaches to data collection and analysis, strengths and limitations, and discusses its use in information systems research. The aim is to explore the use of protocol analysis in studying the creative requirements engineering process.

Requirements engineering during global software development : some impediments to the requirements engineering process : a case study

Requirements engineering is not straightforward for any software development team. Developing software when team members are located in widely distributed geographic locations poses many challenges for developers, particularly during the requirements engineering phase. This paper reports on a case study concerning a large software development project that was completed in just seven months between users located in the UK and software developers from an international software house based in New Zealand. The case indicates that while “true” global requirements engineering may be desirable in achieving economy of resources, a “hybrid” structure of requirements engineering processes is more realistic so that lasting relationships with clients may be formed, and requirements engineering activities achieved. The main impediment to the process of requirements engineering during global software development, as recounted by the team members in this case, is communication. Communication issues may be further described in terms of four categories: 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.

Contextual factors which influence creativity in requirements engineering

In many disciplines, creativity has been recognised as an important part of problem solving. In business, creativity enables the generation of better solutions and provides an opportunity to gain a competitive advantage. In Information Systems (IS) creativity assists developers in finding solutions to difficult problems by helping to efficiently utilise available resources and allows the more effective planning and running of complex projects. One of the most important aspects of IS development is Requirements Engineering (RE), the development activity aimed at understanding the needs and wants of IS customers. While previous RE researchers suggested that creativity is crucial in building high quality information systems, fostering creative outcomes in RE is difficult as it is affected by the multifaceted socioorganisational context within which IS development commonly takes place. This paper reports findings from an empirical study into creativity in RE. Specifically, it reports various contextual factors which were found to influence the creativity of individuals and their teams

Exploring the cultural and social impacts on the requirements engineering processes-highlighting some problems challenging virtual team relationships with clients

Abstract:

Requirements engineering is a crucial phase in software development. Software development in a virtual domain adds another dimension to the process of requirements engineering. There has been growing interest in virtual teams, and more specifically in virtual software development. While structured software development methods are the obvious first choice for project managers to ensure a virtual software development team remains on track, the social and cultural aspects of requirements engineering cannot be ignored. These social aspects are especially important across different cultures, and have been shown to affect the success of an information system. The discussion in this paper is centred around the requirements engineering processes of a virtual team in a Thai Software House. This paper explains the issues and challenges of requirements engineering in a virtual domain from a social and cultural perspective. Project managers need to encourage a balance between structured methods and social aspects in requirements engineering for virtual team members. Cultural and social aspects influence the relationship between the virtual team and the client.