Non functional requirements (NFRs) traceability metamodel for agile development

Jurnal Teknologi

Volumn 77, Issue 9, 2015, Pages 115-125

  Firdaus, Adila ^a   Ghani, Imran ^a   Abg Jawawi, Dayang Norhayati ^a   Wan Kadir, Wan Mohd Nasir ^a  

^a UNIVERSITI TEKNOLOGI MALAYSIA   (Malaysia)

Author keywords

Agile methodologies; Meta model; Performance; Propagation; Security; Traceability

Indexed keywords

EID: 84947282576     PISSN: 01279696     EISSN: None     Source Type: Journal    
DOI: 10.11113/jt.v77.6191     Document Type: Article

References (27)

1. Breivold, H. P, D. Sundmark, P. Wallin, and S. Larsson 2010. What Does Research Say about Agile and Architecture. Fifth International Conference on Software Engineering Advances 32-37. Retrieved April 1, 2013 (http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm?arnumber=5615620).
2. Abbors, F., J. Lilius, A Joukahaisenkatu, E. Fredrik Abbors, and D. Truscan. 2009. Tracing Requirements In A Model-Based Testing Approach. First International Conference on Advances in System Testing and Validation Lifecycle. 123-128.
3. Chung, L., B. A. Nixon. & Yu, E. 1996. Dealing with Change: An Approach Using Non-functional Requirements. Requirements Eng. 1: 238-260, 238-260.
4. Grau, R. 2012. Requirements Engineering in Agile Software Development. Software for People. Springer Berlin Heidelberg
5. Huang, J. C., A. Czauderna, and E. Keenan. 2013. A Persona-Based Approach for Exploring Architecturally Significant Requirements in Agile Projects. Requirements Engineering: Foundation for Software Quality. Springer Berlin Heidelberg.
6. Firdaus, A., Ghani, I, and Jeong, S. R. 2014. Secure Feature Driven Development (SFDD) Model for Secure Software Development. Procedia-Social and Behavioral Sciences. 129: 546-553.
7. Cao, L., Mohan, K., Ramesh, B., & Sarkar, S. 2013. Adapting Funding Processes for Agile IT Projects: An Empirical Investigation. European Journal of Information Systems. 22(2): 191-205.
8. Vander Leest, S., and A. Buter. 2009. Escape the Waterfall: Agile for Aerospace 28th Digital Avionics Systems Conference.
9. Grundy, J., J. Hosking, W. B. Mugridge, 2002. Inconsistency Management for Multiple-View Software Development Environments. Software Engineering, IEEE Transactions on. 24(11).
10. Gotel, O., C., Z., and Finkelstein, C.W, 1994. An analysis of the requirements traceability problem. In: Proceedings of the First International Conference on Requirements Engineering, pp. 94–101.
11. Reshef, A. N., R. F. Paige, J. Rubin, Y. Shaham-Gafni, and D. S. Kolovos.2005. Operational Semantics for Traceability In Proceedings of ECMDA Traceability Workshop, ECMDA-TW ’05, pages 8–14
12. Ajila, S., and A. B. Kaba. 2004. Using Traceability Mechanisms to Support Software Product Line Evolution. In Information Reuse and Integration, 2004. IRI 2004. Proceedings of the 2004 IEEE International Conference on IEEE. 157-162.
13. Chen, J. Y., & S. C. Chou. 1999. Consistency Management in a Process Environment. Journal of Systems and Software. 47(2): 105-110.
14. Huang, J. C. 2005. Toward Improved Traceability of Non-Functional Requirements. Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering. ACM.
15. Kassab, M., and O. Ormandjieva. 2006. Towards an Aspect-Oriented Software Development Model with Tractability Mechanism. Trese.cs.utwente.nl. 1–8.
16. A. G. Kourie and B. W. Watson. 2003. Standards and Agile Software Development. Proceedings of SAICSIT 2003. 1-11.
17. Huang, J. C., O. Gotel, and A. Zisman. 2012. Software and Systems Traceability. 2(3). Springer.
18. Collins, E. F., and V. F. de Lucena. 2012. Software Test Automation Practices in Agile Development Environment: An Industry Experience Report. Automation of Software Test (AST). 7th International Workshop on. IEEE.
19. Julian, R., and J. Green. 2004. Automating Traceability For Generated Software Artifacts. Proceedings of the 19th IEEE International Conference on Automated Software Engineering. IEEE Computer Society.
20. Kassab, M., O. Ormandjieva, and Maya Daneva. 2009. A Metamodel for Tracing Non-functional Requirements. Computer Science and Information Engineering, 2009 WRI World Congress on. 7. IEEE.
21. Huang J. C., R. Settimi, O. BenKhadra, E. Berezhanskaya, and S. Christina. 2005. Goal Centric Traceability for Managing Non-Functional Requirements. Proceedings of the 27th International Conference on Software Engineering. 362-371
22. Kappel, G., Kargl, H., Kramler, G., Schauerhuber, A., Seidl, M. Strommer, M., & Wimmer, M. 2007. Matching Metamodel with Sematics Systems-An Experience Report. Datebanksysteme in Business. Technologie und Web Workshop Proceedings, 5.-6 Marz, Aachen Germany. 38-52.
23. Firdaus A., Ghani I., and Yasin NIM. 2013. Developing Secure Websites Using Feature Driven Development (FDD): A Case Study. Journal of Clean Energy Technologies Issue. 1(4).
24. Inayat, I., Salim, S. S., Marczak, S., Daneva, M., & Shamshirband, S. 2014. A Systematic Literature Review on Agile Requirements Engineering Practices and Challenges. Computers in Human Behavior.
25. Azham Z., Ghani I., and Ithnin N. 2011. Security Backlog In Scrum Security Practices. Software Engineering (Mysec). 2011 5th Malaysian Conference in. 414-417.
26. Ghani I., Azham Z., and Jeong SR. 2014. Integrating Software Security into Agile-Scrum Method. KSII Transactions on Internet and Information Systems (TIIS). 8(2): 646-663.
27. Azham Z., Ghani I., and Ithnin N. 2011. Security Backlog In Scrum Security Practices. Software Engineering (Mysec). 2011 5th Malaysian Conference in. 414-417.