Search This Site
Sep 02 2010 23:03 UTC | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Tutorials
XML ManagerQuestions
Got a question for us? Quality
Bookmarks |
Return On InvestmentOur XML Manager component can save you money and time. A project delivered on time and with zero bugs is, of course, priceless, but here we show you how much you save when it comes to handling XML files. Example ScenarioLet's assume that you want to load transaction data from an XML file and store it in a database. You a get a new file each data, and the file can have thousands of transactions. You don't control the format of the file, so it can and does change. One developer has been assigned to the project and it's a fixed cost project, so every extra day counts. If your developer builds the XML file handling using the usual DOM API, you'll need to account for the following table of costs. Also, the DOM API means that you have to hard-code the XML format into your Java code, so any changes mean extra developer work to implement them. Developer time is charged at $50 dollars per hour which includes all ancillary employment costs and represents a heuristic median value over a range of developer types from high-level consultant to outsourced coder. We'll assume that the some of these costs may or may not occur, and thus calculate the final cost based on their probabilities.
Thus you have an expected cost of $351.25, and a worst case scenario of $725 and 14.5 developer hours lost. Notice that even though the actual coding element takes only one hour, all the additional and sometimes overlooked costs can quickly accumulate. For meetings we assume total time taken over all participants. We also take account of XML schema changes over the lifetime of the project, which can have a significant negative drain on developer time. With our Single Developer License, you invest $170.00 and save on average $181.25 and you could save up to $555.00. The previous table just covers the case of a single developer in a small team. If you need to use the component across teams in your organization, you face the following additional costs.
The XML Schema has to be documented properly, and more schema changes are likely as result of a larger team. Increased organisational demands will also impact the bottom line. Taking the tables together, you have an expected cost of $2401.25 ($351.25+$2050.00), and a worst case scenario of $3725 ($725+$3000) and 74.5 (14.5+60) developer hours lost. With our Business License, you invest $970.00 and save on average $1080.00 and could save up to $2755.00. The foregoing analysis is of course subject to many variables and is not intended to be a replacement for your own assessment. However we believe it does provide a general case for estimating the savings that can be achieved when using our XML Manager component. |
FREE Email SupportAll XML Manager licenses include a FREE 6 month Email Support Package, worth $1500.00. FREE CSV ManagerAll XML Manager licenses include a FREE CSV Manager single developer license, worth $170.00. Easy XML AccessThe XML Manager component lets you access your XML data using standard Java objects such as List, TableModel, and ResultSet.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
comment on this page
Home |
Search |
About Us |
Contact Us |
Our Products |
Documentation |
Resources |
Login
Copyright © 2004-2010 Ricebridge. All Rights Reserved. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||