The document outlines the work done by WeylandCorp to improve the CSC 404 application created by team ASTRO. Key points: - WeylandCorp aimed to increase student retention and passing rates in computer science by improving upon ASTRO's codebase. - They solved issues with modularity, code quality, and the Parse database. All members contributed code commits and tasks like testing, documentation, and database updates. - Tools used included HTML, CSS, JavaScript, the Parse API, and Backbone.js. The application connects a client-side interface to the Parse database. - Future plans could include improved security, a mobile app, and more questions/challenges for students. -

1. CSC 404
WEYLANDCORP

2. Hello!
We are WeylandCorp.
Frances Coronel - PM
Brandon Richards - 2nd in Command
Charles Cephas - Writer/Developer
Jordan Quick - Writer/Developer
Justin Havens - Writer/Developer

3. Agenda
1. The Problem
2. The Solution
3. Tasks
4. Tools
5. Architecture
6. Features
7. Demo
8. Future
9. Challenges Faced
10. Lessons Learned

4. 1. The Problem?
What did we have to solve?

5. Scope
▪ Low retention rate and
low passing rates in the
Computer Science
department
▪ Finish and enhance the
project started by team
ASTRO earlier in the year

6. A very messy application.
▪ Modularity
▫ Messy code
▫ Unneeded code
▪ The Parse Database
▫ Password problems
▫ Didn't know how to work Parse
▪ Hosting
▫ Had problems figuring out how to host a live
website

7. 2. The Solution
How did we go about doing that?

8. Create C#er
Improve upon ASTRO’s code
base to develop a gamification
application that will reinforce
the learning concepts taught in
the classroom and to ultimately
increase the retention rate of
students within the computer
science department through
various types of quizzes.

9. How did we solve our
issues ?
▪ To solve all of the various issues we faced we :
▫ Figured out various HTML issues
▫ Worked together collaboratively to figure out and
fix database problems
▫ Effectively came together to fix the documentation
▫ Brainstormed to come up with better ideas for the
projects layout
▫ Worked together to accomplish all goals set for
the semester

10. 3. Tasks
What was everyone assigned throughout?

11. Tasks
Frances
▪ Optimizing code by
increasing modularity
and updating libraries
▪ UI for Login
Brandon
▪ Worked with code to
deploy product
▪ Updated information
within database
needed for
deployment.
Justin
▪ Updated information
within database
needed for
deployment.
▪ Updated requirements,
functional, and design
documents.
Jordan
▪ Testing of the application and
documenting the testing and
functionality aspects.
▪ Updated information within
database needed for
deployment.
Charles
▪ Updated information within
database needed for
deployment.
▪ Updated documentation
needed for final delivery and
project plan.

12. 70commits on GitHub
100%total deployment success!
2branches (gh-pages & master)

13. Code Contributors?
EVERYONE
Frances
▪ Optimizing code by
increasing modularity
and updating libraries
▪ UI for Login
Brandon
▪ Made changes to UI
▪ Added Timer function
to questions
Justin
▪ Made changes to five
different challenges
in the database
▪ Minor changes to the
UI
Jordan
▪ Made some cosmetic
changes UI
▪ Worked with the
database to make
several updates
Charles
▪ Made changes to the
UI
▪ Updates to the
database

14. 4. Tools
Frameworks, Languages,
Hosting Providers, Online Services, etc.

15. Overview

16. 5. Architecture
How do Parse & C#er Communicate?

17. Security
▪ Security is an integral portion of the development of any software entity. With all of
the data breaches and just loss of information in general in present day society,
securing your application is just as vital as the development of the application itself.
▪ Throughout the production of this application we at WeylandCorp have ensured
that each within each phase/iteration we maintained a secure working
environment.
▪ In addition, with each entity involved, such as the code, database, and
documentation, we were sure that it was password protected, and only the
members of WeylandCorp had access to them.

18. Software is composed of the client side application and the Parse database. The web application interface
was developed using HTML, CSS, and JavaScript. That served as the user interface for the application. The
Parse Framework hosts the database used by the application. The client connects and interacts with the
database through the web interface; the communication between the interface and the database was
programmed with the JavaScript SDK provided by the Parse API, which is built on top of the Backbone.js
framework. Backbone uses a MVC (Model View Controller) design paradigm, and data is represented as
models.

20. 6. Features
What key features did we add on?

21. New Features Added
▪ Modularity
▪ More Questions
▪ Updated Logo and Leaderboard
▪ Updated skills and progress bar
▪ Changed layout of questions
▪ Changed overall theme
▪ Changed Challenges Icons
▪ Revamped Login Screen

22. “
Showcasing
Before
&
After

23. Login

24. Modularity

26. Place your screenshot here
7. DEMO
We will now show you the
new and improved
application.
This is C#er.

27. 8. Future Plans
What key features do we want to add
on?

28. Potential
Improvements
▪ Improve security using oAuth
▪ Create a mobile app while still using Parse framework
▪ Implementing 3rd party logins
▫ Facebook
▫ Twitter
▫ GitHub
▪ Better User Interface and User Experience
▪ More questions added to challenges
▪ More Modularity
▪ Feature to input and implement coding challenges

29. 9. Challenges Faced
What went wrong.

30. Challenges
Faced
▪ Various coding expertise amongst group members
▪ Hosting of the database
▪ Deployment of website for application
▪ Time management throughout the duration of product
▪ Modularity of the original application
▪ Adhering to the various specifications of the client throughout the
development of the product

31. 10. Lessons Learned
Overcoming obstacles.

32. Let’s review
what we learned
Frances
▪ Time management
▪ Assigning enough
work
▪ Teaching others
Brandon
▪ Better Time
Management
▪ Importance of
Deadlines
Justin
▪ Time management
▪ How to collaborate
better with team
members to
accomplish goals
Jordan
▪ Learned how to use
and implement Parse
Databases
▪ Learned how to work
better with a team
▪ How to deal with
time constraints
Charles
▪ Manipulation of
different
development tools
▪ Better collaboration
with team members
on tasks outside of
my comfort zone.

33. “ As PM, I struggled to lead the team
effectively with some iterations.
Everyone came in with a different skill
set and because of how the CS
curriculum is formatted at any school,
barely anyone had experience with
web development.

34. WE CAME THROUGH
Everyone made sure to help out each other in the end
and everyone succeeded in completing their
assignments in regards to documentation and
contributing to the code base.

35. Thanks!!
Any questions,
comments, or
concerns?