Design Documentation

The draft Design Documentation is now complete and can be found at http://docs.google.com/View?id=dk34gp5_15r44fsd6.

Blog input developer Week 1 – Wild thing



Initial ideas written down, idea bounced with DM and DS, mostly about add-ins for PP and back end/tutor tool.



IDEAS FOR REDESIGN



Add-in that allows access to a web base server that can dynamically generate the question pages after user input, this system would include:



BETA



PHP based Web server that, in the beginning, allows a tutor to create questions he/she would be using during the presentations, these would be called into PP via an embedded xhtml add-in. the server would create the pages dynamically for the tutor before the call is made. It will create the necessary forms needed for displaying the answers i.e if it is a set of multiple choice questions, it will display the answers and which student picked answer. If it is a live test, as soon as the choice is made, it will be displayed on the slide.
A standards compliant client that can be accessed or installed on mobile devices. The student will be able to Log in with their student number and gain access to the correct lecture slides. The client must be able to return the generated xhtml questions from the server and display them, and then allow the student to answer them.
Add - in for Microsoft PP that allows embedded xhtml to load without having need for an input button. this will allow a tutor to imbedding slide (which will have the web server address embedded) and they can reference the question ID number to bring out the correct questions for that lecture (allowing the ability to pull the same question for lots of lectures)


This was initial ideas for a beta, the overall finish product maybe integrate the entire system in to a PP add-in. Open source would require us to create different add-ins for different packages.

If you want to find out more about the initial prototype system and its implementation, please go to:

Link to paper

First few weeks

Since obtaining the award letter at the beginning of June we've been involved in setting up the infrastructure we need to have in place including organising the contract programmer associated with the project. We had always thought that this could be one of the hardest things to establish for the project in keeping to HR policy and procurement policy within the institution. After meeting with the key players with regards to ensuring project support it has actually turned out to be fairly simple and not the headache that it could have been. So infrastructure wise everything seems to be in place.

The system involves building upon an institutional learning and teaching innovations project we developed a couple of years ago. The tool esentially was a stand alone application which took a Microsoft Powerpoint presentation and embedded dynamic content within it. There were a number of issues with this at the time with one of the largest issues being negotiating Microsoft's 'standards'. The system was trialed fairly successfully in two modules over two semesters and has been translated into a few academic papers. We have this month reviewed the old system and its problems with the view of tackling this grant as an opportunity of working towards the ideal system. A system which at the very least embeds into MS Powerpoint to encourage ease of use within the user community and in addition is extensible enough to be re-packaged for other presentational environments. To this end we have this week spent some time focused on thinking about our system in terms of essential and desirable requirements and have this week put together a release schedule involving three releases with each to be delivered over a four week period.

Next on our agenda over the next few weeks is a focus on the design of the system at conceptual level and then at physical level in the form of UML and class diagrams. The programmer is due to join our team in mid-July and will contribute to the end of this design process.

Finally, a SWOT analysis for the project.

Stengths

Pre-existing prototype system
Already been trialed within a user community - feedback gathered
Understanding of what the ideal infrastucture should be
Know already some of the problems
Team

Weaknesses

MS Powerpoint as a focus - originally for the old innovations project we wished to use a more open tool, such as openoffice, however, MS PP was the only tool which seemed to be able to work for our purposes - as other environments didn't offer structured xHTML - only static images of slides were used.
Developing a community of users
Challenges traditional views of lectures, however, can be used in lots of other scenarios
Not everyone has a wireless tool in classrooms, however, with the advent of always on contracts such as those supplied with the iPhone this becomes less of a problem.

Opportunities

A real opportunity to learn from the problems of the first tool and develop a much more usable and professional product
Dissemination activities for the product including HEA Physical Sciences workshop in October which was already set-up before award
An opportunity to get people excited about our product and thinking about other ways to use it.
Scope on completion to use technology in conjunction with other innovations projects
Scope on completion for professional use of the technology.

Threats

Scope creep
Staffing
Delays in procurement or at various stages of the project

Wild thing project

Welcome to the JISC sponsored WILD Thing project blog.