2.3.2 Start with Standards
When you begin to build your repository, you may use LANSA's modeling tools or you may manually define objects in the repository. In either case, you should start by creating a set of naming standards for objects (fields, components, files, access routes, etc.) used in the repository. You should also define a set of procedures for repository maintenance.
Standards are needed to protect your investment in the repository.
Rules or standards for driving an automobile were created so that all drivers know how other drivers will behave. For example, they expect cars to be on a particular side of the road and they know who should give way at an intersection. When the rules or standards are not followed, disaster can result and most often the damage is done to the one who did not break the rules.
The same is true of standards necessary for working with a repository. Creating and following standards will:
- protect the information in the repository
- control changes to your existing functions
- improve productivity of the developers
- reduce the maintenance effort for your applications.
The success of a project will be determined by the commitment of all staff to following the standards created at your site. We will review some object naming standards as new objects are created in the repository.
For details about controlling your development environment, refer to Development Environment Administration in the .
Also See