|
|
|
|
| LEADER |
04413nmm a2200433 u 4500 |
| 001 |
EB001918853 |
| 003 |
EBX01000000000000001081755 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 020 |
|
|
|a 0124105076
|
| 020 |
|
|
|a 9780124105072
|
| 020 |
|
|
|a 0124104649
|
| 020 |
|
|
|a 9781306859769
|
| 020 |
|
|
|a 130685976X
|
| 050 |
|
4 |
|a QA76.76.D47
|
| 100 |
1 |
|
|a Mistrík, Ivan
|
| 245 |
0 |
0 |
|a Economics-Driven Software Architecture
|
| 260 |
|
|
|b Morgan Kaufmann
|c 2014
|
| 300 |
|
|
|a 1 online resource
|
| 505 |
0 |
|
|a About the AuthorReferences -- Preface -- Introduction -- Issues in economics-based and value-oriented software design -- Book overview -- Part 1�Fundamentals -- Part 2�Economics-driven architecting: design mechanisms and evaluation -- Part 3�Managing architectural economics -- Part 4�Linking architecture inception and evolution to economics: experiences and approaches -- Reference -- 1 Economics-Driven Software Architecture: Introduction -- 1.1 Introduction -- 1.2 Architecture and project management -- 1.3 Architecture-based economic modeling
|
| 505 |
0 |
|
|a Front Cover -- Economics-Driven Software Architecture -- Copyright Page -- Contents -- Acknowledgments -- About the Editors -- List of Contributors -- Foreword by John Grundy Economics-Driven Software Architecting -- Requirements impact on architecture economics -- Technology impact on architecture economics -- Environmental impact on architecture economics -- Process impact on architecture economics -- Team impact on architecture economics -- Business impact on architecture economics -- About the Author -- References -- Foreword by Len Bass
|
| 505 |
0 |
|
|a 2.5.4 Issue-based variability management2.5.5 Value-based portfolio optimization -- 2.5.6 Discussion and summary -- 2.6 Discussion on architectural issues -- 2.7 Related work -- 2.8 Conclusion -- References -- 3 Aspects of Software Valuation -- 3.1 Introduction -- 3.2 Basics of economic analysis -- 3.3 Valuation of software -- 3.3.1 Valuating a commercial software product -- 3.3.2 Valuating in-house (Internally Developed) software -- 3.3.3 Generalizing the valuation approach -- 3.4 Capitalize software investments or not? -- 3.4.1 What is capitalization?
|
| 505 |
0 |
|
|a 1.4 Architecture-based benefit modeling1.5 Architecture and risk management -- 1.6 Architecture and agility -- 1.7 Runtime economics-driven architecting -- 1.8 Final thoughts -- References -- I: Fundamentals of Economics-Driven Software Architecture -- 2 Economic Models and Value-Based Approaches for Product Line Architectures -- 2.1 Introduction -- 2.2 Background -- 2.2.1 Fundamentals of SPLE -- 2.2.2 Economic models -- 2.2.3 Software architecture -- 2.3 Research framework -- 2.4 Economic models for software product lines
|
| 505 |
0 |
|
|a Includes bibliographical references and indexes
|
| 653 |
|
|
|a Wirtschaftlichkeit / gnd / http://d-nb.info/gnd/4066424-7
|
| 653 |
|
|
|a Computer software / Development / http://id.loc.gov/authorities/subjects/sh85029535
|
| 653 |
|
|
|a Computer software / Development / fast
|
| 653 |
|
|
|a Smith, Glen / gnd
|
| 653 |
|
|
|a Softwareentwicklung / gnd
|
| 700 |
1 |
|
|a Mistrík, Ivan
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 776 |
|
|
|z 9780124104648
|
| 776 |
|
|
|z 9781306859769
|
| 776 |
|
|
|z 130685976X
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9780124104648/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 005.3
|
| 520 |
|
|
|a This is a guide for engineers and architects who need to understand the economic impact of architecture design decisions such as the long term and strategic viability, cost-effectiveness, and sustainability of applications and systems. It covers how to apply economic considerations during the software architecting activities of a project as well as shows the architecture-centric approaches to development and systematic evolution, where managing complexity, cost reduction, risk mitigation, evolvability, strategic planning and long-term value creation are among the major drivers for adopting such approaches. It assists the objective assessment of the lifetime costs and benefits of evolving systems, and the identification of legacy situations. Such consideration will form the scientific foundation for reasoning about the economics of nonfunctional requirements in the context of architectures and architecting. --
|