Doc: ps2001-5-1101-001 Rev: R02. 00
Revision tracking and control
Download 1.5 Mb. View original pdf
|
1486357009-URS, URS
- Navigate this page:
- 4.6.2 Symbolic addressing
| 4.6.1 Revision tracking and control (1) The Validation Plan (VP, [Ref. 002] , identified a potential risk if library modules were being simultaneously developed (see Appendix A of the VP one of the remedial actions needed to mitigate this risk was the requirement for the individual version numbering at the individual module level (i.e. each module, data structure and data block will have its own, tracked revision number. This system of module level revision control will be implemented on this project. (2) Each software module (Controller blocks OB, FC, or FB, see § 4.1.4 for details) and data blocks (DBs) will each have revision data, this will include: • Revision number • Revision status (e.g. draft, test, release c) • Revision date • Revision author Doc PS Rev R 53-71 (3) The module revision data will be contained within the module itself, either in comment fields or hardcoded in the module (where possible. (4) A register of block revisions (external to the software) will be maintained of the current version of all software modules as they are developed. 4.6.2 Symbolic addressing (1) Symbolic addressing will be used throughout the software, all internal memory bits, timers and counters c. will , if they are used, be given a symbolic (mnemonic) name. (2) All blocks used within the software (OB, FC, FB, DB, UDT see § 4.1.4 for details) will be given a symbolic name. (3) All input and output signals will be given a symbolic name. (4) All blocks within the library shall use optimized access (essentially, purely symbolic addressing, the only exception to this shall be if a module is being developed to interface with a system that is incapable of using optimized access. Download 1.5 Mb. Share with your friends:
|