📄 lib0106.html
字号:
<html>
<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<head>
<title>Component Quality</title>
<link rel="STYLESHEET" type="text/css" href="images/xpolecat.css">
<link rel="STYLESHEET" type="text/css" href="images/ie.content.css">
</head>
<body>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr><td><div STYLE="MARGIN-LEFT: 0.15in;"><a href="toc.html"><img src="images/teamlib.gif" width="62" height="15" border="0" align="absmiddle" alt="Team LiB"></a></div></td>
<td align="right"><div STYLE="MARGIN-LEFT: 0.15in;">
<a href="LiB0105.html"><img src="images/previous.gif" width="62" height="15" border="0" align="absmiddle" alt="Previous Section"></a>
<a href="LiB0107.html"><img src="images/next.gif" width="41" height="15" border="0" align="absmiddle" alt="Next Section"></a>
</div></td></tr></table>
<br>
<div class="chapter">
<a name="ch16"></a>
<div class="section">
<h2 class="first-section-title"><a name="514"></a><a name="ch16lev1sec1"></a>Component Quality</h2><a name="515"></a><a name="IDX-212"></a>
<p class="para">High-quality architectural components have the following capabilities:</p>
<ul class="itemizedlist">
<li class="first-listitem">
<p class="first-para">Shorten development time and effort</p>
</li>
<li class="listitem">
<p class="first-para">Shorten expected maintenance time and effort</p>
</li>
<li class="listitem">
<p class="first-para">Work in many applications because they are generic</p>
</li>
<li class="listitem">
<p class="first-para">Work as advertised</p>
</li>
</ul>
<p class="para">These traits are desirable for any component software, whether it is commercial, open source, or authored by you.</p>
<p class="para">A common guideline people use when judging PC software is: if they have to consult a manual to do basic tasks, they judge the software "too hard to use." You can use much the same standard when assessing component software. I consider component software difficult to use if:</p>
<ul class="itemizedlist">
<li class="first-listitem">
<p class="first-para">You have to read more than two pages of material to install and configure the component.</p>
<a name="516"></a><a name="IDX-213"></a>
</li>
<li class="listitem">
<p class="first-para">It takes more than an hour from installing to using a component for a basic task.</p>
</li>
</ul>
<p class="para">Ease of use is the feature most commonly lacking in both commercial and open source component software.</p>
<p class="last-para">A common mistake people use when designing architectural components is choosing a scope that is too large. A large scope usually results in a complex component that will take a long time to become available and have a long learning curve. I use the 80/20 rule when selecting features to implement in an architectural component. Component designers shouldn't get bogged down with features people will rarely use.</p>
</div>
</div><br>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr><td><div STYLE="MARGIN-LEFT: 0.15in;"><a href="toc.html"><img src="images/teamlib.gif" width="62" height="15" border="0" align="absmiddle" alt="Team LiB"></a></div></td>
<td align="right"><div STYLE="MARGIN-LEFT: 0.15in;">
<a href="LiB0105.html"><img src="images/previous.gif" width="62" height="15" border="0" align="absmiddle" alt="Previous Section"></a>
<a href="LiB0107.html"><img src="images/next.gif" width="41" height="15" border="0" align="absmiddle" alt="Next Section"></a>
</div></td></tr></table>
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -