Object-Oriented Analysis and Design

  • John Dooley

Abstract

When defining object-oriented analysis and design, it’s best to keep in mind your objectives. In both of these process phases we’re producing a work product that is closer to the code that is your end goal. In analysis, you’re refining the feature list you’ve created and producing a model of what the customer wants. In design you’re taking that model and creating the classes that will end up being code.

Keywords

Encapsulation Alan 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Beck, K. Extreme Programming Explained: Embrace Change. (Boston, MA: Addison-Wesley, 2000).Google Scholar
  2. Cockburn, A. (2000). Writing Effective Use Cases. (Boston, MA: Addison-Wesley, 2000).Google Scholar
  3. Fowler, M. UML Distilled. (Boston, MA: Addison-Wesley, 2000).Google Scholar
  4. McLaughlin, Brett D., et. al. Head First Object-Oriented Analysis & Design. (Sebastopol, CA: O’Reilly Media, Inc., 2007).Google Scholar
  5. Meyer, Bertrand. Object-Oriented Software Construction. (Upper Saddle River, NJ: Prentice Hall, 1988).Google Scholar
  6. Martin, Robert, Single Responsibility Principle. www.butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod. Retrieved on December 10, 2009.
  7. Wirfs-Brock, R. and A. McKean. Object Design: Roles Responsibilities, and Collaborations. (Boston, MA, Addison-Wesley, 2003).Google Scholar

Copyright information

© John Dooley 2011

Authors and Affiliations

  • John Dooley

There are no affiliations available

Personalised recommendations