PERE: Evaluation and Improvement of Dependable Processes

This second edition follows quickly on the first edition and is an indication of how fast the subject is changing and developing. In the past two years there have been significant advances and these are reflected in this new edition.

2004

Existing Requirements Engineering (RE) process assessment models lack the components necessary to provide enough information about the quality of a RE process. The concept of "COncern of Requirement Engineering" (CORE) and the assessment models proposed in our previous research provide a method and new perspectives to assess the quality of a RE process. The case studies presented in this paper provide a comprehensive view of the application of the CORE model. The advantages of using the model for RE process assessment are two fold: first, it is more flexible because the major COREs assess the main contents of the activities of a RE process. Second, the categories classified in the model allow RE process assessment based on several categories. This allows for process improvement in an incremental manner. The CORE model is part of our RE process development framework and is used to assess the quality of the RE process under development.

1996

The first argument presented in this paper is that i f we have a clear understding of the objectives of the requirements engineering (RE) process then we can identify what techniques we need. No single method or technique will be suficient. The second argumenl is that a key objective of the RE process is to specify LI system which will ultimately be successful. Three common types of failure are eximined, process failure, expectation failure and interaction failure. The third argumerur is that if the causes of each type of failure can be described thm we will be able to identify what techniques are netrded tal help us avo& failure. The five comvnon causes ure described: the requirements engineering process ii'self; human communication within requirements, knowledge development, documentation of requirenxmts cad management. A discussion of each cause is follow<ed a list of the RE techniques needed The paper concludes with a 'wish list' of seventy requirements for RE )techniques, cad a brief discussion of the strengths and weuknessies of the RE community in meeting those requirements. 157

Information and Software Technology, 2008

When software development teams modify their requirements engineering process as an independent variable, they often examine the implications of these process changes by assessing the quality of the products of the requirements engineering process, e.g., a software requirements specification (SRS). Using the quality of the SRS as the dependent variable is flawed. As an alternative, this paper presents a framework of dependent variables that serves as a full range for requirements engineering quality assessment. In this framework, the quality of the SRS itself is just the first level. Other higher, and more significant levels, include whether the project was successful and whether the resulting product was successful. And still higher levels include whether or not the company was successful and whether there was a positive or negative impact on society as a whole.

2003

Abstract. The requirements engineering is the first phase of software engineering process, in which user requirements are collected, understood, and specified. Requirements engineering is recognized as a critical task, since m any software failures originate from inconsistent, incomplete or simply incorrect requirements specifications. In this paper we analyze the root problems of the requirements engineering from several viewpoints.

Software Quality Journal, 1999

This paper presents a system dynamics model for improving the requirements engineering process management. The paper argues that improving RE process management improves the quality of the specification produced. It uses a simulation modelling approach to capture the complex and dynamic nature of quality and also the cost of resources and time needed to complete the process. Current claims by various researchers and empirical evidence has led to our proposition that “the earlier in the requirements engineering phase that system dynamics simulation modelling is used, the more effective the RE process management is and the better its product quality will be.” In developing such a model, the paper fills an important gap in the RE process management literature and has potential to provide requirement engineers, managers and software development organisations with a model-based process framework to aid quality assessment and improvement. The paper concludes by suggesting that the framework makes a useful contribution both in providing the foundations for theory building in RE process management and quality improvement by aiding shared understanding through learning and training situations.

Requirements Engineering, 2013

Your article is protected by copyright and all rights are held exclusively by Springer-Verlag London. This e-offprint is for personal use only and shall not be self-archived in electronic repositories. If you wish to self-archive your article, please use the accepted manuscript version for posting on your own website. You may further deposit the accepted manuscript version in any repository, provided it is only made publicly available 12 months after official publication or later and provided acknowledgement is given to the original source of publication and a link is inserted to the published article on Springer's website. The link must be accompanied by the following text: "The final publication is available at link.springer.com".

Concepts, Methodologies, Tools, and Applications

Requirements Engineering (RE) is a key discipline in software development, and several standards and models are available to help assess and improve RE processes. However, different standards and models can also help achieve different improvement goals. Thus, organizations are challenged to select these standards and models to best suit their specific context and available resources. This chapter presents a review of selected RE-specific and generic process improvement models that are available in the public domain. The review aims to provide preliminary information that might be needed by organizations in selecting these models. The chapter begins with analyses of how RE maturity is addressed in the Capability Maturity Model Integration (CMMI) for Development. Then, it describes the principal characteristics of, and the assessment and improvement framework applied in four RE-specific process assessment and improvement models: the Requirements Engineering Good Practice Guide (REGPG)...

Global journal of computer science and technology, 2017

Requirement engineering is the most important process in software development life cycle. Quality assurance in requirement engineering has a great impact on the product quality. It checks whether the requirements meet the desired quality attributes i.e. adequacy, completeness, consistency etc. Quality Assurance of the requirement is important because the cost of requirements failure is very high. The proposed research is based on the survey of the quality assurance in requirement engineering. The major focus of this research paper is to analyze the quality parameters which assure the overcome of the issues related to the requirements. The research papers include brief overview of those parameters.

Correctly identifying and expressing dependability requirements for software systems has wide-ranging consequences for planning and conducting software development as well as for the final system success. Yet crucial difficulties exist, many stemming from the fact that definitions of "dependable" will vary not only from system to system, but will be perceived differently by different stakeholders of the same system.