Match!

Agile requirements engineering via paraconsistent reasoning

Published on Jul 1, 2014in Information Systems2.07
· DOI :10.1016/j.is.2013.05.008
Neil A. Ernst19
Estimated H-index: 19
(UBC: University of British Columbia),
Alexander Borgida41
Estimated H-index: 41
(RU: Rutgers University)
+ 1 AuthorsJ. Mylopolous74
Estimated H-index: 74
(University of Trento)
Cite
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 (40)
  • Citations (13)
Cite
References40
Newest
Published on Jun 25, 2012 in CAiSE (Conference on Advanced Information Systems Engineering)
Neil A. Ernst19
Estimated H-index: 19
(UBC: University of British Columbia),
Alexander Borgida41
Estimated H-index: 41
(RU: Rutgers University)
+ 1 AuthorsIvan Jureta17
Estimated H-index: 17
(UCL: Université catholique de Louvain)
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...
Published on Aug 1, 2011 in RE (IEEE International Conference on Requirements Engineering)
Sharon McGee4
Estimated H-index: 4
('QUB': Queen's University Belfast),
Des Greer13
Estimated H-index: 13
('QUB': Queen's University Belfast)
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 ...
Published on Aug 1, 2011 in RE (IEEE International Conference on Requirements Engineering)
Neil A. Ernst19
Estimated H-index: 19
(U of T: University of Toronto),
Alexander Borgida41
Estimated H-index: 41
(RU: Rutgers University),
Ivan Jureta17
Estimated H-index: 17
(Université de Namur)
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...
Published on Sep 22, 2010 in RR (Web Reasoning and Rule Systems)
Domenico Lembo28
Estimated H-index: 28
(Sapienza University of Rome),
Maurizio Lenzerini60
Estimated H-index: 60
(Sapienza University of Rome)
+ 2 AuthorsDomenico Fabio Savo13
Estimated H-index: 13
(Sapienza University of Rome)
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...
Published on Sep 1, 2010 in RE (IEEE International Conference on Requirements Engineering)
Ivan Jureta17
Estimated H-index: 17
(Université de Namur),
Alexander Borgida41
Estimated H-index: 41
(RU: Rutgers University)
+ 1 AuthorsJ. Mylopolous74
Estimated H-index: 74
(U of T: University of Toronto)
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.
Published on Jun 7, 2010 in CAiSE (Conference on Advanced Information Systems Engineering)
Matthias Jarke48
Estimated H-index: 48
(RWTH Aachen University),
Pericles Loucopoulos20
Estimated H-index: 20
(Lboro: Loughborough University)
+ 2 AuthorsWilliam N. Robinson22
Estimated H-index: 22
(GSU: Georgia State University)
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...
Published on Dec 1, 2007
Ramon O'Callaghan5
Estimated H-index: 5
(Tilburg University)
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...
Published on Nov 13, 2007in Information Systems Journal3.29
Balasubramaniam Ramesh29
Estimated H-index: 29
(GSU: Georgia State University),
Lan Cao16
Estimated H-index: 16
(ODU: Old Dominion University),
Richard Baskerville48
Estimated H-index: 48
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...
Published on Sep 1, 2006
Sotirios Liaskos16
Estimated H-index: 16
(U of T: University of Toronto),
Alexei Lapouchnian17
Estimated H-index: 17
(U of T: University of Toronto)
+ 2 AuthorsJ. Mylopolous74
Estimated H-index: 74
(U of T: University of Toronto)
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...
Cited By13
Newest
Damjan Vavpotič8
Estimated H-index: 8
(University of Ljubljana),
Marko Robnik-Šikonja14
Estimated H-index: 14
(University of Ljubljana),
Tomaž Hovelja4
Estimated H-index: 4
(University of Ljubljana)
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...
Woogon Shim1
Estimated H-index: 1
(LG Electronics),
Seok-Won Lee12
Estimated H-index: 12
(Ajou University)
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 frequen...
Published on Jun 1, 2018in Requirements Engineering2.76
Chi Mai Nguyen2
Estimated H-index: 2
(University of Trento),
Roberto Sebastiani37
Estimated H-index: 37
(University of Trento)
+ 1 AuthorsJ. Mylopolous74
Estimated H-index: 74
(University of Trento)
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...
Published on Jan 1, 2018in Information & Software Technology2.92
Shalinka Jayatilleke2
Estimated H-index: 2
(La Trobe University),
Richard Lai13
Estimated H-index: 13
(La Trobe University)
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...
Published on Sep 1, 2017
Woogon Shim1
Estimated H-index: 1
,
Seok-Won Lee12
Estimated H-index: 12
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...
Published on Oct 25, 2016in Journal of Logic and Computation0.51
Diana Costa2
Estimated H-index: 2
(University of Aveiro),
Manuel A. Martins9
Estimated H-index: 9
(University of Aveiro)
Published on Aug 1, 2016
Kaiss Elghariani1
Estimated H-index: 1
,
Nazri Kama6
Estimated H-index: 6
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...
Published on Oct 1, 2015in Computers in Human Behavior4.31
Irum Inayat7
Estimated H-index: 7
(Information Technology University),
Siti Salwah Salim11
Estimated H-index: 11
(Information Technology University)
+ 2 AuthorsShahaboddin Shamshirband34
Estimated H-index: 34
(IAU: Islamic Azad University)
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...
Published on Sep 7, 2015
Fabio Papalardo1
Estimated H-index: 1
,
Fábio Romeu de Carvalho1
Estimated H-index: 1
+ 1 AuthorsJayme de Aranha Machado
Competitiveness among enterprises, acting within global sustainability, has resorted to several types of administration in order to keep companies in the vanguard of the market. One of the most efficient types of administration is effective Planning, in such a way as to perform a task at the minimum time required and the lowest possible cost. Planning has become ever so complex, due to the innumerable demands from technology and market. A relevant aspect of Planning is that the sectors that infl...
Published on Jul 22, 2015in arXiv: Software Engineering
Ivan Jureta17
Estimated H-index: 17
Requirements Engineering (RE) focuses on eliciting, modelling, and analyzing the requirements and environment of a system-to-be in order to design its specification. The design of the specification, usually called the Requirements Problem (RP), is a complex problem solving task, as it involves, for each new system-to-be, the discovery and exploration of, and decision making in, new and ill-defined problem and solution spaces. The default RP in RE is to design a specification of the system-to-be ...
View next paperSoftware evolution: a requirements engineering approach