Midterm Exam 1 halfsheets

.gitignore

+.idea/
+out/
\ No newline at end of file

README.md

 # halfsheets
 
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://git.unl.edu/soft-core/soft-160/halfsheets.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://git.unl.edu/soft-core/soft-160/halfsheets/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+Study guides for SOFT 160
\ No newline at end of file

exam1-fullsheets.tex

+\documentclass[11pt, landscape]{article}
+\input{preamble}
+\renewcommand{\exam}{Midterm~1}
+
+\begin{document}
+    \LARGE
+    \renewcommand{\arraystretch}{2}
+    \begin{enumerate}
+        \item \input{exam1/quality_dimension-metric-artifact} \newpage
+        \item \input{exam1/design-an-algorithm_3-things-different} \newpage
+        \item \input{exam1/why-processes} \newpage
+        \item \input{exam1/tools} \newpage
+        \item \input{exam1/actor-activity-artifact} \newpage
+        \item \input{exam1/perspectives} \newpage
+        \item \input{exam1/abstraction-composition} \newpage
+        \item \input{exam1/design-an-algorithm_increase_team_score}
+    \end{enumerate}
+\end{document}
\ No newline at end of file

exam1-halfsheets.tex

+\documentclass[11pt, portrait]{article}
+\input{preamble}
+\renewcommand{\exam}{Midterm~1}
+
+\begin{document}
+    \renewcommand{\arraystretch}{2}
+    \begin{enumerate}
+        \item \input{exam1/quality_dimension-metric-artifact} \vspace{3cm}
+        \item \input{exam1/design-an-algorithm_3-things-different} \newpage
+        \item \input{exam1/why-processes} \vspace{7cm}
+        \item \input{exam1/tools} \newpage
+        \item \input{exam1/actor-activity-artifact} \vspace{1.5cm}
+        \item \input{exam1/perspectives} \newpage
+        \item \input{exam1/abstraction-composition} \vspace{6cm}
+        \item \input{exam1/design-an-algorithm_increase_team_score}
+    \end{enumerate}
+\end{document}
\ No newline at end of file

exam1/abstraction-composition.tex

+Abstraction and composition are both problem-solving techniques that involve thinking about a larger problem.
+\begin{enumerate}
+    \item Define ``abstraction''.
+    \item Define ``composition''.
+    \item Give an example of applying abstraction to a problem.
+    \item Give an example of applying composition to a problem.
+    \item Explain the difference between these two techniques.
+\end{enumerate}
\ No newline at end of file

exam1/actor-activity-artifact.tex

+Suppose you are part of a software team developing a mobile app and that you need to update your app for the latest version of a particular phone.
+Complete the timeline below with software development activities that may be performed to make the update.
+Each row should list who acts, what action they take, and an affected artifact.
+\begin{center}
+%    \renewcommand{\arraystretch}{2}
+    \tabcolsep=10pt
+    \begin{tabular}{cccc}
+        \textbf{\#} & \textbf{Actor} & \textbf{Activity}     & \textbf{Affected Artifact}  \\ \hline
+        1           & Users          & Request the Upgrade   & Issues in the Issue Tracker \\ \hline
+        2           & Developers     &                       & Design Documentation        \\ \hline
+        3           & Developers     & Implement the Upgrade & Code                        \\ \hline
+        4           & Developers     & Review                &                             \\ \hline
+        5           & Testers        &                       & Test Cases                  \\ \hline
+        6           & Testers        &                       & Issues in the Issue Tracker \\ \hline
+    \end{tabular}
+\end{center}
\ No newline at end of file

exam1/design-an-algorithm_3-things-different.tex

+Design an algorithm that when given three items, determines if they are all different.
+\textit{You may assume that comparing two items and printing a result can each be done in a single step.}
+\begin{enumerate}
+    \item State any additional assumptions you make about the problem.
+    \item State the problem inputs and outputs.
+    \item Specify the problem decomposition and solution components and the mapping from solution components to subproblems.
+    \item Write the algorithm in pseudocode.
+    \item Evaluate your algorithm by trying it in at least two different scenarios.
+    Does your algorithm produce the results you expected?
+\end{enumerate}
\ No newline at end of file

exam1/design-an-algorithm_increase_team_score.tex

+Design an algorithm that when given a team name, increases the team's score on the scoreboard by six points.
+\textit{You may assume that getting the first team name on the scoreboard, getting the second team name on the scoreboard, getting the first score on the scoreboard, getting the second score on the scoreboard, and checking if two team names are the same can all each be done in a single step.}
+\begin{enumerate}
+    \item State any additional assumptions you make about the problem.
+    \item State the problem inputs and outputs.
+    \item Specify the problem decomposition and solution components and the mapping from solution components to subproblems.
+    \item Write the algorithm in pseudocode.
+    \item Evaluate your algorithm by trying it in at least two different scenarios.
+    Does your algorithm produce the results you expected?
+\end{enumerate}
\ No newline at end of file

exam1/perspectives.tex

+End users and software developers both have software-quality concerns, although these concerns may differ.
+\begin{enumerate}
+    \item Give an example of a dimension of quality that is important from both perspectives.
+    Justify your answer.
+    \item Give an example of a dimension of quality that is important to developers but not end users.
+    Justify your answer.
+    \item Give an example of a dimension of quality that is important to end users but not developers.
+    Justify your answer.
+\end{enumerate}

exam1/quality_dimension-metric-artifact.tex

+Fill in the blank cells in the following table so that each row lists a quality dimension, a metric that can be used to measure quality along that dimension, and an artifact measured by that metric.
+You may need to repeat entries within a column.
+\begin{center}
+%    \renewcommand{\arraystretch}{3}
+    \tabcolsep=10pt
+    \begin{tabular}{ccc}
+        \textbf{Quality Dimension} & \textbf{Metric}                             & \textbf{Artifact}  \\ \hline
+        Maintainability            & Number of Commits per Week                  &                    \\ \hline
+        Testedness                 &                                             & Test Cases         \\ \hline
+        \phantom{x}                & Number of Methods                           & Code               \\ \hline
+        \phantom{x}                & Number of Officially Supported Devices      & User Documentation \\ \hline
+        Security                   & Number of Security Vulnerabilities Reported &                    \\ \hline
+    \end{tabular}
+\end{center}
\ No newline at end of file

exam1/tools.tex

+For each of the following software engineering tools, describe what functionality the tool provides (i.e., what does it enable software development teams to do?) and explain the potential consequences of not having this functionality available to a software development team.
+\begin{enumerate}
+    \item Issue tracker
+    \item IDE
+    \item Version control system
+\end{enumerate}
\ No newline at end of file

exam1/why-processes.tex

+Without established software quality processes and conventions, software development teams are liable to encounter problems.
+\begin{enumerate}
+    \item List three types of problems you would expect a software development team to face in the absence of processes and conventions?
+    \item For each problem, list a kind of software quality process or convention that could help the team avoid that problem.
+\end{enumerate}
\ No newline at end of file

preamble.tex

+\usepackage{fullpage}
+
+% headers and footers
+\usepackage{fancyhdr}
+\pagestyle{fancy}
+\fancyhf{}
+\headheight=14pt
+\headsep=16pt
+\lhead{SOFT~160}
+\chead{}
+\newcommand{\exam}{specify the exam being reviewed}
+\rhead{\exam~Review}
+\lfoot{}
+%\cfoot{\thepage}
+\cfoot{}
+\rfoot{}
+
+% paragraph formatting
+\parindent=0pt
+\parskip=6pt
+
+% hyperlinks
+\usepackage[hidelinks]{hyperref}
+
+% common math commands
+\usepackage{amsmath}
+\usepackage{amssymb}
+\newcommand{\card}[1]{\ensuremath{\left\lvert #1\right\rvert}}
+\newcommand{\floor}[1]{\ensuremath{\left\lfloor #1\right\rfloor}}
+\newcommand{\ceil}[1]{\ensuremath{\left\lceil #1\right\rceil}}
+\newcommand{\concat}{\ensuremath{\mathbin{+\!\!+}}}
+\newcommand{\false}{\ensuremath{\mathbf{0}}}
+\newcommand{\true}{\ensuremath{\mathbf{1}}}
+
+% pseudocode
+\usepackage[algo2e,lined,nofillcomment]{algorithm2e}
+\DontPrintSemicolon
+\newcommand{\uptext}[1]{\text{\upshape #1}}
+\SetKw{KwLet}{let}
+\newcommand{\Let}[2]{\KwLet{#1\({\null}\leftarrow{\null}\)#2}\;}
+\SetKwFor{Function}{function}{}{end}
+
+% graphics
+\usepackage{graphicx}
+
+% assessment commands
+\newcommand{\nameline}{\hbox{}\centerline{Name: \(\underbar{\qquad\qquad\qquad\qquad\qquad\qquad\qquad\qquad}\)}\hbox{}}
+\newcommand{\instructions}[1]{#1\vskip 0.75cm}
+\newcounter{q}
+\newenvironment{q}[1]{\vbox to #1\relax\bgroup\refstepcounter{q}{\textbf{\arabic{q}.\ }}\ignorespaces}{\par\vfill\egroup}
+\newenvironment{hwq}{\refstepcounter{q}{\textbf{\arabic{q}.\ }}\ignorespaces}{}
+\newcounter{qq}
+\makeatletter % eventually replace this block with \counterwithin*
+\@addtoreset{qq}{q}
+\makeatother % end block to replace
+\newenvironment{qq}{\parskip=-6pt\relax\begin{quote}\leavevmode\llap{\
+    refstepcounter{qq}{\textbf{\alph{qq}.\ }}}\ignorespaces}{\end{quote}}
+\newenvironment{key}{\begin{quote}\textcolor{blue}\bgroup\ignorespaces}{\egroup\end{quote}}
+%%%%% %%%%% %%%%%
+% \usepackage[algo2e,lined,nofillcomment]{../common/libraries/tex/algorithm2e}
+% \dontprintsemicolon
+%\SetKw{KwLet}{let}
+%\newcommand{\Let}[2]{\KwLet{#1\({\null}\leftarrow{\null}\)#2}\;}
+\SetKwFor{Forever}{forever}{do}{end}
+\SetKw{KwEnable}{enable}
+\newcommand{\Enable}[1]{\KwEnable{#1}\;}
+\SetKw{KwClock}{clock}
+
+% numbering
+\renewcommand{\labelenumi}{\textbf{\arabic{enumi}.}}
+\renewcommand{\labelenumii}{\textbf{\alph{enumii}.}}
\ No newline at end of file