Michael Wilkinson English March 24, 2014 Dr.

Daniel Vollaro

Bibliography Min, Hokey, and James Storbeck. "On the Origin and Persistence of Misconceptions in Goal Programming." Journal of the Operational Research Society 42.4 (1991): 301-12. Print. This article attempts to advocate the use of goal programming in the eyes of the reader. It is meant to explain the concept of goal programming and to introduce new ideas about goal programming. The article can be considered outdated because it is over twenty years old, but it lays down some basic concepts in software development. The sources for this article are mostly papers and other academic writings concerning the use of goal programming and its relation/superiority to linear programming.

Banker, R. D., G. B. Davis, and S. A. Slaughter. "Software Development Practices, Software Complexity, and Software Maintenance Performance: A Field Study." Management Science 44.4 (1998): 433-50. Print. This article talks about the main issues with software maintenance cause by its development. It suggest that the manner in which the software is developed determines the amount of effort it takes to maintain it. The authors use a decent amount of statistical models and other sources to solidify their claims, but they appear to approach the matter from a non-neutral point of view. (That is that there are certain practices that are more efficient than others.) However, this is meant to be a persuasive/explanatory article, so the stance is understandable. [Books] Ingram, Dave. Design Build Run: Applied Practices and Principles for Production-Ready Software Development. Indianapolis: Wiley Publishing, Inc, 2009. Print. This book covers the most technical parts of software development. The author is specifically targeting software developers and their team leaders. In this book it explains exactly what produciton-ready software means, looks at the entire process, explains conceptual design, shows patterns of software development and finally shows the implications of applying those patterns. It is divided into five parts (listed above). The third and fourth parts are more relevant to the topics in this paper.

Meziane, Farid, and Sunil Vadera. Artificial Intelligence Applications for Improved Software Engineering Development. Hershey: Information Science Reference, 2010. Print. In this book, the authors describe how artificial intelligence can be used to enhance code development by pre-generating code and also cleaning up code. They begin by explaining its effects on project management. Then they explain the importance of requirements and the ability for artificial intelligence to predict and meet those requirements. Following that they describe the software design and implementation process. Lastly, they overview testing and maintenance. This book, specifically the third section (Software design and implementation), lays down some fundamentals about program design and what is needed to make functioning, efficient programs.

Perks, Mike. "Best Practices for Software Development Projects." Best Practices for Software Development Projects. International Business Machines Corporation, 16 June 2003. Web. 25 Mar. 2014. This article from the website http://www.ibm.com/ contains information sorted into a list pertaining to the best practice for software development. There are sixteen items on the list including: The Development Process, Software Requirements, Architecture, Design, Web-sphere Application Design, Construction of the code, Peer Reviews, Testing, Performance Testing, Configuration Management, Quality and Defects Management, Deployment, System Operations and Support, Data Migration, Project Management and Measuring Success. It asserts that these are all the best practices to keep in mind when developing software and has a list of sources.

"Best Practices in Developing Programs." Best Practices in Developing Programs. N.p., 11 Feb 2013. Web. 25 Mar. 2014. This is a lecture taken from the website of a Professor at the University of Texas in Austin. The professors name is Dr. Shyamal Mitra. Dr Mitra is not officially credited in the document, but I assume they are the lectures composer. This document highlights the importance of certain software design techniques as well as the flaws and problems in the field. Mitra explains how good software development practices address the problems in the development. The document also explains how the practices reinforce one another.