Information Technology Reference
In-Depth Information
33. Orr K (2004) Agile requirements: opportunity or oxymoron? Softw IEEE 21(3):71-73
34. Polanyi M (1966) The tacit dimension. Doubleday, Garden City, NY
35. Potts C, Takahashi K, Anton A (1994) Inquiry-based requirements analysis. Softw IEEE
11(2):21-32
36. Ramesh B, Jarke M (2001) Toward reference models for requirements traceability. IEEE Trans
Softw Eng 27(1):58-93
37. Robinson W (1989) Integrating multiple specifications using domain goals. ACM SIGSOFT
Softw Eng Notes 14(3):219-226
38. Robinson WN, Fickas S (1994) Automated support for requirements negotiation. AAAI-94
workshop on models of conflict management in cooperative problem solving, Menlo Park,
CA, USA, pp 90-96
39. Robinson WN, Fickas S (2009) Designs can talk: a case of feedback for design evolution
in assistive technology. In: Lyytinen KJ, Loucopoulos P, Mylopoulos J, Robinson W (eds)
Design requirements engineering: a ten-year perspective. Springer, Heidelberg, pp 215-237
40. Rolland C, Nurcan S, Grosz G (1997) A way of working for change processes. In: interna-
tional research symposium '97 - effective organisations, Dorset, ENG, UK, pp 201-204
41. Rolland C, Souveyet C, Achour CB (1998) Guiding goal modeling using scenarios. IEEE
Trans Softw Eng 24(12):1055-1071
42. Rolland C, Achour CB (1998) Guiding the construction of textual use case specifications.
Data Knowl Eng 25(1-2):125-160
43. Rolland C, Grosz G, Kla R (1999) Experience with goal-scenario coupling in require-
ments engineering. In: Proceedings of the IEEE international symposium on requirements
engineering (ISRE'99). IEEE Computer Society, Limerick, IRL
44. Rolland C (1999) Requirements engineering for COTS based systems. Inf Softw Tech
41(14):985-990
45. Rolland C, Salinesi C, Etien A (2004) Eliciting gaps in requirements change. Reqs Eng
9(1):1-15
46. Rolland C (2009) Exploring the fitness relationship between system functionality and business
needs. In: Lyytinen KJ, Loucopoulos P, Mylopoulos J, Robinson W (eds) Design requirements
engineering: a ten-year perspective. Springer, Heidelberg, pp. 305-326
47. Ross DT, Schoman KE Jr (1977) Structured analysis for requirements definition. IEEE Trans
Softw Eng 3(1):6-15
48. Sawyer S, Farber J, Spillers R (1996) Supporting the social processes of software develop-
ment. Inf Tech People 10(1):46-62
49. Sawyer S, Guinan PJ (1998) Software development: processes and performance. IBM Syst J
37(4):552-569
50. Senn JA (1978) A management view of systems analysts: failures and shortcomings. MIS Q
2(3):25-32
51. Siddiqi J, Shekaran MC (1996) Requirements engineering: the emerging wisdom. IEEE Softw
13(2):15-19
52. Sutcliffe AG, Maiden NAM, Minocha S et al (1998) Supporting scenario-based requirements
engineering. IEEE Trans Softw Eng 24(12):1072-1088
53. van Lamsweerde A, Darimont R, Letier E (1998) Managing conflicts in goal-driven require-
ments engineering. IEEE Trans Softw Eng 24(11):908-926
54. van Lamsweerde A (2000) Requirements engineering in the year 00: a research perspective.
In: Proceedings of the 22nd international conference on software engineering, Limerick, IRL
pp 5-19
55. Wiegers KE (1998) Read my lips: no new models! IEEE Softw 15(5):10-13
56. Woolgar S (1994) Rethinking requirements analysis: some implications of recent research
into producer-consumer relationships in IT development. In: Jirotka M, Goguen J (eds)
Requirements engineering: social and technical issues. Academic, London, pp 201-216
57. Yin RK (2003) Case study research: design and methods. Sage Publications Inc, Thousand
Oaks, CA
58. Zave P (1997) Classification of research efforts in requirements engineering. ACM Comp
Surv 29(4):315-321
Search WWH ::
Custom Search