Ah, a decently working demo :)
Today, we showed Nikan a demo of the user selecting a car type and symptom (though currently we only have one symptom chart implemented, that the car will not start) by either searching for it or using the provided drop-down menus. The program then displayed a question/request to the user for some kind of diagnostic test (like "does the car's engine try to turn over at all?"), and there were buttons for each possible answer to the question. In this particular diagnostic chart, every question is "Yes-or-No". Through this interaction, the user (Nikan) was able to go through the chart in a simple way to try and diagnose the vehicle. The user interface looked good, the program ran smoothly, and has real-life data being utilized. It's looking like our core functionality is getting close to complete.
We still have much to do. We haven't yet covered the case of when a chart doesn't solve a users' problem (they run through it but say nothing worked). We wish to add some kind of form for this purpose that will email us with the complaint of the user. On my end, there are database functions and tasks which I need to automate (such as adding initial Vehistory (Vehicle-history) objects to the database). There is also content we need to add. We have one full diagnostic chart with about 35 states in it; I envision that by projects' end, we will have something like 3-5 of these to provide a fuller picture. There is also an idea of providing links to YouTube or Wikipedia at steps in the diagnostic process a user may find confusing. This may be a good idea, with a good return on investment, but I'm currently more concerned with adding basic functionality and framework then straight up-content (same goes for new diagnostic charts). Overall, I think the project is on schedule and we're doing pretty good.
No comments:
Post a Comment