Re: ARS as a development system

Mon, 17 Jul 2006 21:52:14 -0700

** I'm working at the California ISO now and we run mostly scratch-built applications.  I inherited most everything, so now I have the joy of deciphering it all.  I'd say that most of them are well built, though, and where they aren't I can see evidence of customer demands on the designs.  8)

Building or buying decisions are as simple as 'can we do it?'  A company must also consider how they intend to support an application once it is in.  You may have a good ARS team in-house, but a scratch-built application is one where your company gets to pay the full burden for support.  If it is business critical it can make sense.  If it isn't your core business processes you are automating, the argument to build can be severely weakened... and should be.  I can't think of a single reason to build my own ITSM suite when I can buy ESS instead.  8)

The one app of mine running at the ISO now is one I had in my own portfolio when I arrived in November.  I've customized it a bit for them now to handle a variety of customer support techniques being used on the business side, but it got its start long ago.  The reason we won the build or buy argument was that we could deliver on the new CIO's need for a quick win.  The purchasing process would have taken too long, so we made the cut.  Now we have a few happy customers and the app is growing through a RAD approach to design and development.  My need to develop for people is mostly satisfied too.  8)

On 7/11/06, Griggs, Thomas <[EMAIL PROTECTED]> wrote:
**

And the off-the-shelf systems aren't so darn good either - despite their huge expense.

I think you've hit the nail on the head - unfortunately.

:-(

Tom Griggs
Information Services Dept.
Bridgeport Hospital
Bridgeport CT 06610
203-384-3133
email to: [EMAIL PROTECTED]


    -----Original Message-----
    From:   Action Request System discussion list(ARSList) [ SMTP:[email protected]] On Behalf Of Barry Lindstrom
    Sent:   Tuesday, July 11, 2006 11:45 AM
    To:     [email protected]
    Subject:        Re: ARS as a development system

    I agree that ARS Developers are a dying breed.
    There are four things that, I feel, have led to our demise:

    1. Very Bad, Very Expensive custom systems that never delivered on the
    promise.
    2. The Buzz word of the day, be it ITIL, SARBANES-OXLEY, Best
    Practices...etc gives Executives rationalization for buying not building
    3. Catch 22, a lack of skilled developers makes companies look for off the
    shelf solutions reducing the market fo skilled developers.
    4. Ignorance, No one wants to take the time to understand their processes,
    review cost benefit analyses or examine the possibities of how it could be
    done better and faster.


    Barry Lindstrom
    [EMAIL PROTECTED]

     

    _______________________________________________________________________________
    UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

    __20060125_______________________This posting was submitted with HTML in it___



    --
    -al __20060125_______________________This posting was submitted with HTML in it___

    Reply via email to