Menu
▾
▴
[opengtoolkit-cvs] deab/Software Project Multi-Map/ReadySET-0-9-1/templates all-in-one.html,NONE,1.1 demo-script.html,NONE,1.1 design-architecture.html,NONE,1.1 design-components.html,NONE,1.1 design-persistence.html,NONE,1.1 design-scalability.html,NONE,1.1 design-security.html,NONE,1.1 design-src-org.html,NONE,1.1 design-ui.html,NONE,1.1 design.html,NONE,1.1 faq.html,NONE,1.1 feature-format.html,NONE,1.1 feature-set.html,NONE,1.1 features.html,NONE,1.1 frame-nav.html,NONE,1.1 frame-select-at-left.html,NONE,1.1 frameset.html,NONE,1.1 glossary-std.html,NONE,1.1 glossary.html,NONE,1.1 implementation-notes.html,NONE,1.1 index.html,NONE,1.1 install.html,NONE,1.1 interview-checklist.html,NONE,1.1 interview-notes.html,NONE,1.1 legal.html,NONE,1.1 plan.html,NONE,1.1 proposal.html,NONE,1.1 qa-plan.html,NONE,1.1 readyset-license.html,NONE,1.1 release-checklist.html,NONE,1.1 release-notes.html,NONE,1.1 resource-needs.html,NONE,1.1 review-meeting-checklists.html,NONE,1.1 review-meeting-notes.html,NONE,1.1 sdm.html,NONE,1.1 srs.html,NONE,1.1 status-report.html,NONE,1.1 target-and-benefits.html,NONE,1.1 test-case-format.html,NONE,1.1 test-cases.html,NONE,1.1 test-run-suite.html,NONE,1.1 test-runs.html,NONE,1.1 test-suite.html,NONE,1.1 use-case-format.html,NONE,1.1 use-case-suite.html,NONE,1.1 use-cases.html,NONE,1.1 user-needs.html,NONE,1.1 userguide.html,NONE,1.1
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/ReadySET-0-9-1/templates In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map/ReadySET-0-9-1/templates Added Files: all-in-one.html demo-script.html design-architecture.html design-components.html design-persistence.html design-scalability.html design-security.html design-src-org.html design-ui.html design.html faq.html feature-format.html feature-set.html features.html frame-nav.html frame-select-at-left.html frameset.html glossary-std.html glossary.html implementation-notes.html index.html install.html interview-checklist.html interview-notes.html legal.html plan.html proposal.html qa-plan.html readyset-license.html release-checklist.html release-notes.html resource-needs.html review-meeting-checklists.html review-meeting-notes.html sdm.html srs.html status-report.html target-and-benefits.html test-case-format.html test-cases.html test-run-suite.html test-runs.html test-suite.html use-case-format.html use-case-suite.html use-cases.html user-needs.html userguide.html Log Message: initial commit --- NEW FILE: frame-nav.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "/branding/css/tigris.css"; @import "/branding/css/inst.css"; @import "css/nav.css"; /* ]]> */ </style> <script src="js/super-simple-tree.js" type="text/javascript"></script> <link rel="stylesheet" type="text/css" href="css/print.css" media="print" /> <title>ReadySET Template Navigation</title> </head> <body onload="collapseAll(); openBookMark();"> <h2><a href="http://readyset.tigris.org/" target="_top">ReadySET</a></h2> <ol id="root"> <li class="panel"><a id="default" href="#default" class="folder" onclick="toggle(this)"></a>By Activity <ol> <li><a id="planning" href="#default.planning" class="folder" onclick="toggle(this)"></a>Project Planning <ol> <li><a href="index.html" target="objects" class="doc"></a><a href="index.html" target="objects">Overview</a></li> <li><a href="proposal.html" target="objects" class="doc"></a><a href="proposal.html" target="objects">Proposal</a> <ul> <li><a href="target-and-benefits.html" target="objects"></a><a href="target-and-benefits.html" target="objects">Target and benefits</a></li> </ul> </li> <li><a href="plan.html" target="objects" class="doc"></a><a href="plan.html" target="objects">Project plan</a> <ul> <li><a href="resource-needs.html" target="objects">Resource needs</a></li> </ul> </li> <li><a href="legal.html" target="objects" class="doc"></a><a href="legal.html" target="objects">Legal issues</a></li> <li><a href="qa-plan.html" target="objects" class="doc"></a><a href="qa-plan.html" target="objects">QA Plan</a></li> </ol> </li> <li><a id="req" href="#default.req" class="folder" onclick="toggle(this)"></a>Requirements and Specification <ol> <li><a href="user-needs.html" target="objects" class="doc"></a><a href="user-needs.html" target="objects">User needs</a> <ul> <li><a href="interview-notes.html" target="objects">Interview notes</a></li> </ul> </li> <li><a href="srs.html" target="objects" class="doc"></a><a href="srs.html" target="objects">Software Requirements Specification</a> <ul> <li><a href="use-case-suite.html" target="objects">Use case suite</a></li> <li><a href="feature-set.html" target="objects">Feature set</a></li> </ul> </li> </ol> </li> <li><a id="design" href="#default.design" class="folder" onclick="toggle(this)"></a>Architecture and Design <ol> <li><a href="design.html" target="objects" class="doc"></a><a href="design.html" target="objects">Design</a> <ul> <li><a href="design-architecture.html" target="objects">Architecture worksheet</a></li> <li><a href="design-src-org.html" target="objects">Source and build</a></li> <li><a href="design-ui.html" target="objects">User interface worksheet</a></li> <li><a href="design-persistence.html" target="objects">Persistence worksheet</a></li> <li><a href="design-security.html" target="objects">Security worksheet</a></li> </ul> </li> </ol> </li> <li><a id="impl" href="#default.impl" class="folder" onclick="toggle(this)"></a>Implementation and Testing <ol> <li><a href="userguide.html" target="objects" class="doc"></a><a href="userguide.html" target="objects">User guide</a></li> <li><a href="test-suite.html" target="objects" class="doc"></a><a href="test-suite.html" target="objects">Test suite</a> <ul> <li><a href="test-case-format.html" target="objects">Test case format</a></li> <li><a href="test-cases.html" target="objects">Test cases</a></li> </ul> </li> </ol> </li> <li><a id="deploy" href="#default.deploy" class="folder" onclick="toggle(this)"></a>Deployment and Installation <ol> <li><a href="release-checklist.html" target="objects" class="doc"></a><a href="release-checklist.html" target="objects">Release checklist</a></li> <li><a href="install.html" target="objects" class="doc"></a><a href="install.html" target="objects">Installation / Quick start guide</a></li> <li><a href="release-notes.html" target="objects" class="doc"></a><a href="release-notes.html" target="objects">Release notes</a></li> <li><a href="demo-script.html" target="objects" class="doc"></a><a href="demo-script.html" target="objects">Demo script</a></li> </ol> </li> <li><a id="ops" href="#default.ops" class="folder" onclick="toggle(this)"></a>Operations and Support <ol> <li><a href="faq.html" target="objects" class="doc"></a><a href="faq.html" target="objects">FAQ / Troubleshooting</a></li> <li><a href="implementation-notes.html" target="objects" class="doc"></a><a href="implementation-notes.html" target="objects">Implementation notes</a></li> </ol> </li> <li><a id="continuous" href="#default.continuous" class="folder" onclick="toggle(this)"></a>Continuous or Final <ol> <li><a href="glossary.html" target="objects" class="doc"></a><a href="glossary.html" target="objects">Glossary</a></li> <li><a href="status-report.html" target="objects" class="doc"></a><a href="status-report.html" target="objects">Status report</a></li> <li><a href="review-meeting-notes.html" target="objects" class="doc"></a><a href="review-meeting-notes.html" target="objects">Review meeting notes</a></li> <li><a href="sdm.html" target="objects" class="doc"></a><a href="sdm.html" target="objects">Software development methodology</a></li> </ol> </li> </ol> </li> <!-- <li class="panel"><a id="stake" href="#stake" class="folder" onclick="toggle(this)"></a>By Stakeholder <ol> <li><a id="everyone" href="#stake.everyone" class="folder" onclick="toggle(this)"></a>For Everyone <ol> <li><a href="glossary.html" target="objects" class="doc"></a><a href="glossary.html" target="objects">Glossary</a></li> <li><a href="index.html" target="objects" class="doc"></a><a href="index.html" target="objects">Overview</a></li> <li><a href="release-checklist.html" target="objects" class="doc"></a><a href="release-checklist.html" target="objects">Release checklist</a></li> <li><a href="user-needs.html" target="objects" class="doc"></a><a href="user-needs.html" target="objects">User needs</a> <ul> <li><a href="interview-notes.html" target="objects">Interview notes</a></li> </ul> </li> <li><a href="srs.html" target="objects" class="doc"></a><a href="srs.html" target="objects">Software Requirements Specification</a> <ul> <li><a href="use-case-suite.html" target="objects">Use case suite</a></li> <li><a href="feature-set.html" target="objects">Feature set</a></li> </ul> </li> <li><a href="plan.html" target="objects" class="doc"></a><a href="plan.html" target="objects">Project plan</a></li> <li><a href="sdm.html" target="objects" class="doc"></a><a href="sdm.html" target="objects">Software development methodology</a></li> </ol> </li> <li><a id="management" href="#stake.management" class="folder" onclick="toggle(this)"></a>For Management <ol> <li><a href="status-report.html" target="objects" class="doc"></a><a href="status-report.html" target="objects">Status report</a></li> <li><a href="proposal.html" target="objects" class="doc"></a><a href="proposal.html" target="objects">Proposal</a></li> <li><a href="resource-needs.html" target="objects" class="doc"></a><a href="resource-needs.html" target="objects">Resource needs</a></li> </ol> </li> <li><a id="dev" href="#stake.dev" class="folder" onclick="toggle(this)"></a>For Developers <ol> <li><a href="design.html" target="objects" class="doc"></a><a href="design.html" target="objects">Design</a> <ul> <li><a href="design-architecture.html" target="objects">Architecture worksheet</a></li> <li><a href="design-src-org.html" target="objects">Source and build</a></li> <li><a href="design-ui.html" target="objects">User interface worksheet</a></li> <li><a href="design-persistence.html" target="objects">Persistence worksheet</a></li> <li><a href="design-security.html" target="objects">Security worksheet</a></li> </ul> </li> <li><a href="review-meeting-notes.html" target="objects" class="doc"></a><a href="review-meeting-notes.html" target="objects">Review meeting notes</a></li> </ol> </li> <li><a id="qa" href="#stake.qa" class="folder" onclick="toggle(this)"></a>For QA <ol> <li><a href="qa-plan.html" target="objects" class="doc"></a><a href="qa-plan.html" target="objects">QA Plan</a></li> <li><a href="test-suite.html" target="objects" class="doc"></a><a href="test-suite.html" target="objects">Test suite</a> <ul> <li><a href="test-case-format.html" target="objects">Test case format</a></li> <li><a href="test-cases.html" target="objects">Test cases</a></li> </ul> </ol> </li> <li><a id="support" href="#stake.support" class="folder" onclick="toggle(this)"></a>For Tech Support and Operations <ol> <li><a href="faq.html" target="objects" class="doc"></a><a href="faq.html" target="objects">FAQ / Troubleshooting</a></li> <li><a href="implementation-notes.html" target="objects" class="doc"></a><a href="implementation-notes.html" target="objects">Implementation notes</a></li> </ol> </li> <li><a id="users" href="#stake.users" class="folder" onclick="toggle(this)"></a>For End Users <ol> <li><a href="install.html" target="objects" class="doc"></a><a href="install.html" target="objects">Installation / Quick start guide</a></li> <li><a href="userguide.html" target="objects" class="doc"></a><a href="userguide.html" target="objects">User guide</a></li> <li><a href="release-notes.html" target="objects" class="doc"></a><a href="release-notes.html" target="objects">Release notes</a></li> <li><a href="faq.html" target="objects" class="doc"></a><a href="faq.html" target="objects">FAQ</a></li> </ol> </li> <li><a id="sales" href="#stake.sales" class="folder" onclick="toggle(this)"></a>For Sales and Marketing <ol> <li><a href="demo-script.html" target="objects" class="doc"></a><a href="demo-script.html" target="objects">Demo script</a></li> <li><a href="target-and-benefits.html" target="objects" class="doc"></a><a href="target-and-benefits.html" target="objects">Target and benefits</a></li> </ol> </li> <li><a id="legal" href="#stake.legal" class="folder" onclick="toggle(this)"></a>For Legal <ol> <li><a href="legal.html" target="objects" class="doc"></a><a href="legal.html" target="objects">Legal issues</a></li> </ol> </li> </ol> </li> --> <li class="panel"><a id="week" href="#week" class="folder" onclick="toggle(this)"></a>By Suggested Sequence <ol> <li><a id="two" href="#week.two" class="folder" onclick="toggle(this)"></a>Step 1 <ol> <li><a href="index.html" target="objects" class="doc"></a><a href="index.html" target="objects">Overview</a></li> <li><a href="proposal.html" target="objects" class="doc"></a><a href="proposal.html" target="objects">Proposal</a> <ul> <li><a href="target-and-benefits.html" target="objects"></a><a href="target-and-benefits.html" target="objects">Target and benefits</a></li> </ul> </li> <li><a href="plan.html" target="objects" class="doc"></a><a href="plan.html" target="objects">Project plan</a> <ul> <li><a href="resource-needs.html" target="objects">Resource needs</a></li> </ul> </li> <li><a href="legal.html" target="objects" class="doc"></a><a href="legal.html" target="objects">Legal issues</a></li> <li><a href="glossary.html" target="objects" class="doc"></a><a href="glossary.html" target="objects">Glossary</a></li> </ol> </li> <li><a id="three" href="#week.three" class="folder" onclick="toggle(this)"></a>Step 2 <ol> <li><a href="user-needs.html" target="objects" class="doc"></a><a href="user-needs.html" target="objects">User needs</a> <ul> <li><a href="interview-notes.html" target="objects">Interview notes</a></li> </ul> </li> <li><a href="srs.html" target="objects" class="doc"></a><a href="srs.html" target="objects">Software Requirements Specification</a> <ul> <li><a href="use-case-suite.html" target="objects">Use case suite</a></li> <li><a href="feature-set.html" target="objects">Feature set</a></li> </ul> </li> </ol> </li> <li><a id="five" href="#week.five" class="folder" onclick="toggle(this)"></a>Step 3 <ol> <li><a href="design.html" target="objects" class="doc"></a><a href="design.html" target="objects">Design</a> <ul> <li><a href="design-architecture.html" target="objects">Architecture worksheet</a></li> <li><a href="design-src-org.html" target="objects">Source and build</a></li> <li><a href="design-ui.html" target="objects">User interface worksheet</a></li> <li><a href="design-persistence.html" target="objects">Persistence worksheet</a></li> <li><a href="design-security.html" target="objects">Security worksheet</a></li> </ul> </li> </ol> </li> <li><a id="seven" href="#week.seven" class="folder" onclick="toggle(this)"></a>Step 4 <ol> <li><a href="qa-plan.html" target="objects" class="doc"></a><a href="qa-plan.html" target="objects">QA Plan</a></li> <li><a href="test-suite.html" target="objects" class="doc"></a><a href="test-suite.html" target="objects">Test suite</a> <ul> <li><a href="test-case-format.html" target="objects">Test case format</a></li> <li><a href="test-cases.html" target="objects">Test cases</a></li> </ul> </li> </ol> </li> <li><a id="eight" href="#week.eight" class="folder" onclick="toggle(this)"></a>Step 5 <ol> <li><a href="review-meeting-notes.html" target="objects" class="doc"></a><a href="review-meeting-notes.html" target="objects">Review meeting notes</a></li> </ol> </li> <li><a id="nine" href="#week.nine" class="folder" onclick="toggle(this)"></a>Step 6 <ol> <li><a href="release-checklist.html" target="objects" class="doc"></a><a href="release-checklist.html" target="objects">Release checklist</a></li> </ol> </li> <li><a id="ten" href="#week.ten" class="folder" onclick="toggle(this)"></a>Step 7 <ol> <li><a href="install.html" target="objects" class="doc"></a><a href="install.html" target="objects">Installation / Quick start guide</a></li> <li><a href="release-notes.html" target="objects" class="doc"></a><a href="release-notes.html" target="objects">Release notes</a></li> <li><a href="userguide.html" target="objects" class="doc"></a><a href="userguide.html" target="objects">User guide</a></li> <li><a href="demo-script.html" target="objects" class="doc"></a><a href="demo-script.html" target="objects">Demo script</a></li> <li><a href="faq.html" target="objects" class="doc"></a><a href="faq.html" target="objects">FAQ / Troubleshooting</a></li> <li><a href="implementation-notes.html" target="objects" class="doc"></a><a href="implementation-notes.html" target="objects">Implementation notes</a></li> </ol> </li> <li><a id="most" href="#week.most" class="folder" onclick="toggle(this)"></a>Every week <ol> <li><a href="status-report.html" target="objects" class="doc"></a><a href="status-report.html" target="objects">Status report</a></li> </ol> </li> </ol> </li> <li class="panel"><a id="all" href="#all" class="folder" onclick="toggle(this)"></a>All Templates <ol> <li><a href="all-in-one.html" target="objects" class="doc"></a><a href="all-in-one.html" target="objects">All-in-one</a></li> <li><a href="index.html" target="objects" class="doc"></a><a href="index.html" target="objects">Overview</a></li> <li><a href="proposal.html" target="objects" class="doc"></a><a href="proposal.html" target="objects">Proposal</a> <ul> <li><a href="target-and-benefits.html" target="objects"></a><a href="target-and-benefits.html" target="objects">Target and benefits</a></li> </ul> </li> <li><a href="plan.html" target="objects" class="doc"></a><a href="plan.html" target="objects">Project plan</a> <ul> <li><a href="resource-needs.html" target="objects"></a><a href="resource-needs.html" target="objects">Resource needs</a></li> </ul> </li> <li><a href="qa-plan.html" target="objects" class="doc"></a><a href="qa-plan.html" target="objects">QA Plan</a> <ul> <li><a href="test-suite.html" target="objects"></a><a href="test-suite.html" target="objects">Test suite</a> <ul> <li><a href="test-case-format.html" target="objects">Test case format</a></li> <li><a href="test-cases.html" target="objects">Test cases</a></li> </ul> </li> <li><a href="review-meeting-notes.html" target="objects"></a><a href="review-meeting-notes.html" target="objects">Review meeting notes</a></li> </ul> </li> <li><a href="legal.html" target="objects" class="doc"></a><a href="legal.html" target="objects">Legal issues</a></li> <li><a href="user-needs.html" target="objects" class="doc"></a><a href="user-needs.html" target="objects">User needs</a> <ul> <li><a href="interview-notes.html" target="objects">Interview notes</a></li> </ul> </li> <li><a href="srs.html" target="objects" class="doc"></a><a href="srs.html" target="objects">Software Requirements Specification</a> <ul> <li><a href="use-case-suite.html" target="objects">Use case suite</a></li> <li><a href="feature-set.html" target="objects">Feature set</a></li> </ul> </li> <li><a href="glossary.html" target="objects" class="doc"></a><a href="glossary.html" target="objects">Glossary</a></li> <li><a href="design.html" target="objects" class="doc"></a><a href="design.html" target="objects">Design</a> <ul> <li><a href="design-architecture.html" target="objects">Architecture worksheet</a></li> <li><a href="design-src-org.html" target="objects">Source and build</a></li> <li><a href="design-ui.html" target="objects">User interface worksheet</a></li> <li><a href="design-persistence.html" target="objects">Persistence worksheet</a></li> <li><a href="design-security.html" target="objects">Security worksheet</a></li> </ul> </li> <li><a href="userguide.html" target="objects" class="doc"></a><a href="userguide.html" target="objects">User guide</a></li> <li><a href="release-checklist.html" target="objects" class="doc"></a><a href="release-checklist.html" target="objects">Release checklist</a></li> <li><a href="install.html" target="objects" class="doc"></a><a href="install.html" target="objects">Installation / Quick start guide</a></li> <li><a href="release-notes.html" target="objects" class="doc"></a><a href="release-notes.html" target="objects">Release notes</a></li> <li><a href="demo-script.html" target="objects" class="doc"></a><a href="demo-script.html" target="objects">Demo script</a></li> <li><a href="faq.html" target="objects" class="doc"></a><a href="faq.html" target="objects">FAQ / Troubleshooting</a></li> <li><a href="implementation-notes.html" target="objects" class="doc"></a><a href="implementation-notes.html" target="objects">Implementation notes</a></li> <li><a href="status-report.html" target="objects" class="doc"></a><a href="status-report.html" target="objects">Status report</a></li> <li><a href="sdm.html" target="objects" class="doc"></a><a href="sdm.html" target="objects">Software development methodology</a></li> </ol> </li> </ol> <p>How to download these templates:</p> <ul style="padding-left: 15px;"> <li><a href="/servlets/ProjectDocumentList" target="_top">Download template archive</a>, or</li> <li>Use CVS to <a href="http://readyset.tigris.org/servlets/ProjectSource" target="_top">check out</a> project "readyset"</li> </ul> </body> </html> --- NEW FILE: use-case-format.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "css/readyset.css"; @import "css/inst.css"; /* ]]> */ </style> <link rel="stylesheet" type="text/css" href="css/print.css" media="print" /> <title>Use Case Format</title> </head> <body> <div class="app"> <div class="readyset"> <h2><a href="srs.html">SRS</a> > <a href="use-case-suite.html">Use Case Suite</a> > Use Case Format</h2> <div id="processimpact"> <b>Process impact:</b> This reference page documents the format of use cases and gives tips on writing use cases. You can copy and paste the sample use case into your <a href="use-cases.html">Use Cases</a> document. This file itself should not be edited to hold specific use cases. </div> <!-- /processimpact --> <div class="todo"> TODO: Use this template once in your <a href="use-cases.html">Use Cases</a> document. Anything you mention here will apply to all use cases in that file. </div> <div id="defaults"> <h3>Aspects common to all use cases</h3> <table border="1" cellpadding="3" cellspacing="2" class="axial"> <tr> <th>Direct Actors:</th> <td> <div>User: end-user in any role</div> <div>System: The system being built</div> <div>When actors are not listed, assume User is doing it.</div> <div>Items beginning with "see" indicate that System has presented a new screen.</div> </td> </tr> <tr> <th>Stakeholders:</th> <td>The user who is entering the data, and those who will read it</td> </tr> <tr> <th>Prereq:</th> <td>Project is set up</td> </tr> </table> </div> <div class="todo"> TODO: Copy and paste this use case template as many times as needed in your <a href="use-cases.html">Use Cases</a> document. Only use those fields that are not the same as the default for all use cases. </div> <div id="UC-00"> <h3>UC-00: USE CASE NAME</h3> <table border="1" cellpadding="3" cellspacing="2" class="axial"> <tr> <th>Summary:</th> <td>1-3 SENTENCES</td> </tr> <tr> <th>Priority:</th> <td>Essential | Expected | Desired | Optional</td> </tr> <tr> <th>Use Frequency:</th> <td>Always | Often | Sometimes | Rarely | Once</td> </tr> <tr> <th>Direct Actors:</th> <td>ACTOR1, ACTOR2, ACTOR3</td> </tr> <tr> <th>Stakeholders:</th> <td>STAKEHOLDER, STAKEHOLDER, STAKEHOLDER</td> </tr> <tr> <th>Prereq:</th> <td> <div>PRECONDITION</div> <div>PRECONDITION</div> <div>PRECONDITION</div> </td> </tr> <tr> <th>Main Success Scenario:</th> <td> <ol> <li>STEP</li> <li>STEP</li> <li>STEP</li> </ol> </td> </tr> <tr> <th>Alternative Scenario Extensions:</th> <td> <ul> <li>If CONDITION, then ALTERNATIVE STEPS. <ul> <li>NOTES or DETAILS.</li> </ul> </li> <li>If CONDITION, then ALTERNATIVE STEPS. <ul> <li>NOTES or DETAILS.</li> </ul> </li> </ul> </td> </tr> <tr> <th>Notes and Questions</th> <td> <ul> <li>NOTE</li> <li>NOTE</li> <li>QUESTION</li> <li>QUESTION</li> </ul> </td> </tr> </table> </div> <div id="steps"> <h3>Format of Use Case Steps</h3> <p>Try to start each step with one of these action words:</p> <dl> <dt>login [as ROLE or USER]</dt> <dd>Log into the system with a given user or a user of the given type. Usually usually only stated explicitly when the test case involves a workflow between different users.</dd> <dt>visit LOCATION</dt> <dd>Visit a page or GUI window. State the user's intention, don't say too much about UI choices that could change later. E.g., WRONG: "Press the 'Advanced...' button on the File | Page Setup dialog". RIGHT: "Visit the page margin configuration dialog". </dd> <dt>enter INFORMATION</dt> <dd>Fill in specific information. Try to state the information in some detail. E.g., WRONG: "Enter customer information." RIGHT: "Enter customer shipping address and discount code." Don't commit to details of a particular UI, i.e., don't name specific UI fields that might change later.</dd> <dt>COMMAND</dt> <dd>Describe a command that the user can tell the system to do. State the user's intent, not the label on a particular UI widget. This will usually be followed by a "see" step where the user sees a confirmation of their action. E.g., WRONG: "Control-P, OK". RIGHT: "Print the current document with default settings".</dd> <dt>see CONTENT</dt> <dd>The user should see the specified information on the currently presented web page or GUI window. Try to be specific about the information that is seen, but try not to refer to specific UI elements. E.g., WRONG: "see UserList.jsp" (what is the user supposed to notice on that page?) RIGHT: "see list of users with the newly added user in the list". </dd> <dt>perform USE-CASE-NAME</dt> <dd>This is like a subroutine call. The user will do all the steps of the named use case and then continue on with the next step of this use case.</dd> </dl> </div> <!-- /steps --> <div id="furtherinfo"> <h3>Further Information</h3> <p>For more information on advice, see:</p> <ul> <li>Words of wisdom on <a href="http://readyset.tigris.org/words-of-wisdom/use-case-suite.html">use case suites</a>.</li> <li>Words of wisdom on <a href="http://readyset.tigris.org/words-of-wisdom/use-cases.html">use cases</a>.</li> </ul> </div> <!-- /furtherinfo --> </div> <div class="todo"> TODO: Check for <a href="http://readyset.tigris.org/words-of-wisdom/use-case-format.html">words of wisdom</a> and discuss ways to improve this template. </div> <div class="legal1">Company Proprietary</div> <div class="footnote"> Copyright © 2003-2004 Jason Robbins. All rights reserved. <a href="readyset-license.html">License terms</a>. Retain this copyright statement whenever this file is used as a template. </div> </div> </body> </html> --- NEW FILE: frame-select-at-left.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <title>Select at left</title> </head> <body> <p>Click on the folders on the left-hand panel to expand.</p> <p>Select a document to display in this panel.</p> <p>Or, view the templates with <a href="index.html" target="_top">no frames</a>.</p> </body> </html> --- NEW FILE: all-in-one.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "css/readyset.css"; @import "css/inst.css"; /* ]]> */ </style> <link rel="stylesheet" type="text/css" href="css/print.css" media="print" /> <title>Summary</title> </head> <body> <h2>Summary</h2> <div class="app"> <div class="readyset"> <div id="mission"> <div id="scope"> <h3>Mission and Scope</h3> <div class="todo"> TODO: Answer these questions in your own words by filling in each <dd> tag. This is condensed from the project <a href="index.html">overview</a>. </div> <dl> <dt>What problem does this project address?</dt> <dd class="sample1">2-4 SENTENCE PROBLEM</dd> <dt>What is the goal of this project?</dt> <dd class="sample1">2-4 SENTENCE GOAL</dd> <dt>What is the scope of this project?</dt> <dd class="sample1">2-4 SENTENCE SCOPE</dd> </dl> </div> <!-- /scope --> </div> <!-- /mission --> <div id="status"> <h3>Status</h3> <div class="todo"> TODO: Briefly describe the status of this project. E.g., what phase are you in? And, what is your next major milestone? Detailed project status is written in the status reports, not here. </div> <div class="sample1"> <p>We have completed our second beta release and are currently working on adding more of the functionality described in our product <a href="srs.html">specification</a> and fixing defects.</p> <p>The next major milestone is a third beta release with nearly complete functionality and a wider set of testers.</p> </div> <p>Status reports:</p> <ul class="sample1"> <li><a href="status-report.html">Status report 1</a></li> <li><a href="status-report2.html">Status report 2</a></li> <li>Etc.</li> </ul> </div> <!-- /status --> <div id="resources"> <div id="schedule"> <h3>Resources and schedule</h3> <div class="todo"> TODO: Briefly describe the project resources and schedule. This is condensed from the <a href="plan.html">project plan</a>, <a href="resource-needs.html">resource needs</a>, and <a href="legal.html">legal issues</a> templates. </div> <dl> <dt>What are the deadlines for this project?</dt> <dd> <ul class="sample1"> <li>DATE: MILESTONE</li> <li>DATE: MILESTONE</li> <li>DATE: MILESTONE</li> <li>DATE: RELEASE-NUMBER</li> </ul> </dd> <dt>Who is working on this project?</dt> <dd> <ul class="sample1"> <li>100% PERSON-NAME</li> <li>100% PERSON-NAME</li> <li>75% PERSON-NAME</li> <li>33% PERSON-NAME</li> </ul> </dd> <dt>What capital resources are allocated to this project?</dt> <dd> <ul class="sample1"> <li>HARDWARE</li> <li>SOFTWARE LICENSE</li> <li>FACILITIES</li> </ul> </dd> <dt>What are the main legal concerns for this project?</dt> <dd> <ul class="sample1"> <li>Intellectual property: DESCRIPTION</li> <li>Privacy and security: DESCRIPTION</li> <li>Potential harm: DESCRIPTION</li> </ul> </dd> </dl> </div> <!-- /schedule --> </div> <!-- /resources --> <div id="requirements"> <h3>Requirements</h3> <div class="todo"> TODO: Briefly describe the most important system requirements. This is condensed from the <a href="user-needs.html">user needs</a>, <a href="interview-notes.html">interview notes</a>, <a href="srs.html">SRS</a>, <a href="use-case-suite.html">use case suite</a>, and <a href="feature-set.html">feature set</a> documents. </div> <dl> <dt>Who are the project stakeholders?</dt> <dd> <ul class="sample1"> <li>PROJECT CHAMPION / EXECUTIVE SPONSOR</li> <li>DEPARTMENTS WITHIN YOUR COMPANY</li> <li>CORPORATE PARTNERS</li> <li>KEY CUSTOMERS</li> </ul> </dd> <dt>What user needs have you gathered?</dt> <dd> <ul class="sample1"> <li><a href="LINK-TO-USER-STORIES">User stories</a></li> <li><a href="LINK-TO-INTERVIEW-NOTES">Interview notes</a></li> </ul> </dd> <dt>What are the requirements specifications?</dt> <dd> <ul class="sample1"> <li><a href="LINK-TO-USE-CASES">Use cases</a></li> <li><a href="LINK-TO-FEATURE-SPECS">Feature specifications</a></li> <li><a href="LINK-TO-ENV-REQ">Environmental requirements</a></li> <li><a href="LINK-TO-OTHER-REQ">Other requirements</a></li> </ul> </dd> </dl> </div> <!-- /requirements --> <div id="design"> <h3>Design</h3> <div class="todo"> TODO: Briefly describe the most important aspects of the design. This is condensed from the <a href="design.html">design</a> template and associated worksheets. </div> <dl> <dt>What are your ranked design goals?</dt> <dd> <ol class="sample1"> <li>Correctness: This design correctly matches the given requirements.</li> <li>Feasibility: This design can be implemented and tested with the planned amount of time and effort.</li> <li>Understandability: Developers can understand this design and correctly implement it. </li> <li>Implementation phase guidance: This design divides the implementation into components or aspects that can correspond to reasonable implementation tasks.</li> <li>Modularity: Concerns are clearly separated so that the impact of most design changes would be limited to only one or a few modules.</li> <li>Extensibility: New features can be easily added later.</li> <li>Testability: It is easy to test components of this design independently, and information is available to help diagnose defects.</li> <li>Efficiency: The design enables the system to perform functions with an acceptable amount of time, storage space, bandwidth, and other resources.</li> </ol> </dd> <dt>Where are your design documents?</dt> <dd> <ul class="sample1"> <li><a href="LINK-TO-CLASS-DIAGRAM">UML class diagram</a></li> <li><a href="LINK-TO-CLASS-DIAGRAM">UML class diagram</a></li> <li><a href="LINK-TO-STATE-DIAGRAM">UML state diagram</a></li> <li><a href="LINK-TO-SEQUENCE-DIAGRAM">UML sequence diagram</a></li> <li><a href="LINK-TO-DEPLOYMENT-DIAGRAM">UML deployment diagram</a></li> <li><a href="LINK-TO-OTHER-DESIGN">Other design</a></li> </ul> </dd> </dl> </div> <!-- /design --> <div id="qa"> <h3>Quality Assurance</h3> <div class="todo"> TODO: Briefly describe your quality goals and how you will achieve them. This is condensed from the <a href="qa-plan.html">QA plan</a>, <a href="test-suite.html">test suite</a>, and <a href="test-cases.html">test cases</a> documents. </div> <dl> <dt>What are your ranked quality goals?</dt> <dd> <ol class="sample1"> <li>Correctness</li> <li>Robustness</li> <li>Accuracy</li> <li>Compatibility</li> <li>Usability</li> <li>Security</li> <li>Reliability</li> <li>Scalability</li> <li>Operability</li> <li>Maintainability</li> </ol> </dd> <dt>What QA activities will you use?</dt> <dd> <ul class="sample1"> <li>Preconditions and assertions</li> <li>Buddy reviews</li> <li>Review meetings</li> <li>Unit testing</li> <li>System testing</li> </ul> </dd> <dt>Where are the test cases?</dt> <dd> <ul class="sample1"> <li><a href="LINK-TO-TEST-CASE">Test case</a></li> <li><a href="LINK-TO-TEST-CASE">Test case</a></li> <li><a href="LINK-TO-TEST-CASE">Test case</a></li> <li><a href="LINK-TO-TEST-CASE">Test case</a></li> </ul> </dd> </dl> </div> <!-- /qa --> <div id="deployment"> <h3>Packaging, Delivery, and Deployment</h3> <dl> <dt>Where is the release checklist or sign-off document?</dt> <dd> <a href="LINK-TO-RELEASE-CHECKLIST">Release checklist</a> </dd> <dt>How is the product packaged and deployed?</dt> <dd> <ul class="sample1"> <li>Packaging: DESCRIPTION</li> <li>Deployment: DESCRIPTION</li> <li><a href="LINK-TO-RELEASE-NOTES">Release notes</a></li> </ul> </dd> <dt>How is the product installed?</dt> <dd> <ul> <li>System requirements: DESCRIPTION</li> <li>STEP</li> <li>STEP</li> <li>STEP</li> </ul> </dd> </dl> </div> <!-- /deployment --> <div id="support"> <h3>User Support</h3> <dl> <dt>Where is the user documentation?</dt> <dd> <ul class="sample1"> <li><a href="LINK-TO-USER-GUIDE">User guide</a></li> <li><a href="LINK-TO-FAQ">User FAQ</a></li> </ul> </dd> <dt>How can users get technical support or report problems?</dt> <dd> <ul class="sample1"> <li>Support: DESCRIPTION</li> <li>Issue tracking: DESCRIPTION</li> </ul> </dd> </dl> </div> <!-- /support --> <div id="glossary"> <h3>Glossary</h3> <div class="todo"> TODO: Define any technical terms that you use above, if a new member of the team would not already know them. This is condensed from the <a href="glossary.html">glossary</a> documents. </div> <dl class="sample1"> <dt>TECHNICAL TERM</dt> <dd>DEFINITION</dd> <dt>TECHNICAL TERM</dt> <dd>DEFINITION</dd> <dt>TECHNICAL TERM</dt> <dd>DEFINITION</dd> <dt>TECHNICAL TERM</dt> <dd>DEFINITION</dd> </dl> </div> <!-- /glossary --> </div> <div class="todo"> TODO: Check for <a href="http://readyset.tigris.org/words-of-wisdom/all-in-one.html">words of wisdom</a> and discuss ways to improve this template. </div> <div class="legal1">Company Proprietary</div> <div class="footnote"> Copyright © 2003-2004 Jason Robbins. All rights reserved. <a href="readyset-license.html">License terms</a>. Retain this copyright statement whenever this file is used as a template. </div> </div> </body> </html> --- NEW FILE: plan.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "css/readyset.css"; @import "css/inst.css"; /* ]]> */ </style> <link rel="stylesheet" type="text/css" href="css/print.css" media="print" /> <title>Project Plan</title> </head> <body> <div class="app"> <div class="readyset"> <h2>Project Plan</h2> <div id="projectinfo"> <h3>Project Information</h3> <table border="1" cellpadding="3" cellspacing="2" class="axial"> <tr> <th>Project:</th> <td><a href="index.html">PROJECTNAME</a></td> </tr> <tr> <th>Project Time-frame:</th> <td>STARTDATE - ENDDATE</td> </tr> <tr> <th>Attached worksheets:</th> <td> <div>Plan > <a href="resource-needs.html">Resource needs</a></div> </td> </tr> <tr> <th>Related Documents:</th> <td> <div><a href="proposal.html">Project proposal</a> > <a href="target-and-benefits.html">Target audience and benefits</a></div> <div><a href="sdm.html">Software development methodology</a></div> <div><a href="glossary.html">Glossary</a></div> </td> </tr> </table> </div> <!-- /projectinfo --> <div id="processimpact"> <strong>Process impact:</strong> This plan will be used to evaluate and manage the project. Key assumptions that affect the plan should be documented here. The project plan should be updated throughout the life-time of the project. </div> <!-- /processimpact --> <div class="todo"> TODO: Fill in the information above and below. Add or remove rows as needed. Use the worksheet to help identify and scope resource needs. </div> <div id="summary"> <h3>Summary of Project</h3> <div class="sample1"> <p>ONE OR TWO SENTENCES HERE. For more information see the <a href="proposal.html">Project proposal</a>.</p> <p>IF YOU PLAN TO ORGANIZE YOUR WORK ACCORDING TO A ROUGH BREAKDOWN OF SOFTWARE COMPONENTS, BRIEFLY DESCRIBE THOSE COMPONENTS HERE. FOUR TO TEN BULLETS.</p> </div> </div> <!-- /summary --> <div id="methodology"> <h3>Summary of Methodology</h3> <dl> <dt>What general development approach will be used?</dt> <dd class="sample1">THREE TO FIVE SENTENCES OR BULLETS HERE. COVER GENERAL APPROACH, IMPORTANT ASSUMPTIONS, KEY PRACTICES, AND PROJECT COORDINATION CONTROLS. For more information see the <a href="sdm.html">Software Development Methodology</a>.</dd> <dt>How will the project team be organized?</dt> <dd class="sample1">The development team will consist of ...</dd> <dd class="sample2">The change control board will consist of ...</dd> <dt>What development and collaboration tools will be use?</dt> <dd>We plan to use the following tools extensively through out the project: <ul> <li>Project website</li> <li>Project mailing lists</li> <li>Issue tracking system</li> <li>Version control system</li> <li>Automated build system</li> <li>Automated unit test system</li> </ul> </dd> <dt>How will changes be controlled?</dt> <dd class="sample1"> <ul> <li>Requests for requirements changes will be tracked in the issue tracker</li> <li>The change control board (<a class="def" href="glossary-std.html#ccb">CCB</a>) will review requested changes and authorize work on them as appropriate</li> <li>After the <a class="def" href="glossary-std.html#featurecomplete">feature complete</a> milestone, no new features will be added to this release.</li> <li>After the <a class="def" href="glossary-std.html#codecomplete">code complete</a> milestone, no entirely new product source code will be added to this release.</li> <li>All source code commit log messages must refer to a specific issue ID, after the feature complete milestone.</li> </ul> </dd> <dt>How will this plan be updated?</dt> <dd>This project plan will be updated as needed throughout the project. It will be placed under version control and instructions for accessing it will be on the <a href="index.html">project website</a>. Any change to the plan will cause an automatic notification to be sent to a project mailing list.</dd> </dl> </div> <!-- /methodology --> <div id="wbs"> <h3>Work Breakdown Structure and Estimates</h3> <div class="todo"> TODO: List tasks that will be needed for this project. Keep dividing tasks into subtasks until you feel that you have enough detail to expose risks and make reasonable estimates in ideal engineering hours. </div> <div class="tip"> TIP: Label each step uniquely to show its position in the WBS, e.g., Step 1.1.4.A. Use numbers for steps that you intend to do in sequence, and use letters for steps that you intend to do in parallel. E.g., Step 1.1 comes before Steps 1.2.A and 1.2.B, but those two steps may be done in parallel, and Step 1.3 will be done after all 1.2.* steps have been finished. Don't worry about renumbering if you delete a step. </div> <div class="sample1"> <table border="1" cellpadding="3" cellspacing="2"> <tr><th>Step</th><th>Description</th><th>Estimate</th></tr> <tr><th>1.</th><td>Preparation</td><td></td></tr> <tr><th>1.1.</th><td class="level2">Developer training</td><td>30h</td></tr> <tr><th>2.</th><td>Inception</td><td></td></tr> <tr><th>2.1.</th><td class="level2">Requirements gathering</td><td>30h</td></tr> <tr><th>2.2.</th><td class="level2">Requirements specification</td><td>20h</td></tr> <tr><th>2.3.</th><td class="level2">Requirements validation</td><td>10h</td></tr> <tr><th>3.</th><td>Elaboration</td><td></td></tr> <tr><th>3.1.</th><td class="level2">High-level design</td><td>5h</td></tr> <tr><th>3.2.</th><td class="level3">Low-level design (break down by component)</td><td></td></tr> <tr><th>3.2.A.</th><td class="level4">Object design</td><td>10h</td></tr> <tr><th>3.2.B.</th><td class="level4">User interface design</td><td>10h</td></tr> <tr><th id="3.2.C">3.2.C.</th><td class="level4">Database design</td><td>3h</td></tr> <tr><th>3.3.</th><td class="level3">Design review and evaluation</td><td>5h</td></tr> <tr><th>4.</th><td>Construction</td><td></td></tr> <tr><th>4.1.A.</th><td class="level2">System implementation</td><td></td></tr> <tr><th>4.1.A.1.</th><td class="level3">Implement COMPONENT-NAME 1</td><td>25h</td></tr> <tr><th>4.1.A.2.</th><td class="level3">Implement COMPONENT-NAME 2</td><td>25h</td></tr> <tr><th>4.1.A.3.</th><td class="level3">Implement COMPONENT-NAME 3</td><td>25h</td></tr> <tr><th>4.1.A.4.</th><td class="level3">Implement COMPONENT-NAME 4</td><td>25h</td></tr> <tr><th>4.1.A.5.</th><td class="level3"> <div>Integrate Components</div> <div>(mostly done during component implementation)</div> </td><td>5h</td></tr> <tr><th>4.1.B.</th><td class="level2">Technical documentation (break down by component)</td><td>10h</td></tr> <tr><th>4.1.C.</th><td class="level2">User documentation (break down by component)</td><td>10h</td></tr> <tr><th>4.1.D.</th><td class="level2">Testing</td><td></td></tr> <tr><th>4.1.D.1.</th><td class="level3">Test planning</td><td>10h</td></tr> <tr><th>4.1.D.2.</th><td class="level3">Test code implementation (break down by component)</td><td>30h</td></tr> <tr><th>4.1.D.3.</th><td class="level3">Test execution</td><td>10h</td></tr> <tr><th>4.2.</th><td class="level2">Implementation review and evaluation</td><td>15h</td></tr> <tr><th>5.</th><td>Transition</td><td></td></tr> <tr><th>5.A.</th><td class="level2">Release packaging</td><td>3h</td></tr> <tr><th>5.B.</th><td class="level2">Documentation for other groups</td><td>3h</td></tr> <tr><th>6.</th><td>Reflection</td><td></td></tr> <tr><th>6.1. </th><td class="level2">Postmortem report</td><td>10h</td></tr> <tr><th></th><th>Total</th><th>329 hours</th></tr> </table> </div> </div> <!-- /wbs --> <div id="deliverables"> <h3>Deliverables in this Release</h3> <div class="todo"> TODO: List project deliverables in detail, with delivery dates. </div> <table border="1" cellpadding="3" cellspacing="2" width="100%"> <tr> <th>Deliverable Name</th> <th>Description</th> <th>Delivery Date</th> </tr> <tr> <td>Deliverable Name</td> <td>Description</td> <td>Delivery Date</td> </tr> <tr> <td>Deliverable Name</td> <td>Description</td> <td>Delivery Date</td> </tr> <tr> <td>Deliverable Name</td> <td>Description Description Description Description Description Description Description Description</td> <td>Delivery Date</td> </tr> <tr> <td>Deliverable Name</td> <td>Description</td> <td>Delivery Date</td> </tr> </table> </div> <!-- /deliverables --> <div id="schedule"> <h3>Schedule for this Release</h3> <div class="todo"> TODO: Make the rows in this table match the steps in your WBS above. If you have a large number of detailed steps, you can skip the most detailed ones. The columns of the table represent weeks of calendar time. For each cell in the table, enter the number of hours ideal engineering time that the team will spend on that task that week. Total your hours across and down. </div> <div class="tip"> TIP: These hours should total to the same as the total of the hours listed in your <a href="resource-needs.html">resource needs</a> document. And, the hours for each type of effort resources needed should correspond to the sum for each type of task. </div> <table border="1" cellpadding="3" cellspacing="2" width="100%"> <tr> <th>Task \ Week</th> <th>W-01</th> <th>W-02</th> <th>W-03</th> <th>W-04</th> <th rowspan="100"> </th> <th>W-05</th> <th>W-06</th> <th>W-07</th> <th>W-08</th> <th rowspan="100"> </th> <th>W-09</th> <th>W-10</th> <th>W-11</th> <th>W-12</th> <th>Task Total </th> </tr> <tr> <th>1.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>2.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>3.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>4.1.A.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>4.1.B.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>4.1.C.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>4.1.D.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>4.2.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>5.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>6.</th> <td>00</td> <!-- Week 01 --> <td>00</td> <!-- Week 02 --> <td>00</td> <!-- Week 03 --> <td>00</td> <!-- Week 04 --> <td>00</td> <!-- Week 05 --> <td>00</td> <!-- Week 06 --> <td>00</td> <!-- Week 07 --> <td>00</td> <!-- Week 08 --> <td>00</td> <!-- Week 09 --> <td>00</td> <!-- Week 10 --> <td>00</td> <!-- Week 11 --> <td>00</td> <!-- Week 12 --> <th>00</th> <!-- Task Total --> </tr> <tr> <th>Weekly Totals</th> <th>00</th> <!-- Week 01 --> <th>00</th> <!-- Week 02 --> <th>00</th> <!-- Week 03 --> <th>00</th> <!-- Week 04 --> <th>00</th> <!-- Week 05 --> <th>00</th> <!-- Week 06 --> <th>00</th> <!-- Week 07 --> <th>00</th> <!-- Week 08 --> <th>00</th> <!-- Week 09 --> <th>00</th> <!-- Week 10 --> <th>00</th> <!-- Week 11 --> <th>00</th> <!-- Week 12 --> <th>00</th> <!-- Project Total --> </tr> </table> </div> <!-- /schedule --> <div id="risks"> <h3>Risk Management</h3> <div class="todo"> TODO: List and rank the major risks of this project, and what you plan to do to mitigate each risk. If you don't plan to do anything to mitigate the risk, state that. </div> <p>The main risks of this project are:</p> <ol class="sample1"> <li>There is a potential conflict between the goals of a high-quality appearance and one that is completely customizable. We can only succeed if players find the web site appealing, and game vendors can customize it with no more effort than would be needed to build a static website. We already have a design in mind that will address this risk and we will review it with a web site designer who worked for a game vendor site.</li> <li>There are significant technical difficulties in building a web site and web application. This will be a risk because one person on our team has much experience with the relevant tools and technologies. Although the others will learn, we will certainly make some mistakes and suboptimal choices. We will address this risk by scoping the project such that we have enough time to train and to review the design and implementation.</li> <li>The schedule for this project is very short. We will manage this by planning a conservatively scoped functional core and series of functional enhancements that can be individually slipped to later releases if needed.</li> <li>The performance of the system will be significantly impacted by the decisions made during the <a href="#3.2.C">database design task</a>. None of our current team members has experience with database optimization. To address this, we will arrange a review meeting with an experienced DBA or hire a consultant from the database vendor.</li> <li>We could be underestimating known tasks. HOW TO AVOID/MITIGATE?</li> <li>We could be underestimating the impact of unknown tasks. HOW TO AVOID/MITIGATE?</li> <li>We could be underestimating the dependencies between tasks. HOW TO AVOID/MITIGATE?</li> <li>We could have misunderstood the customer's requirements. HOW TO AVOID/MITIGATE?</li> <li>The customer could change the requirements. HOW TO AVOID/MITIGATE?</li> <li>We could face major difficulties with the technology chosen for this project. HOW TO AVOID/MITIGATE?</li> <li>We could have low quality that demands significant rework. HOW TO AVOID/MITIGATE?</li> <li>We could incorrectly assess our progress until it is too late to react. HOW TO AVOID/MITIGATE?</li> <li>We could lose resources. E.g., team members could get sick, spend time on other projects, or quit. HOW TO AVOID/MITIGATE?</li> <li>There may be a mis-alignment of stakeholder goals or expectations. HOW TO AVOID/MITIGATE?</li> </ol> </div> <!-- /risks --> <div id="dependencies"> <h3>Project Planning Dependencies</h3> <dl> <dt>Does this project conflict or compete for resources with any other project?</dt> <dd class="sample1">No, this is the only project that we are working on.</dd> <dd class="sample2">Yes, and we have determined how many hours each person can actually dedicate to this project.</dd> <dt>Are the same human or machine resources allocated to maintenance of past versions and/or planning of future versions during this release time period?</dt> <dd class="sample1">No, this is the first release and we will not plan the next release.</dd> <dd class="sample2">Yes, we predict that team members will spend an average of 20% of their time maintaining previous releases and planning future releases during this release time frame. Some weeks may be higher if an urgent patch to a previous release is needed.</dd> <dt>Does this project depend on the success of any other project?</dt> <dd class="sample1">No, this project stands alone.</dd> <dd class="sample2">Yes, project P1 must provide library L, and project P2 must prove the usability of feature F, and....</dd> <dt>Does any other project depend on this project?</dt> <dd class="sample1">No, project is not producing any components that will be used in other current projects.</dd> <dd class="sample2">Yes, we must produce library L for our project and support users of L in projects P1 and P2.</dd> <dt>Are there any other important depenencies that will affect this project?</dt> <dd class="sample1">No, everything is covered above.</dd> <dd class="sample2">Yes. DETAILS....</dd> </dl> </div> <!-- /depenencies --> </div> <div class="todo"> TODO: Check for <a href="http://readyset.tigris.org/words-of-wisdom/plan.html">words of wisdom</a> and discuss ways to improve this template. </div> <div class="legal1">Company Proprietary</div> <div class="footnote"> Copyright © 2003-2004 Jason Robbins. All rights reserved. <a href="readyset-license.html">License terms</a>. Retain this copyright statement whenever this file is used as a template. </div> </div> </body> </html> --- NEW FILE: user-needs.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "css/readyset.css"; @import "css/inst.css"; /* ]]> */ </style> <link rel="stylesheet" type="text/css" href="css/print.css" media="print" /> <title>User Needs</title> </head> <body> <div class="app"> <div class="readyset"> <h2>User Needs</h2> <div id="projectinfo"> <h3>Project Information</h3> <div class="axial"> <table border="1" cellpadding="3" cellspacing="2"> <tr> <th>Project:</th> <td><a href="index.html">PROJECTNAME</a></td> </tr> <tr> <th>Attached worksheets:</th> <td> <div>User needs > <a href="interview-notes.html">Interview notes</a></div> </td> </tr> <tr> <th>Related Documents:</th> <td> <div><a href="proposal.html">Project proposal</a> > <a href="target-and-benefits.html">Target audience and benefits</a></div> <div><a href="srs.html">Software requirements specification</a></div> <div><a href="glossary.html">Glossary</a></div> </td> </tr> </table> </div> </div> <!-- /projectinfo --> <div id="processimpact"> <strong>Process impact:</strong> The statement of user needs documents and explains the actual desires of stakeholders in roughly their own words. What they <i>desire</i> is never exactly what the product <i>provides</i>. Documenting user needs here, independently from the <a href="srs.html">SRS</a>, helps to keep the SRS precise and makes the tasks of verification and validation more effective. This document is <em>not</em> an informal draft of the SRS, it is different document with a complementary purpose. </div> <!-- /processimpact --> <div id="agreedgoals"> <h3>Agreed Goals</h3> <div class="todo"> TODO: Has there been a clear statement of the overall goal of this project that the stakeholders agree to? If so, paste it here or add a hyperlink. If not, you should summarize your understanding of the project goals into a brief statement and try to get the stakeholders to agree to it. The text below gi... [truncated message content] |
