An objectives-driven process for selecting methods to support requirements engineering activities

Proceedings of the 2005 29th Annual IEEE/NASA Software Engineering Workshop, SEW'05

Volumn 2005, Issue , 2005, Pages 118-127

  Lobo, Lester O ^a   Arthur, James D ^a  

^a Virginia Polytechnic Institute and State University   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

DECISION SUPPORT SYSTEMS; INFORMATION ANALYSIS; MATHEMATICAL MODELS; OPTIMIZATION; PROCESS CONTROL;

ENGINEERING ACTIVITIES; OBJECTIVES-DRIVEN PROCESS;

SOFTWARE ENGINEERING;

EID: 33646914497     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/SEW.2005.18     Document Type: Conference Paper

References (17)

1. Standish Group, "Extreme CHAOS", Found at www.standishgroup. com, 2001
2. Kasser, J.E., Williams, V.R., "What Do You Mean You Can't Tell Me if My Project is in Trouble?" First European Conference on Software Metrics (FESMA 98), Antwerp, Belgium, 1998.
3. Boehm, B.W., Bose, P., Horowitz, E., Lee, M.J. "Software Requirements As Negotiated Win Conditions", Proceedings of ICRE, April 1994, pp.74-83.
4. Alan Davis, "The Art of Requirements Triage", IEEE Computer, March 2003, pp. 42-48.
5. Patrick H. Loy, "A Comparison of Object-Oriented and Structured Development Methods", Pacific Northwest Software Quality Conference, 1989.
6. Alan Davis, "Elicitation Technique. Selection: How Do Experts Do IT?", Proceedings of the 11th IEEE International Requirements Engineering Conference, IEEE Computer, 2003.
7. Arthur, J.D. and Markus K. Groener, 1999, "An Operational Model Supporting the Generation of Requirements that Capture Customer Intent", Proceedings of the Pacific Northwest Software Quality Conference, Portland OR, October 1999, pp. 286-302.
8. Walter Hursh and Christina Lopes, "Separation of Concerns" (Technical Report), College of Computer Science, Northeaster University, 1995.
9. Greenspan, S., Mylopoulos, J., and Borgida, A., "On formal requirements modeling languages: RML revisited', In Proceedings of IEEE International Conference on Software Engineering (ICSE16), 1994.
10. Michael Palmer, "Problem-Solving Negotiation: What's In It for You and Your Clients" In 26 Oct. Vermont B. Journal 1, 2000
11. Alan Davis, R. Fairley, E. Yourdon, "Software Product Planning", Omni-Vista White Paper #99-002, 1999.
12. SEI Software Risk Taxonomy, Technical Report CMU/SEI-96-TR-012, June 1996.
13. Lester Lobo, "Analysis and Evaluation of Methods for Activities in the expanded Requirements Genertion Model (xRGM)" (Masters thesis), Computer Science department, Virginia Tech, 2004.
14. Garcia Alcazar, E.; Monzon, A.; "A process framework for requirements analysis and specification", Requirements Engineering, 2000. Proceedings. 4th International Conference on, 19-23 June 2000 Page(s): 27-35
15. Boehm, B.W., Bose, P., Horowitz, E., Lee, M.J. "Software Requirements As Negotiated Win Conditions", Proceedings of ICRE, April 1994, pp.74-1983.
16. Military Standard, "Procedures for Performing a Failure Mode, Effects and Criticality Analysis", MIL-STD-1629A, 12 June 1977.
17. H.M.N. Raafat, "Risk Assessment and Machinery Safety", Journal of Occupational Accidents, pp. 37-50, 1989.