CTUDGC Companion Application

Capitol Technology University Disc Golf Course Companion Application

Author: Leif Heaney Date: September 29, 2020 Capitol Technology University

You can view the original post on LinkedIn. You can view the free on-demand webinar recording on Cap Tech’s YouTube channel.

“Disc Golf Course Companion Application” – What is involved in creating a mobile app? _ The Capitol Technology University Disc Golf Course app was designed and constructed by student and recent graduate Leif Heaney over the past two years. Leif’s senior project was to create a companion application to help disc golf players navigate the course with ease as well as improve their disc golf skills using technology. This presentation highlights the key features of the CapTechU DGC Companion Application. It discusses the thought process behind the application functionality and design as well as plans for the future of the application and its development goals._

CTUDGC Companion Application: Presentation Demo

CTUDGC Companion Application: Presentation Slides

capitol-technology-university-disc-golf-course-analytics-app Download

CTUDGC Companion Application: Diagrams

Below are diagrams created during the brainstorming and development phases of the project. UML Diagrams in the slideshow module below include:

• High-level Use Case Diagram

• Entity-Relationship Diagram

• Context Diagram

• Process Flow Diagram

• Data Flow Diagrams (multiple)

Use Case Diagram

Entity Relationship Diagram (ERD)

Context Diagram

Process Flow Diagram

Data Flow Diagram (DFD)

CTUDGC Companion Application: Lean Agile, Development Approach, & Gantt Charts

For my senior project, I embraced the Lean Startup approach.

I incorporated a Lean Agile methodology into my project.

Finally, I implemented Gantt charts to manage tasking and timelines.

• January – February saw longer Sprints (set to 4 weeks max per Scrum ideology) in order to afford myself enough development time to effectively execute my Sprint tasking for that period.

• March – April was broken up into standardized lean Agile sprints.

• The latter part of April followed the aforementioned sprints up with extremely quick user test & validation sessions (see QA testing rows).

• After user testing immediately came the Go-to-Market stint, including implementation, deployment and official go-live.

• Marketing was ran in conjunction with Go-to-Market processes in the late-April time period.