FINAL DISC 8

By now, you should have a good understanding what it takes to engineer complete and correct requirements, secure design  and secure code. You are also exposed to process improvement techniques. Now you are in a good position to analyze or critique systems that have failed in the past. Search the web for an example(s) of software development projects which failed. There will be many.  Pick one which interests you. Briefly post your summary of the failed project. Be sure to touch up on the following points:

1. Why did it fail? Was it poor requirements, poor design, poor coding and poor testing, validation & verification?
2. Did it fail because of project and program management?
3. Did it follow good assurance techniques?
4. Did the project pay attention to secure design and coding?

   OERs

• DHS. (2007). Software Assurance: A Curriculum Guide to the Common Body of Knowledge to Produce, Acquire, and Sustain Secure Software. Retrieved from:https://learn.umgc.edu/content/enforced/313879-M_022073-01-2185/Common_Body_of_Knowledge2007.pdf?_&d2lSessionVal=yHNXTIp6y56ZPEX8jKq29unVQ&ou=313879 .
  • Chapter 6 Secure Software Design Pages 89 – 107
  • Chapter 7  Secure Software Construction Pages 109 – 125
• OWASP. (2010). Secure Coding Practices. Retrieved from: https://www.owasp.org/images/0/08/OWASP_SCP_Quick_Reference_Guide_v2.pdf.
• Carnegie-Mellon University CERT. (n.d.). SEI CERT Coding Standards (n.d.).Retrieved from: https://www.securecoding.cert.org/confluence/display/seccode/SEI+CERT+Coding+Standards.
• Microsoft. (n.d.). Secure Coding Guidelines. Retrieved from: https://msdn.microsoft.com/en-us/library/d55zzx87%28v=vs.90%29.aspx

  Due Sep 1st