Selecting among alternatives using dependencies

Mehta, R. Vasanth Kumar; Ruiz-López, Tomás; Chung, Lawrence; Noguera, Manuel

doi:10.1145/2480362.2480603

Cited by 4 publications

(2 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…• Personal Construct Theory [50] • Architecturedriven requirements prioritization [51] • NFR prioritization algorithm [52] • NFRs conflicts catalogue [53] • NFR dependency classification [54] • NFR conflicts analysis [55] • Constraint hierarchy tradeoff [56] In goal-oriented prioritization approach, conflict analysis [38][39][40][41][42][43], business rules [44], user satisfaction priority lists [45,46] based techniques are proposed to deal with NFRs interdependencies towards trade-off and prioritization. Techniques are also proposed to make automatic trade-off decision [47,48] among NFRs alternatives based on their relative interdependencies.…”

Section: Goal-orientedmentioning

confidence: 99%

“…In aspect-oriented solution design, several approaches are proposed to provide required information about NFRs and its correlation [49][50][51], user satisfaction [52] to the process of trade-off analysis and requirements prioritization. In pattern-based approach, catalogue of potential NFRs conflicts [53], classification of NFRs dependencies [54], conflicts identification from prior experience [55], quality constraint hierarchy [56] are proposed to aid conflict analysis in the selection among alternatives.…”

Section: Goal-orientedmentioning

confidence: 99%

See 1 more Smart Citation

Classification and Qualitative Analysis of Non-Functional Requirements Approaches

Hasan

Loucopoulos

Νικολαϊδου

2014

Enterprise, Business-Process and Information Systems Modeling

View full text Add to dashboard Cite

LNBIP reports state-of-the-art results in areas related to business information systems and industrial application software development -timely, at a high level, and in both printed and electronic form. The type of material published includes• Proceedings (published in time for the respective event)• Postproceedings (consisting of thoroughly revised and/or extended final papers) • Other edited monographs (such as, for example, project reports or invited volumes) • Tutorials (coherently integrated collections of lectures given at advanced courses, seminars, schools, etc.) • Award-winning or exceptional theses LNBIP is abstracted/indexed in DBLP, EI and Scopus. LNBIP volumes are also submitted for the inclusion in ISI Proceedings.

show abstract

Section: Goal-orientedmentioning

confidence: 99%

Section: Goal-orientedmentioning

confidence: 99%

Classification and Qualitative Analysis of Non-Functional Requirements Approaches

Hasan

Loucopoulos

Νικολαϊδου

2014

Enterprise, Business-Process and Information Systems Modeling

View full text Add to dashboard Cite

show abstract

Framework for examination of software quality characteristics in conflict: A security and usability exemplar

2020

View full text Add to dashboard Cite

Standards and best practices for software quality guide on handling each quality characteristic individually, but not when two or more characteristics come into conflict such as security and usability. The objectives of this paper are twofold: (a) to argue on the importance of handling the conflicts between quality characteristics in general; (b) to formulate a framework for conflict examination of the software quality characteristics, we do so while considering the specific case of security and usability. In line with the objectives, a framework called Patternoriented Design Framework (PoDF) was formulated. The PoDF provides a mechanism for identification of the conflicts, modeling the conflicts to illuminate the reason for their occurrence, and eliciting the suitable trade-offs between the conflicting characteristics. The suitable trade-offs are thus documented as design patterns. The patterns can assist developers and designers in handling the conflicts in other but similar context of use. To validate and instantiate the PoDF, two studies were conducted. Usable security patterns discovered as a result of the studies are also presented in the paper.

show abstract

A retrospective analysis of SAC requirements

Vilela

Gonçalves

Holanda

et al. 2016

SIGAPP Appl. Comput. Rev.

View full text Add to dashboard Cite

Context: The activities related to Requirements engineering (RE) are some of the most important steps in software development, since the requirements describe what will be provided in a software system in order to fulfill the stakeholders' needs. In this context, the ACM Symposium on Applied Computing (SAC) has been a primary gathering forum for many RE activities. When studying a research area, it is important to identify the most active groups, topics, the research trends and so forth. Objective: In a previous paper, we investigated how the SAC RE-Track is evolving, by analyzing the papers published in its 8 previous editions. In this paper, we extended the analysis including the papers of the last edition (2016) and a brief resume of all papers published in the nine editions of SAC-RE track. Method: We adopted a research strategy that combines scoping study and systematic review good practices. Results: We investigated the most active countries, institutions and authors, the main topics discussed, the types of the contributions, the conferences and journals that have most referenced SAC RE-Track papers, the phases of the RE process supported by the contributions, the publications with the greatest impact, and the trends in RE. Conclusions: We found 86 papers over the 9 previous SAC RETrack editions, which were analyzed and discussed.

show abstract

Selecting among alternatives using dependencies

Cited by 4 publications

References 9 publications

Classification and Qualitative Analysis of Non-Functional Requirements Approaches

Classification and Qualitative Analysis of Non-Functional Requirements Approaches

Framework for examination of software quality characteristics in conflict: A security and usability exemplar

A retrospective analysis of SAC requirements

Contact Info

Product

Resources

About