Dr. Gernot Starke - arc42 by Example: Software architecture documentation in practice
Here you can read online Dr. Gernot Starke - arc42 by Example: Software architecture documentation in practice full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2019, publisher: Packt Publishing, genre: Home and family. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:arc42 by Example: Software architecture documentation in practice
- Author:
- Publisher:Packt Publishing
- Genre:
- Year:2019
- Rating:5 / 5
- Favourites:Add to favourites
- Your mark:
arc42 by Example: Software architecture documentation in practice: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "arc42 by Example: Software architecture documentation in practice" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Document the architecture of your software easily with this highly practical, open-source template.
Key Features
- Learn the concepts of software architecture documentation through real-world examples
- Discover techniques to create compact, helpful, and easy-to-read documentation
Book Description
When developers document the architecture of their systems, they often invent their own specific ways of articulating structures, designs, concepts, and decisions. What they need is a template that enables simple and efficient software architecture documentation. arc42 by Example shows how its done through several real-world examples.
Each example in the book, whether it is a chess engine, a huge CRM system, or a cool web system, starts with a brief description of the problem domain and the quality requirements. Then, youll discover the system context with all the external interfaces. Youll dive into an overview of the solution strategy to implement the building blocks and runtime scenarios. The later chapters also explain various cross-cutting concerns and how they affect other aspects of a program.
What you will learn
- Utilize arc42 to document a systems physical infrastructure
- Learn how to identify a systems scope and boundaries
- Break a system down into building blocks and illustrate the relationships between them
- Discover how to describe the runtime behavior of a system
- Know how to document design decisions and their reasons
- Explore the risks and technical debt of your system
Who this book is for
This book is for software developers and solutions architects who are looking for an easy, open-source tool to document their systems. It is a useful reference for those who are already using arc42. If you are new to arc42, this book is a great learning resource. For those of you who want to write better technical documentation will benefit from the general concepts covered in this book.
Dr. Gernot Starke: author's other books
Who wrote arc42 by Example: Software architecture documentation in practice? Find out the surname, the name of the author of the book and a list of all author's works by series.
arc42 by Example: Software architecture documentation in practice — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "arc42 by Example: Software architecture documentation in practice" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
Software architecture documentation in practice
Dr. Gernot Starke
Michael Simons
Stefan Zrner
Ralf D. Mller
Copyright 2019 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book.
Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information.
Authors: Dr. Gernot Starke, Michael Simons, Stefan Zrner, and Ralf D. Mller
Managing Editor: Snehal Tambe
Acquisitions Editor: Bridget Neale
Production Editor: Samita Warang
Editorial Board: Shubhopriya Banerjee, Bharat Botle, Ewan Buckingham, Mahesh Dhyani, Taabish Khan, Manasa Kumar, Alex Mazonowicz, Bridget Neale, Dominic Pereira, Shiny Poojary, Erol Staveley, Ankita Thakur, Nitesh Thakur, and Jonathan Wray
First Published: October 2019
Production Reference: 1041019
ISBN: 978-1-83921-435-6
Published by Packt Publishing Ltd.
Livery Place, 35 Livery Street
Birmingham B3 2PB, UK
Dr. Gernot Starke
Long ago, on a winter's day in 2004, I sat together with Peter Hruschka, a long-time friend of mine and discussed one of our mutual favorite subjects the structure and concepts of software systems. We reflected on an issue we had both encountered often within our work, independent of client, domain, or technology: developers know their way around implementation/technologies; managers know their way around budgets and risk management. But when forced to communicate (or even document) the architecture of systems, they often start inventing their own specific ways of articulating structures, designs, concepts, and decisions.
Font size:
Interval:
Bookmark:
Similar books «arc42 by Example: Software architecture documentation in practice»
Look at similar books to arc42 by Example: Software architecture documentation in practice. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book arc42 by Example: Software architecture documentation in practice and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.