McLean, VA (PRWEB) August 03, 2012
Managing and assuring quality in a widget development effort presents some challenges in regards to best practices and defining areas of responsibility. Due to the varying nature of functionality from the data sources widgets may be using, defining what layers or tiers are needed by a widget in general is challenging. The design choices that are made to satisfy the needs of a widget will also affect the basic architecture. This document sketches out general patterns seen in widget development and what implications these patterns have for implementing best practices. Additionally, this document attempts to define what constitutes a widget to establish the area of developers’ responsibilities for development and support.
Highlights from Ozone Widget Development Standards white paper include:
- Widget Development - Widget application design, aside from the technologies used, is similar in most respects to the design of any web application. The exact coverage of functionality a developer may be responsible for creating when they are tasked with developing a widget may vary greatly in the context of the overall enterprise.
- Widget Development Architecture Patterns - Which pattern will be appropriate for development is a function of the features available at the data level. This document lays out a set of best practices to which Ozone widgets should adhere. The widget developer should use a pattern that is capable of meeting all best practices when taken in conjunction with the capabilities of the data provider.
- Ozone Widget Best Practices
About NuWave Solutions
NuWave Solutions, with offices in McLean, VA and Columbia, MD has been delivering data management solutions, custom applications, analytic services and business intelligence systems to the federal government and commercial customers for 12 years.