Skip to Main Content
Software Essentials
book

Software Essentials

by Adair Dingle
July 2014
Intermediate to advanced content levelIntermediate to advanced
436 pages
12h 27m
English
Chapman and Hall/CRC
Content preview from Software Essentials
Design and Documentation 139
expected use of subordinate data structures, legal values of data elds,
ownership responsibilities, relationships between elds (e.g., inven-
tory value drives commission percentage), and bookkeeping details.
Reasonable examples of implementation invariants include: interface of
subobject echoed for utility; linked list structure used to support frequent
modication of sorted data; internal (static) registry guarantees unique
ID. By identifying implementation structures and design constraints,
implementation invariants communicate design intent, and prioritization
of requirements.
Class integrity can be more easily maintained when implementation pri-
orities and details are clearly specied. What happens whe ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Software Architect’s Handbook

Software Architect’s Handbook

Joseph Ingeno
Economics-Driven Software Architecture

Economics-Driven Software Architecture

Ivan Mistrik, Rami Bahsoon, Rick Kazman, Yuanyuan Zhang
Software Architect Bootcamp

Software Architect Bootcamp

Raphael Malveau, Ph.D. Thomas J. Mowbray

Publisher Resources

ISBN: 9781439841204