-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathtImplBridgeWebsite.htm
198 lines (184 loc) · 11.5 KB
/
tImplBridgeWebsite.htm
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en"><head><!-- saved from url=(0022)http://internet.e-mail -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Duplicate Bridge Contest Website</title>
<style>
</style>
</head><body _texified="true">
<h2>tDsgnRvw, tDsgn, tCodeRvw, tImpl, tPoster<br>
Duplicate Bridge Contest
Website
<a href="http://www.cs.ou.edu/%7Erlpage/SEtools/Projects/tImplFAQ.htm">FAQ</a></h2>
<p>Due dates - see lesson plan: <a href="http://www.cs.ou.edu/%7Erlpage/SEtools/syllabusSEf10.pdf">http://www.cs.ou.edu/~rlpage/SEtools/syllabusSEf10.pdf<br>
</a><i>Note</i>: This project has five deliverables: tDsgnRvw, tDsgn, tCodeRvw,
tImpl, tPoster</p>
<h3>Purpose of exercise</h3>
<ul>
<li>Practice working as a team in a software development project</li>
<li>Practice creating and documenting a modular software design</li>
<li>Practice doing proxy-based estimation of software size from historical
data and conceptual design</li>
<li>Practice performing design and code reviews as a team</li>
<li>Practice writing equation-based software using Modular ACL2</li>
<li>Practice developing software testing suites</li>
<li>Practice defining contracts guaranteeing properties of objects delivered
by software modules</li>
<li><a href="http://www.cs.ou.edu/%7Erlpage/SEtools/ABEToutcomes.pdf">ABET
Outcomes</a> C, D, H, I, K</li>
</ul>
<h3>Project</h3>
<p>Design, document, and implement software to generate, from XML data
files, interlinked HTML files that make it convenient for participants
in a
duplicate bridge contest to review results. Contestants should be able
to see <a href="http://www.cs.ou.edu/%7Erlpage/SEtools/Projects/tImplFiles/Ex1/HR051115A.html">boards</a>,
with or without <a href="http://www.cs.ou.edu/%7Erlpage/SEtools/Projects/tImplFiles/Ex1/HRTR051115A.html">travelers</a>, <a href="http://www.cs.ou.edu/%7Erlpage/SEtools/Projects/tImplFiles/Ex1/RK051115A.html">rankings</a>,
and <a href="http://www.cs.ou.edu/%7Erlpage/SEtools/Projects/tImplFiles/Ex1/PSC051115A.html">personal score cards</a>. They
should also be able navigate among these displays. For example, contestants
looking at rankings may want to see their personal scorecards. Or, a contestant
looking at a personal scorecard may want to link to the display for a particular
board. A contestant looking at a board may want to see expand the view to see
the traveler associated with it.</p>
<p> You can <a href="http://www.cs.ou.edu/%7Erlpage/SEtools/Projects/tImplFiles.zip"> download</a> some example XML data files and
associated HTML files containing board displays, travelers, rankings, and
personal scorecards. </p>
<p>To get some ideas for designing the interlinked HTML
files your software will deliver, you might want to look at an <a href="http://www.bridgewebs.com/cgi-bin/bwnd/travellers.cgi?pid=display_hands&msec=1&sessid=314675036769792&event=20101001_1&wd=1&club=denverhousecards">existing
website</a>.<br>
<i>Note</i>: This website one is more elaborate and contains more kinds of data than the example XML files
provided for this project.</p>
<h3><font color="#0000ff">What to turn in<br>
</font>There are five separate deliverables, four of which require both paper and
dropbox submissions</h3>
<h4><i><font color="#0000ff">tDsgnRvw </font></i></h4>
<ul>
<li>Paper submission:</li>
</ul>
<blockquote>
<ol>
<li>Requirements stating the services that the software will provide, including
the interlinking scheme designed for the convenience of contestants in
reviewing results.</li>
<li>Design describing the planned architecture of modules comprising the
software, interfaces between components, and services supplied by modules
and components, with annotations from design review<br>
<i>Note</i>: Design review focuses on finding defects in the design. Annotations
describe defects found and, for each defect, specify which team member will
follow up with a solution. Annotations may be hand written and do not need
to be cleaned up for presentation. The goal is to document the review
proceedings and results.</li>
</ol>
</blockquote>
<ul>
<li><a href="http://www.cs.ou.edu/%7Erlpage/SEtools/RulesForProjectSubmissions.htm#naming">Dropbox
submission</a>: PDF scan of the
submitted paper</li>
</ul>
<h4><i><font color="#0000ff">tDsgn</font></i></h4>
<ul>
<li> Paper submission:</li>
</ul>
<blockquote>
<ol>
<li>Modular architecture of software design</li>
<li>Interfaces between modules and components, including descriptions data
structures for communication of data among components</li>
<li>Contracts guaranteeing a few important properties of components in modules</li>
<li>Algorithmic considerations where appropriate</li>
<li>PROBE estimate of software size</li>
<li>PSP++ report providing estimated time and confidence intervals for this
project, based on project data for past projects of all team members and
PROBE estimates for this project</li>
</ol>
</blockquote>
<ul>
<li><a href="http://www.cs.ou.edu/%7Erlpage/SEtools/RulesForProjectSubmissions.htm#naming">Dropbox archive</a>:</li>
</ul>
<blockquote>
<ol>
<li>PDF version of paper submission</li>
<li>PSP data files used to generate the PSP++ report (includes PSP data
files of all team members for past projects)</li>
</ol>
</blockquote>
<h4><i><font color="#0000ff">tCodeRvw </font></i></h4>
<ul>
<li> Paper submission: printed copy of code reviewed, with annotations
describing defects uncovered in review and team members assigned to fix them</li>
<li><a href="http://www.cs.ou.edu/%7Erlpage/SEtools/RulesForProjectSubmissions.htm#naming">Dropbox
submission</a>: PDF scan of the
submitted paper</li>
</ul>
<h4><i><font color="#0000ff">tImpl</font></i></h4>
<ul>
<li>Paper submission:</li>
</ul>
<blockquote>
<ol>
<li>Updated software design</li>
<li>Test files (adequate sanity checks, non-i/o functions)</li>
<li>Predicate-test file (predicate-based tests of functions a few functions that do not perform
i/o)</li>
<li>Modular ACL2 code implementing required software</li>
<li>Browser display of HTML file produced by running PSP++ on the completed
PSP records for project combining contributions of all team members</li>
</ol>
</blockquote>
<ul>
<li><a href="http://www.cs.ou.edu/%7Erlpage/SEtools/RulesForProjectSubmissions.htm#naming"> Dropbox archive</a>:</li>
</ul>
<blockquote>
<ol>
<li>PDF version of paper submission</li>
<li>PSP data files used to generate the PSP++ report</li>
<li>Input files used to demonstrate the software</li>
<li>Corresponding output files</li>
</ol>
</blockquote>
<h4><i><font color="#0000ff">tPoster </font></i>(paper submission and
poster-session participation; no dropbox submission required)</h4>
<blockquote>
<p>The team will prepare a product demonstration and poster presentation (one
science-fair style poster, describing the project history, results, and
features) suitable for supporting one-on-one discussions about the team
project with other students and faculty members. Team members will conduct
their demo and display and discuss their poster with visitors during the
Poster Presentation Session. </p>
<p>During part of the afternoon, team members will be discussing its poster
with others, and in the remainder of the afternoon, they will be visiting the
poster presentations of teams from other courses. All team members must be
present for the during the entire session. (If you have a conflict that
prevents your presence at all or part of the session, please discuss it with
the instructor.)</p>
<p>At least two team members must be with the poster at all times. Team
members not on duty with the poster will be talking to other presenters, many
of whom will be students representing other projects and courses, not SE
students. Arrange your schedule so that you are working at your poster during
half of the period and visiting other posters during the remaining half.</p>
<p><b>Poster Guidelines<br>
</b>When preparing your poster, imagine trying to pitch your software
product to an engineering manager knowledgeable about software, but who knows
nothing about what your product does or how it does it. Your poster should be
visually appealing, easy to read from three feet away, and attractive from
eight feet away. It should elucidate ideas in a way that prompts questions
from interested observers, giving you a chance to describe your product in
more detail. </p>
<p>A 30"x40" poster board and easel to support it will be provided, along with some
kind of horizontal surface for a laptop. Could be as primitive as a chair. No
power. Teams are responsible for mounting their presentation to the board and
setting up their demo prior to the Poster Presentation Session. The materials
will be available in the poster-session location one hour prior to the
session. Further guidelines reside on the <a href="#wiki">poster registration
website</a>. However, ignore the guidelines about abstracts, conclusions, and
"the paper." You won't have those things.</p>
<p><b><a name="wiki"></a>Poster Registration</b><br>
Register through the following wiki by Monday, November 30:<a href="http://www.cs.ou.edu/twiki/bin/view/TWiki/TWikiRegistration"><br>
</a><a href="http://www.cs.ou.edu/twiki/bin/view/ComputerScience/CSPosterSessionFall2010">http://www.cs.ou.edu/twiki/bin/view/ComputerScience/CSPosterSessionFall2010</a><br>
One member from each team must register the team's poster. That team member's
name and email address go into the registration (but list all team members as
authors). The team should agree on a password. Use the team name for the
WikiName entry. Leave the entry for "organization name" blank, but use <a href="http://www.cs.ou.edu/">http://www.cs.ou.edu</a>
for the URL of the organization.</p>
</blockquote>
<p> </p>
</body></html>