[LINK] What's a reasonable level of code-checking?

[David Lochrin]

On Thu, 17 Aug 2006 17:35, Bernard Robertson-Dunn wrote:
>>    Developing reliable and properly engineered software in any environment requires an appropriate end-to-end "process" which begins with a specification of the process itself, continues with development of formal software requirements, and extends through to testing & maintenance.  Properly developed business software is no less "engineered" than biomedical or other embedded software, whether or not the physical world forms part of the system.
>
>Where do you draw the line when it comes to software?
>
> Is a program written in Excel and/or its macro language, software?

   In principle, a "program" written in Excel is certainly "software" in the context of this discussion.

   However a simple spreadsheet (say an invoice) is distinguished by having some phases of the appropriate software engineering process almost null while others, including the software design, implementation, and user documentation, are pretty much embodied in the end-product.

   A more complex spreadsheet (say a financial model of a proposed enterprise) may require far more software engineering, including a formal set of requirements, detailed user documentation, and systematic testing.

   But the principles of good software engineering are still relevant.

> I've seen many examples of Excel programs that are not properly engineered. The Federal budget for example.

   I'm a little surprised to hear the budget is prepared, or even presented, as a spreadsheet.  I wonder if any detailed user documentation exists, and whether everyone who uses it or contributes to it's creation, fully understands it.

David