Building Maintainable Software-java篇之Couple Architecture Components Loosely
There are two ways of constructing a software design: one way is to make it so simple
that there are obviously no deficiencies, and the other way is to make it so complicated
that there are no obvious deficiencies.
—C.A.R. Hoare
Guideline:
• Achieve loose coupling between top-level components.
• Do this by minimizing the relative amount of code within modules that is exposed to (i.e., can receive calls from) mod‐
ules in other components.
• This improves maintainability because independent components ease isolated maintenance.
Motivation
Low Component Dependence Allows for Isolated Maintenance
A low level of dependence means that changes can be made in an isolated manner.
This applies when most of a component’s code volume is either internal or outgoing.
Isolated maintenance means less work, as coding changes do not have effects outside
the functionality that you are modifying.
Low Component Dependence Separates Maintenance Responsibilities
If all components are independent from each other, it is easier to distribute responsi‐
bilities for maintenance among separate teams. This follows from the advantage of
isolated modification. Isolation is in fact a prerequisite for efficient division of devel‐
opment work among team members or among different teams.
By contrast, if components are tightly intertwined with each other, one cannot isolate
and separate maintenance responsibilities among teams, since the effects of modifica‐
tions will spill over to other teams. Aside from that code being hard to test, the effects
of modifications may also be unpredictable. So, dependencies may lead to inconsis‐
tencies, more time spent on communication between developers, and time wasted
waiting for others to complete their modifications.
Low Component Dependence Eases Testing
Code that has a low dependence on other components (modules with mainly internal
and outgoing code) is easier to test. For internal calls, functionality can be traced and
tested within the component. For outgoing calls, you do not need to mock or stub
functionality that is provided by other components (given that functionality in that
other component is finished).
How to Apply the Guideline
The following principles help you apply the guideline of this chapter:
• Limit the size of modules that are the component’s interface.
• Define component interfaces on a high level of abstraction. This limits the types
of requests that cross component borders. That avoids requests that “know too
much” about the implementation details.
• Avoid throughput code, because it has the most serious effect on testing func‐
tionality. In other words, avoid interface modules that put through calls to other
components. If throughput code exists, analyze the concerned modules in order
to solve calls that are put through to other components
Abstract Factory Design Pattern
Component independence reflects the high-level architecture of a software system.
However, this is not a book on software architecture. In this section, we discuss only
one design pattern that we frequently see applied in practice to successfully limit the
amount of interface code exposed by a component: the Abstract Factory design pat‐
tern. A system that is loosely coupled is characterized by relying more on contracts
and less on implementation details.
Many more design patterns and software architecture styles can help in keeping your
architecture components loosely coupled. An example is using a framework for
dependency injection (which allows Inversion of Control). For elaboration on other
patterns, we kindly direct you to the many great books on design patterns and soft‐
ware architecture (see, for example, “Related Books” on page xiv).
The Abstract Factory design pattern hides (or encapsulates) the creation of specific
“products” behind a generic “product factory” interface. In this context, products are
typically entities for which more than one variant exists.
读书笔记:
by Joost Visser
Copyright © 2016 Software Improvement Group, B.V. All rights reserved.
Printed in the United States of America.
Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472.
O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are
also available for most titles (http://safaribooksonline.com). For more information, contact our corporate/
institutional sales department: 800-998-9938 or corporate@oreilly.com.
Acquisitions Editor: Rachel Roumeliotis
Editor: Nan Barber
Production Editor: Matthew Hacker
Copyeditor: Rachel Monaghan
Proofreader: Marta Justak
Indexer: WordCo Indexing Services, Inc.
Interior Designer: David Futato
Cover Designer: Randy Comer
Illustrator: Rebecca Demarest
February 2016: First Edition
Revision History for the First Edition
2016-01-25: First Release
See http://shop.oreilly.com/product/0636920049159.do
Building Maintainable Software-java篇之Couple Architecture Components Loosely的更多相关文章
- Building Maintainable Software-java篇之Separate Concerns in Modules
Building Maintainable Software-java篇之Separate Concerns in Modules In a system that is both complex ...
- JSON总结(java篇)
JSON总结(java篇一) JSON简介 JSON(JavaScript Object Notation) 是一种轻量级的数据交换格式.它基于ECMAScript的一个子集. JSON采用完全独立于 ...
- [转]有哪些值得关注的技术博客(Java篇)
有哪些值得关注的技术博客(Java篇) 大部分程序员在自学的道路上不知道走了多少坑,这个视频那个网站搞得自己晕头转向.对我个人来说我平常在学习的过程中喜欢看一些教程式的博客.这些博客的特点: 1. ...
- 面试总结——Java篇
前言:前期对Java基础的相关知识点进行了总结,具体参看:Java基础和面试知识点.近期由于笔者正在换工作(ing),因此下面将笔者在面试过程中或笔者朋友面试过程中反馈的题目进行总结,相信弄清楚下面题 ...
- 事件驱动模型实例详解(Java篇)
或许每个软件从业者都有从学习控制台应用程序到学习可视化编程的转变过程,控制台应用程序的优点在于可以方便的练习某个语言的语法和开发习惯(如.net和java),而可视化编程的学习又可以非常方便开发出各类 ...
- Tools:downloading and Building EDK II工具篇:安装/使用EDKII源代码获取/编译工具[2.3]
Tools:Installing and using the Required Tools for downloading and Building EDK II工具篇:安装/使用EDKII源代码获取 ...
- 管中窥豹——框架下的SQL注入 Java篇
管中窥豹--框架下的SQL注入 Java篇 背景 SQL注入漏洞应该算是很有年代感的漏洞了,但是现在依然活跃在各大漏洞榜单中,究其原因还是数据和代码的问题. SQL 语句在DBMS系统中作为表达式被解 ...
- App 组件化/模块化之路——Android 框架组件(Android Architecture Components)使用指南
面对越来越复杂的 App 需求,Google 官方发布了Android 框架组件库(Android Architecture Components ).为开发者更好的开发 App 提供了非常好的样本. ...
- 安卓构架组件——概述 Android Architecture Components
谷歌官文文档地址:https://developer.android.google.cn/topic/libraries/architecture 安卓构架组建是库的集合:帮助你设计健壮的.易测试的. ...
随机推荐
- Java_注解之一
注解可以替换复杂的hbm.xml文件,使得程序的开发大大简化 @Override :子类重写父类方法 @Test :junit测试 @Before :测试之前执行 @SuppressWarnin ...
- 程序员的幽默-献给所有Java程序员
1. 一程序员去面试,面试官问:“你毕业才两年,这三年工作经验是怎么来的?!”程序员答:“加班.” 2. 某程序员对书法十分感兴趣,退休后决定在这方面有所建树.于是花重金购买了上等的文房四宝.一日,饭 ...
- win7 硬盘安装suse双系统启动顺序更改
使用win7硬盘安装suse双系统之后,首先面临的问题是,PC默认启动的系统更改的问题,有些人可能想默认启动是win7,只有在使用linux的时候在去选择suse系统,这里我告诉大家更改的办法: 首先 ...
- Redis主从复制失败(master_link_status:down)
今天配置redis主从复制时出现master_link_status:down提示. 首先打开slave的redis.conf配置文件,确定slaveof 和masterauth 两个选项配置是否正确 ...
- 【PostgreSQL-9.6.3】触发器实例
1. 创建一个触发器,表中的行在任何时候被插入或更新时,当前用户名和时间也会被标记在该行中.并且它会检查雇员的姓名以及薪水. --创建测试表 CREATE TABLE emp ( empname te ...
- JS——事件冒泡与捕获
事件冒泡与事件捕获 1.冒泡:addEventListener("click",fn,false)或者addEventListener("click",fn): ...
- CSS——font
行高的量取方式: 1.第一行可设置margin-top值.然后将第一文字顶部到第二行文字顶部的值作为行高的值(要注意对齐方式) 2.将 3.电视上 font:12px/1.5//字体12px,行高1. ...
- jboss-eap-6.2修改端口号
最近要改版一个项目,用来配合日常工作使用,需要在服务器上放多个jboss,那么就需要修改jboss的端口,如果服务器上配置了JBOSS_HOME,需要先删除,否则配置修改不会生效,会依然用老的jbos ...
- IntentService和HandlerThread的使用以及源码阅读
使用MyIntentService.java public class MyIntentService extends IntentService { /** * 是否正在运行 */ private ...
- C - CJSON
cJSON API 说明 cJSON_Version() 获得cJSON的版本 cJSON_InitHooks(); 初始化cJSON_Hooks结构体 cJSON_Parse(); 将字符串解析 ...