<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Head first object-oriented analysis and design</title>
    <subTitle>A Brain-Friendly Guide to OOA&amp;D</subTitle>
  </titleInfo>
  <name type="personal">
    <namePart>McLaughlin, Brett D.</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
    <role>
      <roleTerm type="text">autor.</roleTerm>
    </role>
    <role>
      <roleTerm authority="marcrelator" type="code">aut</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Pollice, Gary</namePart>
  </name>
  <name type="personal">
    <namePart>West, David</namePart>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <dateIssued encoding="marc">2007</dateIssued>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">spa</languageTerm>
  </language>
  <language objectPart="translation">
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
    <extent>600 páginas : : fig, ; ils.</extent>
  </physicalDescription>
  <abstract>Tired of reading Object Oriented Analysis and Design books that only makes sense after you're an expert? You've heard OOA&amp;D can help you write great software every time-software that makes your boss happy, your customers satisfied and gives you more time to do what makes you happy. But how? Head First Object-Oriented Analysis &amp; Design shows you how to analyze, design, and write serious object-oriented software: software that's easy to reuse, maintain, and extend; software that doesn't hurt your head;</abstract>
  <tableOfContents>1. Well-Designed Apps Rock: Great Software Begins Here. -- 2. Gathering Requirements: Give Them What They Want. -- 3. Requirements Change: I Love You, You’re Perfect... Now Change. -- 4. Analysis: Taking Your Software into the Real World. -- 5. (Part 1) Good Design = Flexible Software: Nothing Ever Stays the Same. -- 6. Solving Really Big Problems: “My Name is Art Vandelay... I am an Architect”. -- 7. Architecture: Bringing Order to Chaos. -- 8. Design Principles: Originality is Overrated. -- 9. Iterating and Testing: The Software is Still for the Customer. -- 10. The OOA&amp;D Lifecycle: Putting It All Together. -- A. Leftovers: The Top Ten Topics (we didn’t cover). -- B. Welcome to Objectville: Speaking the Language of OO.</tableOfContents>
  <note>Contents.</note>
  <subject authority="lcsh">
    <topic>Object-oriented programming</topic>
    <topic>Computer science</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Computer software</topic>
    <topic>Development</topic>
  </subject>
  <classification authority="ddc" edition="23">005.117 M478</classification>
  <identifier type="isbn">9780596008673</identifier>
  <identifier type="isbn">0596008678</identifier>
  <recordInfo>
    <recordContentSource authority="marcorg">CO-ViULL</recordContentSource>
    <recordCreationDate encoding="marc">230502</recordCreationDate>
    <recordChangeDate encoding="iso8601">20251030135902.0</recordChangeDate>
    <languageOfCataloging>
      <languageTerm authority="iso639-2b" type="code">spa</languageTerm>
    </languageOfCataloging>
  </recordInfo>
</mods>
