Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
labs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
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
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
LiU-TDDD25
labs
Commits
4a1e1cde
Commit
4a1e1cde
authored
1 year ago
by
Anders Märak Leffler
Browse files
Options
Downloads
Patches
Plain Diff
lab0: Additional questions about system boundaries
parent
e220cdfb
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/lab0.pdf
+0
-0
0 additions, 0 deletions
doc/lab0.pdf
doc/lab0.tex
+19
-0
19 additions, 0 deletions
doc/lab0.tex
with
19 additions
and
0 deletions
doc/lab0.pdf
+
0
−
0
View file @
4a1e1cde
No preview for this file type
This diff is collapsed.
Click to expand it.
doc/lab0.tex
+
19
−
0
View file @
4a1e1cde
...
...
@@ -167,6 +167,25 @@ you should complete the implementation of the following three function in
\end{itemize}
Recall the note at the end of
\sref
{
data-format
}
.
\subsection
{
Additional questions
}
When demonstrating this lab (as with any lab in the course), you
should be able to explain your code, but also to evaluate it, and
relate it to course concepts. In many cases this will involve
discussing design choices and simplifications that have been made for
you, and may be somewhat speculative. In some cases you might be asked
to answer questions with (at least in retrospect) quite obvious
answers. In this lab, this might include questions such as
\begin{itemize}
\item
Thinking about the boundaries of the system: what happens if
two processes try to write to the database at the same time? Is
this something that we need to handle?
\end{itemize}
We do not require written answers to this, and you might not need to
provide a solution to all issues raised by the questions.
\section
{
Conclusion
}
Having completed the lab, you can now perform the reading and writing operations
on the database. However, if you run several instances of the application on
...
...
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