Professional Software Development
Here&#x27;s some for you collection given I see some omissions. Cleanroom, always omitted (sighs), is a big one as it was doing agile-like development in 80&#x27;s with code so reliable it was sometimes warrantied. Also one of first, formal methods that didn&#x27;t require a mathematician to use. Fagan&#x27;s Software Inspection Process came before that in the 70&#x27;s. I throw in Praxis and 001 for good measure as they&#x27;re <i>engineered</i> software methods with better results than Cleanroom albeit at higher cost. Leave off plenty of others too constrained for most software development but did prove out in smaller projects. The B Method &amp; Chlipala&#x27;s Certified Programming in Coq are examples if you want to Google around.<p><a href="http:&#x2F;&#x2F;citeseerx.ist.psu.edu&#x2F;viewdoc&#x2F;download?doi=10.1.1.88.2667&amp;rep=rep1&amp;type=pdf" rel="nofollow">http:&#x2F;&#x2F;citeseerx.ist.psu.edu&#x2F;viewdoc&#x2F;download?doi=10.1.1.88....</a><p>Note: An academic recently combined Cleanroom with Python for some nice results given how high-level Python is. I thought Haskell would be more ideal.<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Major_Defect" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Major_Defect</a><p>Note: Describes Fagan process with relevant links.<p><a href="http:&#x2F;&#x2F;www.sis.pitt.edu&#x2F;jjoshi&#x2F;Devsec&#x2F;CorrectnessByConstruction.pdf" rel="nofollow">http:&#x2F;&#x2F;www.sis.pitt.edu&#x2F;jjoshi&#x2F;Devsec&#x2F;CorrectnessByConstruct...</a><p>Note: Altran&#x2F;Praxis Correct by Construction is a modern high-assurance method with numerous successes. Cost a 50% premium for nearly defect-free systems. SPARK Ada is GPL these days.<p><a href="http:&#x2F;&#x2F;htius.com&#x2F;Articles&#x2F;articles.htm" rel="nofollow">http:&#x2F;&#x2F;htius.com&#x2F;Articles&#x2F;articles.htm</a><p>Note: Margaret Hamilton, who helped invent software engineering on Apollo mission, deserves mention for the first tool that automated most of software process. You can spec a whole system... one company specified their whole factory haha... then it semi-automates design then automatically does code, testing, portability, requirements traces, and so on. Guarantees no interface errors, which are 80+% of software faults. Today&#x27;s tools have better notations &amp; performance but still can&#x27;t do all that for general-purpose systems: always a niche.<p><a href="https:&#x2F;&#x2F;www.eiffel.com&#x2F;values&#x2F;design-by-contract&#x2F;introduction&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.eiffel.com&#x2F;values&#x2F;design-by-contract&#x2F;introductio...</a><p>Note: Added Eiffel method to make up for fact that I have little to nothing on OOP given I don&#x27;t use OOP. Meyer et al get credit for a powerful combo of language features and methodology in Eiffel platform with huge impact on software. Specifically, Design-by-Contract has so many benefits that even SPARK and Ada both added it to their languages. Just knocks out all kinds of problems plus can support automated generation of tests and such.<p>So, there&#x27;s you some reading on methods of making robust software that might fit into your book or something else you do. :)