TagPrototyping

Axure Prototype 6

A

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...

Axure Prototype 5

A

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.  

Axure Prototype 4

A

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.  

Axure Prototype 3

A

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.

Axure Prototype 2

A

This prototype was developed after several discussions via email regarding the initial requirements of the project.  The kickoff meeting was helpful in framing the basics of the system in the first prototype, however it was lacking detail and missing some of the crucial elements of an EL map.  

Axure Prototype 1

A

This prototype was developed after the initial April 10th requirements meeting.  It includes a basic design with an incomplete ‘dashboard’ page providing user interactions for various parts of the system.  Upon learning more about the unique needs of EL, it was determined the main expedition form / interactions was fundamentally flawed.  

About Author

Ian Carnaghan

I am a software developer and online educator who likes to keep up with all the latest in technology. I also manage cloud infrastructure, continuous monitoring, DevOps processes, security, and continuous integration and deployment.

Follow Me