2015
DOI: 10.1016/j.infsof.2015.06.007
|View full text |Cite
|
Sign up to set email alerts
|

Requirements communication and balancing in large-scale software-intensive product development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

1
5
0
1

Year Published

2016
2016
2021
2021

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 17 publications
(9 citation statements)
references
References 38 publications
1
5
0
1
Order By: Relevance
“…Consequently, this study implies that BA must be a bridge between users and developers. This result also validates research on the methods to solve communication problems about project requirements [16,23] and the social relationship between users and analysts to identify early requirements [71].…”
Section: Resultssupporting
confidence: 74%
See 1 more Smart Citation
“…Consequently, this study implies that BA must be a bridge between users and developers. This result also validates research on the methods to solve communication problems about project requirements [16,23] and the social relationship between users and analysts to identify early requirements [71].…”
Section: Resultssupporting
confidence: 74%
“…It is a systematic and disciplined approach to identify, analyze, and specify requirements and it provides guidelines on requirements processes or techniques, such as elicitation, analysis, specification, and traceability [18][19][20][21][22]. Requirements engineering is useful for effective communication with stakeholders for project success [23,24] as ineffective communication on requirements may result in project failure [25].…”
Section: Introductionmentioning
confidence: 99%
“…Coordination modes were previously used to study work coordination in large‐scale software development, 47 and it was found that both scheduled and unscheduled meetings are important for coordination and that needs of work coordination change over time. Large‐scale software development projects have been traditionally associated with plan‐driven management and coordination by standardization 20,21 . However, empirical studies in large‐scale software development suggest that the success of standardization and modularization is limited 39 .…”
Section: Related Workmentioning
confidence: 99%
“…18,19 Finally, to address coordination challenges, software companies have tried to limit task interdependence with approaches such as centralization and modularization. 9 The centralization approach prescribes that certain functions such as communication with the customer, 3 system testing, or system integration 20,21 are centralized and moved out of development teams. However, this creates new dependencies and requires software teams to synchronize their work, including the exchange of feedback, with the supporting functions and roles.…”
mentioning
confidence: 99%
“…In software engineering, human factor has been recognized as critical for success, especially in SRE that is based on collaboration of different stakeholders (Pernstål et al, 2015). In this course of thinking, Andreou (2003) stated that rules and focus in collecting software requirements shift from the operations and the data to be processed by the system to human-computer interaction and organizational factors.…”
Section: Related Workmentioning
confidence: 99%