A Formal Knowledge Level Process Model of Requirements Engineering

Herlea, Daniela E.; Jonker, Catholijn M.; Treur, Jan; Wijngaards, Nick J. E.

doi:10.1007/978-3-540-48765-4_92

Cited by 4 publications

(3 citation statements)

References 4 publications

(3 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is well known that these activities are critical for supporting the analysis of requirements. However, most of the current models such as the Knowledge Level Process Model [9] and the Win-Win model [3] focus on providing a high-level perspective of the requirements process. As a result, lower level activities such as Modeling are often excluded, obscured, or ignored.…”

Section: Figure 1 Local Analysis Phase and Its Activitiesmentioning

confidence: 99%

Local and global analysis

Lobo

Arthur

2005

Proceedings of the 43rd Annual Southeast Regional Conference - Volume 2

View full text Add to dashboard Cite

This paper presents a unique approach to connecting requirements engineering activities into a process framework that can be employed to obtain quality requirements with reduced expenditures of effort and cost. It is well understood that early detection and correction of errors offers the greatest potential for improving requirements quality and avoiding cost overruns in the development of software systems. To realize the maximum benefits of this ideology, we propose a two-phase model that is novel in that it introduces the concept of verification and validation (V&V) early in the requirements life cycle. In the first phase, we perform V&V immediately following the elicitation of requirements for each individually distinct function of the system. Because the first phase focuses on capturing smaller sets of related requirements iteratively, each corresponding V&V activity is better focused for detecting and correcting errors in each requirement set. In the second phase, a complementary verification activity is initiated; the corresponding focus is on the quality of linkages between requirements sets rather than on the requirements within the sets. Consequently, this approach reduces the effort in verification and enhances the focus on the verification task. The second phase also addresses the business concerns collectively, and thereby produces requirements that are not only quality adherent, but are also business compliant. Our approach, unlike other models, has a minimal time delay between the elicitation of requirements and the execution of the V&V activities. Because of this short time gap, the stakeholders have a clearer recollection of the requirements, their context and rationale; this enhances the feedback during the V&V activities. Furthermore, our model includes activities that closely align with the effective requirements engineering processes employed in the software industry. Thus, our approach facilitates a better understanding of the flow of requirements, and provides guidance for the implementation of the requirements engineering process. This paper describes a well-defined, two-phase requirements engineering approach that incorporates the principles of early V&V to provide the benefits of reduced costs and enhanced quality requirements.

show abstract

Section: Figure 1 Local Analysis Phase and Its Activitiesmentioning

confidence: 99%

Local and global analysis

Lobo

Arthur

2005

Proceedings of the 43rd Annual Southeast Regional Conference - Volume 2

View full text Add to dashboard Cite

show abstract

“…Requirements describe, for example, functional and behavioural properties of the (Herlea, Jonker, Treur, and Wijngaards, 1999b). system to be built, while scenarios describe use-cases of interactions between a user and the system; e.g., (Erdmann and Studer, 1998;Weidenhaupt, Pohl, Jarke, and Haumer, 1998).…”

Section: Introductionmentioning

confidence: 99%

A Compositional Knowledge Level Process Model of Requirements Engineering

Herlea

Jonker

Treur

et al. 2002

Int. J. Soft. Eng. Knowl. Eng.

Self Cite

View full text Add to dashboard Cite

In current literature few detailed process models for Requirements Engineering are presented: usually high-level activities are distinguished, without a more precise specification of each activity. In this paper the process of Requirements Engineering has been analyzed using knowledge-level modelling techniques, resulting in a well-specified compositional process model for the Requirements Engineering task. This process model is considered to be a generic process model: it can be refined (by instantiation or specialisation) into a process model for a specific kind of Requirements Engineering process.

show abstract

“…Similar to the stepwise refinement that has occurred in the past for those software development phases that succeed requirements engineering in the lifecycle development process, we are now seeing the emergence of methodologies, tools, and techniques to support the production of quality requirements. Several requirements generation process models that support the production of quality requirements include the RGM [2], the Agile Requirements Model [1], the Requirements Triage [4], the Knowledge Level Process Model [7] and Volere [10].…”

Section: Introductionmentioning

confidence: 99%

RGML: a markup language for characterizing requirements generation processes

Sidky

Arthur

28th Annual NASA Goddard Software Engineering Workshop, 2003. Proceedings.

View full text Add to dashboard Cite

Despite advancements in requirements generation models, methods and tools, low quality requirements are still being produced. One potential avenue for addressing this problem is to provide the requirements engineer with an interactive environment that leads (or guides) him/her through a structured set of integrated activities that foster "good" quality requirements. While that is our ultimate goal, a necessary first step in developing such an environment is to create a formal specification mechanism for characterizing the structure, process flow and activities inherent to the requirements generation process. In turn, such specifications can serve as a basis for developing an interactive environment supporting requirements engineering.Reflecting the above need, we have developed a markup language, the Requirements Generation Markup Language (RGML), which can be used to characterize a requirements generation process.The RGML can describe process structure, flow of control, and individual activities. Within activities, the RGML supports the characterization of application instantiation, the use of templates and the production of artifacts. The RGML can also describe temporal control within a process as well as conditional expressions that control if and when various activity scenarios will be executed. The language is expressively powerful, yet flexible in its characterization capabilities, and thereby, provides the capability to describe a wide spectrum of different requirements generation processes.

show abstract

A Formal Knowledge Level Process Model of Requirements Engineering

Cited by 4 publications

References 4 publications

Local and global analysis

Local and global analysis

A Compositional Knowledge Level Process Model of Requirements Engineering

RGML: a markup language for characterizing requirements generation processes

Contact Info

Product

Resources

About