A metamodel for tracing non-functional requirements

2009 WRI World Congress on Computer Science and Information Engineering, CSIE 2009

Volumn 7, Issue , 2009, Pages 687-694

  Kassab, M ^a   Ormandjieva, O ^b   Daneva, M ^b  

^a Dept of Electrical and Computer Engineering   (Canada)

^b UNIVERSITY OF TWENTE   (Netherlands)

Author keywords

[No Author keywords available]

Indexed keywords

DATALOG; META MODEL; NON-FUNCTIONAL REQUIREMENTS; PROGRAMMING PARADIGMS; RELATIONAL MODEL; SOFTWARE MODELING; SOFTWARE PROJECT; SOFTWARE SYSTEMS;

COMPUTER SCIENCE; LARGE SCALE SYSTEMS;

COMPUTER SOFTWARE;

EID: 71049119046     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/CSIE.2009.946     Document Type: Conference Paper

References (29)

1. A. Egyed, P. Grunbacher, "Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability Can Help", IEEE Software, 21(6), 2004, p.p.50-58.
2. A. Finkelstein, and J. Dowell, "A Comedy of Errors: The London Ambulance Service Case Study", Proc. Eighth International Workshop Software Spec and Design, 1996, pp. 2-5.
3. A. Finkelstein and W. Emmerich, "The Future of Requirements Management Tools", In Information Systems in Public Administration and Law, 2000.
4. A. M. Salem, "Improving Software Quality through Requirements Traceability Models", Proc. of Int. Conf on Computer Systems and Applications, 2006, pp. 1159-1162.
5. A. Moreira, J. Araujo and I. Brito, "Crosscutting Quality Attributes for Requirements Engineering", In 14th Int. Conf. on Soft. Eng. and Knowledge Eng. 2002, Ischia, Italy, 2002, pp. 167-174.
6. B. Ramesh, and M. Jarke, "Toward a Reference Model for Requirements Traceability", IEEE Transactions on Software Engineering, 27(1), 2001, pp. 58-93
7. C. Hofmeister, R.L. Nord, D. Soni, "Global Analysis: moving from software requirements specification to structural views of the software architecture", IEEE Proceedings - Software, Vol. 152 Issue 4, Aug2005, pp.187-197.
8. Chung, L., "Representing and Using Non-Functional Requirements: A Process-Oriented Approach." Ph.D. Thesis, Dept. of Computer Science, Univ. of Toronto. 1993. Also Technical Report DKBS-TR-93-1.
9. Chung L., Nixon B.A. , Yu E. and Mylopoulos J., Nonfunctional Requirements in Software Engineering, Kluwer Academic Publishing, 2000.
10. th Int. Conf. on Software Engineering, 2007, pp. 159-160.
11. D. Park, S. Kang, J. Lee, "Design Phase Analysis of Software Performance Using Aspect-Oriented Programming", In 5th Aspect-Oriented Modeling Workshop in Conjunction with UML 2004, Lisbon, Portugal, 2004.
12. E. Baniassad, P.C. Clements, J. Araujo, A. Moreira, A. Rashid, B.Tekinerdogan, "Discovering Early Aspects", IEEE Software, Jan-Feb 2006, 23(1), pp. 61-70.
13. E. Niemelä, A. Immonen, "Capturing Quality Requirements of Product Family Architecture", Information and Software Technology, Vol. 49, Issues 11-12, November 2007, pp. 1107-1120.
14. F. A. Blaauboer, K. Sikkel, M.N Aydin, "Deciding to Adopt Requirements Traceability in Practice", In Proc. of 19th Int. Conf. on Advanced Information Systems Engineering (CAiSE'07), Springer Lecture Notes in Computer Science 4495, Norway, 2007, pp. 294-308.
15. J. Araujo, A. Moreira, I. Brito, and A. Rashid, "Aspect-Oriented Requirements With UML", Workshop on Aspect-Oriented Modeling with UML (held with UML 2002, Dresden, Germany, 2002.
16. rd international workshop on Traceability in emerging forms of software engineering, Long Beach, California, 2005, pp. 14-19.
17. J. Cleland-Huang, R. Settimi, O. BenKhadra, E. Berezhanskaya, S. Christina, "Goal Centric Traceability for Managing Non-Functional Requirements", Proceedings of the 27th international conference on Software engineering, 2005, pp. 362-371.
18. K. K Breitman, J. C. S. P. Leite and A. Finkelstein, "The World's Stage: A Survey on Requirements Engineering Using a Real-Life Case Study", Journal of the Brazilian Computer Society No 1 Vol. 6, Jul. 1999, pp.13-37.
19. L. Chung, B.A. Nixon, E. Yu, "Using Non-Functional Requirements to Systematically Support Change", Proceedings of the Second IEEE International Symposium on Requirements Engineering, 1995, York, U.K., pp. 132-139.
20. L. Leveson, and C.S. Turner, "An Investigation of the Therac-25 Accidents", IEEE Computer., 26, 7, 1993, pp.18-41.
21. M. Weber, J. Wesbrot, "Requirements Engineering in Automotive Development: Experiences and Challenges", IEEE Software 20(1), pp.16-24.
22. Mercdes A-Class: "Mercedes: Wie sicher ist die A-Klasse?", German news magazine: "Der Spiegel", ISSN 0038-7452, Oct. 27th 1997, p. 120; English translation: http://www.geocities.com/MotorCity/downs/9323/ aclacap.htm, last visited on Feb. 11th, 2005.
23. N. Aizenbud-Reshef, B.T. Nolan, J. Rubin, Y. Shaham-Gafni , "Model Traceability", IBM System Journal, 45(3), 2006, pp. 515-526.
24. O. Gotel, "Contribution Structures for Requirements Traceability", London, England: Imperial College, Department of Computing, 1995.
25. O. Gotel and A. Finkelstein, "An Analysis of the Requirements Traceability Problem", Proc. First International Conf. Requirements Eng., Colorado, U.S.A, 1994, pp. 94-101.
26. P. Letelier, "A Framework for Requirements Traceability in UML-Based Projects", Proc. of the 1st Int. Workshop on Traceability in Emerging Forms of Software Engineering, Edinburgh, 2002, pp. 30-41.
27. R.J. Wieringa and J.M.G. Heerkens, "The methodological soundness of requirements engineering papers: a conceptual framework and two case studies", Requirements engineering, 11(4), 2006, pp. 295-307.
28. Ullman J. and J. Widom, Database Systems: The Complete Book, Prentice Hall, 2002.
29. V. Winter, H. Siy, M. Zand, P. Aryal, Aspect Workshop at AOSD'06, Bonn, Germany, 2006.