Skip to content
This repository was archived by the owner on Jan 17, 2024. It is now read-only.

Approach

Jason McNutt edited this page Jun 24, 2015 · 10 revisions

In order to provide a true Human Centric Design there are principles and practices that you must adhere to, where Design, Usability, Responsiveness, Fluidity and Intuitive navigation all come into play.

  1. Discover
    a. Understand criteria and parameters around prototype (See RFQ documentation- Attachment D and body of document)
    b. Brainstorm on prototype ideas, use trello board to crowdsource and then narrow down to final choice(s)
    c. Stand up Source Control in Github
    d. Define Goal of application and high level use Cases for Alpha Release e. Setup Github issues as Backlog for work items, define items in broad use case manner - "As a , I would like to "
  2. Alpha
    a. Planning for Alpha release based on Goal and use Cases
    b. Implement application scaffolding for User Interface - AngularJs, BootStrap,
    c. Implement backend development - API, persistent store, server tech (Node.js/hapi.js)
    d. Implement Platform-As-A-Service (PaaS) Cloud Foundry
    e. Implement Continuous Integration platform - Travis CI
    f. Round #1 of Wireframes
    e. Human Centric Design (HCD) Approach 1 - User Survey performed - Usability Testing Surveys
  3. Beta
    a. Planning for Beta release based on remaining use Cases and discovered issues b. Implement more advanced functionality c. Round #2 Wireframes d. HCD Approach 2 -Refined Wireframes based on Usability testing feedback and chosen Style Tiles as well -
  4. Live

Clone this wiki locally