Requirements Engineering 2000
DOI: 10.1007/978-3-663-07965-1_3
|View full text |Cite
|
Sign up to set email alerts
|

Requirements Engineering in the Software Process

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2003
2003
2023
2023

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(2 citation statements)
references
References 0 publications
0
2
0
Order By: Relevance
“…Business consultants and project managers are two examples of types of stakeholder who are of particular interest to the RE process, as their remit requires strong communication skills [24].…”
Section: Stakeholder Participation and Selectionmentioning
confidence: 99%
“…Business consultants and project managers are two examples of types of stakeholder who are of particular interest to the RE process, as their remit requires strong communication skills [24].…”
Section: Stakeholder Participation and Selectionmentioning
confidence: 99%
“…Requirements are the source of product development's design, implementation, and validation phases. Compiling requirements by systematically studying, analyzing, and refining users' needs is called requirements engineering (RE) (Hofmann 2013). The main result of RE is called system specification, which is a brief statement of the requirements that the system must meet to fulfil a contract or standard (IEEE 1996).…”
Section: Introductionmentioning
confidence: 99%