You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

66 lines
3.2 KiB

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>CS 495 Assignments</title>
<style>
table {
border-collapse: collapse;
}
td {
border: 1px solid black;
}
.center {
text-align: center;
}
.top {
vertical-align: top;
}
</style>
</head>
<body>
<h1>CS 495 Assignments</h1>
<table>
<tr>
<th>Due date</th>
<th>Assignment</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td class="center top">Wednesday 9/18/2024 9:00am</td>
<td class="center top">Assignment 1</td>
<td class="center top">5 points</td>
<td class="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>
</tr>
<tr>
<td class="center top">Monday 9/16/2024 10:00pm</td>
<td class="center top">Milestone 1</td>
<td class="center top">80 points</td>
<td class="top">With your team, complete the requirements document for your project. Use the &ldquo;campus visits&rdquo; 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.
</td>
</tr>
</table>
</body>
</html>