1 / 7

Web Application Development

Web Application Development. Coursework. Coursework Setup. 5 groups of 4-5 students 2 project options Full project specifications on 3 rd March Final deadline 10 th May 2011 Code storage on Sourceforge.net. Marking Schema. Performance Deadlines Communication Delivery

val
Download Presentation

Web Application Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Application Development Coursework

  2. Coursework Setup • 5 groups of 4-5 students • 2 project options • Full project specifications on 3rd March • Final deadline 10thMay 2011 • Code storage on Sourceforge.net

  3. Marking Schema • Performance • Deadlines • Communication • Delivery • Specification Implementation • Usability • Maintenance • MVC Framework • Documentation

  4. Deadlines • 14th March: Draft implementation plan • 28th March: First Prototype • 25th April: Final Prototype • 10thMay: Final Submission

  5. Project 1: Content Creation Tool • Content Authoring • Edit/Import document into editor • Tag content to split into small content blocks • Export XML in the CAF format • Strategy Repository • Create repository for LAG adaptation language files • Provide web service interface to share items in repository (upload, download) • Content Repository • Store content and strategies in database • Provide web service interface to share items in repository (upload, download) • Project Contacts: Jonathan Foss and Joshua Scotton

  6. Project 2: User Model (UM) Management Tool • User Model authoring • Create a tool to specify which user model variables are scrutable (the user can see them) and which are changeable by the user (& where they should appear) • The interface should allow for specification of user model variable name, domain (allowed values), update method (and how it may depend on other variables) • Export this to the API as below via (an extended) LAG language • User Model delivery • As an output of the previous tool, a XHTML page is created, which represents the interface between scrutable User Model variables and the user. This interface should be able to be added to a tool like ADE (together with the appropriate DM and strategy) • Handle user input and display of UM variables • Create API specification and implementation for the storage sharing of UM information • Handle input of background information • Interrogate remote web service for details of cultural stereotype based on UM state. • Map stereotype to LAG input strategy and UM • Export result to delivery platform • Project Contacts: Craig Stewart and Joshua Scotton

  7. Questions

More Related