Details
| Original language | English |
|---|---|
| Title of host publication | 2008 3rd International Workshop on Requirements Engineering Visualization, REV'08 |
| Publisher | IEEE Computer Society |
| Pages | 31-40 |
| Number of pages | 10 |
| ISBN (print) | 9780769536293 |
| Publication status | Published - 2008 |
| Event | 2008 3rd International Workshop on Requirements Engineering Visualization, REV'08 - Barcelona, Spain Duration: 8 Sept 2008 → 8 Sept 2008 |
Publication series
| Name | 2008 3rd International Workshop on Requirements Engineering Visualization, REV'08 |
|---|
Abstract
Requirements engineering heavily relies on oral and informal communication like meetings, phone calls, and e-mails. Some requirements are traditionally communicated outside formal documents in many companies. Considering document-based communication only is, therefore, not sufficient. Communication beyond documents should be taken into account when a company wants to improve its requirements engineering practices. We present a notation for visualizing the flow of requirements, explicitly including both informal and document-based communication. An example illustrates the notation by applying it to eliciting and validating security requirements. We compare our visualization approach for flows of requirements to related notations. The comparison shows how differences in notations affect the ability to model essential concepts of our approach. Explicitly modeling flows beyond documents provides new opportunities for requirement awareness, process improvement and innovation of tools and techniques.
ASJC Scopus subject areas
- Computer Science(all)
- Computer Science Applications
- Computer Science(all)
- Computer Vision and Pattern Recognition
- Computer Science(all)
- Software
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
2008 3rd International Workshop on Requirements Engineering Visualization, REV'08. IEEE Computer Society, 2008. p. 31-40 4797480 (2008 3rd International Workshop on Requirements Engineering Visualization, REV'08).
Research output: Chapter in book/report/conference proceeding › Conference contribution › Research › peer review
}
TY - GEN
T1 - Beyond documents
T2 - 2008 3rd International Workshop on Requirements Engineering Visualization, REV'08
AU - Schneider, Kurt
AU - Stapel, Kai
AU - Knauss, Eric
PY - 2008
Y1 - 2008
N2 - Requirements engineering heavily relies on oral and informal communication like meetings, phone calls, and e-mails. Some requirements are traditionally communicated outside formal documents in many companies. Considering document-based communication only is, therefore, not sufficient. Communication beyond documents should be taken into account when a company wants to improve its requirements engineering practices. We present a notation for visualizing the flow of requirements, explicitly including both informal and document-based communication. An example illustrates the notation by applying it to eliciting and validating security requirements. We compare our visualization approach for flows of requirements to related notations. The comparison shows how differences in notations affect the ability to model essential concepts of our approach. Explicitly modeling flows beyond documents provides new opportunities for requirement awareness, process improvement and innovation of tools and techniques.
AB - Requirements engineering heavily relies on oral and informal communication like meetings, phone calls, and e-mails. Some requirements are traditionally communicated outside formal documents in many companies. Considering document-based communication only is, therefore, not sufficient. Communication beyond documents should be taken into account when a company wants to improve its requirements engineering practices. We present a notation for visualizing the flow of requirements, explicitly including both informal and document-based communication. An example illustrates the notation by applying it to eliciting and validating security requirements. We compare our visualization approach for flows of requirements to related notations. The comparison shows how differences in notations affect the ability to model essential concepts of our approach. Explicitly modeling flows beyond documents provides new opportunities for requirement awareness, process improvement and innovation of tools and techniques.
UR - http://www.scopus.com/inward/record.url?scp=64849090022&partnerID=8YFLogxK
U2 - 10.1109/REV.2008.1
DO - 10.1109/REV.2008.1
M3 - Conference contribution
AN - SCOPUS:64849090022
SN - 9780769536293
T3 - 2008 3rd International Workshop on Requirements Engineering Visualization, REV'08
SP - 31
EP - 40
BT - 2008 3rd International Workshop on Requirements Engineering Visualization, REV'08
PB - IEEE Computer Society
Y2 - 8 September 2008 through 8 September 2008
ER -