Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
se2aa4_cs2me3
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
W. Spencer Smith
se2aa4_cs2me3
Commits
d46b870d
Commit
d46b870d
authored
7 years ago
by
W. Spencer Smith
Browse files
Options
Downloads
Patches
Plain Diff
Note added to A4 that performance is not an important consideration for the design
parent
9bb2dffd
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Assignments/A4/A4.tex
+7
-5
7 additions, 5 deletions
Assignments/A4/A4.tex
with
7 additions
and
5 deletions
Assignments/A4/A4.tex
+
7
−
5
View file @
d46b870d
...
...
@@ -63,11 +63,13 @@ using doxygen. Your test code should use \texttt{catch}, version 2.
\section
*
{
Step
\refstepcounter
{
stepnum
}
\thestepnum
}
Submit your design specification, written in LaTeX, of the MIS for the game state module. If your
specification requires additional modules, you should include their MISes as
well. It is up to you to determine your modules interface; that is, you decide
on the exported constants, access programs, exceptions etc. You also determine
your state variables and specify the semantics for your access program calls.
Submit your design specification, written in LaTeX, of the MIS for the game
state module. If your specification requires additional modules, you should
include their MISes as well. It is up to you to determine your modules
interface; that is, you decide on the exported constants, access programs,
exceptions etc. You also determine your state variables and specify the
semantics for your access program calls. Your design does not need to concern
itself with performance.
\section*
{
Part 2
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment