Clovertech

budgeting development hours & ODBC module

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › budgeting development hours & ODBC module

  • Creator
    Topic
  • February 12, 2007 at 2:31 pm #49067
    Kathy Riggle
    Participant

      I’ve been asked to “rough out” hours (for budgeting purposes) for interface development on a very large project. The project will involve multiple message types. I know how about how long it takes me to do certain things, but I won’t be doing the work myself.

      So here’s my question – does anyone use any kind of formula, or have numbers that they use for this purpose? For example, how much time would you allot for an HL7-HL7 ADT interface?….etc.

      Also, we’re intending to buy the Cloverleaf ODBC module to communicate with a SQL database. What kind of learning curve is associated with that in terms of Cloverleaf (not on the SQL side.) How much time does that add to development?

      Thanks in advance….Kathy

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • February 12, 2007 at 2:52 pm #60618
        Darren Powell
        Participant

          I usually start with 40 hours estimated for an ADT interface.  This includes building and testing support.  Notice I did not say testing, as ADT testing should be done be analysts for the ADT and Ancillary system.

          Hope that helps!

        • April 23, 2007 at 1:19 pm #60619
          Steve Robertson
          Participant

            Kathy,

            FWIW, it took me about 80 hours or more to get the ODBC interface working the way we needed it to. I wrote our code to hold a persistient connection to the database. That made it harder. I had to find out the hard way which error codes from the database (Oracle here) needed to be trapped and handled in tcl.

            Email me if you want more details – I don’t check Clovertech regularly.

          • April 23, 2007 at 2:53 pm #60620
            Daniel Lee
            Participant

              I had a class on IT project management and they gave me a formula that seems to work pretty well.  Take three guesses at how long it will take.  Call your “best case scenario” B, your “worst case scenario” W, and your “realistic guess” R.  Then use the formula (B + 4(R) + W)/6 = T where T = the time that a project step will take.  This formula works best when you break the project down into smaller steps and use this formula for each project step.  This way if worst case scenario happens on one of the steps then you can make up the time if best case scenario happens on a different step.

            • April 24, 2007 at 8:29 am #60621
              garry r fisher
              Participant

                Hi,

                Purely for estimating we work on 1 day per message. Total overkill but we normally have to estimate without any knowledge of mapping etc – just told ADT, OCM’s etc.

                ODBC is not (too) difficult – Again for estimating we add 3 days to write the code for a simple seelct, fetch loop and map message(s).

                Testing, QC etc are all additional.

                Regards

                Garry

            • Author
              Replies
            Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.