Agile Scorecard for the Mapplet Project

The customer’s original concept of the mapplet search form was that it would allow display filtering (i.e., filtering the hotels being displayed by various criteria, such as price band and amenities). However, during one of the design review meetings at ESRI, the team discussed performance ramifications and decided that only the price-band filtering would be done as a display filter. The other features (filter by chain, filter by amenity, etc.) would instead be done using a query filter.

This decision was driven by performance data on the map server, the estimated amount of traffic, and so on. The idea was that the load on the server could be dramatically reduced by taking the most common display-filter operation (flipping the price-band switch), and caching that operation and its associated data in the user’s web browser.

From a design perspective, this still leaves us with a DisplayFilter class on the client side. But there’s also a QueryFilter class that is on the server side. And so the sequence diagrams will use both of these classes appropriately.

Note that the performance-driven decisions were made after doing some exploratory coding on the brand-new server software. This is true agility and yet it remains model driven. We’re “proving with code” the performance parameters on the Map Server, and then adjusting our modeling based on this information at the same time that we’re refining the original models from the JumpStart workshop using the persona analysis.



Agile Development with ICONIX Process. People, Process, and Pragmatism
Agile Development with ICONIX Process: People, Process, and Pragmatism
ISBN: 1590594649
EAN: 2147483647
Year: 2005
Pages: 97

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net