Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
12
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
7
1
1

Relationship

0
9

Authors

Journals

citations
Cited by 22 publications
(12 citation statements)
references
References 25 publications
0
12
0
Order By: Relevance
“…Although there are several techniques to involve stakeholders in prioritizing software requirements (such as [16] and [17]), it is still hard to involve them in the decision-making of software architectures. Schulenklopper et al [5] attribute this gap to the communication problems between architects and stakeholders.…”
Section: Problem Statementmentioning
confidence: 99%
“…Although there are several techniques to involve stakeholders in prioritizing software requirements (such as [16] and [17]), it is still hard to involve them in the decision-making of software architectures. Schulenklopper et al [5] attribute this gap to the communication problems between architects and stakeholders.…”
Section: Problem Statementmentioning
confidence: 99%
“…Hence, multiple perspectives based on business, customer and technical prioritisation algorithm provided in [29 ], for solution‐oriented application requirements. Similarly, some other researchers have also presented prioritisation techniques to resolve issues by appropriate selection, specification, cost‐effective and decision‐making processes to reduce failure in systems after implementations [30–35 ].…”
Section: Related Workmentioning
confidence: 99%
“…Open interfaces are desirable, as they allow for easier extensibility and integration [30]. Likewise, the number of stakeholders may become too large to manage completely [9]. This presents challenges in the case of requirements elicitation.…”
Section: Introductionmentioning
confidence: 99%
“…The person (or company) making requirements to software products are called 'stakeholders', and without identifying a representative group of stakeholders before the requirements elicitation process, the software is likely developed with an incomplete view of the stakeholder needs, which in turn leads to poor adoption or a delayed timeline to compensate for late requirements [1] [23]. These factors are both very expensive, and harmful to the reputation of the software company [9] [1] [19]. Furthermore, requirements elicitation and stakeholder identification is iterative and repetitive process [15] [2].…”
Section: Introductionmentioning
confidence: 99%