Discussion Locked

Software Quality Issues

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am a developer/supervisor and I recently told my ceo that we need to do a better job of documenting and following a process for our internal software development. I was surprised to hear that he felt we didn't need to improve upon our developmentpractices because we aren't a software (i.e. we are a manufacturing) company. He felt that software developed in-house was unsupportable after the developer that wrote the software left the company so why worry about it. I agree that the software can be unsupportable if there is inadequate documentation, but that doesn't need to be the case as we should do whatever it takes to reduce that risk of losing the investment made on developing the internal apps. Let me know what you think and any arguments that I can make for a structured software development process.

Thanks.

Regards,
J

5 replies

by jim hawken

Software unsupportable after the original developer left? I'll have to try that out on my boss...
The company I work for isn't a software company either, but we support and extend lots of legacy systems where the original programmers are long gone. The code that's written to current coding standards and has useful comments for each block of code is a lot easier to maintain than earlier programs. I've tried to maintain external documentation - program structure charts, dataflow diagrams and such - but wind up letting them get out of synch with the programs.
Coding standards including expectations for comments and maintenance histories go a long way toward making things easier - saving time and money - without requiring much extra work. So does documenting testing so that the same tests can be run when the program's changed.
Too much structuring of the development process can slow things down though. A lot of the paper-chasing's been cut out of our system, but I used to spend a lot of time running around getting forms signed off.

by al macintyre

Most of the software I develop is add ons to packages, which in general have programming standards vastly inferior to what I developed over the years at many employers, but some standards seem to be common to all decent packages.

Copyright noticein consistent location.
Name of Program (title) standard boiler plate format stating what the function of the program is & for what purpose various files are accessed ... an overall summary word picture of how the program is accomplishing what.

There is a modification history, consisting of a date, change tracking number, initials of programmer, initials of who asked for the change, then 2-3 line explanation of why this change was made & which subroutines contain the change.

Every line affected by a change have a code that agrees with the change tracking number ... so if people happy with program on date X but not on date T, we can review all the changes to that software between the 2 dates.

There is something called a data dictionary within the program ... comments near the top that explain the function of various types of variables.

Every subroutine has a block in the title section giving 2-3 line explanation of function ... some of them say what field names need to be passed here with what types of values & what will be returned.

And I am just telling you some basics.

Recently I have been working with copying lists of programs from source code library to a work file sorted by description & linked with whatmenus they are on ... so if user wants to do X ... we have a program to do X & what menu it is on ... this has led to me tinkering with the titles of the programs in the source code to make the result a bit more user friendly.

by al macintyre

CEO obviously inexperienced in supervising software quality. I have been in the business 40 years & it is typical in some industries for a company to have thousands of programs written in such a manner that a new programmer can maintain a program written by a former employee we never met & successfully enhance it.

This is accomplished via PROGRAMMING STANDARDS which you can find through the associations of whatever programming languages you are using.

The idea that a person writes a program & when they leave the company that no one else will be able to do anything with it is to say that your salary is a throw away a waste what are you there for?

by donq

How many times have we all heard comments similar to those of your CEO?

PROPOSED FIX: Electronic business data is stored in a data repository (or Object Warehouse) - 1 server OR many servers w/ 1 PC and/or many PCs. It is still "a" data repository OR SHOULD BE!!! A single well protected Object Warehouse accessed through User Level Intranet Security that should (if ONE doesn't exist today) serve everyone. Replication, Synchronization, and on demand and/or pre programmed Updates make data access a mute issue today in a well designed system IF THERE IS A SINGLE PROPERLY STRUCTURED (Normalized) Object Warehouse. All ODBC products essentially recognize the same thing - Tables and Fields (that's it, can't make it any more complicated than that)!

HARD SELL: Sell your CEO on allowing you to develop a single Object Warehouse based on Business Notation the next time there is a (database) software development project. Or just do it on your own because it will save your boss money AND fully document your new software structure (providing both business function definitions and technical definitions for every "data bucket" the business uses. "Business Notation" (the naming convention) and "Business Notation" (the book series), and BNM2K (the software) is the key and proves why Hungarian notation (the naming convention) does NOT work, + how Business Notation using any ODBC product will work! Absolutely eliminated software "tunnelvision" when an ODBC product stores ANYTHING making your structure portable for ANY programmer using your ODBC product of choice!!!

Contact me at "Don Quigg" for particulars if interested.

This discussion is closed to new replies.