Towards a Discipline of Software Engineering Forensics Analysis

Paul Bailes, Christine Cornish, Toby Myers, Louis Rago, Nick Tate, Mal Thatcher

2014

Abstract

Software development and procurement continues to be a source of great disappointment for its social and economic stakeholders, with literally billions of dollars being expended for little ostensible benefit. But significant progress can be made in engineering domains that match software for complexity and novelty: the international regime of aviation accident and incident reporting has been the basis for a wide range of evidence-based technical and process improvements in applied aeronautical engineering. Accordingly, we set out to characterise the knowledge, activities and structures that would promise to deliver analogous benefits to software engineering. While we are hopeful of early positive outcomes, a significant research agenda lies before us.

References

  1. CAA, 2011. CAP 382 Mandatory Occurrence Reporting Scheme (9th ed.), TSO.
  2. Charette, R., 2005. Why Software Fails. IEEE Spectrum. http://spectrum.ieee.org/computing/software/why-soft ware-fails
  3. Chesterman, N., 2013. Queensland Health Payroll System Commission of Inquiry Report. http://www.healthpayrollinquiry.qld.gov.au/__data/ass ets/pdf_file/0014/207203/Queensland-Health-PayrollSystem-Commission-of-Inquiry-Report-31-July2013.pdf
  4. Dromey, R.G., 2006. Formalizing the Transition from Requirements to Design. In Mathematical Frameworks for Component Software - Models for Analysis and Synthesis, Jifeng He, and Zhiming Liu (Eds.), World Scientific Series on Component-Based Development, pp. 156-187
  5. Ford, P., 2013. The Obamacare Website Didn't Have to Fail. How to Do Better Next Time. Bloomberg Businessweek. http://www.businessweek.com/articles/ 2013-10-16/open-source-everything-the-moral-of-thehealthcare-dot-gov-debacle.
  6. ICAO, 2001. Aircraft Accident and Incident Investigation. Annex 13 to the Convention on International Civil Aviation. International Civil Aviation Organization.
  7. Job, M., 1998a. American 191, do you want to come back. In Air Disaster Volume 2. Aerospace Publications.
  8. Job, M., 1998b. I don't like this. In Air Disaster Volume 2. Aerospace Publications.
  9. Job, M., 1998c. Air Disaster Volume 3. Aerospace Publications.
  10. Job, M., 2001. The Lockheed Electra Saga. In Air Disaster Volume 4 The Propellor Era. Aerospace Publications.
  11. Kanaracus, C., 2012a. Air Force scraps massive ERP project after racking up $1 billion in costs. CIO. http://www.cio.com/article/721628/Air_Force_scraps_ massive_ERP_project_after_racking_up_1_billion_in _costs
  12. Kanaracus, C., 2012b. The scariest software project horror stories of 2012. Computerworld. http://www.computerworld.com/s/article/9234581/The _scariest_software_project_horror_stories_of_2012
  13. Mathieson, S., 2011. Scrapping the National Programme for IT: a journey not a destination. The Guardian. http://www.theguardian.com/healthcarenetwork/2011/sep/22/npfit-ends-cfh-andrew-lansleybt-csc?newsfeed=true
  14. MTCA, 1955. Report of the Public Inquiry into the causes and circumstances of the accident which occurred on the 10th January, 1954, to the Comet aircraft GALYP, London: HMSO
  15. NAO, 2013. Universal Credit: early progress. National Audit Office. http://www.nao.org.uk/report/universalcredit-early-progress/
  16. Naur, P. and Randell, B. (Ed.) 1969. Software Engineering: Report on a Conference sponsored by the NATO Science Committee, Garmisch, Germany, 7th to 11th October 1968. Brussels, Scientific Affairs Division, NATO.
  17. OMG, 2011. Documents Associated With Unified Modeling Language (UML), V2.4.1. http://www.omg.org/spec/UML/2.4.1/
  18. Peterson, J., 1977. Petri Nets. ACM Computing Surveys vol. 9 no. 3 pp. 223-252.
  19. Sauer, C. and Cuthbertson, C., 2003. The State of IT Project Management in the UK 2002-2003. Computer Weekly Project/Programme Management Survey. http://www.bestpracticehelp.com/The_State_of_IT_Pr oject_Management_in_the_UK_2003_2004.pdf
  20. Sommerville, I., 2011. Software engineering (9th ed.). Pearson.
  21. Spivey, J.M., 1992. The Z Notation: A reference manual. International Series in Computer Science (2nd ed.). Prentice Hall.
Download


Paper Citation


in Harvard Style

Bailes P., Cornish C., Myers T., Rago L., Tate N. and Thatcher M. (2014). Towards a Discipline of Software Engineering Forensics Analysis . In Proceedings of the 9th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE, ISBN 978-989-758-030-7, pages 235-240. DOI: 10.5220/0004970002350240


in Bibtex Style

@conference{enase14,
author={Paul Bailes and Christine Cornish and Toby Myers and Louis Rago and Nick Tate and Mal Thatcher},
title={Towards a Discipline of Software Engineering Forensics Analysis},
booktitle={Proceedings of the 9th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE,},
year={2014},
pages={235-240},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0004970002350240},
isbn={978-989-758-030-7},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 9th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE,
TI - Towards a Discipline of Software Engineering Forensics Analysis
SN - 978-989-758-030-7
AU - Bailes P.
AU - Cornish C.
AU - Myers T.
AU - Rago L.
AU - Tate N.
AU - Thatcher M.
PY - 2014
SP - 235
EP - 240
DO - 10.5220/0004970002350240