A life in the day

1/6/2005

Arguing for an upgrade

Filed under: — site admin @ 12:41 pm

My team has a big architectural meeting coming up soon; it will be time to discuss what’s working, what’s not, what our system wants to be when it grows up. It’s a three-day, offsite meeting. We’re flying in team members from Houston and Indianapolis. It’s a big deal. And I’m trying to prepare.

I want to write a document describing some of the benefits of many of the modern software development tools and techniques. But I’m stumped at where to begin. The problem is that there’s far too much to say.

Our current system is an ASP/VB/SQL Server web application. It works only with IE6. Our ASP pages are mixes of presentation, business logic, and data access. Parts of the navigation relies on Javascript. Some of the HTML is generated inside VB DLLs. There are client-specific functions mixed in with generic stuff. There is a very flat directory structure, with no way to distinguish the functionality of various modules.

There are no automated tests, nor any scripts for manual testing. Building the system is a matter of grabbing the code from several different source-code control databases (and all the code that developers have forgotten to check in), moving it to the production machine, then manually trying out anything you’ve been working on, finding the DLLs you forgot you needed to register, trying it again, calling everyone who worked on the system, adding to the database the tables someone forgot to tell you you needed, lathering, rinsing, and repeating until no one notices any further errors.

And of course there is absolutely no documentation.

The initial system was built by a very talented programmer who was quite new to all the technologies used. She did a great job getting things working, but the system has grown in all directions, and there has been little coordination of the efforts.

What I want to propose is a multi-tiered application architecture, using modern development technologies and techniques. My choice would be Java with Hibernate and Spring, although I don’t have much experience with either framework. But I would certainly be willing to live with .NET or a Python framework. I could even see doing all or some of it in PHP. I would be willing to consider full-fledged J2EE, although that scares me a bit.

Out output should be standards-compliant XHTML and CSS. Javascript should be optional, used only to enhance a working page(1).

Everything should be test-driven. No code should be checked in without passing unit tests, and no code should be written without having tests for it to pass. The builds should be automated. There should be automated functional tests.

In short, we should be building a modern, modular, scalable, testable, automated system.

The trouble is in having so much to say that I can’t seem to even begin actually writing my document. I’ve been working around the edges, mostly analysis of the various options for technology. But I need to work on the main part, and I need to do so soon.

Anyone ever seen good sites describing in management’s terms the advantages to modern techniques?


(1) There is one inescapable exception to this. We have a Javascript WYSIWYG editor. We are told we need to maintain a WYSIWYG editor without relying on any plug-in. Nonetheless, everything else should still work with Javascript turned off.

One Response to “Arguing for an upgrade”

  1. Chuck Says:

    I suspect the way to argue your case sucessfully is to show them that (time saved) - (effort spent) will still pay for itself. I’m not aware of any good sites that address what you’re talking about, but there should be scads of info about cost justification, ’cause that’s what the tool builders try to use to sell to big companies.

    I’m lucky enough to be in an environment that’s much closer to what you described (though still far from perfect, see my buddy’s last post) and I appreciate the luxury. Well, I appreciate it, except for today, when I’m trying to get a nice clean build box made to replace the one that blew up yesterday, for a release that should’ve gone oput last week :)

Leave a Reply

Powered by WordPress