Match!

Agile requirements engineering via paraconsistent reasoning

Published on Jul 1, 2014in Information Systems2.066
· DOI :10.1016/j.is.2013.05.008
Neil A. Ernst20
Estimated H-index: 20
(UBC: University of British Columbia),
Alexander Borgida41
Estimated H-index: 41
(RU: Rutgers University)
+ 1 AuthorsJ. Mylopolous78
Estimated H-index: 78
(University of Trento)
Sources
Abstract
Innovative companies need an agile approach towards product and service requirements, to rapidly respond to and exploit changing conditions. The agile approach to requirements must nonetheless be systematic, especially with respect to accommodating legal and non-functional requirements. This paper examines how to support lightweight, agile requirements processes which can still be systematically modeled, analyzed and changed. We propose a framework, RE-KOMBINE, which is based on a propositional language for requirements modeling called Techne. We define operations on Techne models which tolerate the presence of inconsistencies. This paraconsistent reasoning is vital for supporting delayed commitment to particular design solutions. We evaluate these operations with an industry case study using two well-known formal analysis tools. Our evaluations show that the proposed framework scales to industry-sized requirements model, while still retaining (via propositional logic) the informality that is so useful during early requirements analysis. HighlightsMotivates importance of managing software variability via paraconsistent reasoning.Introduces RE-KOMBINE for solving inconsistent requirements problems.Creates language T1 for expressing inconsistent requirements problems.Specifies and implements operators for querying requirements problems.Evaluates the RE-KOMBINE framework with a retrospective industrial case study.
  • References (42)
  • Citations (15)
📖 Papers frequently viewed together
2012
3 Authors (J. Mylopolous, ..., Neil A. Ernst)
4 Citations
6 Citations
2010ESEM: Empirical Software Engineering and Measurement
20 Citations
78% of Scinapse members use related papers. After signing in, all features are FREE.
References42
Newest
#2Lan CaoH-Index: 16
Last. Richard L. BaskervilleH-Index: 51
view all 3 authors...
2 CitationsSource
Jun 25, 2012 in CAiSE (Conference on Advanced Information Systems Engineering)
#1Neil A. Ernst (UBC: University of British Columbia)H-Index: 20
#2Alexander Borgida (RU: Rutgers University)H-Index: 41
Last. Ivan Jureta (UCL: Université catholique de Louvain)H-Index: 17
view all 4 authors...
Innovative companies need an agile approach for the engineering of their product requirements, to rapidly respond to and exploit changing conditions. The agile approach to requirements must nonetheless be systematic, especially with respect to accommodating legal and nonfunctional requirements. This paper examines how to support a combination of lightweight, agile requirements which can still be systematically modeled, analyzed and changed. We propose a framework, RE-KOMBINE, which is based on a...
26 CitationsSource
Aug 1, 2011 in RE (IEEE International Conference on Requirements Engineering)
#1Neil A. Ernst (U of T: University of Toronto)H-Index: 20
#2Alexander Borgida (RU: Rutgers University)H-Index: 41
Last. Ivan Jureta (Université de Namur)H-Index: 17
view all 3 authors...
This paper investigates aspects of the problem of software evolution resulting from top-level requirements change. In particular, while most research on design for software focuses on finding some correct solution, this ignores that such a solution is often only correct in a particular, and often short-lived, context. Using a logic-based goal-oriented requirements modeling language, the paper poses the problem of finding desirable solutions as the requirements change. Among other possible criter...
35 CitationsSource
Aug 1, 2011 in RE (IEEE International Conference on Requirements Engineering)
#1Sharon McGee ('QUB': Queen's University Belfast)H-Index: 4
#2Des Greer ('QUB': Queen's University Belfast)H-Index: 14
Although a number of requirements change classifications have been proposed in the literature, there is no empirical assessment of their practical value in terms of their capacity to inform change monitoring and management. This paper describes an investigation of the informative efficacy of a taxonomy of requirements change sources which distinguishes between changes arising from ‘market’, ‘organisation’, ‘project vision’, ‘specification’ and ‘solution’. This investigation was effected through ...
14 CitationsSource
Sep 1, 2010 in RE (IEEE International Conference on Requirements Engineering)
#1Ivan Jureta (Université de Namur)H-Index: 17
#2Alexander Borgida (RU: Rutgers University)H-Index: 41
Last. J. Mylopolous (U of T: University of Toronto)H-Index: 78
view all 4 authors...
Techne is an abstract requirements modeling language that lays formal foundations for new modeling languages applicable during early phases of the requirements engineering process. During these phases, the requirements problem for the system-to-be is being structured, its candidate solutions described and compared in terms of how desirable they are to stakeholders. We motivate the need for Techne, introduce it through examples, and sketch its formalization.
98 CitationsSource
Sep 22, 2010 in RR (Web Reasoning and Rule Systems)
#1Domenico Lembo (Sapienza University of Rome)H-Index: 28
#2Maurizio Lenzerini (Sapienza University of Rome)H-Index: 63
Last. Domenico Fabio Savo (Sapienza University of Rome)H-Index: 14
view all 5 authors...
We address the problem of dealing with inconsistencies in Description Logic (DL) knowledge bases. Our general goal is both to study DL semantical frameworks which are inconsistency-tolerant, and to devise techniques for answering unions of conjunctive queries posed to DL knowledge bases under such inconsistency-tolerant semantics. Our work is inspired by the approaches to consistent query answering in databases, which are based on the idea of living with inconsistencies in the database, but tryi...
133 CitationsSource
Jun 7, 2010 in CAiSE (Conference on Advanced Information Systems Engineering)
#1Matthias Jarke (RWTH Aachen University)H-Index: 48
#2Pericles Loucopoulos (Lboro: Loughborough University)H-Index: 26
Last. William N. Robinson (GSU: Georgia State University)H-Index: 22
view all 5 authors...
Despite its undoubted success, Requirements Engineering (RE) needs a better alignment between its research focus and its grounding in practical needs as these needs have changed significantly recently. We explore changes in the environment, targets, and the process of requirements engineering (RE) that influence the nature of fundamental RE questions. Based on these explorations we propose four key principles that underlie current requirements processes: (1) intertwining of requirements with imp...
25 CitationsSource
#1Ramon O'Callaghan (Tilburg University)H-Index: 3
This case describes the implementation and subsequent failure of an innovative system installed in the bars of Alvalade XXI, the recently built football stadium in Lisbon, Portugal. Casa XXI, the company running the bars, had entrusted the project to an IT supplier who had limited experience with large systems. During the inauguration, the system failed spectacularly creating a chaotic situation. The fiasco meant not only a financial loss, but also a blow to the reputation of the company. The ma...
5 CitationsSource
#1Balasubramaniam Ramesh (GSU: Georgia State University)H-Index: 30
#2Lan Cao (ODU: Old Dominion University)H-Index: 16
Last. Richard L. BaskervilleH-Index: 51
view all 3 authors...
This paper describes empirical research into agile requirements engineering (RE) practices. Based on an analysis of data collected in 16 US software development organizations, we identify six agile practices. We also identify seven challenges that are created by the use of these practices. We further analyse how this collection of practices helps mitigate some, while exacerbating other risks in RE. We provide a framework for evaluating the impact and appropriateness of agile RE practices by rela...
162 CitationsSource
#1Sotirios Liaskos (U of T: University of Toronto)H-Index: 16
#2Alexei (U of T: University of Toronto)H-Index: 1
Last. J. Mylopolous (U of T: University of Toronto)H-Index: 78
view all 5 authors...
We introduce a variability-intensive approach to goal decomposition that is tailored to support requirements identification for highly customizable software. The approach is based on the semantic characterization of OR-decompositions of goals. We first show that each high-level goal can be associated with a set of concerns, in response to which, alternative refinements of the goal can be introduced. A text corpus relevant to the domain of discourse can be used to derive such variability concerns...
118 CitationsSource
Cited By15
Newest
#2Everton GuimaraesH-Index: 5
Last. Hyggo AlmeidaH-Index: 10
view all 7 authors...
Source
#1Woogon Shim (Ajou University)
Agile and lean are now the mainstream tenets of software development. This development methodology is attracting attention because it can develop software that operates quickly despite uncertain situations and limited information (requirements), and it can adaptively develop while checking feedback both frequently and regularly. The key is to welcome change without resistance, which is not limited to development but also requires changes in requirement management. However, there is a lack of pra...
Source
#1Damjan Vavpotič (University of Ljubljana)H-Index: 8
#2Marko Robnik-Šikonja (University of Ljubljana)H-Index: 15
Last. Tomaž Hovelja (University of Ljubljana)H-Index: 3
view all 3 authors...
Software development enterprises are under consistent pressure to improve their management techniques and development processes. These are comprised of several software development methodology (SDM) disciplines such as requirements acquisition, design, coding, testing, etc. that must be continuously improved and individually tailored to suit specific software development projects. The paper proposes a methodology that enables the identification of SDM discipline quality categories and the evalua...
Source
#1Woogon Shim (LG Electronics)H-Index: 1
#2Seok-Won Lee (Ajou University)H-Index: 13
Abstract Nowadays agile development has become a mainstream development methodology. Yet agile is still lacking in how in-depth it deals with Requirement Engineering (RE) compared to the other development stages. There have been attempts to apply agile RE techniques to traditional development and conversely to apply traditional RE techniques to agile development. But the biggest problem is that it is difficult to maintain the essence of agile which is to “collaborate”, “(iterative and frequent) ...
3 CitationsSource
#1Chi Mai Nguyen (University of Trento)H-Index: 2
#2Roberto Sebastiani (University of Trento)H-Index: 40
Last. J. Mylopolous (University of Trento)H-Index: 78
view all 4 authors...
Goal models have been widely used in computer science to represent software requirements, business objectives, and design qualities. Existing goal modelling techniques, however, have shown limitations of expressiveness and/or tractability in coping with complex real-world problems. In this work, we exploit advances in automated reasoning technologies, notably satisfiability and optimization modulo theories (SMT/OMT), and we propose and formalize: (1) an extended modelling language for goals, nam...
24 CitationsSource
#1Shalinka Jayatilleke (La Trobe University)H-Index: 2
#2Richard Lai (La Trobe University)H-Index: 13
ContextSoftware requirements are often not set in concrete at the start of a software development project; and requirements changes become necessary and sometimes inevitable due to changes in customer requirements and changes in business rules and operating environments; hence, requirements development, which includes requirements changes, is a part of a software process. Previous work has shown that failing to manage software requirements changes well is a main contributor to project failure. G...
8 CitationsSource
#1Woogon ShimH-Index: 1
#2Seok-Won LeeH-Index: 13
Nowadays agile development has become a mainstream development methodology. Yet agile is still lacking in how in-depth it deals with Requirement Engineering (RE) compared to the other development stages. There have been attempts to apply agile RE techniques to traditional development and conversely to apply traditional RE techniques to agile development. But the biggest problem is that it is difficult to maintain the essence of agile which is to "collaborate", "(iterative and frequent) inspect a...
1 CitationsSource
#1Diana Costa (University of Aveiro)H-Index: 2
#2Manuel A. Martins (University of Aveiro)H-Index: 9
5 CitationsSource
#1Kaiss ElgharianiH-Index: 1
#2Nazri KamaH-Index: 7
The popularity of agile methodology has been increased since agile offers further collaboration. Requirements engineering (RE) is one of the software development process in agile approaches. The features of face to face communication is one of agile way which unlike to other traditional software methods. Software developers are using the definition agile way to improve the agile way of activities. Besides, the challenge of dealing with RE practices is not much is known in agile way or model. How...
6 CitationsSource
#1Irum Inayat (Information Technology University)H-Index: 7
#2Siti Salwah Salim (Information Technology University)H-Index: 12
Last. Shahaboddin Shamshirband (IAU: Islamic Azad University)H-Index: 38
view all 5 authors...
We mapped out 17 requirements engineering practices adopted by agile practitioners so far.Identified 5 challenges of traditional requirements engineering overcome by adopting agile requirements engineering.Found 8 challenges posed by following agile requirements engineering.Findings suggest that research context needs attention in terms of more empirical.The empirical results can help to analyse impact of adopting agile requirements engineering. Unlike traditional software development methods, a...
135 CitationsSource