<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>04577aam a22003732i 4500</leader>
  <controlfield tag="001">000024771</controlfield>
  <controlfield tag="003">PE-TmUNAS</controlfield>
  <controlfield tag="005">20250224115707.0</controlfield>
  <controlfield tag="006">a||||fr|||| 00| 0|</controlfield>
  <controlfield tag="007">ta</controlfield>
  <controlfield tag="008">170914s2011    us adk|frfn|| 00| 0 engsd</controlfield>
  <datafield tag="017" ind1=" " ind2=" ">
    <subfield code="a">&#xA9; 2011, 2006, 2005, 2001, 1996</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">978-0-13-703515-1</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">Biblioteca Central de la Universidad Nacional Agraria de la Selva</subfield>
    <subfield code="b">spa</subfield>
    <subfield code="c">Catalogaci&#xF3;n de la Biblioteca Central de la Universidad Nacional Agraria de la Selva, transcrita por la Biblioteca Central de la Universidad Nacional Agraria de la Selva, sin modificaciones posteriores</subfield>
    <subfield code="d">Biblioteca Central de la Universidad Nacional Agraria de la Selva</subfield>
    <subfield code="e">rda</subfield>
  </datafield>
  <datafield tag="041" ind1="0" ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="082" ind1="0" ind2="4">
    <subfield code="2">22</subfield>
    <subfield code="a">005.1</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Software engineering 9 /</subfield>
    <subfield code="c">Ian Sommerville.</subfield>
    <subfield code="b"> </subfield>
  </datafield>
  <datafield tag="250" ind1=" " ind2=" ">
    <subfield code="a">9th ed.</subfield>
  </datafield>
  <datafield tag="264" ind1="3" ind2="1">
    <subfield code="a">Estados Unidos  : </subfield>
    <subfield code="b">Pearson Education,</subfield>
    <subfield code="c">2011.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">773 p&#xE1;ginas :</subfield>
    <subfield code="b">figuras (color)</subfield>
    <subfield code="c">25.cm</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
    <subfield code="2">rdacontent</subfield>
    <subfield code="a">texto impreso</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
    <subfield code="2">rdamedia</subfield>
    <subfield code="a">sin mediaci&#xF3;n</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
    <subfield code="2">rdacarrier</subfield>
    <subfield code="a">volumen</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Incluye anexos 
       
</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Incluye informaci&#xF3;n acad&#xE9;mica y profesional en la cubierta posterior 
</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">bibliograf&#xED;a: p&#xE1;ginas 767 - 773</subfield>
    <subfield code="b">24</subfield>
  </datafield>
  <datafield tag="505" ind1="2" ind2=" ">
    <subfield code="a">Introduction to Software Engineering: Introduction --Software processes --  Agile software development -- Requirements engineering -- System modeling -- Architectural design -- Design and implementaci&#xF3;n --  Software testing --  Software evolution -- Dependability and Security:  Sociotechnical systems --  Dependability and security --  Dependability and security specification -- Dependability engineering -- Security engineering -- Dependability and security assurance -- Advanced Software Engineering -- Software reuse -- Component-based software engineering --  Distributed software engineering --  Service-oriented architecture --  Embedded software -- : Aspect-oriented software engineering -- : Project management --  Project planning --  Quality management -- Configuration management -- Process improvement.</subfield>
  </datafield>
  <datafield tag="520" ind1="2" ind2=" ">
    <subfield code="a">"As l was writing the final chapters in this book in the summer of 2009, I realized that software engineering was 40 years old. The name 'software engineering' was proposed in 1969 at a NATO conference to discuss software development problems large software systems were late, did not deliver the functionality needed by their users, cost more than expected, and were unreliable. I did not attend that conference but. a year later, I wrote my first program and started my professional life in software. Progress in software engineering has been remarkable over my professional life time. Our societies could not function without large, professional software systems. For building business systems, there is an alphabet soup of technologies-J2EE. NET. SaaS, SAP. BPEL4WS, SOAP, CBSE, etc.-that support the development and deployment of large enterprise applications. National utilities and infrastructure energy, communications, and transport-all rely on complex and mostly reliable computer systems. Software has allowed us to explore space and to create the World Wide Web, the most significant information system in the history of mankind. Humanity is now faced with a new set of challenges-climate change and extreme weather, declining natural resources, an increasing world population to be fed and housed, international terrorism, and the need to help elderly people lead satisfying and fulfilled lives. We need new technologies to help us address these problems and, for sure, software will play a central role in these technologies. Software engineering is, therefore, a critically important technology for the future of mankind. We must continue to educate software engineers and develop the disci pline so that we can create more compleX software systems. Of course, there are still problems with software projects. Software is still sometimes late and costs more than expected. However, we should not let these problems conceal the real successes in software engineering and the impressive software engineering methods and tech nologies that have been developed. Software engineering is now such a huge area that it is impossible to cover the whole subject in one book. My focus, therefore, is on key topics that are fundamental."--p&#xE1;gina VI</subfield>
  </datafield>
  <datafield tag="521" ind1="3" ind2=" ">
    <subfield code="a">Material bibliogr&#xE1;fico para estudiantes universitarios, docentes e investigadores.</subfield>
    <subfield code="b">PE-TmUNAS</subfield>
  </datafield>
  <datafield tag="526" ind1="0" ind2=" ">
    <subfield code="a">Ingenier&#xED;a en Inform&#xE1;tica y Sistemas.</subfield>
  </datafield>
  <datafield tag="546" ind1=" " ind2=" ">
    <subfield code="a">En ingles. </subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">BK</subfield>
  </datafield>
  <datafield tag="998" ind1=" " ind2=" ">
    <subfield code="c">zmvv/bmsda/bmml/mrh</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">698</subfield>
    <subfield code="d">698</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">ddc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="8">Book</subfield>
    <subfield code="a">BCUNAS</subfield>
    <subfield code="b">BCUNAS</subfield>
    <subfield code="c">PROC</subfield>
    <subfield code="d">2020-03-03</subfield>
    <subfield code="e">Donaci&#xF3;n</subfield>
    <subfield code="o">005.1 SO697 2011</subfield>
    <subfield code="p">0009696</subfield>
    <subfield code="r">2020-03-03 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2020-03-03</subfield>
    <subfield code="y">BK</subfield>
    <subfield code="z">Pr&#xE9;stamo en Sala </subfield>
  </datafield>
</record>
