loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Using Viewpoints to Define Domain Requirements
January/February 1998 (vol. 15 no. 1)
pp. 95-102
ASCII Text
x 
 
Mike Mannion, Barry Keepence, David Harper, "Using Viewpoints to Define Domain Requirements," IEEE Software, vol. 15, no. 1, pp. 95-102, January/February, 1998.
 
 
BibTex
x
 
@article{ 10.1109/52.646889,
author = {Mike Mannion and Barry Keepence and David Harper},
title = {Using Viewpoints to Define Domain Requirements},
journal ={IEEE Software},
volume = {15},
number = {1},
issn = {0740-7459},
year = {1998},
pages = {95-102},
doi = {http://doi.ieeecomputersociety.org/10.1109/52.646889},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Using Viewpoints to Define Domain Requirements
IS - 1
SN - 0740-7459
SP95
EP102
EPD - 95-102
A1 - Mike Mannion,
A1 - Barry Keepence,
A1 - David Harper,
PY - 1998
VL - 15
JA - IEEE Software
ER -
 
Although requirement s reuse has many potential benefits, a lack of accepted methodology for sorting through a domain's myriad requirement specifications makes the task daunting. The authors' VODRD method relies on stakeholder viewpoint s to organize user requirement s . Here, they describe their method and its application in a mission planning system for the European Space Agency.
Citation:
Mike Mannion, Barry Keepence, David Harper, "Using Viewpoints to Define Domain Requirements," IEEE Software, vol. 15, no. 1, pp. 95-102, Jan./Feb. 1998, doi:10.1109/52.646889
Usage of this product signifies your acceptance of the Terms of Use.