Our Reading Group meets each week to discuss papers suggested by our members. Attendance is open to everybody. Feel free to add paper suggestions to our paper queue. Occasionally, members give practice talks. Contact Neil to arrange a talk.
- When: 1pm - 3pm, alternating Tuesdays
- Where: SE Debugging Room (the lounge area in the new SE Lab)
- Bonus: tea/coffee and dessert
- Nov 18 -- Arisholm, E. and Briand, L.C. and Hove, S.E. and Labiche, Y. The impact of UML documentation on software maintenance. IEEE ToSE 32(6), p. 365--381, June 2006.
- ? -- C.W. Johnson and C.M. Holloway. Questioning the Role of Requirements Engineering in the Causes of Safety-Critical Software Failures International Conference on System Safety, page352-361. 2006
- ? -- Jo E. Hannay and Magne Jørgensen. The Role of Deliberate Artificial Design Elements in Software Engineering Experiments. IEEE Transactions on Software Engineering, 34(2): 242-259, Mar/Apr 2008.
- ? -- Barry Boehm and Jo Ann Lane. Using the Incremental Commitment Model to Integrate System Acquisition, Systems Engineering, and Software Engineering. Crosstalk: Journal of Defence Software Engineering, October 2007.
- ? - P. Abrahamsson and J. Koskela. Extreme programming: a survey of empirical data from a controlled case study. International Symposium on Empirical Software Engineering, page 73-82. Redondo Beach, CA, August 2004.
- ?? - Lorna Uden, Pedro Valderas and Oscar Pastor. An activity-theory-based model to analyse Web application requirements. Information Research, vol. 13 no. 2, June 2008.
- Nov 4 - Helen Sharp and Hugh Robinson. An Ethnographic Study of XP Practice. Empirical Software Engineering, 2004.
- Oct 7 - M. Pikkarainen and J. Haikara and O. Salo and P. Abrahamsson and J. Still. The impact of agile practices on communication in software development. Empirical Software Engineering, 2008.
- Sept 23 -- Ahmed Egyed. Fixing Inconsistencies in UML Design Models. International Conference on Software Engineering, 2007.
- Apr 7 -- Jo E. Hannay and Dag I.K. Sjøberg and Tore Dybå. A Systematic Review of Theory Use in Software Engineering Experiments. IEEE Transactions on Software Engineering, 33(2): 87-107, 2007.
- Mar 10 -- Martin Feather and S. Cornford. Quantitative risk-based requirements reasoning. REJ, 8(4), 2003.
- Feb 25 -- Yudistira Asnar and Paolo Giorgini. Modelling Risk and Identifying Countermeasure in Organizations. First International Workshop on Critical Information Infrastructures Security, : 55--66, 2006.
- Jan 21 -- John Grundy and John Hosking. Supporting Generic Sketching-Based Input of Diagrams in a Domain-Specific Visual Language Meta-Tool. International Conference on Software Engineering, 282-291, Minneapolis, Minnesota, 2007.
Software engineers often use hand-drawn diagrams as preliminary design
artefacts and as annotations during reviews. We describe the addition of
sketching support to a domain-specific visual language meta-tool
enabling a wide range of diagram-based design tools to leverage this
human-centric interaction support. Our approach allows visual design
tools generated from high-level specifications to incorporate a range of
sketching-based functionality including both eager and lazy
recognition, moving from sketch to formalized content and back, and
using sketches for secondary annotation and collaborative design review.
We illustrate the use of our sketching extension for an example
domain-specific visual design tool and describe the architecture and
implementation of the extension as a plug-in for our Eclipse-based
As for structure and readings, I (Neil) was thinking of organizing
the papers along the lines of "great problems in software engineering".
Here are a few of my suggestions:
- how to tell if a problem is 'essentially complex' or 'accidentally complex'; if the former, how can we manage it?
- why is it that UML has a penetration rate of <40%? Whither agile software development?
- does agility have any place in large-scale projects?
- is model-driven development the next big thing, or industry hype?
- is service orientation the next big thing, or industry hype?
- is <insert technology here> the next big thing, or vendor hype?
- why do few organizations do requirements 'well'?
- what degree of formality is necessary/acceptable in software engineering?
There are many papers that we could choose from, and I welcome
suggestions. However, to maintain interest I suggest we focus on work
that has been published quite recently, e.g., the last 2 ICSEs, the last
Papers are not listed in any particular order. Feel free to add/remove papers/categories.