URL

https://egt-gsa-catalyst.egt-labs.com/

Local Development & Install Instructions

• Install command line tools:
  • Node and npm
  • bower: npm install -g bower
  • gulp: npm install -g gulp
• Update dependencies
  • npm install
  • bower install
• Run development application locally: gulp
• Test code
  • check code formatting with JSHint and JSCS gulp control
  • protractor end-to-end one-time setup: gulp e2e:update
  • protractor end-to-end tests: gulp e2e
• Deploy Application
  • build package: gulp deploy
  • contents will be located in the dist folder
  • Optionally set enviornment variables:
    • NODE_ENV=production
    • PORT=12345
    • OPEN_FDA_API_KEY=YOUR_API_KEY
      • This app is powered by the Open FDA API. While you can run without a key, it is recommended for production use to acquire one.
  • run production package: node dist/server/server.js

Docker Containerization

• Use git to pull our repository onto Docker host

• Path to repository root, e.g. egt-gsa-proto

• Build and run (don't forget the hard-to-see dot at the end of the docker build line below): * docker build -t catalyst:YOUR_TAG_GOES_HERE . * docker run -P catalyst:YOUR_TAG_GOES_HERE

• docker ps to find the docker host port you're mapped to, e.g.:

  0.0.0.0:49157->9000/tcp

You can also map the internal (9000) port at will, for example to run the application so it can be accessed on host port 80 you'd run:

docker run -p 80:9000 catalyst:YOUR_TAG_GOES_HERE

More options and details are available in the README.md in the docker folder.

Minimal Viable Product (MVP) Challenge

Our challenge was to develop and deploy a simple app using OpenFDA datasets to search, explore, & interact with data on drug labeling and adverse events. Core functionality was focused on faceted search and analytics on adverse events. Team eGT developed the application using Scrum and the US Digital Services Playbook enhancing the application over a number of iterations.

For more information on our evidence, please see the MVP Wiki Document.

Team

eGT assembled a multi-disciplinary, collaborative core DevOps team of experienced engineers, agilists, testers, and architects, with members chosen for their experience designing web applications using automated testing frameworks, continuous integration and continuous deployment to build and deliver a prototype.

• Product Manager: Jennifer Hinton - @jhinton
• Technical Architect: Eric Hanson - @jehanson
• Backend Web Developer: Eric Hanson -@jehanson
• Frontend Web Developer: Mansi Pandurangi -@mpandurangi
• DevOps Engineer: John Stange - @jstange
• DevOps Engineer: Jai Bapna - @jaibapna
• DevOps Engineer/Automated Test Engineer: Zach Rowe - @zr2d2

For more information about our team and to view our evidence please see our Team Wiki Document.

[Technical Stack] (https://github.com/eGT-Labs/egt-gsa-proto/blob/master/docs/Tech%20Stack/18F-GSA-Agile-eGlobaltech-Tech-Stack-Wiki.docx)

Team eGT chose to leverage over five modern, open source tools & frameworks as they offer maximum productivity in a prototyping effort of this nature. We implemented continuous integration automating the entire build, test and deployment process further enhancing our productivity and accelerating our solution’s maturity. All underlying platforms used to create and run the prototype are openly licensed and free of charge.

Below we highlight our technical stack on how we met the requirements:

Modern, Open Source Technologies

• Node.js - Cross-platform runtime environment
• Angular.js - Front-end framework
• Bootstrap - Front-end framework
• Chef and Cloudamatic for Continuous Deployment & Configuration Management
• Docker for Operating-system-level virtualization

Other Technologies

• Github for Source Control Repository
• Amazon Web Services as our Infrastructure as a Service Provider
• Jenkins for Continuous Integration with Protractor to enable Automation of Unit Tests
• Nagios for Continuous Monitoring
• OpenFDA's API to consume APIs for Adverse Events, Recalls, and Drug Labeling

To view our evidence, please see our Technical Stack Wiki Document.

Process & Tools

Our lead, Jennifer Hinton, facilitated a kick-off meeting to gain alignment on the tech stack and creation of the environment with necessary permissions, collaboration tools, sprint schedules and ceremonies, and determined the MVP challenge based on suggestions from SMEs and the team.

The team followed a daily ceremony schedule, including the following:

• Daily Stand Up - to coordinate efforts and remove blockers
• Daily Grooming Session - to slice and prioritize new functionality and to discuss mock-up designs created by the Product Manager and value team
• Sprint review & demo to view and provide suggestions to improve new functionality, provide updates about the infrastructure and testing roadmap, and to close out completed stories in GitHub

For more information and to view our evidence on our Iterative, Agile Approach, please see our Process & Tools Wiki Document.

Attachment E Evidence

All attachment E evidence is located in the docs folder of the repository