About This Site
High School Computer Clubs Project
Doc. Resource 111
Java CodingStyle (pdf)
Programming Standards Draft
Rules For Good Programming
If we want to write real programs - we need to write programs like the real programmers do.
We need to be able to understand programs other people write. We also need to be able to understand the programs we wrote last week. If we write our programs neatly, using consistent standards, then reading and writing our programs becomes easier.
Documentation is also important. It helps us at every stage of a project from planning to final installation.
There are many existing standards. These are useful and it makes no sense to try and reinvent them.
One problem is that some of these standards are very long and much of that length is concerned with issues, such as legal and copyright issues, which are of less importance to us in a University. Another problem is that some existing standards contradict one another. So we have to choose.
The aim of this standards project is to produce a simple set of standards,
for documentation, for project proposals, for theses, for project reports
and for coding and comments.
What do we want?Simple, comprehensive and easily understood standards, sufficiently firm to give good guidance and sufficiently flexible that no-one will feel that they are being forced to do something a way that they do not want to do.
How can we do it?By discussion and consensus. Post messages on cs-discuss. This concerns everybody. If the traffic gets too much, we can open a separate list.
Where can we start?Coding standards - some resources and suggestions
Documentation standards - some resources and suggestions
Last Updated : 2002-03-24 14:16:22