Using soft systems methodology to improve requirements practices: an exploratory case study

Niu, Nan; Lopez, Alejandra Yepez; Cheng, Jing-Ru C.

doi:10.1049/iet-sen.2010.0096

Cited by 16 publications

(7 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In turn, Dey and Lee (2015) highlight that the technique helps identify the most relevant characteristics of a system. More over, , Shaw and Gaines (1996), Niu et al (2011), andJoseph (2017) say that the technique allows the detection of misunderstandings while helping to establish common points among stakeholders, avoiding com mon mistakes such as using different words to refer to the same idea and using the same word for different ideas. Ac cording to Davis et al (2006), some stakeholders may have difficulty expressing and articulating ideas, a situation in which RGT can be of great help.…”

Section: Why Use Rgt For Requirements Elicita Tion?mentioning

confidence: 99%

Repertory Grid Technique in a participatory design of games for older people

Fonseca

Duque

Silva

et al. 2022

JIS

View full text Add to dashboard Cite

With the aging society, there is an increasing need for services and software focused on older people. Digital games are one option of software to be provided as tools for entertainment, education, and well-being. However, to deliver these benefits, games must be developed according to the needs and preferences of older people. Seeking to improve the process of eliciting preferences from the target public, we applied Repertory Grid Technique (RGT) during the participatory design of a game. RGT is a cognitive interviewing technique based on Personal Construct Psychology, which has applications in different areas, including computer science. Although many articles discuss the application of RGT in the development of systems, we did not find, in the literature, any application of the technique with older people. We developed a game focusing on older people to understand better how such technique could contribute to game development, following action research methodology. We carried out three cycles of action research, all of which involved the use of RGT. The results indicate some benefits of using RGT instead of traditional semi-structured interviews. The main contribution of this work is to provide researchers with an initial understanding of the benefits of the application of the Repertory Grid Technique for the interviews with older people and how to use it during a participatory design.

show abstract

Section: Why Use Rgt For Requirements Elicita Tion?mentioning

confidence: 99%

Repertory Grid Technique in a participatory design of games for older people

Fonseca

Duque

Silva

et al. 2022

JIS

View full text Add to dashboard Cite

show abstract

“…Studies have shown that requirements defects cost 10-200 times more to correct once fielded than they would if they were detected during early architectural analysis stages [15], [24]. However, engineering an enterprise system's requirements is not without challenges.…”

Section: A Challenges Of Engineering Significant Requirementsmentioning

confidence: 99%

“…Despite the increasing number of proposals for designing enterprise systems, little is known about analyzing software architecture tradeoffs to tackle the dependencies, interactions, and interplays of architecturally significant requirements [14], [15]. Lack of this knowledge is a serious problem since systematic methods are not yet available for systems engineers to reason, analyze, and determine a suitable software infrastructure to parallel modern industrial automation.…”

mentioning

confidence: 99%

Analysis of Architecturally Significant Requirements for Enterprise Systems

Niu

Cheng

et al. 2014

IEEE Systems Journal

View full text Add to dashboard Cite

In designing and developing enterprise systems, systems engineers must consider the requirements that drive the important architecture decisions. Architecturally significant requirements tend to have a global impact on the underlying software infrastructure, and therefore need to be thoroughly examined. Despite the increasing effort in engineering enterprise systems' requirements, little is known about the analysis of architecture interactions and tradeoffs. In this paper, we propose a framework consisting of an integrated set of activities to help tackle requirements analysis in practice. Specifically, we leverage the quality attribute scenarios to elicit implicit yet significant requirements, to model requirements interplays, to manage terminological interferences, and to determine change impacts. We apply the proposed framework to a customer relationship management software system. The results show that the framework offers concrete insights and can be incorporated into an organization's systems practice with a moderate cost.

show abstract

“…This has resulted in a highly extended use of requirements engineering during the development of complex systems [NASA, 2007; INCOSE, ]. The recognition of importance of doing requirements correctly as an enabler to succeed in system development has initiated a continuous effort for improving and promoting requirements engineering [Hooks, ; Kaindl et al., ; Niu, Lopez, and Cheng, ; INCOSE, ], although its proper adoption does not seem to have arrived yet [Hooks, 2010; Fanmuy and Foughali, ] and failure in complex systems remains persistently [Bahill and Henderson, ; Schwenn, et al., ].…”

Section: Introductionmentioning

confidence: 99%

Adaptive Requirements Prioritization (ARP): Improving Decisions between Conflicting Requirements

Salado

Nilchiani

2015

Systems Engineering

View full text Add to dashboard Cite

Prioritization of requirements is a core activity of requirements engineering. Conventionally used to resolve conflicting requirements, it can be performed on a wide variety of attributes, reflecting, for example, stakeholder value, value to business, cost, connectivity, or risk. Its benefit in decision making is unquestionable, yet existing techniques are ineffective for realistic sets of requirements and consequently their adoption by practitioners is scarce, particularly in the fields of hardware‐intensive systems. The present research proposes an Adaptive Requirements Prioritization (ARP) method that improves decision making between conflicting requirements due to its principles of multidimensionality and objective‐base (the right criteria are used for any particular decision), and its usability due its principles of openness (it can be tailored according to specific project needs) and structure (requirements are grouped in subsets so that existing techniques become effective). The effectiveness of the proposed method is evaluated using Monte Carlo simulation for a variety of priority dimensions and priority levels.

show abstract

Using soft systems methodology to improve requirements practices: an exploratory case study

Cited by 16 publications

References 24 publications

Repertory Grid Technique in a participatory design of games for older people

Repertory Grid Technique in a participatory design of games for older people

Analysis of Architecturally Significant Requirements for Enterprise Systems

Adaptive Requirements Prioritization (ARP): Improving Decisions between Conflicting Requirements

Contact Info

Product

Resources

About