Added my bio stuff, reformated tex file to 80 character lines. :-)
This commit is contained in:
4
.gitignore
vendored
4
.gitignore
vendored
@@ -26,3 +26,7 @@ node_modules
|
||||
|
||||
# Users Environment Variables
|
||||
.lock-wscript
|
||||
|
||||
#tex stuff
|
||||
.aux
|
||||
.toc
|
||||
|
||||
Binary file not shown.
@@ -135,78 +135,85 @@ to more people.
|
||||
|
||||
\section{Approach}
|
||||
\par
|
||||
The approach section contains our methodology, how we plan to implement the project,
|
||||
and our project schedule, the timeline we plan to adhere to.
|
||||
The methodology outlines the specific tools we will use to complete the project in a
|
||||
timely manner whereas the schedule outlines the deadlines by which we hope to have
|
||||
certain tasks completed.
|
||||
The approach section contains our methodology, how we plan to implement the
|
||||
project, and our project schedule, the timeline we plan to adhere to. The
|
||||
methodology outlines the specific tools we will use to complete the project in
|
||||
a timely manner whereas the schedule outlines the deadlines by which we hope to
|
||||
have certain tasks completed.
|
||||
|
||||
\subsection{Methodology}
|
||||
The C0 Debugger is designed for the CMU teaching language, C0.
|
||||
It will be hosted on <BLANK> with the website itself designed in CSS and HTML,
|
||||
using Node.js to run most of the core functionality.
|
||||
We will first deploy a blank template website after which half of the team wil work on
|
||||
parsing C0 bytecode and the other half will work on creating a meaningful user experience.
|
||||
Once both teams have made reasonable progress, they will combine the two units to
|
||||
The C0 Debugger is designed for the CMU teaching language, C0. It will be
|
||||
hosted on <BLANK> with the website itself designed in CSS and HTML, using
|
||||
Node.js to run most of the core functionality. We will first deploy a blank
|
||||
template website after which half of the team wil work on parsing C0 bytecode
|
||||
and the other half will work on creating a meaningful user experience. Once
|
||||
both teams have made reasonable progress, they will combine the two units to
|
||||
complete the basic outline of the project.
|
||||
|
||||
\subsection{Project Schedule}
|
||||
The project will be separated into five main phases: Basic Website Design,
|
||||
Backend implementation, Frontend Implementation, User Testing, and Revisions.
|
||||
The first phase should take <POSSIBLY CHANGE THIS> less than a week with the
|
||||
next two phases occurring simultaneously and composing the rest of the month's work.
|
||||
User implementation and revisions will then hopefully take up the remainder of the
|
||||
alloted time, with extra time padded in case implementation or revisions are more
|
||||
extensive than we have predicted.
|
||||
next two phases occurring simultaneously and composing the rest of the month's
|
||||
work. User implementation and revisions will then hopefully take up the
|
||||
remainder of the alloted time, with extra time padded in case implementation or
|
||||
revisions are more extensive than we have predicted.
|
||||
|
||||
\section{Evaluation Criteria}
|
||||
\par
|
||||
The goal of our website, as mentioned earlier in the proposal,
|
||||
is to provide a tool for 15-122 students to easily step through their C0 code
|
||||
as a means of debugging and to gain a deeper level of understanding for the steps
|
||||
their code is actually taking.
|
||||
The goal of our website, as mentioned earlier in the proposal, is to provide a
|
||||
tool for 15-122 students to easily step through their C0 code as a means of
|
||||
debugging and to gain a deeper level of understanding for the steps their code
|
||||
is actually taking.
|
||||
\par
|
||||
In order to evaluate our final project, we would test the product on various groups of students.
|
||||
Both those who have completed 15-122 in the past and those currently enrolled.
|
||||
Unfortunately, due to the time constraints of the project, these students will no
|
||||
longer actively code in C0 by the time they see our product, but their interactions
|
||||
with it will still have been recent enough for them to provide meaningful feedback.
|
||||
With their feedback, we will determine how well our product succeeds at its aforementioned
|
||||
objectives and plan a series of modifications based on the comments we receive. We will make
|
||||
sure that the stepping tool and GUI are fully functional before the group testing phase so
|
||||
that uninformative bugs do not catch the attention of our test subjects, and they instead
|
||||
provide us with information to improve the user experience as a whole.
|
||||
In order to evaluate our final project, we would test the product on various
|
||||
groups of students. Both those who have completed 15-122 in the past and those
|
||||
currently enrolled. Unfortunately, due to the time constraints of the project,
|
||||
these students will no longer actively code in C0 by the time they see our
|
||||
product, but their interactions with it will still have been recent enough for
|
||||
them to provide meaningful feedback. With their feedback, we will determine
|
||||
how well our product succeeds at its aforementioned objectives and plan a
|
||||
series of modifications based on the comments we receive. We will make sure
|
||||
that the stepping tool and GUI are fully functional before the group testing
|
||||
phase so that uninformative bugs do not catch the attention of our test
|
||||
subjects, and they instead provide us with information to improve the user
|
||||
experience as a whole.
|
||||
\par
|
||||
Our main goal is to provide these students with a useful debugging tool,
|
||||
so their feedback is invaluable in slowly modifying our project to better suit their needs.
|
||||
Our main goal is to provide these students with a useful debugging tool, so
|
||||
their feedback is invaluable in slowly modifying our project to better suit
|
||||
their needs.
|
||||
|
||||
\section{Qualifications of Team Members}
|
||||
\par
|
||||
We are a team of sophomore CS majors who have varied experience in the field.
|
||||
\par
|
||||
Suhaas Reddy has had two years of programming experience.
|
||||
He has also served as a course assistant for the School of Computer Science
|
||||
for three semesters which gives him an understanding of what computer science students may
|
||||
need from a debugging tool. This spring Suhaas competed in his first Hackathon where he and a
|
||||
group of three other students worked to create a webapp which eliminated unwanted Craigslist
|
||||
postings from view using machine learning, and sorted the rest based on specific attributes.
|
||||
He is well-versed in Python, C0, and C.
|
||||
Suhaas Reddy has had two years of programming experience. He has also served
|
||||
as a course assistant for the School of Computer Science for three semesters
|
||||
which gives him an understanding of what computer science students may need
|
||||
from a debugging tool. This spring Suhaas competed in his first Hackathon where
|
||||
he and a group of three other students worked to create a webapp which
|
||||
eliminated unwanted Craigslist postings from view using machine learning, and
|
||||
sorted the rest based on specific attributes. He is well-versed in Python, C0,
|
||||
and C.
|
||||
\par
|
||||
Shyam Raghavan has had seven years of programming experience.
|
||||
He has served as a teaching assistant for the School of Computer Science for two semesters,
|
||||
specifically for 15-122, which makes him especially prepared to create a teaching tool for C0,
|
||||
the main language used in the course.
|
||||
In the past, Shyam has interned at Thumbtack, a west coast company which specializes in
|
||||
enabling consumers to hire experience professionals from a variety of fields.
|
||||
Shyam has experience with C, JavaScript, and C0.
|
||||
Shyam Raghavan has had seven years of programming experience. He has served as
|
||||
a teaching assistant for the School of Computer Science for two semesters,
|
||||
specifically for 15-122, which makes him especially prepared to create a
|
||||
teaching tool for C0, the main language used in the course. In the past, Shyam
|
||||
has interned at Thumbtack, a west coast company which specializes in enabling
|
||||
consumers to hire experience professionals from a variety of fields. Shyam has
|
||||
experience with C, JavaScript, and C0.
|
||||
\par
|
||||
Aaron Gutierrez has had <blank> years of programming experience.
|
||||
He has also served as a teaching assistant for the School of Computer Science for two semesters,
|
||||
specifically for 15-122 just like Shyam. Aaron is very well-versed in JavaScript, C, and C0.
|
||||
Aaron Gutierrez has had ten years of programming experience. He has also served
|
||||
as a teaching assistant for the School of Computer Science for two semesters in
|
||||
15-122 with Shyam. This past summer Aaron worked at Orion Pipeline developing
|
||||
web applications for real-time resource monitoring. Aaron is very well-versed in
|
||||
JavaScript, C, and C0.
|
||||
\par
|
||||
Mitchell Plamann has had nine years of programming experience.
|
||||
He has interned at Rockwell Automation, doing firmware developement for embedded systems.
|
||||
Mitchell has coded extensively in C, Python, and Haskell. % You know I had to say it, right?
|
||||
Mitchell Plamann has had nine years of programming experience. He has interned
|
||||
at Rockwell Automation, doing firmware developement for embedded systems.
|
||||
Mitchell has coded extensively in C, Python, and Haskell.
|
||||
% You know I had to say it, right?
|
||||
|
||||
\section{Sources Cited}
|
||||
TBD
|
||||
|
||||
@@ -2,5 +2,5 @@ Qualifications of Team Members
|
||||
We are a team of sophomore CS majors who have varied experience in the field.
|
||||
Suhaas Reddy has had two years of programming experience. He has also served as a course assistant for the School of Computer Science for three semesters which gives him an understanding of what computer science students may need from a debugging tool. This spring Suhaas competed in his first Hackathon where he and a group of three other students worked to create a webapp which eliminated unwanted Craigslist postings from view using machine learning, and sorted the rest based on specific attributes. He is well-versed in Python, C$_0$, and C.
|
||||
Shyam Raghavan has had seven years of programming experience. He has served as a teaching assistant for the School of Computer Science for two semesters, specifically for 15-122, which makes him especially prepared to create a teaching tool for C$_0$, the main language used in the course.. In the past, Shyam has interned at Thumbtack, a west coast company which specializes in enabling consumers to hire experience professionals from a variety of fields. Shyam has experience with C, JavaScript, and C$_0$.
|
||||
Aaron Gutierrez has had <blank> years of programming experience. He has also served as a teaching assistant for the School of Computer Science for two semesters, specifically for 15-122 just like Shyam. Aaron is very well-versed in JavaScript, C, and C$_0$.
|
||||
Mitchell Plamann has had <blank> years of programming experience. He is very experienced in creating projects designed to <blank>. Mitchell has coded extensively in <blank>, <blank>, and <blank>.
|
||||
Aaron Gutierrez has had ten years of programming experience. He has also served as a teaching assistant for the School of Computer Science for two semesters, specifically for 15-122 just like Shyam. Aaron is very well-versed in JavaScript, C, and C$_0$.
|
||||
Mitchell Plamann has had <blank> years of programming experience. He is very experienced in creating projects designed to <blank>. Mitchell has coded extensively in <blank>, <blank>, and <blank>.
|
||||
|
||||
Reference in New Issue
Block a user