And the relevant links are...

Maintenance categories (applicable to SW development, of course):

• https://en.wikipedia.org/wiki/Software_maintenance#Categories_of_maintenance_in_ISO.2FIEC_14764
• https://en.wikipedia.org/wiki/Change_request (and the various names it might get to be called: CR, SCR, CCN, ...)
• Note: ISO/IEC 14764 does not mention the term "Evolutionary Maintenance" that in a SW Maintenance contract means that there is a budget (in hours) for developing new features to the product being maintained (avoiding explicit change requests and additional contract management activities). "Predictive maintenance"is also relevant for HUMS (Health and Usage Maintenance [management] Systems)

About SDP and life cycles (some not widely used nowadays):

• https://en.wikipedia.org/wiki/Software_development_process
• https://en.wikipedia.org/wiki/Spiral_model
• https://en.wikipedia.org/wiki/Extreme_programming
• https://en.wikipedia.org/wiki/V-Model_(software_development)
• Make sure you also read about TDD, RUP, etc.

ENG QMS Process example (for TOC analysis, INTERNAL):

• https://quality.critical.pt/qmsunified/ENG-engineering/ENG01-requirements-analysis/CSW-QMS-2005-PCS-3424-requirements-analysis.pdf#search=eng01

And some relevant links include...

The NASA report about the (failed Mars mission) Mars Climate Orbiter and the ICD/ICS problem:

• https://llis.nasa.gov/llis_lib/pdf/1009464main1_0641-mr.pdf

About risk management in SW Development (a NASA doc) and why it is important to do it  - see next link:

• http://csse.usc.edu/csse/event/2009/UARC/material/Macro%20Risk%20Model.pdf

On software project failures

Software projects fail a lot. And since software is on most modern equipments (read carefully: almost everywhere) most equipments will also fail when running faulty software produced by some of those projects. This is one of the reasons current systems (meaning hardware + software) will also fail a lot.

How much do software projects fail? It's an interesting question and here are some possible "answers":

• The CHAOS report: https://www.projectsmart.co.uk/white-papers/chaos-report.pdf
• The Ambysoft "2013 IT Project Success Rates Survey Results": http://www.ambysoft.com/surveys/success2013.html
• The final presentation of the latter: http://www.ambysoft.com/downloads/surveys/Success2013.pptx

The latter study, published on Dr. Dobbs (which is now inactive BTW), criticizes the CHAOS report. On any case, a good percentage of projects fail and / or are challenged (they do not meet the on-quality, on-budget, on-schedule initial criteria). Just look at the trailer, I mean, just look at the numbers.