Identifying Stakeholders and Their Preferences about NFR by Comparing Use Case Diagrams of Several Existing Systems

Kaiya, Haruhiko; Osada, Akira; Kaijiri, Kenji

doi:10.1093/ietisy/e91-d.4.897

Cited by 9 publications

(7 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [6], such similarity is identified based on the structure of a use case diagram for each system. Because a use case diagram specifies the context of the system as well as externally observable functions of the system, such context and functions are main information for identifying system similarity.…”

Section: Requirements Specification and Similar Systemsmentioning

confidence: 99%

Improving Reliability of Spectrum Analysis for Software Quality Requirements Using TCM

Kaiya

Tanigawa

Suzuki

et al. 2010

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYQuality requirements are scattered over a requirements specification, thus it is hard to measure and trace such quality requirements to validate the specification against stakeholders' needs. We proposed a technique called "spectrum analysis for quality requirements" which enabled analysts to sort a requirements specification to measure and track quality requirements in the specification. In the same way as a spectrum in optics, a quality spectrum of a specification shows a quantitative feature of the specification with respect to quality. Therefore, we can compare a specification of a system to another one with respect to quality. As a result, we can validate such a specification because we can check whether the specification has common quality features and know its specific features against specifications of existing similar systems. However, our first spectrum analysis for quality requirements required a lot of effort and knowledge of a problem domain and it was hard to reuse such knowledge to reduce the effort. We thus introduce domain knowledge called term-characteristic map (TCM) to reuse the knowledge for our quality spectrum analysis. Through several experiments, we evaluate our spectrum analysis, and main finding are as follows. First, we confirmed specifications of similar systems have similar quality spectra. Second, results of spectrum analysis using TCM are objective, i.e., different analysts can generate almost the same spectra when they analyze the same specification.

show abstract

Section: Requirements Specification and Similar Systemsmentioning

confidence: 99%

Improving Reliability of Spectrum Analysis for Software Quality Requirements Using TCM

Kaiya

Tanigawa

Suzuki

et al. 2010

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

show abstract

“…An elicitation method where functional use-cases are created and associated QRs are identified by the use of a checklist is proposed by Doerr et al in [13]. A similar approach is proposed by Kaiya et al [14] but they use the goal-question-metric (GQM) model to explore quality requirements and their interdependencies.…”

Section: Related Workmentioning

confidence: 99%

The effect of stakeholder inertia on product line requirements

Wnuk

Svensson

Callele³

2012

2012 Second IEEE International Workshop on Requirements Engineering for Systems, Services, and Systems-of-Systems (RESS)

View full text Add to dashboard Cite

One of the goals of requirements engineering is to capture and document innovation in the form of new product requirements. These product requirements need to express new system functions or new qualities that are most desired by customers while maintaining customer familiarity with existing products. This paper explores the contradiction between the customer desire for revolutionary advancement and their desire to maintain familiarity with existing systems. This customer inertia creates a bias toward incremental (evolutionary) advancement, potentially multiplying the risks associated with revolutionary innovations. We present a review of scenarios illustrating this stakeholder bias and propose a research agenda for further work in the area.

show abstract

“…Some of the prominent GORE methods include: Keep All Objectives Satisfied (KAOS) method [13], Tropos [14], NFR framework [2,15]. Our GORE method retains the generic features of other techniques in extracting hard and soft goals, decomposing the goals and refining them.…”

Section: Identifying Soft Goals and Contribution Links Using Gore Metmentioning

confidence: 99%

Integrating TOPSIS and AHP into GORE Decision Support System

Vinay¹,

Aithal²,

Sudhakara³

2012

IJCA

View full text Add to dashboard Cite

Decision making in Software Engineering plays an important role at different stages of Software development life cycle. In this paper we consider the case study of selecting one among the three Content Management Systems (CMS) for a university website. We use our Goal-Oriented Requirements Engineering (GORE) method to identify the soft goals which play a vital role in deciding which CMS is chosen. Analytic Hierarchy Process (AHP) is then used to prioritize the soft goals. The output of AHP is used as input to Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS) which produces a metric which decides the best alternative among the candidates.

show abstract

Identifying Stakeholders and Their Preferences about NFR by Comparing Use Case Diagrams of Several Existing Systems

Cited by 9 publications

References 12 publications

Improving Reliability of Spectrum Analysis for Software Quality Requirements Using TCM

Improving Reliability of Spectrum Analysis for Software Quality Requirements Using TCM

The effect of stakeholder inertia on product line requirements

Integrating TOPSIS and AHP into GORE Decision Support System

Contact Info

Product

Resources

About