Re: [xml-dev] How to estimate the time needed to create an XML schema?

To which we may add,
* Testing with users
* Feedback + changes
* Testing

etc.

How long was that piece of string?
On Wed, 19 Sep 2018 at 15:54, Tony Graham <> wrote:
>
> On 19/09/2018 14:13, G. Ken Holman wrote:
> > Whatever you come up with, multiply it by pi before submitting the
> > estimate. A long-ago colleague advised me of that and it has worked
> > well for me.
>
> I tend to use the kg-lb conversion factor, but pi may be better.
>
> ...
> > At 2018-09-19 12:56 +0000, Costello, Roger L. wrote:
> ...
> >> For example, the estimated time needed to create an XML schema
> >> containing 200 elements, each element having 1-3 attributes, is
> >> ____ hours.
>
> If you know that you have 200 elements, each having 1-3 attributes, then
> you've done most of the work already.  In the general case, the work
> required to go from knowing that you have 200 elements to having a
> schema file (or files) would be a fraction of the work required to work
> out the 200 elements needed to model the thing that you are modeling.
>
> Where does 'create' end?  Beyond the schema file, does 'create' include
> the element and attribute documentation, comprehensive examples, sample
> documents, template documents, editor customization, and other things
> that may be required for people to be able to actually use the schema?
>
> Regards,
>
>
> Tony Graham.
> --
> Senior Architect
> XML Division
> Antenna House, Inc.
> ----
> Skerries, Ireland
> 
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: 
> subscribe: 
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.