|
Showing 1 - 2 of
2 matches in All Departments
|
Software Architecture - 14th European Conference, ECSA 2020, L'Aquila, Italy, September 14-18, 2020, Proceedings (Paperback, 1st ed. 2020)
Anton Jansen, Ivano Malavolta, Henry Muccini, Ipek Ozkaya, Olaf Zimmermann
|
R1,525
Discovery Miles 15 250
|
Out of stock
|
This book constitutes the refereed proceedings of the 14th
International Conference on Software Architecture, ECSA 2020, held
in A'quila, Italy, in September 2020. In the Research Track, 12
full papers presented together with 5 short papers were carefully
reviewed and selected from 103 submissions. They are organized in
topical sections as follows: microservices; uncertainty,
self-adaptive, and open systems; model-based approaches;
performance and security engineering; architectural smells and
source code analysis; education and training; experiences and
learnings from industrial case studies; and architecting
contemporary distributed systems. In the Industrial Track, 11
submissions were received and 6 were accepted to form part of these
proceedings. In addition the book contains 3 keynote talks. Due to
the Corona pandemic ECSA 2020 was held as an virtual event.
"This is an incredibly wise and useful book. The authors have
considerable real-world experience in delivering quality systems
that matter, and their expertise shines through in these pages.
Here you will learn what technical debt is, what is it not, how to
manage it, and how to pay it down in responsible ways. This is a
book I wish I had when I was just beginning my career. The authors
present a myriad of case studies, born from years of experience,
and offer a multitude of actionable insights for how to apply it to
your project." -Grady Booch, IBM Fellow Master Best Practices for
Managing Technical Debt to Promote Software Quality and
Productivity As software systems mature, earlier design or code
decisions made in the context of budget or schedule constraints
increasingly impede evolution and innovation. This phenomenon is
called technical debt, and practical solutions exist. In Managing
Technical Debt, three leading experts introduce integrated,
empirically developed principles and practices that any software
professional can use to gain control of technical debt in any
software system. Using real-life examples, the authors explain the
forms of technical debt that afflict software-intensive systems,
their root causes, and their impacts. They introduce proven
approaches for identifying and assessing specific sources of
technical debt, limiting new debt, and "paying off" debt over time.
They describe how to establish managing technical debt as a core
software engineering practice in your organization. Discover how
technical debt damages manageability, quality, productivity, and
morale-and what you can do about it Clarify root causes of debt,
including the linked roles of business goals, source code,
architecture, testing, and infrastructure Identify technical debt
items, and analyze their costs so you can prioritize action Choose
the right solution for each technical debt item: eliminate, reduce,
or mitigate Integrate software engineering practices that minimize
new debt Managing Technical Debt will be a valuable resource for
every software professional who wants to accelerate innovation in
existing systems, or build new systems that will be easier to
maintain and evolve.
|
|