Managing requirements uncertainty with partial models

Salay, Rick; Chećhik, Marsha; Horkoff, Jennifer; Sandro, Alessio Di

doi:10.1007/s00766-013-0170-y

Cited by 47 publications

(20 citation statements)

References 51 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Similar to work described by Salay, R., Chechik, M., & Horkoff, J. [12], we would transform the dependency link to a contribution link in the opposite direction. So, if A is dependent on B for its satisfaction, we say that B makes A.…”

Section: Means-end Linkmentioning

confidence: 76%

“…The Tropos methodology has been formalized by Paolo Giorgini, John Mylopoulos, Eleonora Nicchiarelli and Roberto Sebastiani [11], where axiomitization has been done for all the rules. The uncertainties and incompletenesses in partial goal models have been handled so that they are not passed off to design and implementation phases [12]. There are other approaches like constraints [13] or mixed [14] or metrics based approaches [15] [16].…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Evaluation of web-specific goal oriented requirements language models with quantitative reasoning

Chawla

Srivastava

Bedi

2014

SIGSOFT Softw. Eng. Notes

View full text Add to dashboard Cite

In this paper, we propose to evaluate Web-specific Goal Driven Models to choose amongst various design alternatives, deal with conflicts, check completeness and reaffirm the sanity of the model. The work is based on Web specific User Requirements Notation (WebURN), which is an enhancement of a goal and scenario based standard, User Requirements Notation (URN). We present the forward reasoning approach for finding the satisfaction level of the root/parent goals from the sub-goals in the goal model. The Quantitative Reasoning method called Forward Reasoning and Evaluation: Numeric (FREN) is apt when enough domain knowledge is there and precise results are expected. We propose a Quantitative Reasoning and Evaluation approach in this paper wherein the requirements engineer has an estimate of the satisfaction level of tasks and knows the priorities of various goals and sub-goals. The rules for propagation of satisfaction values from the leaves to the root level goals are specified in detail. The approach is then applied to the Webspecific Goal driven Requirements models for evaluation. The methodology has been implemented in the WebURN tool, built upon Microsoft Visio for editing and analyzing the WebURN diagrams. The results of evaluations are also compared with other prominent approaches in the area of Goal oriented Requirements Engineering. The methodology used for evaluation enables choice amongst design alternatives, resolves conflicts automatically and incorporates the role of priority in making design decisions.

show abstract

Section: Means-end Linkmentioning

confidence: 76%

Section: Related Workmentioning

confidence: 99%

Evaluation of web-specific goal oriented requirements language models with quantitative reasoning

Chawla

Srivastava

Bedi

2014

SIGSOFT Softw. Eng. Notes

View full text Add to dashboard Cite

show abstract

“…A symbolic model checker χ chek is also implemented to support multi-valued model checking [5]. Salay et al propose an approach for expressing unknown information using partial models [21] and apply it to management of requirements uncertainty in [20]. But they have not been directly applied to model checking software product lines.…”

Section: Related Workmentioning

confidence: 98%

“…In this paper, we consider model checking software product lines with uncertainty, i.e., the incomplete design models in the early stage of software product line development, where the design decisions for a feature may be unknown. By conducting verification on early design models, it allows for detecting errors, particularly the ones associated with different features, earlier in the development life cycle, and thus reduces the cost of fixing the problems; the model checking results also help to resolve design uncertainties that influence later implementation choices of the systems [20].…”

Section: Introductionmentioning

confidence: 99%

Model checking partial software product line designs

Shi

Zhou

2014

Proceedings of the International Workshop on Innovative Software Development Methodologies and Practices

View full text Add to dashboard Cite

Software product line (SPL) maximizes commonality between software products to reduce cost and improve productivity, where each product is represented by a selection of features that corresponds to particular customer requirements. SPL has been widely applied in critical systems such as communications, automobile, and aerospace, and ensuring correctness of the system is thus of great importance. In this paper, we consider model checking partial software product line designs, i.e., the incomplete designs in the early stage of software development, where the design decisions for a feature may be unknown. This enables detecting design errors earlier, reducing the cost of later development of final products. To this end, we first propose bilatticebased feature transitions systems (BFTSs) for modeling partial software product line designs, which support description of uncertainty and preserve features as a first class notion. We then express system behavioral properties using ACTL formulas and define its semantics over BFTSs. Finally, to leverage the power of existing model checking engine for verification, we provide the procedures that translate BFTSs and ACTL formulas to the inputs of the symbolic model checker χ Chek. We implement our approach and illustrate its effectiveness on a benchmark from literature.

show abstract

“…In [9], partial models are introduced in order to let the designer specify uncertain information by means of a base model enriched with annotations and first-order logic. In [17] a formal approach called MAVO is proposed and applied to design models in order to express and allow automated reasoning in presence of uncertainty. Model transformation techniques typically operate under the assumption that models do not contain uncertainty.…”

Section: Related Workmentioning

confidence: 99%

Uncertainty in bidirectional transformations

Eramo

Pierantonio

Rosa

2014

Proceedings of the 6th International Workshop on Modeling in Software Engineering

View full text Add to dashboard Cite

In Model-Driven Engineering, models are primary artifact manipulated by means of automated transformations. Recently, a notion of uncertainty has been introduced in models permitting modelers to postpone design decisions in case of lack of information. Interestingly, other forms of model uncertainty are induced by bidirectional transformations. In fact, in certain situations more than one admissible solution is in principle possible, despite most of the current languages generate only one model at time, possibly not the desired one.In this paper, the uncertainty due to the solution multiplicity in bidirectional transformations is discussed. In particular, we propose to represent the models in the solution space as concretizations of an uncertain model because there are cases where the responsibility of identifying the solution must be left to the modeler. The problem is illustrated by a round-tripping scenario realized with the JTL transformation language.

show abstract

Managing requirements uncertainty with partial models

Cited by 47 publications

References 51 publications

Evaluation of web-specific goal oriented requirements language models with quantitative reasoning

Evaluation of web-specific goal oriented requirements language models with quantitative reasoning

Model checking partial software product line designs

Uncertainty in bidirectional transformations

Contact Info

Product

Resources

About