📄 lib0021.html
字号:
<html>
<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<head>
<title>Architect's Exercise: ProjectTrak</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="LiB0020.html"><img src="images/previous.gif" width="62" height="15" border="0" align="absmiddle" alt="Previous Section"></a>
<a href="LiB0022.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="ch03"></a>
<div class="section">
<h2 class="first-section-title"><a name="93"></a><a name="ch03lev1sec4"></a>Architect's Exercise: ProjectTrak</h2><p class="first-para">Based on the requirements documented in the use cases we identified in <a href="LiB0010.html#59" target="_parent" class="chapterjump">chapter 2</a>, we would expect screens or pages for the following topics:</p>
<ul class="itemizedlist">
<li class="first-listitem">
<p class="first-para">Project definition view/edit</p>
</li>
<li class="listitem">
<p class="first-para">Task definition view/edit</p>
</li>
<li class="listitem">
<p class="first-para">Resource definition view/edit</p>
</li>
<li class="listitem">
<p class="first-para">Resource calendar definition view/edit</p>
</li>
<li class="listitem">
<p class="first-para">Skill set view/edit</p>
</li>
<li class="listitem">
<p class="first-para">Project work schedule view and calculation</p>
</li>
<li class="listitem">
<p class="first-para">Progress report view</p>
</li>
<li class="listitem">
<p class="first-para">Gantt chart view</p>
</li>
</ul>
<p class="para">Some of these pages will be more complicated than others, but at this stage, we don't need to worry about that. Let's assume that it will average out. Working with an estimate of two man-weeks for each page, let's add sixteen man-weeks to the estimate.</p>
<p class="para">There are no external interfaces or data conversions for this product, so we don't need to add time to the estimate for these activities.</p>
<p class="para">Based on the requirements, at a minimum, we will have database tables for the following constructs:</p>
<a name="94"></a><a name="IDX-32"></a>
<ul class="itemizedlist">
<li class="first-listitem">
<p class="first-para">Project</p>
</li>
<li class="listitem">
<p class="first-para">Task</p>
</li>
<li class="listitem">
<p class="first-para">Task resource assignment</p>
</li>
<li class="listitem">
<p class="first-para">Resource</p>
</li>
<li class="listitem">
<p class="first-para">Resource work schedule</p>
</li>
<li class="listitem">
<p class="first-para">Skill set</p>
</li>
<li class="listitem">
<p class="first-para">Resource skill set</p>
</li>
</ul>
<p class="para">Working with an estimate of two man-weeks per table, let's add fourteen man-weeks to the estimate.</p>
<p class="para">The base estimate is then approximately 30 man-weeks, or 1,200 hours of coding and unit-testing time. Because this is only coding and testing time, we estimate the total number of hours left for the project at 1,200 ⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -