<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Template: Design</title>
<meta content="Template" name="uma.type">
<meta content="design" name="uma.name">
<meta content="Design" name="uma.presentationName">
<meta name="element_type" content="other">
<meta content="description" name="filetype">
<meta name="role" content="">
<link type="text/css" href="./../../../css/default.css" rel="StyleSheet">
<script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
					var backPath = './../../../';
					var imgPath = './../../../images/';
					var nodeInfo=null;
					contentPage.preload(imgPath, backPath, nodeInfo,  '', false, false, false);
				</script>
</head>
<body>
<div id="breadcrumbs"></div>
<table width="100%" cellspacing="0" cellpadding="0" border="0">
<tr>
<td valign="top"><a name="Top"></a>
<div id="page-guid" value="_EOPcMAMUEdylNddAObilIA"></div>
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr>
<td nowrap="true" class="pageTitle">Template: Design</td><td width="100%">
<div id="contentPageToolbar" align="right"></div>
</td><td align="right" class="expandCollapseLink" width="100%"><a href="./../../../index.htm" name="mainIndex"></a><script src="./../../../scripts/treebrowser.js" type="text/javascript" language="JavaScript"></script></td>
</tr>
</table>
<table cellspacing="0" cellpadding="0" border="0" width="100%">
<tr>
<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../../images/shim.gif"></td>
</tr>
</table>
<div class="overview">
<table cellpadding="0" cellspacing="0" border="0" width="97%">
<tr>
<td width="50"><img title="" alt="" src="./../../../images/template.gif"></td><td>
<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
<tr>
<td valign="top">This is the informal template suggested for representing design.</td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Relationships</div>
<div class="sectionContent">
<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
<tr valign="top">
<th scope="row" class="sectionTableHeading">Related Elements</th><td class="sectionTableCell">
<ul>
<li>
<a href="./../../../openup/workproducts/design_D677D182.html" guid="_0WuL8slgEdmt3adZL5Dmdw">Design</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Description</div>
<div class="sectionContent">
<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
<tr valign="top">
<th scope="row" class="sectionTableHeading">Main Description</th><td class="sectionTableCell"><p> This template describes how the design can be organized to be understood from 
  multiple perspectives. It also provides suggestions for how patterns and descriptions 
  of small, reusable interactions can be used to minimize redundancy. </p>
<p> It is important not to think of design as &quot;a document." Design information 
  that is worth keeping for some duration must have a long-lived form. But that 
  form might be as a repository in a visual modeling tool, or as subdirectories 
  of whiteboard diagrams captured with a digital camera, or as an actual document 
  that provides structure for images taken from a myriad of sources. </p>
<p> This template describes the information that should be conveyed. Typically, 
  it works best to convey the information graphically (either with UML or another 
  unambiguous notation), or at least in words, at an abstract level. You can enhance 
  this with code examples, but best not to render the design solely at the code 
  level. </p>
<p>
    The structure of the design is suggested in this template.
</p>
<h1> Design structure </h1>
<p style="COLOR: #0000ff"> [Describe the design from the highest level. This 
  is commonly done with a diagram that shows a layered architecture.] </p>
<h1> Subsystems </h1>
<h2> [Sub-system1] </h2>
<p style="COLOR: #0000ff"> [Describe the design of a portion of the system (a 
  package or component, for instance). The design should capture both static and 
  dynamic perspectives. </p>
<p style="COLOR: #0000ff"> When capturing dynamic descriptions of behavior, look 
  for reusable chunks of behavior that you can reference to simplify the design 
  of the use-case realizations. </p>
<p style="COLOR: #0000ff"> You can break this section down into lower-level subsections 
  to describe lower-level, encapsulated subsystems.] </p>
<h1> Patterns </h1>
<h2> [Pattern1] </h2>
<h3> Overview </h3>
<p style="COLOR: #0000ff"> [Provide an overview of the pattern in words in some 
  consistent form. The overview of a pattern can include the intent, motivation, 
  and applicability.] </p>
<h3> Structure </h3>
<p style="COLOR: #0000ff"> [Describe the pattern from a static perspective. Include 
  all of the participants and how they relate to one another, and call out the&nbsp;relevant 
  data and behavior.] </p>
<h3> Behavior </h3>
<p style="COLOR: #0000ff"> [Describe the pattern from a dynamic perspective. Walk 
  the reader through how the participants collaborate to support various scenarios.] 
</p>
Example 
<p style="COLOR: #0000ff"> [Often, you can convey the nature of the pattern better 
  with an additional concrete example.] </p>
<h1> Use-case realizations </h1>
<h2> [Realization1] </h2>
<h3> View of participants </h3>
<p style="COLOR: #0000ff"> [Describe the participating design elements from a 
  static perspective, giving details such as behavior, relationships, and attributes 
  relevant to this use-case realization.] </p>
<h3> Basic scenario </h3>
<p style="COLOR: #0000ff"> [For the main flow, describe how instances of the design 
  elements collaborate to realize the use case. When using UML, this can be done 
  with collaboration diagrams (sequence or communication).] </p>
<h3> Additional scenarios </h3>
<p style="COLOR: #0000ff"> [For other scenarios that must be described to convey 
  an appropriate amount of information about how the use-case behavior will be 
  realized, describe how instances of the design elements collaborate to realize 
  the use case. When using UML, you can do this with collaboration diagrams (sequence 
  or communication).] </p></td>
</tr>
</table>
</div>
<table cellpadding="0" cellspacing="0" border="0" class="copyright">
<tr>
<td class="copyright"><p>
    This program and the accompanying materials are made available under the<br />
     <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
    accompanies this distribution.
</p><p/><p>
    <a class="elementLink" href="./../../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
</p></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
<script language="JavaScript" type="text/javascript">
				contentPage.onload();
			</script>
</html>
