Software essentials: design and construction
"Preface Why this book? Why should you read this book? The short answer is to study software design from a structured but hands-on perspective and to understand different models of control flow, memory, dynamic behavior, extensibility, etc. Software complexity and the growing impact of legacy s...
Gespeichert in:
| Beteilige Person: | |
|---|---|
| Format: | Elektronisch E-Book |
| Sprache: | Englisch |
| Veröffentlicht: |
Boca Raton
Taylor & Francis
[2014]
|
| Schriftenreihe: | Chapman & Hall/CRC innovations in software engineering and software development
|
| Schlagwörter: | |
| Links: | https://learning.oreilly.com/library/view/-/9781439841204/?ar |
| Zusammenfassung: | "Preface Why this book? Why should you read this book? The short answer is to study software design from a structured but hands-on perspective and to understand different models of control flow, memory, dynamic behavior, extensibility, etc. Software complexity and the growing impact of legacy systems motivate a renewed interest in software design and modeling. We emphasize design (and construction) in this text, using and contrasting C♯ and C++. Many CS texts are 'learn to' books that focus on one programming language or tool. When perspective is so limited to a specific tool or programming language, high-level concepts are often slighted. Students may gain exposure to an idea via a 'cookbook' implementation and thus fail to truly absorb essential concepts. Students and/or practitioners can understand and apply design principles more readily when such concepts are explicitly defined and illustrated. Design, not just syntax, must be stressed. The progression of programming languages, software process methodologies and development tools continues to support abstraction: software developers should exploit this abstraction and solve problems (design) without being tied to a particular syntax or tool. Software design and modeling are neither new nor trendy topics. Software development often focuses on immediate effect: implement, test (minimally) and deploy. Yet, the complexity, scale and longevity of modern software require an intricate understanding of a software system as a whole -- components and relationships, user interfaces, persistent data, etc. To accommodate existing use while preserving longevity, a software developer must look forward for extensibility and backward for compatibility. Hence, software developers must understand software design."-- |
| Beschreibung: | Includes bibliographical references and index. - Print version record |
| Umfang: | 1 Online-Ressource (xxi, 413 Seiten) |
| ISBN: | 9781439841211 1439841217 9781439841204 |
Internformat
MARC
| LEADER | 00000cam a22000002 4500 | ||
|---|---|---|---|
| 001 | ZDB-30-ORH-051700867 | ||
| 003 | DE-627-1 | ||
| 005 | 20240228115600.0 | ||
| 007 | cr uuu---uuuuu | ||
| 008 | 200417s2014 xx |||||o 00| ||eng c | ||
| 020 | |a 9781439841211 |c electronic bk. |9 978-1-4398-4121-1 | ||
| 020 | |a 1439841217 |c electronic bk. |9 1-4398-4121-7 | ||
| 020 | |a 9781439841204 |9 978-1-4398-4120-4 | ||
| 035 | |a (DE-627-1)051700867 | ||
| 035 | |a (DE-599)KEP051700867 | ||
| 035 | |a (ORHE)9781439841204 | ||
| 035 | |a (DE-627-1)051700867 | ||
| 040 | |a DE-627 |b ger |c DE-627 |e rda | ||
| 041 | |a eng | ||
| 072 | 7 | |a COM |2 bisacsh | |
| 082 | 0 | |a 005.1/2 |2 23 | |
| 100 | 1 | |a Dingle, Adair |e VerfasserIn |4 aut | |
| 245 | 1 | 0 | |a Software essentials |b design and construction |c Adair Dingle |
| 264 | 1 | |a Boca Raton |b Taylor & Francis |c [2014] | |
| 264 | 4 | |c ©20 | |
| 264 | 4 | |c ©2014 | |
| 300 | |a 1 Online-Ressource (xxi, 413 Seiten) | ||
| 336 | |a Text |b txt |2 rdacontent | ||
| 337 | |a Computermedien |b c |2 rdamedia | ||
| 338 | |a Online-Ressource |b cr |2 rdacarrier | ||
| 490 | 0 | |a Chapman & Hall/CRC innovations in software engineering and software development | |
| 500 | |a Includes bibliographical references and index. - Print version record | ||
| 520 | |a "Preface Why this book? Why should you read this book? The short answer is to study software design from a structured but hands-on perspective and to understand different models of control flow, memory, dynamic behavior, extensibility, etc. Software complexity and the growing impact of legacy systems motivate a renewed interest in software design and modeling. We emphasize design (and construction) in this text, using and contrasting C♯ and C++. Many CS texts are 'learn to' books that focus on one programming language or tool. When perspective is so limited to a specific tool or programming language, high-level concepts are often slighted. Students may gain exposure to an idea via a 'cookbook' implementation and thus fail to truly absorb essential concepts. Students and/or practitioners can understand and apply design principles more readily when such concepts are explicitly defined and illustrated. Design, not just syntax, must be stressed. The progression of programming languages, software process methodologies and development tools continues to support abstraction: software developers should exploit this abstraction and solve problems (design) without being tied to a particular syntax or tool. Software design and modeling are neither new nor trendy topics. Software development often focuses on immediate effect: implement, test (minimally) and deploy. Yet, the complexity, scale and longevity of modern software require an intricate understanding of a software system as a whole -- components and relationships, user interfaces, persistent data, etc. To accommodate existing use while preserving longevity, a software developer must look forward for extensibility and backward for compatibility. Hence, software developers must understand software design."-- | ||
| 650 | 0 | |a Software architecture | |
| 650 | 0 | |a Computer software |x Development | |
| 650 | 4 | |a Architecture logicielle | |
| 650 | 4 | |a COMPUTERS ; Software Development & Engineering ; General | |
| 650 | 4 | |a COMPUTERS ; Programming ; Algorithms | |
| 650 | 4 | |a Computer software ; Development | |
| 650 | 4 | |a Software architecture | |
| 776 | 1 | |z 9781439841204 | |
| 776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe |z 9781439841204 |
| 966 | 4 | 0 | |l DE-91 |p ZDB-30-ORH |q TUM_PDA_ORH |u https://learning.oreilly.com/library/view/-/9781439841204/?ar |m X:ORHE |x Aggregator |z lizenzpflichtig |3 Volltext |
| 912 | |a ZDB-30-ORH | ||
| 912 | |a ZDB-30-ORH | ||
| 951 | |a BO | ||
| 912 | |a ZDB-30-ORH | ||
| 049 | |a DE-91 | ||
Datensatz im Suchindex
| DE-BY-TUM_katkey | ZDB-30-ORH-051700867 |
|---|---|
| _version_ | 1821494841295503360 |
| adam_text | |
| any_adam_object | |
| author | Dingle, Adair |
| author_facet | Dingle, Adair |
| author_role | aut |
| author_sort | Dingle, Adair |
| author_variant | a d ad |
| building | Verbundindex |
| bvnumber | localTUM |
| collection | ZDB-30-ORH |
| ctrlnum | (DE-627-1)051700867 (DE-599)KEP051700867 (ORHE)9781439841204 |
| dewey-full | 005.1/2 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.1/2 |
| dewey-search | 005.1/2 |
| dewey-sort | 15.1 12 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>03620cam a22005172 4500</leader><controlfield tag="001">ZDB-30-ORH-051700867</controlfield><controlfield tag="003">DE-627-1</controlfield><controlfield tag="005">20240228115600.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">200417s2014 xx |||||o 00| ||eng c</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781439841211</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">978-1-4398-4121-1</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1439841217</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">1-4398-4121-7</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781439841204</subfield><subfield code="9">978-1-4398-4120-4</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)051700867</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)KEP051700867</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ORHE)9781439841204</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)051700867</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="072" ind1=" " ind2="7"><subfield code="a">COM</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.1/2</subfield><subfield code="2">23</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Dingle, Adair</subfield><subfield code="e">VerfasserIn</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Software essentials</subfield><subfield code="b">design and construction</subfield><subfield code="c">Adair Dingle</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Boca Raton</subfield><subfield code="b">Taylor & Francis</subfield><subfield code="c">[2014]</subfield></datafield><datafield tag="264" ind1=" " ind2="4"><subfield code="c">©20</subfield></datafield><datafield tag="264" ind1=" " ind2="4"><subfield code="c">©2014</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource (xxi, 413 Seiten)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">Computermedien</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="490" ind1="0" ind2=" "><subfield code="a">Chapman & Hall/CRC innovations in software engineering and software development</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Includes bibliographical references and index. - Print version record</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">"Preface Why this book? Why should you read this book? The short answer is to study software design from a structured but hands-on perspective and to understand different models of control flow, memory, dynamic behavior, extensibility, etc. Software complexity and the growing impact of legacy systems motivate a renewed interest in software design and modeling. We emphasize design (and construction) in this text, using and contrasting C♯ and C++. Many CS texts are 'learn to' books that focus on one programming language or tool. When perspective is so limited to a specific tool or programming language, high-level concepts are often slighted. Students may gain exposure to an idea via a 'cookbook' implementation and thus fail to truly absorb essential concepts. Students and/or practitioners can understand and apply design principles more readily when such concepts are explicitly defined and illustrated. Design, not just syntax, must be stressed. The progression of programming languages, software process methodologies and development tools continues to support abstraction: software developers should exploit this abstraction and solve problems (design) without being tied to a particular syntax or tool. Software design and modeling are neither new nor trendy topics. Software development often focuses on immediate effect: implement, test (minimally) and deploy. Yet, the complexity, scale and longevity of modern software require an intricate understanding of a software system as a whole -- components and relationships, user interfaces, persistent data, etc. To accommodate existing use while preserving longevity, a software developer must look forward for extensibility and backward for compatibility. Hence, software developers must understand software design."--</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Software architecture</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Computer software</subfield><subfield code="x">Development</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Architecture logicielle</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">COMPUTERS ; Software Development & Engineering ; General</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">COMPUTERS ; Programming ; Algorithms</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer software ; Development</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software architecture</subfield></datafield><datafield tag="776" ind1="1" ind2=" "><subfield code="z">9781439841204</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druck-Ausgabe</subfield><subfield code="z">9781439841204</subfield></datafield><datafield tag="966" ind1="4" ind2="0"><subfield code="l">DE-91</subfield><subfield code="p">ZDB-30-ORH</subfield><subfield code="q">TUM_PDA_ORH</subfield><subfield code="u">https://learning.oreilly.com/library/view/-/9781439841204/?ar</subfield><subfield code="m">X:ORHE</subfield><subfield code="x">Aggregator</subfield><subfield code="z">lizenzpflichtig</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">BO</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91</subfield></datafield></record></collection> |
| id | ZDB-30-ORH-051700867 |
| illustrated | Not Illustrated |
| indexdate | 2025-01-17T11:20:47Z |
| institution | BVB |
| isbn | 9781439841211 1439841217 9781439841204 |
| language | English |
| open_access_boolean | |
| owner | DE-91 DE-BY-TUM |
| owner_facet | DE-91 DE-BY-TUM |
| physical | 1 Online-Ressource (xxi, 413 Seiten) |
| psigel | ZDB-30-ORH TUM_PDA_ORH ZDB-30-ORH |
| publishDate | 2014 |
| publishDateSearch | 2014 |
| publishDateSort | 2014 |
| publisher | Taylor & Francis |
| record_format | marc |
| series2 | Chapman & Hall/CRC innovations in software engineering and software development |
| spelling | Dingle, Adair VerfasserIn aut Software essentials design and construction Adair Dingle Boca Raton Taylor & Francis [2014] ©20 ©2014 1 Online-Ressource (xxi, 413 Seiten) Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier Chapman & Hall/CRC innovations in software engineering and software development Includes bibliographical references and index. - Print version record "Preface Why this book? Why should you read this book? The short answer is to study software design from a structured but hands-on perspective and to understand different models of control flow, memory, dynamic behavior, extensibility, etc. Software complexity and the growing impact of legacy systems motivate a renewed interest in software design and modeling. We emphasize design (and construction) in this text, using and contrasting C♯ and C++. Many CS texts are 'learn to' books that focus on one programming language or tool. When perspective is so limited to a specific tool or programming language, high-level concepts are often slighted. Students may gain exposure to an idea via a 'cookbook' implementation and thus fail to truly absorb essential concepts. Students and/or practitioners can understand and apply design principles more readily when such concepts are explicitly defined and illustrated. Design, not just syntax, must be stressed. The progression of programming languages, software process methodologies and development tools continues to support abstraction: software developers should exploit this abstraction and solve problems (design) without being tied to a particular syntax or tool. Software design and modeling are neither new nor trendy topics. Software development often focuses on immediate effect: implement, test (minimally) and deploy. Yet, the complexity, scale and longevity of modern software require an intricate understanding of a software system as a whole -- components and relationships, user interfaces, persistent data, etc. To accommodate existing use while preserving longevity, a software developer must look forward for extensibility and backward for compatibility. Hence, software developers must understand software design."-- Software architecture Computer software Development Architecture logicielle COMPUTERS ; Software Development & Engineering ; General COMPUTERS ; Programming ; Algorithms Computer software ; Development 9781439841204 Erscheint auch als Druck-Ausgabe 9781439841204 |
| spellingShingle | Dingle, Adair Software essentials design and construction Software architecture Computer software Development Architecture logicielle COMPUTERS ; Software Development & Engineering ; General COMPUTERS ; Programming ; Algorithms Computer software ; Development |
| title | Software essentials design and construction |
| title_auth | Software essentials design and construction |
| title_exact_search | Software essentials design and construction |
| title_full | Software essentials design and construction Adair Dingle |
| title_fullStr | Software essentials design and construction Adair Dingle |
| title_full_unstemmed | Software essentials design and construction Adair Dingle |
| title_short | Software essentials |
| title_sort | software essentials design and construction |
| title_sub | design and construction |
| topic | Software architecture Computer software Development Architecture logicielle COMPUTERS ; Software Development & Engineering ; General COMPUTERS ; Programming ; Algorithms Computer software ; Development |
| topic_facet | Software architecture Computer software Development Architecture logicielle COMPUTERS ; Software Development & Engineering ; General COMPUTERS ; Programming ; Algorithms Computer software ; Development |
| work_keys_str_mv | AT dingleadair softwareessentialsdesignandconstruction |