Home arrow SOAP & Web Services arrow Page 2 - Dynamic Data Analysis on the Web-a Design Approach

Data analysis concepts - Web Services

Learn about an adaptable approach which separates programming tasks from Web page design tasks. This strong conceptual model encourages good design, enables re-use of data definitions, and is well-suited to the construction of dynamic user interfaces. The authors also illustrate the particular challenges you might encounter when you dynamically change the analysis performed by Web pages. (This intermediate-level article was first published by IBM developerWorks, August 5, 2004, at http://www.ibm.com/developerWorks).

  1. Dynamic Data Analysis on the Web-a Design Approach
  2. Data analysis concepts
  3. Dimensions and measures
  4. Filtering and ordering
  5. Dimension, measure, and slice dimension tags
  6. Presenting data
  7. Value formatting tags
  8. Use of JavaBeans to provide dynamic values
  9. Reporting common errors
  10. Tag containment
  11. Custom tags: lightweight, cheap, replaceable
  12. Benefits of this design approach
  13. In conclusion
By: developerWorks
Rating: starstarstarstarstar / 15
December 29, 2004

print this article



Understanding data and being able to express it in an appropriate form is a key task. Many often overlook this task in the rush to get information to the user. By providing a means to focus on the important concepts and a tool set to exploit them, our design approach encourages an up-front analysis of data that pays dividends in the development cycle.

Data Sources

Early in the development cycle, and typically during the requirements gathering phase, you develop an understanding of the required data. The questions that need to be answered during this phase include:

  • What are the user tasks to be supported, and what data is needed to perform those tasks?
  • Where is the source data, and how closely does it match the required data?
  • If there is a mismatch between the required data and the source data, how can the mismatch be remedied?
  • If the source data is distributed over more than one location, how can it be joined?
  • In what ways will the user need to aggregate, filter, and sequence the data?
  • What metrics does the user need to view and manipulate?

Arriving at the correct answers to these questions requires user consultation, as well as the services of an expert in the data domain. The use of low-fidelity prototyping helps to clarify user thinking and hone in on the true requirements. This iterative phase will identify the shape and characteristics of the required data, and from this, the programmer will be able to define one or more data sources which will be made available to the page author. The lessons learned about the user tasks will be important to the page author, who can now focus on the user interface (UI) details secure in the knowledge that the building blocks necessary for accessing and presenting the data will be there.

>>> More SOAP & Web Services Articles          >>> More By developerWorks

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort


- Google Play Launched to Revive Brand
- Google Releases Preview of its Cloud SQL Ser...
- Microsoft and Amazon Team Up for the Cloud
- GoDaddy Joining the Cloud
- Amazon EBS Outage Challenges Cloud Supporters
- Dynamic Data Analysis on the Web-a Design Ap...
- Use collection types with SOAP and JAX-RPC
- Blogging Away To Glory (A bBlog Primer)
- Introduction to Service Oriented Architectur...
- Connecting Smart Devices on the Internet
- An Embeddable Standards Compliant Web Servic...

Developer Shed Affiliates


Dev Shed Tutorial Topics: