Full Stack Development Certificate

The Full Stack Development Certificate program focuses on the use of front-end libraries or frameworks, programming website backend content management, managing deployment and installation on servers, and running SQL queries on databases.  Total 18 semester credit hours.
Technologies studied:
JavaScript               React JS               Python 3               UML
Flask                        SQL Database      JSON                     Git
SCSS/SASS            FlexBox                 CSS Grid               Typescript
MongoDB               HTML5

Potential Job Titles:

Junior Developer, Freelance Developer, Full Stack Developer, Zoho Developer, Software QA Engineer, Software Tester, Software Developer, Support Specialist, Tech Support Specialist, Backend Developer, Front End Developer, App Developer, Associate Software Engineer, etc.

Program Objectives

1. Demonstrate knowledge of advanced concepts and theories of computer science including issues of computability, data organization, binary data manipulation, data storage, and data retrieval.
2. Utilize high-level, computer languages that incorporate object-oriented design techniques.
3. Utilize advanced problem-solving and critical-thinking techniques to design, develop, and use complex computer applications, data analytics systems, and security protocols.
4. Apply advanced numeracy and economic management skills in business and technology industry settings.

Full Stack Development Certificate

Course No. Course Name Prerequisites Credits
FS999 Full Stack Development Certificate None 18
Total Credits Required 18

Attendance Policy:  Full Stack Development Certificate Only

Full Time Progression

In order to ensure the students’ progress meets completion requirements, the following attendance is required.

Each student’s term is 13 weeks (8 hours/day, M-F) or 26 weeks (4 hours/day, M-F) in length and determined by the start and end dates signed on the enrollment agreement.  Students must not miss more than 40 hours during the 13-week or 26-week term to prevent being dismissed directly due to attendance.

Students who fail to progress to each benchmark within the suggested timeline, must participate in remediation which consists of the following steps:

a) official notification of unsatisfactory progress with the student committing to an academic progress plan (email and follow-up call, from program administration), then, the following if no improvement,

b) official notification of unsatisfactory progress from the Academic Team and follow-up call,

and finally,

c) the student may be academically withdrawn. (Extenuating circumstances must be approved by Academic Dean.)

 

Weekly Benchmark/13 weeks Weekly Benchmark/26 weeks Percent Completion
Week 1 Week 1-2 100% – Coding Foundations completed
Week 2 Week 3-4 17.5% completion
Week 3 Week 5-6 25% completion
Week 4 Week 7-8 32.5% completion
Week 5 Week 9-10 40% completion
Week 6 Week 11-12 47.5% completion
Week 7 Week 13-14 55% completion
Week 8 Week 15-16 62.5% completion
Week 9 Week 17-18 70% completion
Week 10 Week 19-20 77.5% completion
Week 11 Week 21-22 85% completion
Week 12 Week 23-24 95% completion
Week 13 Week 25-26 100% completion by the end

 

(Any academic change to a student’s status will be documented in the student’s academic file.)

Attendance will be marked for all students each designed class period. The instructor will indicate percentage of progression by the end of each week of the program.

Status Academic Standing
On-time Progression Satisfactory Progress
Fail to progress to each benchmark within the suggested timeline Unsatisfactory Progress

 

Part Time Progression

Full Stack Development Program

The Full Stack Development program term length is ten months for part time students and determined by the start and end dates signed on the enrollment agreement. Students should complete Coding Foundations (prerequisite) in the first month to be able to proceed in the Full Stack Development Certificate program in the second month. The following progression is the suggested benchmark achievements to keep the student on track.  However, the student will be evaluated monthly on progression through to the end of the program at month ten.  The measurement of completion (attainment of benchmark) will be recorded at the end of each month.

Monthly Benchmark Percentage Percent Completion
Month 1 100% –  Coding Foundations completed
Month 2 15% completion by the EOM
Month 3 20% completion by the EOM
Month 4 35% completion by the EOM
Month 5 45% completion by the EOM
Month 6 55% completion by the EOM
Month 7 70% completion by the EOM
Month 8 85% completion by the EOM
Month 9 95% completion by the EOM
Month 10 (including Capstone) 100% completion by the EOM

 

Status Academic Standing
On Time Progression Satisfactory Progress
Fail to progress to each benchmark within the suggested timeline Unsatisfactory Progress

 

Students who fall behind the suggested benchmarks must participate in remediation.

a) official notification of unsatisfactory progress with the student committing to an academic progress plan (email and follow-up call, from program administration), then,

b) official notification of unsatisfactory progress from Academics and follow-up call,

and finally

c) the student may be academically withdrawn. (Extenuating circumstances must be approved by Academic Dean.)

(Any academic change to a student’s status will be documented in the student’s academic file.)

Final Project Directions & Rubric

The mentors and instructors will be there to help you with some issues but this is a project you must do on your own with little support.

Capstone Project Requirements
  • Build a Project using six of each from the following lists:
    • Languages and Technologies (six from this list)
      • Python
      • React
      • GitHub
      • Ajax / Fetch / Axios
      • JSON
      • CSS or SCSS
      • Data Types
      • SQL or NoSQL
      • JavaScript
      • HTML
      • UML
      • UI/UX
    • Methodologies / Best Practices (six from this list)
      • Control Structures
      • Algorithms
      • Quality
      • Project Management
      • Problem Solving
      • Agile
      • Object-Oriented Programming
      • Functional Programming
      • Software Engineering
      • Behavior Driven Development
      • Test-Driven Development
      • API’s
    • You must include one language/feature/framework that you did not learn in the course.  For example:  Search Bars, Payment Processing, Picture Carousel, etc… Be Creative
  • You must build a Microservice App Process
    • The backend is Python, Ruby or any other backend language.
    • The back end must be connected to the Front-End via API.
  • The App must be mobile responsive
    • Unless you can provide a good reason why it cannot be.  For example: Browser-based video game
  • Hosted on any hosting service
  • It is permissible to use tutorials, The tutorial cannot make up more than 40% of the FInal Capstone Project. 
List of Approved Projects

The following list is available to help you come up with ideas.  You can build anything as long as it follows the guidelines listed above.

  • eCommerce – Build an online shop. User Story: A user can select from a set of products and walk through the full purchase process.
  • Modern Blog – Building a blog that allows for Omniauth and Elasticsearch. User Story: A user can create a blog account by logging in with one or more social accounts (Facebook, Twitter, GitHub, etc.) User Story: Visitors can search through content via Elasticsearch, including an auto-complete component.
  • Chat App – Build the key features utilized for chat functionality. User Story: A user can create a group chat room and post messages in the group. User Story: A message is only shown in the group it has been posted in.
  • LMS – Rebuild DevCamp. User Story: A user can create a set of courses, organized by courses, sections, and guides.
  • Factory Automation System – Build an application that manages each state of a factory’s manufacturing process. User Story: A digital production can be taken from one stage through a full workflow. E.g. A fleet management program where a vehicle can be added, then have a custom set of maintenance requirements added, then be assigned to a driver, all by different managers.
PROJECT SUBMISSION INSTRUCTIONS

You will go to Canvas to the Modules tab and will uploan your final project to the Final Project Submission. Please do not send this directly to your Instructor or Mentor.

  • Description of your application
    • If you did version control, your README.md is a great spot for this
  • App Url
  • GitHub Url
  • Passwords and Usernames needed to test the application
  • Let us know what you included for your new language/feature/framework
  • Any extra data to help assist us in grading your application

Your assignment will not be returned to you so keep a copy for your files.

It will take approximately 2 – 3 business days to review your code and make sure you have a functioning Application.

Do not be discouraged if we do not approve your application right away.  We will include in the email back to you a description of what to add and what more we want to see.

Use your imagination to be creative and have fun with it.