loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
13th IEEE International Requirements Engineering Conference (RE'05)
Modelling Assumptions and Requirements in the Context of Project Risk
Paris, France
August 29-September 02
ISBN: 0-7695-2425-7
ASCII Text
x 
 
Andriy Miranskyy, Nazim Madhavji, Matt Davison, Mark Reesor, "Modelling Assumptions and Requirements in the Context of Project Risk," Requirements Engineering, IEEE International Conference on, pp. 471-472, 13th IEEE International Requirements Engineering Conference (RE'05), 2005.
 
 
BibTex
x
 
@article{ 10.1109/RE.2005.44,
author = {Andriy Miranskyy and Nazim Madhavji and Matt Davison and Mark Reesor},
title = {Modelling Assumptions and Requirements in the Context of Project Risk},
journal ={Requirements Engineering, IEEE International Conference on},
volume = {0},
year = {2005},
isbn = {0-7695-2425-7},
pages = {471-472},
doi = {http://doi.ieeecomputersociety.org/10.1109/RE.2005.44},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - Requirements Engineering, IEEE International Conference on
TI - Modelling Assumptions and Requirements in the Context of Project Risk
SN - 0-7695-2425-7
SP471
EP472
A1 - Andriy Miranskyy,
A1 - Nazim Madhavji,
A1 - Matt Davison,
A1 - Mark Reesor,
PY - 2005
KW - null
VL - 0
JA - Requirements Engineering, IEEE International Conference on
ER -
 
Andriy Miranskyy, Department of Applied Mathematics, University of Western Ontario
Nazim Madhavji, Department of Computer Science, University of Western Ontario
Matt Davison, Department of Applied Mathematics, University of Western Ontario
Mark Reesor, Department of Applied Mathematics, University of Western Ontario

Many researchers have emphasized the importance of documenting assumptions (As) underlying software requirements (Rs) [2]. However, As and Rs can change with time for reasons such as: (i) an A or R was elicited incorrectly and subsequently needs to be changed; (ii) operational domain changes induce changes in the A and R sets; and (iii) the change in validity of an A, or desirability of an R, respectively, causes the validity of another A or desirability of an R to change.

Citation:
Andriy Miranskyy, Nazim Madhavji, Matt Davison, Mark Reesor, "Modelling Assumptions and Requirements in the Context of Project Risk," re, pp.471-472, 13th IEEE International Requirements Engineering Conference (RE'05), 2005
Usage of this product signifies your acceptance of the Terms of Use.