CS 112 PA #4 Like the previous programming assignment, this assignment builds off of a prior lab. In this assignment you will write a program that solves a maze by finding a connection between two locations within the maze. As was the case with the prior assignment, you will probably need the StringSplitter used in class and lab. Maze Text File Our maze will be read in via text file. The first line informs us of the number of spaces in the maze. Each line afterwards describes a connection between two points in the maze. For example: 2 1 S 2 2 N 1 The example above tells us that we have two spaces in our maze. Furthermore, we see that space 1 has a southern connection to space 2. Similarly, space 2 has a northward connection to space 1. The possible connections are N (north), E (east), S (south), and W (west). MazeSpace Each space in the maze will be represented by an object of type MazeSpace. Here's the UML class diagram: Additional Functions In addition to the MazeSpace class above, you must implement the following two functions. string depthFirstSearch(MazeSpace *spaces, int num_spaces, int start, int end) string breadthFirstSearch(MazeSpace *spaces, int num_spaces, int start, int end) These functions perform the depth / breadth first searches and returns a string that represents the path taken by each search pattern (see screenshot in the next section). Note that depending on how you implement your searches, you may not get the exact same output as what I provide. This is okay! Sample Output Below is sample output from my program: Header Comment, and Formatting 1. Be sure to modify the file header comment at the top of your script to indicate your name, student ID, completion time, and the names of any individuals that you collaborated with on the assignment. 2. Remember to follow the basic coding style guide. For a list of basic rules, see my website or examine my example files from previous assignments and labs. Reflection Essay In addition to the programming tasks listed above, your submission must include an essay that reflects on your experiences with this homework. This essay must be at least 350 words long. Note that the focus of this paper should be on your reflection, not on structure (e.g. introductory paragraph, conclusion, etc.). The essay is graded on content (i.e. it shows deep though) rather than syntax (e.g. spelling) and structure. Below are some prompts that can be used to get you thinking. Feel free to use these or to make up your own. · Describe a particular struggle that you overcame when working on this programming assignment. · Conversely, describe an issue with your assignment that you were unable to resolve. · Provide advice to a future student on how he or she might succeed on this assignment. 1. Describe the most fun aspect of the assignment. 1. Describe the most challenging aspect of the assignment. 1. Describe the most difficult aspect of the assignment to understand. 1. Provide.

1. CS 112 PA #4
Like the previous programming assignment, this assignment
builds off of a prior lab. In this assignment you will write a
program that solves a maze by finding a connection between
two locations within the maze. As was the case with the prior
assignment, you will probably need the StringSplitter used in
class and lab.
Maze Text File
Our maze will be read in via text file. The first line informs us
of the number of spaces in the maze. Each line afterwards
describes a connection between two points in the maze. For
example:
2
1 S 2
2 N 1
The example above tells us that we have two spaces in our
maze. Furthermore, we see that space 1 has a southern
connection to space 2. Similarly, space 2 has a northward
connection to space 1. The possible connections are N (north),
E (east), S (south), and W (west).
MazeSpace
Each space in the maze will be represented by an object of type
MazeSpace. Here's the UML class diagram:
Additional Functions
In addition to the MazeSpace class above, you must implement
the following two functions.
string depthFirstSearch(MazeSpace *spaces, int num_spaces, int
start, int end)
string breadthFirstSearch(MazeSpace *spaces, int num_spaces,
int start, int end)

2. These functions perform the depth / breadth first searches and
returns a string that represents the path taken by each search
pattern (see screenshot in the next section). Note that
depending on how you implement your searches, you may not
get the exact same output as what I provide. This is okay!
Sample Output
Below is sample output from my program:
Header Comment, and Formatting
1. Be sure to modify the file header comment at the top of your
script to indicate your name, student ID, completion time, and
the names of any individuals that you collaborated with on the
assignment.
2. Remember to follow the basic coding style guide. For a list
of basic rules, see my website or examine my example files
from previous assignments and labs.
Reflection Essay
In addition to the programming tasks listed above, your
submission must include an essay that reflects on your
experiences with this homework. This essay must be at least
350 words long. Note that the focus of this paper should be on
your reflection, not on structure (e.g. introductory paragraph,
conclusion, etc.). The essay is graded on content (i.e. it shows
deep though) rather than syntax (e.g. spelling) and structure.
Below are some prompts that can be used to get you thinking.
Feel free to use these or to make up your own.
· Describe a particular struggle that you overcame when
working on this programming assignment.
· Conversely, describe an issue with your assignment that you
were unable to resolve.
· Provide advice to a future student on how he or she might
succeed on this assignment.
1. Describe the most fun aspect of the assignment.

3. 1. Describe the most challenging aspect of the assignment.
1. Describe the most difficult aspect of the assignment to
understand.
1. Provide any suggestions for improving the assignment in the
future.
Deliverables
You must upload your assignment through Canvas no later than
midnight on Friday, October 28, 2016. Remember that your
submission must either contain a CodeBlocks or Visual Studio
project file!
Grading Criteria
Your assignment will be judged by the following
criteria:Reflection essay (5pts)
· Your reflection meets the minimum requirements as specified
earlier in this document. Error Free Compile (5pts)
· [0] Your program contains compiler errors.
· [1] Your program compiles without issue.Error Free Runtime
(5pts)
· [0] Your program throws a runtime exception.
· [1] Your program does not encounter any runtime
exceptions.User Interface (5pts)
· [0] Your program does not even attempt to follow the UI
guidelines
· [1] Your program's UI has major inconsistencies when
compared to the sample output
· [2] Your program's UI has minor inconsistencies when
compared to the sample output
· [3] Your program completely matches the specified user
interface guidelinesPath Calculation (20pts)
· [0-5] You attempt to calculate a path, but it is vastly incorrect.
· [6-10] Your attempt to calculate a path, but it is slightly
incorrect.
· [11-15] Your path calculations are mostly correct.
· [16-20] Your path calculations are correct.Implementation

4. (10pts)
· [0-2] Your program's implementation is inefficient. Class
usage is non-existent, your code has a lot of redundancy, and is
generally not up to the standards of what is expected of a CS
112 student.
· [3-7] Your program's implementation is acceptable, but can be
improved upon. You may use classes, but they are used poorly.
Likewise, some redundancy must exist.
· [8-10] Your program's implementation is exemplar. Classes
are used in thoughtful and meaningful ways. There is little, if
any, redundancy. If this were kindergarten, you would receive a
gold star.Style (5pts)
· [0] Your code contains more than 7 distinct stylistic errors
· [1] Your code contains between 2 and 7 distinct stylistic
errors
· [2] Your code contains 1 or 0 stylistic errors
First/Parallel-Job-Scheduler-master/.gitattributes
#####################################################
##########################
# Set default behavior to automatically normalize line endings.
#####################################################
##########################
* text=auto
#####################################################
##########################
# Set default behavior for command prompt diff.
#
# This is need for earlier builds of msysgit that does not have it
on by
# default for csharp files.
# Note: This is only used by command line
#####################################################
##########################

5. #*.cs diff=csharp
#####################################################
##########################
# Set the merge driver for project and solution files
#
# Merging from the command prompt will add diff markers to
the files if there
# are conflicts (Merging from VS is not affected by the settings
below, in VS
# the diff markers are never inserted). Diff markers may cause
the following
# file extensions to fail to load in VS. An alternative would be
to treat
# these files as binary and thus will always conflict and require
user
# intervention with every merge. To do so, just uncomment the
entries below
#####################################################
##########################
#*.sln merge=binary
#*.csproj merge=binary
#*.vbproj merge=binary
#*.vcxproj merge=binary
#*.vcproj merge=binary
#*.dbproj merge=binary
#*.fsproj merge=binary
#*.lsproj merge=binary
#*.wixproj merge=binary
#*.modelproj merge=binary
#*.sqlproj merge=binary
#*.wwaproj merge=binary
#####################################################
##########################
# behavior for image files

6. #
# image files are treated as binary by default.
#####################################################
##########################
#*.jpg binary
#*.png binary
#*.gif binary
#####################################################
##########################
# diff behavior for common document formats
#
# Convert binary document formats to text before diffing them.
This feature
# is only available from the command line. Turn it on by
uncommenting the
# entries below.
#####################################################
##########################
#*.doc diff=astextplain
#*.DOC diff=astextplain
#*.docx diff=astextplain
#*.DOCX diff=astextplain
#*.dot diff=astextplain
#*.DOT diff=astextplain
#*.pdf diff=astextplain
#*.PDF diff=astextplain
#*.rtf diff=astextplain
#*.RTF diff=astextplain
First/Parallel-Job-Scheduler-master/.gitignore
## Ignore Visual Studio temporary files, build results, and
## files generated by popular Visual Studio add-ons.
# User-specific files

7. *.suo
*.user
*.userosscache
*.sln.docstates
# User-specific files (MonoDevelop/Xamarin Studio)
*.userprefs
# Build results
[Dd]ebug/
[Dd]ebugPublic/
[Rr]elease/
[Rr]eleases/
x64/
x86/
build/
bld/
[Bb]in/
[Oo]bj/
# Visual Studio 2015 cache/options directory
.vs/
# MSTest test Results
[Tt]est[Rr]esult*/
[Bb]uild[Ll]og.*
# NUNIT
*.VisualState.xml
TestResult.xml
# Build Results of an ATL Project
[Dd]ebugPS/
[Rr]eleasePS/
dlldata.c

8. # DNX
project.lock.json
artifacts/
*_i.c
*_p.c
*_i.h
*.ilk
*.meta
*.obj
*.pch
*.pdb
*.pgc
*.pgd
*.rsp
*.sbr
*.tlb
*.tli
*.tlh
*.tmp
*.tmp_proj
*.log
*.vspscc
*.vssscc
.builds
*.pidb
*.svclog
*.scc
# Chutzpah Test files
_Chutzpah*
# Visual C++ cache files
ipch/
*.aps
*.ncb

9. *.opensdf
*.sdf
*.cachefile
# Visual Studio profiler
*.psess
*.vsp
*.vspx
# TFS 2012 Local Workspace
$tf/
# Guidance Automation Toolkit
*.gpState
# ReSharper is a .NET coding add-in
_ReSharper*/
*.[Rr]e[Ss]harper
*.DotSettings.user
# JustCode is a .NET coding add-in
.JustCode
# TeamCity is a build add-in
_TeamCity*
# DotCover is a Code Coverage Tool
*.dotCover
# NCrunch
_NCrunch_*
.*crunch*.local.xml
# MightyMoose
*.mm.*
AutoTest.Net/

10. # Web workbench (sass)
.sass-cache/
# Installshield output folder
[Ee]xpress/
# DocProject is a documentation generator add-in
DocProject/buildhelp/
DocProject/Help/*.HxT
DocProject/Help/*.HxC
DocProject/Help/*.hhc
DocProject/Help/*.hhk
DocProject/Help/*.hhp
DocProject/Help/Html2
DocProject/Help/html
# Click-Once directory
publish/
# Publish Web Output
*.[Pp]ublish.xml
*.azurePubxml
## TODO: Comment the next line if you want to checkin your
## web deploy settings but do note that will include
unencrypted
## passwords
#*.pubxml
*.publishproj
# NuGet Packages
*.nupkg
# The packages folder can be ignored because of Package
Restore
**/packages/*

11. # except build/, which is used as an MSBuild target.
!**/packages/build/
# Uncomment if necessary however generally it will be
regenerated when needed
#!**/packages/repositories.config
# Windows Azure Build Output
csx/
*.build.csdef
# Windows Store app package directory
AppPackages/
# Visual Studio cache files
# files ending in .cache can be ignored
*.[Cc]ache
# but keep track of directories ending in .cache
!*.[Cc]ache/
# Others
ClientBin/
[Ss]tyle[Cc]op.*
~$*
*~
*.dbmdl
*.dbproj.schemaview
*.pfx
*.publishsettings
node_modules/
orleans.codegen.cs
# RIA/Silverlight projects
Generated_Code/
# Backup & report files from converting an old project file
# to a newer Visual Studio version. Backup files are not needed,

12. # because we have git ;-)
_UpgradeReport_Files/
Backup*/
UpgradeLog*.XML
UpgradeLog*.htm
# SQL Server files
*.mdf
*.ldf
# Business Intelligence projects
*.rdl.data
*.bim.layout
*.bim_*.settings
# Microsoft Fakes
FakesAssemblies/
# Node.js Tools for Visual Studio
.ntvs_analysis.dat
# Visual Studio 6 build log
*.plg
# Visual Studio 6 workspace options file
*.opt
# LightSwitch generated files
GeneratedArtifacts/
_Pvt_Extensions/
ModelManifest.xml
First/Parallel-Job-Scheduler-master/HW6 - Parallel Job
Scheduler.sln

13. Microsoft Visual Studio
Solution
File, Format Version 12.00
# Visual Studio 2013
VisualStudioVersion = 12.0.30110.0
MinimumVisualStudioVersion = 10.0.40219.1
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") =
"HW6 - Parallel Job Scheduler", "HW6 - Parallel Job
SchedulerHW6 - Parallel Job Scheduler.vcxproj",
"{AF23A572-92CE-41E6-A2BE-28594543F594}"
EndProject
Global
GlobalSection(