![](bg5.png)
record” of a particular software development
project from whatever evidentiary trail exists?
b. then, how do we evaluate/assess/critique such a
narrative against the prevailing understanding of
correct/canonical software process(es)?
c. likewise, how do we evaluate/assess/critique
artefacts produced at each stage e.g. requirement
specs, designs, code, test plans, etc.
Hopefully “big data” analysis solutions may be
discovered that can be applied to this domain.
Chief among the social prerequisites is how to
inculcate as far as possible a blame-free culture that
is conducive to open self-criticism by software
developers in the aftermath of a failed project, e.g.
as with the UK Civil Aviation Authority Mandatory
Occurrence Reporting (MOR) Scheme (CAA, 2011).
7 CONCLUSIONS
While being frank about the challenges, we propose
SEFA development as a worthwhile undertaking.
Generally, the goals as per our Introduction above
are worthwhile, and we have established the
plausibility of the precedent from
aeronautics/aviation.
Specifically, SEFA raises hopes for the
following:
an evidence-based, more specific understanding
of the different circumstances under which
different software processes and tools are more
or less appropriate;
hopefully including a rubric when “agile”
methods are appropriate (or not)!
similarly for other variations from canonical
process(es);
meta-level tools and techniques to enable the
above;
more specific directions in software engineering
education and training;
incidentally, because software systems dominate
aeronautical engineering, a formally-established
“Software Forensics Institute” would discharge
implicit ICAO obligations in software dimension
of air accident investigations.
REFERENCES
CAA, 2011. CAP 382 Mandatory Occurrence Reporting
Scheme (9
th
ed.), TSO.
Charette, R., 2005. Why Software Fails. IEEE Spectrum.
http://spectrum.ieee.org/computing/software/why-soft
ware-fails
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-Payroll-
System-Commission-of-Inquiry-Report-31-July-
2013.pdf
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
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-the-
healthcare-dot-gov-debacle.
ICAO, 2001. Aircraft Accident and Incident Investigation.
Annex 13 to the Convention on International Civil
Aviation. International Civil Aviation Organization.
Job, M., 1998a. American 191, do you want to come back.
In Air Disaster Volume 2. Aerospace Publications.
Job, M., 1998b. I don’t like this. In Air Disaster Volume 2.
Aerospace Publications.
Job, M., 1998c. Air Disaster Volume 3. Aerospace
Publications.
Job, M., 2001. The Lockheed Electra Saga. In Air Disaster
Volume 4 The Propellor Era. Aerospace Publications.
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
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
Mathieson, S., 2011. Scrapping the National Programme
for IT: a journey not a destination. The Guardian.
http://www.theguardian.com/healthcare-
network/2011/sep/22/npfit-ends-cfh-andrew-lansley-
bt-csc?newsfeed=true
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 G-
ALYP, London: HMSO
NAO, 2013. Universal Credit: early progress. National
Audit Office. http://www.nao.org.uk/report/universal-
credit-early-progress/
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.
OMG, 2011. Documents Associated With Unified
Modeling Language (UML), V2.4.1.
http://www.omg.org/spec/UML/2.4.1/
Peterson, J., 1977. Petri Nets. ACM Computing Surveys
TowardsaDisciplineofSoftwareEngineeringForensicsAnalysis
239