HP WBEM Services Software Developer's Kit for HP-UX Provider and Client Developer's Guide A.01

Factors for Estimating Provider Effort
Appendix E140
This is just a tool to help with estimates. Providers can take as little as
two weeks to as long as several months depending on a variety of factors.
Each item below adds time to the schedule. To get a very rough estimate
of provider effort, answer the questions below and add the days together.
• Schema complexity
Defining the schema can be very simple or can be very complex and
time consuming. The effort required for schema is one of the most
variable parts of writing a provider.
— Schema defined and solid (e.g. implementing existing CIM
Classes with no changes) - 1 Day
— Schema defined but may change slightly - 3 Days
— Schema not defined and/or requires coordination with other
groups and/or other companies - ranges greatly
• Number and kind of operations implemented
Some operations require a lot more work (for example write
operations in Instance Providers, and Association, Query, and
Indication Providers).
— No difficult operations - 0 Days
— Otherwise, could be up to 4-6 weeks extra
• Number of properties and extrinsic methods
The more of these, the more code needs to be written, tested, and
documented.
— < 10 - 3 Days
— < 25 - 6 Days
— < 50 - 10 Days
— more - ranges greatly
• Stability and definition of how to get the information
If you know how to get the information (via APIs, system calls, CLIs,
or data structure access) and you don't have to test usage of the calls,
provider development will be much quicker.
— Know exactly how to get the information and trust usage of the
call - 0 Days