|
|
|
|
| LEADER |
02958nmm a2200397 u 4500 |
| 001 |
EB002200343 |
| 003 |
EBX01000000000000001337546 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
240402 ||| jpn |
| 020 |
|
|
|a 9784814400607
|
| 050 |
|
4 |
|a QA76.76.S65
|
| 100 |
1 |
|
|a Ciceri, Christian
|
| 130 |
0 |
|
|a Software architecture metrics
|
| 245 |
0 |
0 |
|a Sofutowea ākitekucha metorikusu
|b ākitekucha hinshitsu o kaizensuru 10 no adobaisu = Software architecture metrics : case studies to improve the quality of your architecture
|c Christian Ciceri, Dave Farley, Neal Ford, Andrew Harmel-Law, Michael Keeling, Carola Lilienthal, João Rosa, Alexander von Zitzewitz, Rene Weiss, Eoin Woods cho ; Shimada Kōji yaku
|
| 246 |
3 |
1 |
|a Software architecture metrics
|
| 250 |
|
|
|a Shohan
|
| 260 |
|
|
|a Tōkyō-to Shinjuku-ku
|b Orairī Japan
|c 2024
|
| 300 |
|
|
|a 276 pages
|
| 505 |
0 |
|
|a Includes bibliographical references
|
| 653 |
|
|
|a Software measurement / Case studies
|
| 653 |
|
|
|a Software architecture / http://id.loc.gov/authorities/subjects/sh2004001071
|
| 653 |
|
|
|a Architecture logicielle
|
| 653 |
|
|
|a Mesure du logiciel / Études de cas
|
| 653 |
|
|
|a Sofutōea kōgaku / jlabsh/4
|
| 700 |
1 |
|
|a Farley, Dave
|e author
|
| 700 |
1 |
|
|a Ford, Neal
|e author
|
| 700 |
1 |
|
|a Harmel-Law, Andrew
|e author
|
| 041 |
0 |
7 |
|a jpn
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 776 |
|
|
|z 9784814400607
|
| 776 |
|
|
|z 4814400608
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9784814400607/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 005.1/4
|
| 082 |
0 |
|
|a 001.4
|
| 520 |
|
|
|a Software architecture metrics are key to the maintainability and architectural quality of a software project and they can warn you about dangerous accumulations of architectural and technical debt early in the process. In this practical book, leading hands-on software architects share case studies to introduce metrics that every software architect should know. This isn't a book about theory. It's more about practice and implementation, about what has already been tried and worked. Detecting software architectural issues early is crucial for the success of your software: it helps mitigate the risk of poor performance and lowers the cost of repairing those issues. Written by practitioners for software architects and software developers eager to explore successful case studies, this guide will help you learn more about decision and measurement effectiveness. Through contributions from 10 prominent practitioners, this book shares key software architecture metrics to help you set the right KPIs and measure the results. You'll learn how to: measure how well your software architecture is meeting your goals, choose the right metrics to track (and skip the ones you don't need), improve observability, testability, and deployability, prioritize software architecture projects, and build insightful and relevant dashboards--Publisher's description
|