Trip Planner

A school project oriented around team-based software development and Capability Maturity Model Integration (CMMI). The objective was to create a trip planning website.

Experience

  • CMMI
    • Configuration management
    • Change management
    • Development and release of baselines
    • Record keeping
    • Integrity & maintainability audits
    • Integration strategies
    • Design evaluation
    • Peer evaluation
  • GitHub
  • ZenHub
  • Reactstrap
  • Clean Code
  • Team-oriented programming
  • Iterative design
  • Database implementation

Click to read more

Hold click on an image to see it's caption

Trip Planner

The Trip Planner is a project from CSU's CS 314 class taught by an incredible instructor, Dave Matthews.

Trip Planner applied Capability Maturity Model Integration (CMMI) into our developmental process. We worked in teams on an existing codebase.

title

Full Demo

Here is a full demo of the functionality of the project. Unfortunately, I cannot host the site on a public domain as it is still in development.

title

Iterative Design

While the iterative design process was not foreign to me, its implementation in the Trip Planner project was fantastic because it demanded more forethought and accountability than my personal projects. Additionally, the iterative design process was consistent throughout the whole semester, which developed beneficial habits and opened my team and my eyes to the sum of our incremental progress.

The majority of our design changes revolved around feedback. The feedback came in two forms. Most significantly, 'customer' demand for new features required UX adjustments to implement well. The second source of design feedback was from external people, which we used as UX testers.

title

Databases

One of the most rewarding factors of Trip Planner was working with databases to provide users with practical information.

This demonstration contains querying the database efficiently and applying filters to the query.

title

Interoperability

Interoperability was an exciting requirement for this project. Each team had to follow protocols so each team's front end could work with any team's backend and vice versa.

This demonstration shows my team's front end connecting with another teams' back end.

title

Storage

The storage portion involved being able to save and load user trips. My team went above and beyond and implemented browser storage to retain loaded trips and download preferences.

title

Advanced Algorithms

We were tasked with completing the classic Traveling Salesman problem to optimize the user's trip. We had to be very mindful about our implementation because we had to be able to optimize any size trip in under a second. This helped us practice testing and efficient resource usage.

title