Switch branches/tags
Nothing to show
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
Screen Shot 2016-06-09 at 10.02.42 PM.png
Screen Shot 2016-06-09 at 6.49.03 PM.png
Screen Shot 2016-06-09 at 7.03.00 PM.png
Screen Shot 2016-06-09 at 7.07.22 PM.png
Screen Shot 2016-06-09 at 7.10.09 PM.png
Screen Shot 2016-06-09 at 7.12.24 PM.png
Screen Shot 2016-06-09 at 7.16.38 PM.png
Screen Shot 2016-06-09 at 7.19.57 PM.png
Screen Shot 2016-06-09 at 7.26.51 PM.png


Prototype URL: https://parentportal.tabordasolutions.net

User Guide

Taborda - ADPQ Prototype

Technical Approach (2)

Our team utilized an “outside-in” product development approach to create our ADPQ prototype. “Outside-in” focuses on the end user’s needs and experience to drive features, along with supporting application program interfaces (API). Focusing on the end user means that their needs are implemented pervasively throughout the application. This practice promotes user satisfaction and adoption through continuous interaction/feedback. Our team utilized the following approach for this prototype:

  • Conducted user research to understand needs and trends within related industry. Our User Researcher conducted user interviews with a current CPS worker, along with people acting as the identified personas (parent/guardian) to create the initial application concept (2c).
  • Created initial UI documented as wireframes (Balsamiq) which were presented to both CPS workers and staff members representing the personas associated with the system. Feedback was incorporated into an updated UI design (InVision) (2g).
  • Identified user stories to form initial product backlog.
  • Developed fully interactive prototype web/mobile application. The initial prototype was presented to the representative user base from the user research phase. The findings from users interacting with the application, such as usability improvements, were incorporated into the final design (2g).
  • Developed fully functioning prototype including back end API for data persistence as a series of “vertical slices” allowing testing throughout the effort.

The “outside-in” product development approach incorporates the application development aspects of the U.S. Digital Services Playbook .


Our architecture is based on JavaScript (Angular.js) with a Java API (Dropwizard) and PostgreSQL database.

Application Architecture

Adherence to U.S. Digital Services Playbook (2)

We followed all of the applicable Playbook plays. Details here.

Taborda Prototype Team

Team Leader (2a)

Taborda assigned Brendan McGuire as the one leader with authority, responsibility, and accountability for prototype quality.

Product Development Team (2b)

Multi-disciplinary and collaborative team includes eight (8) labor categories:

  1. Product Owner – Brendan McGuire, CSM
  2. Technical Architect – Rich Bach, CSM
  3. Interaction Designer/User Researcher/Usability Tester – Lacy Carter, CSPO
  4. Visual Designer – Husam Alrubaye
  5. Front End Web Developer – Justin Castillo, Husam Alrubaye
  6. Back End Web Developer – Tom Parker
  7. DevOps Engineer – Chris O'Meara, CSM
  8. Agile Coach – Gregg Hill, CSM

Understanding of User Needs*(2c)*

We employed Human-Centered Design (HCD) to elicit user requirements to form the Product Backlog. The section below summarizes our HCD process for the prototype. Details here

Human-Centered Design (2d)

Our HCD process leveraged the following techniques:


  • Developed Design Challenge: "How might we implement a modern, convenient app for parents to communicate with case workers and easily access resources?"
  • Conducted 1:1 and Group Interviews with real case worker and several non-participating staff
  • Conducted user research to identify target audiences
  • Developed personas
  • Brainstormed, starting with "Diverge" step to get all ideas (no concern for viability/feasibility), then "Converged" to reduce ideas list to only viable/feasible.



  • Developed Balsamiq low-fi wireframes - using whiteboard designs & feedback from internal / user testing (2g)
  • Conducted user tests and gathered feedback (2f)
  • Developed PhotoShop/InVision high-fi web mockup prototype - using wireframes / user testing feedback (2g)
  • Conducted mockup prototype user tests; gathered feedback (2f)
  • Developed live Design Style Guide (DSG) using bootstrap/SASS/CSS/HTML. DSG elements leveraged HTML mockup / user testing feedback. (2g)
  • Conducted responsive design testing on desktop (Mac, PC) and mobile devices (iOS, Android) (2h)
  • Updated DSG Design elements as prototype was elaborated – keeping DSG and prototype pages consistent and synchronized (2e)
  • Developed prototype HTML using HTML mockup, user testing feedback, and DSG
  • Iterated on pages, incorporating user testing feedback between iterations, finally reaching minimal viable product (MVP) (2g)

Prototype Development

Modern Open Source Technologies (2i)

All Open Source Solution Components with Build Dates

  • Front end
    • Bootstrap (5/2016)
    • Javascript
    • Angular.js (5/2016)
    • jQuery (5/2016)
    • SASS (5/2016)
    • Font-Awesome (5/2016)
    • JSON Web Token (5/2015)
    • WAVE (3/2016)
    • Web Server – NGINX
  • Back end
    • Java (6/2016)
    • Dropwizard (5/2016)
    • Jetty – Web Server (6/2016)
    • Jersey – RESTful web services (6/2016)
    • Jackson – JSON Processor (5/2016)
    • Hibernate ORM (4/2016)
  • Database – PostgreSQL

Automated Unit Testing (2k)

  • Front end
    • Protractor (6/2016)
    • Jasmine (3/2016)
  • Back end
    • Junit 4 (6/2016)
    • Mockito (6/2016)

Continuous Integration (2i, 2l, 2m)

Implemented Jenkins inside Docker container on AWS for automated testing as code is checked in to GitHub.

  • Deploy
    • Server – Docker (5/2016)
    • Developer – Docker Composer (5/2016)

Prototype Deployment Environment (2j)

The prototype deployed to AWS (FedRAMP-certified IaaS).

Infrastructure Architecture

Configuration Management (2n)

The GitHub Repository is organized as:

Additional repositories were utilized to support CI pipelines and are available below:

GitHub Repositories

Continuous Monitoring (2o)

Implemented the following monitoring:

  • NodePing validates availability every 3 minutes and alerts the Taborda operations team of service availability disruption.
  • Datadog continuously monitors system resources and alerts the Taborda operations team of potential issues.
  • PagerDuty delivers alerts to the Taborda operations team according to a 24x7 duty schedule.

Containerization (2p)

Deployment in Docker container.

Deployment Documentation (2q)

Deployment Docs

Prototype / Underlying Platform Licensing (2r)

The prototype and underlying platforms are open licensed and free of charge.

Notes and Assumptions