Mark: New page: ==Requirements== These are based around the MoSCoW prioritisation. They will be updated after we decide how to proceed with the project. ===Must Have=== :*An...

2008-02-15T20:02:44Z

New page: ==<font color=#00267c>Requirements</font>== These are based around the MoSCoW prioritisation. They will be updated after we decide how to proceed with the project. ===Must Have=== :*An...

New page

==<font color=#00267c>Requirements</font>==

These are based around the MoSCoW prioritisation.

They will be updated after we decide how to proceed with the project.

===Must Have===
:*An easy to use User Interface.
:*A way to specify data sources.
:*Output code that is valid for the major web browsers.
::*HTML.
::*PHP.
::*JavaScript.
:*A visual representation of the mashup.
:*''Support specific APIs.''

===Should Have===
:*Blacklist for sites that do not want there site to be used in Mashups.
:*Set a page refresh time (only get dynamic content every x minutes/hours).
:*Combine multiple data sources into one. E.g. Progressive website lists store locations over multiple pages, should record all stores as one data source.
:*Decent regular expression handling that users can understand.

===Could Have===
:*Output JSP source.
:*Output ASP source.
:*Page scraper to get data.
:*Don't refresh dynamic content if the data cannot be retrieved, but add a warning that it may be out of date.
:*Log in facility to get data that requires a login/password (This may be to hard to design one for every site).

===Won't Have===
:*Support for the less popular Browsers (Code Generator won't have specific conditions for some browsers).
:*Output for less common dynamic page generators.

[[SE401:33:Mashup_Creation_Tool|◄ Back]]

SE401:33:Project Scope - Revision history

Mark: New page: ==Requirements== These are based around the MoSCoW prioritisation. They will be updated after we decide how to proceed with the project. ===Must Have=== :*An...