Patterns of software construction: how to predictably build results
Master how to implement a repeatable software construction system. This book closely examines how a system is designed to tie a series of activities together that are needed when building software-intensive systems. Software construction and operations don't get enough attention as a repeatable...
Gespeichert in:
1. Verfasser: | |
---|---|
Format: | Buch |
Sprache: | English |
Veröffentlicht: |
Berkeley, CA
Apress
[2022]
|
Ausgabe: | 1st ed |
Schlagworte: | |
Zusammenfassung: | Master how to implement a repeatable software construction system. This book closely examines how a system is designed to tie a series of activities together that are needed when building software-intensive systems. Software construction and operations don't get enough attention as a repeatable system. The world is stuck in agile backlog grooming sessions, and quality is not increasing. Companies' budgets are shrinking, and teams need a way to get more done with less, consistently. This topic is very relevant to our current economic conditions and continuing globalization trends. A reason we constantly need more hands-on-the-keyboards is because of all the waste created in development cycles. We need more literature on how to "do software" not just write software. These goals are accomplished using the concept of evolutions, much like the Navy SEALS train their team members. For LIFT, the evolutions are: Plan, Build, Test, Release, Operate and Manage. The entire purpose of the book is instructing professionals how to use these distinct evolutions while remaining agile. And then, inside of each evolution, to explicitly break down the inputs to the evolution, outputs and series of activities taking place. Patterns of Software Construction clearly outlines how together this becomes the system.What You Will Learn - Optimize each evolution of a software delivery cycle- Review best practices of planning, highest return in the build cycle, and ignored practices in test, release, and operate - Apply the highest return techniques during the software build evolutionWho This Book is ForManagers, developers, tech lead, team lead, aspiring engineer, department leaders in corporations, executives, small business owner, IT Director |
Beschreibung: | 145 Seiten Diagramme 250 grams |
ISBN: | 9781484279359 |
Internformat
MARC
LEADER | 00000nam a2200000 c 4500 | ||
---|---|---|---|
001 | BV048203242 | ||
003 | DE-604 | ||
005 | 20220622 | ||
007 | t | ||
008 | 220506s2022 |||| |||| 00||| eng d | ||
020 | |a 9781484279359 |c pbk |9 978-1-4842-7935-9 | ||
024 | 3 | |a 9781484279359 | |
035 | |a (OCoLC)1334043846 | ||
035 | |a (DE-599)BVBBV048203242 | ||
040 | |a DE-604 |b ger |e rda | ||
041 | 0 | |a eng | |
049 | |a DE-29T | ||
100 | 1 | |a Rylander, Stephen |4 aut | |
245 | 1 | 0 | |a Patterns of software construction |b how to predictably build results |c Stephen Rylander |
250 | |a 1st ed | ||
264 | 1 | |a Berkeley, CA |b Apress |c [2022] | |
264 | 4 | |c © 2022 | |
300 | |a 145 Seiten |b Diagramme |c 250 grams | ||
336 | |b txt |2 rdacontent | ||
337 | |b n |2 rdamedia | ||
338 | |b nc |2 rdacarrier | ||
520 | |a Master how to implement a repeatable software construction system. This book closely examines how a system is designed to tie a series of activities together that are needed when building software-intensive systems. Software construction and operations don't get enough attention as a repeatable system. The world is stuck in agile backlog grooming sessions, and quality is not increasing. Companies' budgets are shrinking, and teams need a way to get more done with less, consistently. This topic is very relevant to our current economic conditions and continuing globalization trends. A reason we constantly need more hands-on-the-keyboards is because of all the waste created in development cycles. We need more literature on how to "do software" not just write software. These goals are accomplished using the concept of evolutions, much like the Navy SEALS train their team members. For LIFT, the evolutions are: Plan, Build, Test, Release, Operate and Manage. The entire purpose of the book is instructing professionals how to use these distinct evolutions while remaining agile. And then, inside of each evolution, to explicitly break down the inputs to the evolution, outputs and series of activities taking place. Patterns of Software Construction clearly outlines how together this becomes the system.What You Will Learn - Optimize each evolution of a software delivery cycle- Review best practices of planning, highest return in the build cycle, and ignored practices in test, release, and operate - Apply the highest return techniques during the software build evolutionWho This Book is ForManagers, developers, tech lead, team lead, aspiring engineer, department leaders in corporations, executives, small business owner, IT Director | ||
650 | 4 | |a bicssc | |
650 | 4 | |a bisacsh | |
650 | 4 | |a Computer programs—Testing | |
650 | 4 | |a Software engineering—Management | |
650 | 4 | |a Computer programming | |
650 | 4 | |a Internet programming | |
650 | 4 | |a Software engineering | |
653 | |a Hardcover, Softcover / Informatik, EDV/Informatik | ||
776 | 0 | 8 | |i Erscheint auch als |n Online-Ausgabe |z 978-1-4842-7936-6 |
999 | |a oai:aleph.bib-bvb.de:BVB01-033584197 |
Datensatz im Suchindex
_version_ | 1804183969934082048 |
---|---|
adam_txt | |
any_adam_object | |
any_adam_object_boolean | |
author | Rylander, Stephen |
author_facet | Rylander, Stephen |
author_role | aut |
author_sort | Rylander, Stephen |
author_variant | s r sr |
building | Verbundindex |
bvnumber | BV048203242 |
ctrlnum | (OCoLC)1334043846 (DE-599)BVBBV048203242 |
edition | 1st ed |
format | Book |
fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>02975nam a2200409 c 4500</leader><controlfield tag="001">BV048203242</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20220622 </controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">220506s2022 |||| |||| 00||| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781484279359</subfield><subfield code="c">pbk</subfield><subfield code="9">978-1-4842-7935-9</subfield></datafield><datafield tag="024" ind1="3" ind2=" "><subfield code="a">9781484279359</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)1334043846</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV048203242</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-29T</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Rylander, Stephen</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Patterns of software construction</subfield><subfield code="b">how to predictably build results</subfield><subfield code="c">Stephen Rylander</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">1st ed</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Berkeley, CA</subfield><subfield code="b">Apress</subfield><subfield code="c">[2022]</subfield></datafield><datafield tag="264" ind1=" " ind2="4"><subfield code="c">© 2022</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">145 Seiten</subfield><subfield code="b">Diagramme</subfield><subfield code="c">250 grams</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Master how to implement a repeatable software construction system. This book closely examines how a system is designed to tie a series of activities together that are needed when building software-intensive systems. Software construction and operations don't get enough attention as a repeatable system. The world is stuck in agile backlog grooming sessions, and quality is not increasing. Companies' budgets are shrinking, and teams need a way to get more done with less, consistently. This topic is very relevant to our current economic conditions and continuing globalization trends. A reason we constantly need more hands-on-the-keyboards is because of all the waste created in development cycles. We need more literature on how to "do software" not just write software. These goals are accomplished using the concept of evolutions, much like the Navy SEALS train their team members. For LIFT, the evolutions are: Plan, Build, Test, Release, Operate and Manage. The entire purpose of the book is instructing professionals how to use these distinct evolutions while remaining agile. And then, inside of each evolution, to explicitly break down the inputs to the evolution, outputs and series of activities taking place. Patterns of Software Construction clearly outlines how together this becomes the system.What You Will Learn - Optimize each evolution of a software delivery cycle- Review best practices of planning, highest return in the build cycle, and ignored practices in test, release, and operate - Apply the highest return techniques during the software build evolutionWho This Book is ForManagers, developers, tech lead, team lead, aspiring engineer, department leaders in corporations, executives, small business owner, IT Director</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">bicssc</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer programs—Testing</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software engineering—Management</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer programming</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Internet programming</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software engineering</subfield></datafield><datafield tag="653" ind1=" " ind2=" "><subfield code="a">Hardcover, Softcover / Informatik, EDV/Informatik</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Online-Ausgabe</subfield><subfield code="z">978-1-4842-7936-6</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-033584197</subfield></datafield></record></collection> |
id | DE-604.BV048203242 |
illustrated | Not Illustrated |
index_date | 2024-07-03T19:47:13Z |
indexdate | 2024-07-10T09:31:54Z |
institution | BVB |
isbn | 9781484279359 |
language | English |
oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-033584197 |
oclc_num | 1334043846 |
open_access_boolean | |
owner | DE-29T |
owner_facet | DE-29T |
physical | 145 Seiten Diagramme 250 grams |
publishDate | 2022 |
publishDateSearch | 2022 |
publishDateSort | 2022 |
publisher | Apress |
record_format | marc |
spelling | Rylander, Stephen aut Patterns of software construction how to predictably build results Stephen Rylander 1st ed Berkeley, CA Apress [2022] © 2022 145 Seiten Diagramme 250 grams txt rdacontent n rdamedia nc rdacarrier Master how to implement a repeatable software construction system. This book closely examines how a system is designed to tie a series of activities together that are needed when building software-intensive systems. Software construction and operations don't get enough attention as a repeatable system. The world is stuck in agile backlog grooming sessions, and quality is not increasing. Companies' budgets are shrinking, and teams need a way to get more done with less, consistently. This topic is very relevant to our current economic conditions and continuing globalization trends. A reason we constantly need more hands-on-the-keyboards is because of all the waste created in development cycles. We need more literature on how to "do software" not just write software. These goals are accomplished using the concept of evolutions, much like the Navy SEALS train their team members. For LIFT, the evolutions are: Plan, Build, Test, Release, Operate and Manage. The entire purpose of the book is instructing professionals how to use these distinct evolutions while remaining agile. And then, inside of each evolution, to explicitly break down the inputs to the evolution, outputs and series of activities taking place. Patterns of Software Construction clearly outlines how together this becomes the system.What You Will Learn - Optimize each evolution of a software delivery cycle- Review best practices of planning, highest return in the build cycle, and ignored practices in test, release, and operate - Apply the highest return techniques during the software build evolutionWho This Book is ForManagers, developers, tech lead, team lead, aspiring engineer, department leaders in corporations, executives, small business owner, IT Director bicssc bisacsh Computer programs—Testing Software engineering—Management Computer programming Internet programming Software engineering Hardcover, Softcover / Informatik, EDV/Informatik Erscheint auch als Online-Ausgabe 978-1-4842-7936-6 |
spellingShingle | Rylander, Stephen Patterns of software construction how to predictably build results bicssc bisacsh Computer programs—Testing Software engineering—Management Computer programming Internet programming Software engineering |
title | Patterns of software construction how to predictably build results |
title_auth | Patterns of software construction how to predictably build results |
title_exact_search | Patterns of software construction how to predictably build results |
title_exact_search_txtP | Patterns of software construction how to predictably build results |
title_full | Patterns of software construction how to predictably build results Stephen Rylander |
title_fullStr | Patterns of software construction how to predictably build results Stephen Rylander |
title_full_unstemmed | Patterns of software construction how to predictably build results Stephen Rylander |
title_short | Patterns of software construction |
title_sort | patterns of software construction how to predictably build results |
title_sub | how to predictably build results |
topic | bicssc bisacsh Computer programs—Testing Software engineering—Management Computer programming Internet programming Software engineering |
topic_facet | bicssc bisacsh Computer programs—Testing Software engineering—Management Computer programming Internet programming Software engineering |
work_keys_str_mv | AT rylanderstephen patternsofsoftwareconstructionhowtopredictablybuildresults |