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. ...
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 share feedback at our next meeting. ...
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. ...
Prototype 4 includes a lot of design changes stemming from our FSW and Winter Terms sprint. These changes include improvements to the homepage and accomodation for non-expedition placeholders for FSW, winter and subject areas. Other enhancements were made in the expedition forms and sub sections as well as proper differentiation between them and their non-expedition counterparts. ...
The purpose of this meeting was to finalize the data-entry sections of the system by further describing functionality specifically on non-expedition semesters. Non-expeditions were discussed both as FSW / Winter term as well as other subject areas or strands of the curriculum delivered in parallel to expeditions. The majority of this meeting focused on refining prototype 3 further by improving the placement of FSW and winter semesters. ...
After presenting the second prototype at the last requirements meeting, it was apparent that more work needed to be done with defining what an expedition is and where its sub-sections correctly belong. Much of the discussion of the meeting concentrated on Standards, Learning Targets, Assessment (STAs) and their correct placement in the map. ...