Jeff ran into some problems when he did not save the form page he was on and lost changes. He had trouble remembering to press the update button on the various grids. In addition to this, he also came across problems with the ‘Big Ideas’ control and text area bug for ‘Final Product’ that others faced. ...
This usability testing session revealed some issues with the using the Big Ideas drop-down selectors for adding new records. In addition to this, the process for adding standards, targets and assessments appeared confusing to the user. There were some issues with workflow where the user was confused about which screen she was on. Recommendations were made for allowing file uploads. ...
Megan was able to complete most tasks with ease. The only issue she seemed to have was related to workflow and finding specific sections or areas of the application. The confusion stemmed from differentiating between the case study and expedition screens. ...
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. ...
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. ...
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 other related concerns and questions regarding the proposed system. ...
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 producing complex interactions has proven to be time consuming and difficult. ...