Project Requirements

Here we cover each point of the RFI to demonstrate our holistic response.

Technical Requirements	Successful Completion of RFI Requirements
2a. Assigned one (1) leader and gave that person authority and responsibility and held that person accountable for the quality of the prototype submitted;	Yes. Stephan Garbler who was the Technical Architect was the primary person of authority. More info on the management approach can be found here.
2b. Assembled a multidisciplinary and collaborative team that includes, at a minimum, five (5) of the labor categories as identified in Attachment B: PQVP DS-AD Labor Category Descriptions;	Our team consists of 5 labor categories. More info on our team can be found on our here.
2c. Understood what people needed, by including people in the prototype development and design process;	Our iterative prototyping with constant user feedback created 4 versions of our development application. More info on our iterative prototyping can be found here.
2d. Used at least a minimum of three (3) “user-centric design” techniques and/or tools;	The design method utilized by Bayes Impact involved 1) putting users first in the development process 2) iteratively designing the application according to user feedback 3) developing product specification according to user interviews. Further info on our user-centric design approach can be found here.
2e. Used GitHub to document code commits;	Github is our primary source of all code commits, ensuring a common codebase.
2f. Used Swagger to document the RESTful API, and provided a link to the Swagger API;	Yes. Our full technical approach can be found here.
2g. Complied with Section 508 of the Americans with Disabilities Act and WCAG 2.0;	Bayes Impact fulfilled the requirements to the best of our capabilities.
2h. Created or used a design style guide and/or a pattern library;	Bayes Impact utilized the U.S. Web Design Standards for the design of the product, following the U.S. Digital Services Playbook.
2i. Performed usability tests with people;	Each design and product development version was defined by the user feedback of avid outdoor enthusiasts and one emergency responder.
2j. Used an iterative approach, where feedback informed subsequent work or versions of the prototype;	Our iterative approach is the hallmark of our development process. User feedback is at the center of our development. Refer to our rapid prototyping for more info.
2k. Created a prototype that works on multiple devices, and presents a responsive design;	Our device has been optimized to perform on all computers, notepads, and mobile.
2l. Used at least five (5) modern and open-source technologies, regardless of architectural layer (frontend, backend, etc.);	Our prototype used more than five modern and open source technologies. Technologies include Docker, Python, React, Webpack, Eslint, Jest, Targaryan, Firebase, CircleCI, AWS ECS, and Twilio. For a full list of our technology stack, refer to our Technical Approach.
2m. Deployed the prototype on an Infrastructure as a Service (IaaS) or Platform as Service (PaaS) provider, and indicated which provider they used;	We deployed our prototype on Google Firebase (PaaS) and Amazon Web Services (ECS) to host our Docker container. For detailed documentation, refer to our Technical Approach.
2n. Developed automated unit tests for their code;	We developed automated unit tests in our code.For detailed documentation, refer to our Technical Approach.
2o. Setup or used a continuous integration system to automate the running of tests and continuously deployed their code to their IaaS or PaaS provider;	We used CircleCI to run more tests and linters and continuously deploy code to Firebase and AWS. For detailed documentation, refer to our Technical Approach.
2p. Setup or used configuration management;	We setup configuration management using configuration files in a separate folder for front-end and backend. For detailed documentation, refer to our Technical Approach for set up.
2q. Setup or used continuous monitoring;	We have setup continuous monitoring through Amazon Web Services ECS and CloudWatch. For detailed documentation, refer to our Technical Approach.
2r. Deployed their software in an open source container, such as Docker (i.e., utilized operating-system-level virtualization);	We deployed our software using Docker. For detailed documentation, refer to our Technical Approach.
2s. Provided sufficient documentation to install and run their prototype on another machine;	We provided significant documentation in the Technical Approach section that includes information about how to install and run our prototype on another machine.
2t. Prototype and underlying platforms used to create and run the prototype are openly licensed and free of charge.	Our prototype is completely open source and openly licensed free of charge as are the underlying platforms used to create and run it.