This week, we had our Halves Presentations, which, unlike Quarters, are a lot more formal. Halves are meant to give everybody an update of what we have done so far, and how we’re continuing onward with the rest of the semester.
Here’s a video of our presentation:
https://www.youtube.com/watch?v=PAz2we-n1aI
We got a lot of really great feedback from the presentation. These are 4 of the more interesting ones, and how we’re addressing them.
Q: Nice that you addressed a main Quarters comment – to reshoot the video. You can’t. You are given a foundation on which to build but not change. You probably should have a document to the client about what they might want to change with the video, if they choose to do so later in their research cycle. You do have experience in this space thanks to Ralph, John, and others!
A: Yup, we’re currently working on a list of recommendations and best practices for our client when they reshoot / add on to the video collection. It’ll be part of the documentation which we hand off to them at the end of the semester.
Q: With such a tiny video corpus, does it make sense to have full text search? I thought I saw a search box in your interface. Not sure if your shown interfaces were mockups or actual – would have been nice to see a demo of each of the 4 website components in action with a clearer idea of their mockup–final-form status as of today (to see where you will invest time for Nov/Dec).
A: The video library may be small now, but the client will be adding onto it in future. Because of this, we are focused on the functionality rather than the amount of content. Unfortunately, the interfaces were all mockups, and not final ones at that. We’ll definitely be showing a playable prototype during Softs though. As for how we’re investing our time for Nov/Dec, please refer to the Schedule slide in our presentation.
Q: I followed your point about “research time” versus “ETC project time.” You may need to build your own scaffolding, noting the extra investment needed by your team, rather than wait for details from the client. For example, you could create 4 vignettes in the low/high risk, low/high change in quality of life (or whatever scales you wish to use), iterate on them a bit with ETC story faculty, and then use those vignettes in place of actual patient data in order to get some playtesting done.
A: Our client is actually providing us with the spoofed patient prognosis to work with. It’s similar to the 4 suggested vignettes, except that these have a lot more details and are based off real patients. Each of the spoofed data sets has a ton of background factors (more than 100), so our problem here is how to simplify / summarize them into something that’s easily consumable by our playtesters.
Q: You ended your presentation far too quickly, leaving unstated how you are addressing some implementation concerns, e.g., you will run on iPads but also want to support phones and desktops. Will you be building a responsive web interface? Using Bootstrap or some other framework for responsive styling? Using Angular 2 or some other JavaScript library(ies) for platform portability? Will you use the html video tag, your own custom video player, or a JS-based video player library for video playback?
A: In short, we are building a responsive website. Our client has given us an ideal use case for this: the website with the patient’s information is pre-downloaded onto an iPad, which the doctor will give the patient to take home. It is a website, not a native iPad app, so that the patients’ family members who are not in the same location can also view the information online. Here’s the exact technology we’re using:
- Bootstrap and JQuery for responsive front end
- VideoJS for the video player
- OpenNLP for language processing
- Java Servlet with Maven and Tomcat for the back end
- MySQL for the database
Here’s the slide deck we used for the presentation. It doesn’t make much sense if you just look through it, so watch the video instead!
Recent Comments