Ad Hoc Development
- 338 Downloads
Quality is usually invisible (from the viewpoint of customers and management), and many problems are only noticeable by software engineers. This chapter presents a long software development/evolution story to highlight many problems that will surface when quality is not treated seriously. It showcases how ignoring maintainability instigates an exponential growth in expenses.
Unable to display preview. Download preview PDF.
- 1.Guttag J, Liskov B (2000) Program development in Java: abstraction, specification, and object-oriented design. Addison-Wesley Professional, Boston, MA. This book is the foundation for learning how to produce high quality products using Java. It fully covers the systems development life-cycle, and contains explanations for doing object-oriented program design and component-based software developmentGoogle Scholar
Regular Bibliographic References
- 2.Kuipers T (2016) Why you need to know about code maintainability. www.oreilly.com/ideas/why-you-need-to-know-about-code-maintainability. Accessed 25 Aug 2017
- 3.IEEE/ACM (2015) Software engineering code of ethics and professional practice. www.acm.org/about/se-code. Accessed 26 Aug 2017
- 4.Robinson I (2008) Service-oriented development with consumer-driven contracts. www.infoq.com/articles/consumer-driven-contracts. Accessed 26 Aug 2017
- 5.Mili H, Mili A, Yacoub S, Addy E (2001) Reuse-based software engineering: techniques, organizations, and controls. Wiley Inter-Science, ChichesterGoogle Scholar
- 6.Mind Tools Editorial Team (2017) 5 whys: getting to the root of a problem quickly. www.mindtools.com/pages/article/newTMC_5W.htm. Accessed 28 Aug 2017
- 7.Kamp HP (2012) A generation lost in the bazaar. queue.acm.org/detail.cfm?id=2349257. Accessed 29 Aug 2017
- 8.Sommerville I (2014) Warsaw airbus accident. www.slideshare.net/sommerville-videos/warsaw-airbus-accident. Accessed 30 Aug 2017
- 9.Bloch J (2008) Effective Java, 2nd edn. Addison-Wesley, Upper Saddle River, NJGoogle Scholar
- 10.Seibel P (2009) Coders at work: reflections on the craft of programming. Apress, New YorkGoogle Scholar
- 11.Fowler M, Beck K, Brant J, Opdyke W, Roberts D (1999) Refactoring: improving the design of existing code. Addison Wesley, Upper Saddle River, NJGoogle Scholar