Complete SQL commands as directed in the <ahref="Homework\01\index.html">assignment writeup</a>. Submit your work in Educat.
</td>
</tr>
<tr>
<tdclass="center top">Wednesday 11/6/2024</td>
<tdclass="center top">In class: refactor the code</td>
<tdclass="center top">20 points</td>
<tdclass="top">
In a small group, refactor the .java code from the repo to increase cohesion and decrease coupling: <pre>notes\Day 38 (class and function design)\Improve the design</pre>Show me your work to get credit on this one.
<tdclass="top">Read section 2.3 starting with 2.3.1 (pg 39-50). Read Chapter 3 up through and including section 3.3. Also read 3.5.2, 3.6, and 3.7.</td>
<!-- Choose an agility principle from section 3.3.1 in the text (pg 69) and comment on whether and how it can be applied to each of the following lifecycle models: waterfall, iterative, incremental, spiral, evolutionary, code & fix. -->
With your team, make any fixes/additions to the requirements document, as indicated in my feedback.<br>
<br>
Also create a user interface prototype.
<ul>
<li>The prototype needs to be detailed enough to demonstrate how all queries, requirements, and notifications from your amended requirements document are met. If automated email or notifications are used as part of the system, provide a preview of that as well (please see the campus visit prototype in the notes for an example of how to do this).</li>
<li>It should be easy to split up the work on this one; people can work on different screens. If necessary, you can copy-paste screens in between two instances of Pencil to combine work.</li>
<li>For grading purposes, I will make a copy of your team's repository shortly after the deadline.</li>
<tdclass="top">In Chapter 11 of Pressman, read sections 11.1, 11.6, and 11.7. Do problem 11.1 at the end of the chapter and submit your answer in Educat.</td>
<tdclass="top">With your team, complete the requirements document for your project. Use the “campus visits” document as a guide. The completed document needs to include:
<ol>
<li>all relevant problem domain entities, their attributes, a short description of each attribute, and (in the case of enumeration types) a short description of each enumeration value,</li>
<li>the relations between entities and their cardinalities (if relations are few and simple this can be done with text, otherwise use a diagram; complicated relations may need both),</li>
<li>all queries (information the system provides to the users about the problem domain) including the query results and user-provided parameters,</li>
<li>any notifications and their triggers,</li>
<li>every problem domain event (occurences that have effects on the output of queries or notifications) and the source (how the system becomes aware of it),</li>
<li>and if any external (i.e. problem domain) software/hardware is under the system's direct control: each external piece's possible states, state transitions, and actions that can be performed on it by the system (including parameters, when the action happens, its duration, possible results, and how/if the sytem becomes aware of those results).</li>
</ol>
Also, include the following sections (some might be quite brief, depending on your project):
<ul>
<li>Overview</li>
<li>System Expectations</li>
<li>Platform</li>
<li>User Permissions</li>
<li>Security</li>
<li>Preferences</li>
<li>Likely Changes</li>
</ul>
For grading purposes, I will make a copy of your team's repository shortly after the deadline.
