This remote usability test also revealed some problems with workflow as well as keyboard accessibility problems not previously discovered. In addition to this, Kate noted several problems with form controls including the ‘Big Ideas’ dropdown selection and ‘Common Core’ search picker.
The second remote usability test revealed some recurring issues as well as new observations. Rob noted some issues in remembering to click update on the various grids. He also ran into some problems with workflow and general navigation in terms of locating various parts of the system.
Since the last sprint, the first iteration of the actual application was developed using ASP.NET MVC 5 and SQL Server backend database. This application is being used for the upcoming remote usability testing sessions.
On December 17th, a Professional Development (PD) meeting was held at Monarch and 18 teachers and staff members attended. At the even the researcher presented the Axure prototype and discussed the current development of Expedition Mapper. Field surveys were distributed and completed by teachers, who were then divided into three groups afterwards to elaborate on their answers and to discuss …
The first remote usability test revealed some issues regarding various interactions within the application. For the most part the various tasks were completed with ease, however on one occasion a system bug caused problems. Later in the session, Beth ran into problems using the text area box for final product description.
The pilot usability testing was held at the University of Baltimore’s usability lab. The pilot involved the new ASP.NET application, which enabled for more realistic interactions when compared to the earlier Axure wireframes. Several problems were discovered with the application in terms of bugs identified with browser inconsistencies, not previously anticipated.
This is the final Axure prototype that will be developed for this project. It build on the design of prototype 5 and increased consistency between screens. Additional data elements were added and the interface for creating and managing case studies was redesigned. Axure has been a useful tool for developing these initial prototypes, however limitations of static web pages and …
Today a short meeting was held to discuss the overall progress of the prototype to date and demonstrate the key functionality to the EL representative for the school. Comments were made on how further improvements could be made to the data collection part of the system. The group is going to review the prototype over the next week further and …
Prototype 5 integrated both expedition and non-expedition subject areas. The concept of ‘strands’ being units within the system has been further defined in this design. The interactions for strands and sub-sections as well as optional elements has been further developed in this prototype.
This sprint continued discussion of non-expeditions. This week we focused primarily on restructuring the prototype to correctly integrate subject areas that do not fall under the typical expedition. The home page was refined further and several changes were made to the math non-expedition subject area created for prototype 4.