Eight key issues for an effective reuse-based requirements process

Computer Systems Science and Engineering

Volumn 23, Issue 6, 2008, Pages 373-385

  Toval, Ambrosio ^a   Moros, Begoña ^a   Nicolás, Joaquín ^a   Lasheras, Joaquín ^a  

^a Campus de Espinardo   (Spain)

Author keywords

Computer Aided Requirements Engineering (CARE); Requirements engineering; Requirements reuse

Indexed keywords

COMPUTER AIDED ANALYSIS; COMPUTER SOFTWARE REUSABILITY; ENGINEERING; INDUSTRIAL MANAGEMENT;

AUTOMATED SUPPORTS; QUALITY OF SOFTWARES; REQUIREMENTS PROCESS; REQUIREMENTS REUSE; TECHNICAL SOLUTIONS;

REQUIREMENTS ENGINEERING;

EID: 62349097120     PISSN: 02676192     EISSN: None     Source Type: Journal    
DOI: None     Document Type: Article

References (47)

1. Alexander, I. (2003). Requirements Engineering Tool Vendors and Freeware Suppliers, http://easyweb.easynet.co.uk/~iany/other/vendors.htm
2. Alexander, I. and F. Kiedaisch (2002). Towards Recyclable System Requirements. Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems (ECBS'02), Lund, Sweden
3. Caliber-RM (2005). http://www.borland.com/us/products/caliber/index.html, Borland.
4. Cybulsky, J. and K. Reed (2000). Requirements Classification and Reuse: Crossing Domains Boundaries. 6th International Conference on Software Reuse (ICSR'2000), Viena, Springer, Lecture Notes in Computer Science
5. Doors (2003). http://www.telelogic.com/doors, Quality Systems & Software.
6. EU ( 1995). Directive 95/46/CE of the European Parliament and Council, dated October 24th, on people protection regarding personal data management and the free circulation of these data. DOCE no. L281, 23/11/1995,
7. Favaro, J. (2002). "Managing Requirements for Business Value." IEEE Software 9(2): 15-17
8. Firesmith, D. (2003). "Modern Requirements Specification." Journal of Object Technology 2(2): 53-64. http://www.jot.fm/issues/issue- 2003-03/column6
9. Firesmith, D. G. (2004). "Specifying Reusable Security Requirements." Journal of Object Technology 3(1): 61-75
10. Fowler, M. (1997). Analysis Patterns-Reusable Objects Models, Addison Wesley.
11. Gamma, E., R. Helm, et al. (1995). Design Patterns: Elements of Reusable Object-Oriented Software Addison-Wesley Professional Computing Series.
12. Glass, R. L. (1998). Software Runaways: Monumental Disasters, Prentice Hall.
13. Glass, R. L. (2002). Software Engineering: Facts and Fallacies, Addison-Wesley.
14. IEEE (1999a). Std 830-1998 Guide to Software Requirements Specifications (ANSI). Volume 4: Resource and Technique Standards, The Institute of Electrical and Electronics Engineers, Inc. IEEE Software Engineering Standards Collection.
15. IEEE (1999b). Std 1233-1998 Guide for Developing System Requirements Specifications. Volume 1: Customer and Terminology Standards, The Institute of Electrical and Electronics Engineers, Inc. IEEE Software Engineering Standards Collection.
16. INCOSE (2006). Requirements Management Tools Survey. International Council on Systems Engineering, http://www.incose.org/ProductsPubs/products/ toolsdatabase.aspx
17. Kaindl, H., S. Brinkkemper, et al. (2002). "Requirements Engineering and Technology Transfer: Obstacles, Incentives and Improvement Agenda." Requirements Engineering 7(3): 113-123
18. Kang, K., S. Cohen, et al. (1990). "A. Feature-Oriented Domain Analysis (FODA) Feasibility Study (CMU/SEI-90-TR-021, ADA235785)." Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University
19. Kang, K., S. Kim, et al. (1998). "FORM: A Feature-Oriented Reuse Method with Domain-Specific Reference Architectures." Annals of Software Engineering 5(5): 143-168.
20. Knethen, A. v., B. Paech, et al. (2002). Systematic Requirements Recycling throug Abstraction and Traceability. IEEE Joint International Conference on Requirements Engineering (RE'02), University of Essen. Germany
21. Konrad, S. and B. H. C. Cheng (2002). Requirements Patterns for Embedded Systems. IEEE Joint International Conference on Requirements Engineering (RE'02), University of Essen. Germany
22. Kotonya, G. and I. Sommerville (1998). Requirements Engineering. Processes and Techniques, John Wiley & Sons.
23. Lam, W., J. A. MacDermid, et al. (1997). Ten StepsTowards Systematic Requirements Reuse. 3rd IEEE International Symposium on Requirements Engineering (RE'97), Annapolis, MD
24. Maiden, N. A. and A. G. Sutcliffe (1996). "Analogical Retrieval in reuse-oriented requirements engineering." Software Engineering Journal 11(5): 281-292
25. Martinez, M. A., J. Lasheras, et al. (2006). An audit Method of Personal Data based on Requirements Engineering. IV International Workshop on Security In Information Systems (WOSIS 2006), Chipre
26. Matulevicius, R. (2005). Process Support for Requirements Engineering. A Requirements Engineering Tool Evaluation Approach. Department of Computer and Information Science. Faculty of Information Technology, Mathematics and Electrical Engineering. Trondheim, Norwegian University of Science and Technology.
27. Mili, H., F. Mili, et al.(1995). "Reusing Software: Issues and Research Directions." IEEE Transactions on Software Engineering 21(6): 528-562
28. Neill, C. J. and P. Laplante (2003). "Requirements Engineering: The State of the Practice." IEEE Software. 2003 20(6)
29. Nicolás, J., J. Lasheras, et al. (2006). A Collaborative Learning Experience in Modelling the Requirements of Teleoperated Systems for Ship Hull Maintenance. Learning Software Organizations + Requirements Engineering (LSO+RE 2006), Hannover. Germany
30. Pantoquilho, M., R. Raminhos, et al. (2003). Analysis Patterns Specifications: Filling the Gaps. The Second Nordic Conference on Pattern Languages of Programs, ViKingPLoP 2003, Bergen. Norway
31. Pisan, Y. (2000). Extending Requirements Specifications Using Analogy. ICSE 2000, Limerick, Ireland
32. Prieto-Díaz, R. (1993). "Status Report: Software Reusability." IEEE Software 10(3): 61-66
33. Ramesh, B. and M. Jarke (2001). "Toward Reference Models for Requirements Traceability." IEEE Transactions on Software Engineering 27(1): 58-93
34. Reifer, D. J. (2003). "Is the Software Engineering State of the Practice Getting Closer to the State of the Art?." IEEE Software 2003. 20(6)
35. RequisitePro®I. R. (2006). http://www-306.ibm.com/software/awdtools/ reqpro/, Rational Software.
36. Rine, D. C. and N. Nada (2000). "An empirical study of a software reuse reference model." Information and Software Technology 42(1): 47-65
37. Robertson, S. (1996). "Requirements Patterns via Events/Use Cases." http://www.systemsguild.com/GuildSite/SQR/RequirementsPatterns.html
38. Robertson, S. and J. Robertson (2006). Mastering the Requirements Process (2nd edition), Addison-Wesley.
39. Rothenberger, M. A., K. J. Dooley, et al. (2003). "Strategies for Software Reuse: A Principal Component Analysis of Reuse Practices." IEEE Trans. on Soft. Eng. 29(9): 825-837
40. Sindre, G., D. G. Firesmith, et al. (2003). A Reused-based Approach to Determining Security Requirements. The Ninth International Workshop on Requirements Engineering: Foundation for Software Quality - REFSQ'03
41. Smith, J. M. (2001 ). Troubled IT Projects prevention and turnaround. London, IEEE.
42. Sommerville, I. (2004). Software Engineering (7th edition), Addison-Wesley.
43. Sommerville, I. and J. Ransom (2005). "An Empirical Study of Industrial Requirements Engineering Process Assesment and Improvement." ACM Transactions on Software Engineering and Methodology 14(1): 85-117
44. Toval, A., J. Nicolás, et al. (2002). "Requirements Reuse for Improving Information Systems Security: A Practicioner's Approach." Requirements Engineering Journal. Springer 6(4): 205-219
45. Toval, A., A. Olmos, et al. (2002). Legal Requirements Reuse: A Critical Success Factor for Requirements Quality and Personal Data Protection. IEEE Joint International Conference on Requirements Engineering (ICRE'02 and RE'02), Essen, Alemania
46. Volere (2006). VOLERE, Requirements Tools. http://www.volere.co.uk/tools. htm
47. Wiegers, K. E. (1998). "Read My Lips: No New Models!." IEEE Software 15(5): 10-13