Raising Awareness of the Constituents of Software Design – The Case of Documentation
- 1 Management Information Systems, Emek Yezreel Academic College, Emek Yezreel, Israel.
- 2 Management Information Systems, Emek Yezreel Academic College, Emek Yezreel, Israel.
Abstract
This research was performed within a software engineering workshop for Computer Science students. For addressing the soft skills issues required by the industry, the course was delivered as a workshop with various (inter and intra) team based activities. An additional objective of outlining the importance of software maintainability issues was achieved through team-based role play. There were three assignments in which each team had to continue the work performed by another team, thus creating a dependency between the teams as might happen during maintenance. The main research study objective was to examine the effect of employing this kind of a team-based role-play peer-review on the students’ learning process regarding maintainability. Data referring to the students’ perceptions is presented and analyzed in addition to student reflections on the workshop which demonstrate their expanded understanding of the design and application process.
- P. Naur and B. Randell, “Software Engineering: Report of a Conference Sponsored by the NATO Science Committee,” Garmisch, Germany, Scientific Affairs Division, NATO, 1968. http://homepages.cs.ncl.ac.uk/brian.randell/NATO/ nato1968.PDF
- R. J. Veldwijk, M. Boogaard and E. R. K. Spoor, “Assess- ing the Software Crisis-Why Information Systems are Beyond Control,” Vrije Universiteit, the Netherlands, 1992. ftp://zappa.ubvu.vu.nl/19920006.pdf
- J. Burge, “Exploiting Multiplicity to Teach Reliability and Maintainability in a Capstone Project,” 20th Conference on Software Engineering Education & Training, Dublin, 2007.
- L. T. Cheng, S. Hupper, S. Ross and J. Patterson, “Jazzing up Eclipse with Collaborative Tools,” Proceedings of the 2003 OOPSLA Workshop on Eclipse Technology eX- change, Anaheim, October 2003.
- S. C. Souza, N. Anquetil and K. M. Oliveira, “Which Documentation for Software Maintenance,” Journal of the Brazilian Computer Society, Vol. 13, No. 2, 2007, pp. 31- 44.
- S. Das, W. G. Lutters and C. B. Seaman , “Understanding Documentation Value in Software Maintenance,” Pro- ceedings of the 2007 Symposium on Computer human interaction for the management of information technology, Cambridge, Massachusetts, 30-31 March 2007.
- M. K. Mattsson, “Problems in Agile Trenches,” Proceed- ings of the Second ACM-IEEE international symposium on Empirical Software Engineering and Measurement, Kai- serslautern, 09-10 October 2008.
- G. T. Daich, “Document Diseases and Software Mal- practice”. http://www.sstc.online.org/Proceedings/2003/P DFFiles/p961pap.pdf
- P. Clements, “Comparing the SEI’s Views and Beyond Approach for Documenting Software Architectures with ANSI-IEEE 1471-2000,” Technical Note CMU/SEI-2005- TN-017.http://www.sei.cmu.edu/pub/documents/05.eports/ pdf/05tn017.pdf
- R. C. Seacord, D. Plakosh and G. A. Lewis, “Modernizing Legacy Systems–Software Technologies, Engineering Processes and Business Practices,” New York, Addison- Wesley, 2003.
- D. Brolund and Ohlrogge, “Streamlining the Agile Documentation Demonstration for the XP 2006 Confe- rence,” Lecture Notes in Computer Science, Springer, Vol. 4044, 2006, pp. 215-216.
- G. Canfora and A. Cimitile, “Software Maintenance.” http://www.compaid.com/caiInternet/ezine/maintenance-canfora.pdf
- M. M. Lehman, “Lifecycles and the Laws of Software Evolution,” Proceedings of the IEEE, Special Issue on Software Engineering, Vol. 68, No. 9, 1980, pp. 1060- 1076.