國立虎尾科技大學 |

Patterns of Software Construction = How to Predictably Build Results /

紀錄類型:	書目-語言資料,印刷品 : Monograph/item
正題名/作者:	Patterns of Software Construction/ by Stephen Rylander.
其他題名:	How to Predictably Build Results /
作者:	Rylander, Stephen.
面頁冊數:	IX, 145 p. 41 illus.online resource. :
Contained By:	Springer Nature eBook
標題:	Web Development. -
電子資源:	https://doi.org/10.1007/978-1-4842-7936-6
ISBN:	9781484279366

Patterns of Software Construction = How to Predictably Build Results /
Rylander, Stephen.

Patterns of Software ConstructionHow to Predictably Build Results /[electronic resource] :by Stephen Rylander. - 1st ed. 2022. - IX, 145 p. 41 illus.online resource.

Chapter 1: Patterns -- Chapter 2 Getting Started -- Chapter 3: Plan -- Chapter 4: Build -- Chapter 5: Test -- Chapter 6: Release- Chapter 7: Operate -- Chapter 8: Manage -- Chapter 9:Summary.

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. You will: 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 evolution.

ISBN: 9781484279366

Standard No.: 10.1007/978-1-4842-7936-6doiSubjects--Topical Terms:

1114136
Web Development.

LC Class. No.: QA76.758

Dewey Class. No.: 005.1

Patterns of Software Construction = How to Predictably Build Results /
LDR:03111nam a22003975i 4500 001 1088636
003 DE-He213
005 20220512145748.0
007 cr nn 008mamaa
008 221228s2022 xxu| s |||| 0|eng d
020 $a 9781484279366 $9 978-1-4842-7936-6
024 7 $a 10.1007/978-1-4842-7936-6 $2 doi
035 $a 978-1-4842-7936-6
050 4 $a QA76.758
072 7 $a UMZ $2 bicssc
072 7 $a COM051230 $2 bisacsh
072 7 $a UMZ $2 thema
082 0 4 $a 005.1 $2 23
100 1 $a Rylander, Stephen. $e author. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1395832
245 1 0 $a Patterns of Software Construction $h [electronic resource] : $b How to Predictably Build Results / $c by Stephen Rylander.
250 $a 1st ed. 2022.
264 1 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2022.
300 $a IX, 145 p. 41 illus. $b online resource.
336 $a text $b txt $2 rdacontent
337 $a computer $b c $2 rdamedia
338 $a online resource $b cr $2 rdacarrier
347 $a text file $b PDF $2 rda
505 0 $a Chapter 1: Patterns -- Chapter 2 Getting Started -- Chapter 3: Plan -- Chapter 4: Build -- Chapter 5: Test -- Chapter 6: Release- Chapter 7: Operate -- Chapter 8: Manage -- Chapter 9:Summary.
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. You will: 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 evolution.
650 2 4 $a Web Development. $3 1114136
650 2 4 $a Programming Techniques. $3 669781
650 2 4 $a Software Management. $3 1069200
650 2 4 $a Software Testing. $3 1394505
650 1 4 $a Software Engineering. $3 669632
650 0 $a Internet programming. $3 565353
650 0 $a Computer programming. $3 527822
650 0 $a Software engineering—Management. $3 1366259
650 0 $a Computer programs—Testing. $3 1394504
650 0 $a Software engineering. $3 562952
710 2 $a SpringerLink (Online service) $3 593884
773 0 $t Springer Nature eBook
776 0 8 $i Printed edition: $z 9781484279359
776 0 8 $i Printed edition: $z 9781484279373
776 0 8 $i Printed edition: $z 9781484285329
856 4 0 $u https://doi.org/10.1007/978-1-4842-7936-6
912 $a ZDB-2-CWD
912 $a ZDB-2-SXPC
950 $a Professional and Applied Computing (SpringerNature-12059)
950 $a Professional and Applied Computing (R0) (SpringerNature-43716)