我正好做这个作业,以下是我写的:
• File Names
File names should be as clear as possible, they must be meaningful which can tell other programmer what is this module tells about, what is the functionality of this module. For example, I_module.cpp indicates “Input module” and so on.
These module files should be well grouped into different directory. This helps to manage software product, and form a good develop habit. For example: src/ is the subdirectory for storing source code files; include/ is for head files; bak/ is for back up; doc/ is for document like Javadoc and etc. bin/ and class/ is the place for created files.
Version numbers should appear in module names also to keep it clear which version performs which task. For example, I_module_version.cpp tells “Input module with version”.
• Version numbers
Version numbers are combined by three parts. They are major version numbers, minor version numbers and build. Major and minor version indicates the release version and the changes in products, respectively. Build changes into letters when release.
There is no limit in digits used, like zoneAlarm 3.7.159. Note, it is a very bad idea that if version number increased from 3.0.1 to 3.0.20 to 4.0.1. For example, you first version numbered 3.0.1 for your product. And later you did 20 minor changes, the version number increased to 3.0.20. Then you think you made enough changes, and release a 4.0.1 product. This confuses users because the second digit did not increase at all! Good numbering should be: from 3.0 to 3.20 to 4.0.
• Tags
Tags are release information indicates the improvement changes between old version and new version.