國立高雄大學圖資館 |

Language: English

Back

Patterns of software constructionhow to predictably build results /

Record Type:	Electronic resources : Monograph/item
Title/Author:	Patterns of software constructionby Stephen Rylander.
Reminder of title:	how to predictably build results /
Author:	Rylander, Stephen.
Published:	Berkeley, CA :Apress :2022.
Description:	ix, 145 p. :ill., digital ;24 cm.
Contained By:	Springer Nature eBook
Subject:	Software engineering.
Online resource:	https://doi.org/10.1007/978-1-4842-7936-6
ISBN:	9781484279366$q(electronic bk.)

Patterns of software constructionhow to predictably build results /
Rylander, Stephen.

Patterns of software constructionhow to predictably build results /[electronic resource] :by Stephen Rylander. - Berkeley, CA :Apress :2022. - ix, 145 p. :ill., digital ;24 cm.

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$q(electronic bk.)

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

184729
Software engineering.

LC Class. No.: QA76.758 / .R95 2022

Dewey Class. No.: 005.1

Patterns of software constructionhow to predictably build results /
LDR:02776nmm a2200325 a 4500 001 623454
003 DE-He213
005 20220228154607.0
006 m d
007 cr nn 008maaau
008 221209s2022 cau s 0 eng d
020 $a 9781484279366$q(electronic bk.)
020 $a 9781484279359$q(paper)
024 7 $a 10.1007/978-1-4842-7936-6 $2 doi
035 $a 978-1-4842-7936-6
040 $a GP $c GP
041 0 $a eng
050 4 $a QA76.758 $b .R95 2022
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
090 $a QA76.758 $b .R994 2022
100 1 $a Rylander, Stephen. $3 925675
245 1 0 $a Patterns of software construction $h [electronic resource] : $b how to predictably build results / $c by Stephen Rylander.
260 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2022.
300 $a ix, 145 p. : $b ill., digital ; $c 24 cm.
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 0 $a Software engineering. $3 184729
650 0 $a Software architecture. $3 230927
650 2 4 $a Software Testing. $3 925676
650 2 4 $a Software Management. $3 715554
650 2 4 $a Programming Techniques. $3 274470
650 2 4 $a Web Development. $3 760534
710 2 $a SpringerLink (Online service) $3 273601
773 0 $t Springer Nature eBook
856 4 0 $u https://doi.org/10.1007/978-1-4842-7936-6
950 $a Professional and Applied Computing (SpringerNature-12059)