MARC details
| 000 -LEADER |
|---|
| fixed length control field |
02397nam a22002057a 4500 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
|---|
| fixed length control field |
240123b2022 |||||||| |||| 00| 0 eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
9781484285329 |
| 082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER |
|---|
| Classification number |
005.1 RYL-S |
| 100 ## - MAIN ENTRY--PERSONAL NAME |
|---|
| Personal name |
Rylander, Stephen |
| 245 ## - TITLE STATEMENT |
|---|
| Title |
Pattern of software construction : |
| Remainder of title |
how to predictably build results / |
| Statement of responsibility, etc. |
Stephen Rylander |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) |
|---|
| Place of publication, distribution, etc. |
New York |
| Name of publisher, distributor, etc. |
Springer Science Business Media |
| Date of publication, distribution, etc. |
2022 |
| 300 ## - PHYSICAL DESCRIPTION |
|---|
| Extent |
145p. |
| 500 ## - GENERAL NOTE |
|---|
| General note |
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 evolution Who This Book is For Managers, developers, tech lead, team lead, aspiring engineer, department leaders in corporations, executives, small business owner, IT Director |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Software engineering |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Software architecture |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Software engineering--Management |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Computer programming |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Computer programs--Testing |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Internet programming |
| 952 ## - LOCATION AND ITEM INFORMATION (KOHA) |
|---|
| Withdrawn status |
|
