WWW/Internet - Portal do Software Público Brasileiro

ISBN: 978-972-8939-25-0 © 2010 IADISAlthough helpful the annotation model is very poor and needs to be improved and so does thedocumentation generation tool which does not provide any graphical visualization of the Use Cases and itsmapping to the code. Developing a tool like Lagrein (Jermakovics, 2008) would be a good next step for thistechnique.Another issue that requires further research is how to integrate this technique with requirementsmanagement tools.Besides all this issued the technique proved that requirements could be recorded directly in the sourcecode in a way that they are readable and traceable. Documenting requirements directly in the code has theadvantage of having it easily accessible and read by developers. Also as the flow of episodes is determinedby the code, some changes in the requirements will be updated in the documentation without any extra effortfrom the developer.Finally, the case study showed that requirements knowledge and traceability has a big positive impact ofmaintenance productivity.REFERENCESBennett, K; Rajlich, V. “Software maintenance and evolution: a roadmap”. Proceedings of the Conference on The Futureof Software Engineering. Limerick, Ireland. p. 73 – 87. ISBN:1-58113-253-0. Publisher ACM Press New York, NY,USA, 2000Canfora, G., Di Penta, M. “New frontiers of reverse engineering”. In: Future of Software Engineering, Citeseer, 2007.Daneva, M. “Reuse measurement in the ERP requirements engineering process” In:Software Reuse: Advances inSoftware Reusability,p.211--230,Springer, 2006.De Lucia, A. et alli. “ADAMS Retrace: a Traceability Recovery Tool”, 9th European Conference on SoftwareMaintenance and Reegineering (CSMR 2005), March. 2005.Ernst, M., Coward D. “JSR 308: Annotations on Java types”. http://pag.csail.mit.edu/jsr308/, March 1st , 2010.Fahmi, S.A. and Choi, H.J. “Software Reverse Engineering to Requirements”, In: 2007 ICCIT, p. 2199--2204, IEEEComputer Society, 2007.Jermakovics, A. and Moser, R. and Sillitti, A. and Succi, G. “Visualizing software evolution with lagrein”. In:Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages andapplications, p. 749—750. ACM, 2008.Lamsweerde, A. “Requirements engineering: from craft to discipline”. In: Proceedings of the 16th ACM SIGSOFTInternational Symposium on Foundations of software engineering, p.238—249. ACM, 2008.Robbes, R., Lanza, M. “A Change-based Approach to Software Evolution”. In: Electronic Notes in Theoretical ComputerScience. Elsevier, vol. 166, p. 93-109, 2007Rui, K. “Refactoring use case models”. Concordia University Montreal, PQ, Canada, 2007.Schwarz, H. and Ebert, J. and Riediger, V. and Winter, A. “Towards querying of traceability information in the context ofsoftware evolution”. In: 10th Workshop Software Reengineering (WSR 2008), 2008.Taylor, K.B. and Rieken, J. and Leavens, G.T.. “Adapting the Java Modeling Language for Java 5 Annotations”.Technical Report 08-06, Department of Computer Science, Iowa State University, 2008.Weber, R. and Helfenberger, T. and Keller, R.K. “Fit for Change: Steps towards Effective Software Maintenance”, In:Industrial and Tool Proceedings of the International Conference on Software Maintenance, p.26--33, Citeseer, 2005.Yang, SU and Sheng-ming, HU and Yu-ying, W. and Ping, C. “Recovering early-aspects at requirements level fromsoftware legacy system”. In: CIT 2006. IEEE Computer Society, India, 2006.Liu, K. “Requirements Reengineering from Legacy Information Systems Using Semiotic Techniques”, In: Systems,Signs & Actions, Vol.1, No 1, p. 38-61. CITW, 2005.292