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

A model of requirements engineering in software startups

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
40
0
4

Year Published

2019
2019
2023
2023

Publication Types

Select...
5
3
1

Relationship

1
8

Authors

Journals

citations
Cited by 68 publications
(58 citation statements)
references
References 85 publications
1
40
0
4
Order By: Relevance
“…The underlying idea is that during the requirement elicitation phase, the purpose is to describe the full context of a need or a problem to be solved, such as its application domain, business context, stakeholders' expectations and constraints [21]. In change-driven ISD, the backlog in Scrum (and lean portfolio management with epics and programs in SAFe) are used for the same purpose [25].…”
Section: The Role Methods and Practices Of Requirements Engineering mentioning
confidence: 99%
See 1 more Smart Citation
“…The underlying idea is that during the requirement elicitation phase, the purpose is to describe the full context of a need or a problem to be solved, such as its application domain, business context, stakeholders' expectations and constraints [21]. In change-driven ISD, the backlog in Scrum (and lean portfolio management with epics and programs in SAFe) are used for the same purpose [25].…”
Section: The Role Methods and Practices Of Requirements Engineering mentioning
confidence: 99%
“…In a project, requirements are elicited at the beginning of the project. All methods do so whether waterfall or agile [25]. Waterfall methods conduct RE at the beginning of a project, and re-plan the project, should requirements change.…”
Section: Theoretical Backgroundmentioning
confidence: 99%
“…Up to now, although a broad literature on the topic are being raised in the last years [ 3 ], there are no scientific studies proposing specific practices for these companies. Academic authors focused on describing the context including currently used practices (e.g., [ 8 , 11 , 12 ]) and faced challenges (e.g., [ 11 , 14 ]).…”
Section: Current Proposals and Future Directionsmentioning
confidence: 99%
“…In this case, the defining process is considered as a key to determining specific solutions to stakeholders' problems. According Nuseibeh and Easterbrook as cited by Melegati, define requierement or information system needs as the process of discovering the purpose that a piece of software intended by identifying the stake holders and their needs, documenting the discoveries for future analysis, communication and implementation [14][15].…”
Section: Software Engineeringmentioning
confidence: 99%