diff --git a/assignments.html b/assignments.html new file mode 100644 index 0000000..a37692f --- /dev/null +++ b/assignments.html @@ -0,0 +1,60 @@ + + + + + + CS 495 Assignments + + + +

CS 495 Assignments

+ + + + + + + + + + + + + + +
Due dateAssignmentValueDescription
Monday 9/16/2024 10:00pmMilestone 180 pointsWith your team, complete the requirements document for your project. Use the “campus visits” document as a guide. The completed document needs to include: +
    +
  1. 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,
    2. +
  2. 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),
    3. +
  3. all queries (information the system provides to the users about the problem domain) including the query results and user-provided parameters,
    4. +
  4. any notifications and their triggers,
    5. +
  5. 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),
    6. +
  6. 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).
    7. +
+ Also, include the following sections (some might be quite brief, depending on your project): +
    +
  • Overview
    • +
  • System Expectations
    • +
  • Platform
    • +
  • User Permissions
    • +
  • Security
    • +
  • Preferences
    • +
  • Likely Changes
    • +
+ For grading purposes, I will make a copy of your team's repository shortly after the deadline. +
+ + \ No newline at end of file