Skip to main content

Home/ Educational Mashups/ Group items tagged model

Rss Feed Group items tagged

Sebastian Weber

Mashups: Strukturelle Eigenschaften und Herausforderungen von End-User Development im W... - 0 views

  •  
    In diesem Beitrag wird ein konzeptuelles Rahmenwerk zur Analyse und Evaluierung von Mashups vorgeschlagen und in einer explorativen Studie angewandt. Die Studienergebnisse identifizieren die aktuellen Trends und ein dominantes Design-Modell erfolgreicher
Sebastian Weber

Mashup Component Isolation via Server-Side Analysis and Instrumentation - 0 views

  •  
    Web 2.0 and mashups provide opportunities for exciting new applications. However, the security model of the underlying browser technology is quite inadequate to deal withthe new trust and security issues.
Sebastian Weber

Swashup: Situational Web Application Mashups - 0 views

  •  
    ... this programmable Web lacks unified models that can facilitate mashup creation, reuse, and deployments. This poster demonstrates a platform to facilitate Web 2.0 mashups.
Sebastian Weber

Mashups und Composite Apps - Gartner: Die zehn wichtigsten strategischen Tech... - 0 views

  •  
    Bis 2010 sollen Web-Mashups sich zum dominierenden Modell (80 Prozent) für die Erstellung zusammengesetzter Unternehmensanwendungen entwickeln. Die Mashup-Techniken sollen sich in den nächsten fünf Jahren deutlich weiterentwickeln.
Sebastian Weber

Gartner urges action on data-centre emissions - ZDNet UK - 0 views

  •  
    Mashup and composite applications. By 2010, web mashups will be the dominant model for the creation of composite enterprise applications.
Sebastian Weber

JackBe.com - Enterprise Mashup Solutions | Products - 0 views

  •  
    The mashup platform Presto provides either the familiar Eclipse IDE model for mashup creation that developers will insist on, or an end-user friendly version that workers can use to build their own applications out of developed services.
Sebastian Weber

Web 2.0: A Pattern Library - 0 views

  • Iterative launches The best way to launch web products is to first release the smallest parts that will be useful and which can stand up as a "product." Then, follow this up by watching user behavior closely and letting your users steer the product toward the real demand while adding more features. Leave your product in "beta" for a year or more if you want.
  • The biggest problem with the old "big release" model is that it required design and development teams to go quite far down the road of development before seeing any real-world user action, which meant that the builders had to make many more predictions about how users would behave before seeing real user behavior.
  • Mashup-ability Mashups add value when two or more web apps have more meaning mixed together than the component parts did separately. If the mashup doesn't add considerable value, it's not worth doing. Unless you're doing it for fun.
1 - 9 of 9
Showing 20 items per page