Control version

Lippman, J. Lajoie, C++ Primer, Addison Wesley Professional, Reading, Mass 1998. 

Johnson, Design Patterns, Addison Wesley, Reading, Mass 1997. 

Rumbaugh, I. Jacobson, Unified Modelling Language User Guide, Addison Wesley Longman, Reading, Mass 1999. 

---

Administrative procedures for software-version control are more manageable. 

Research reports—Research reports such as stability reports, method validation and transfer reports, and pharmaceutical development reports are key documents used for NDA/MAA filings. These documents are strictly version controlled. 

All data must, of course, be searchable, retrievable, and subject to acceptance or rejection based on both automated and retrospective QC analysis. Reports must be flexible in content yet easily assembled, intuitively understandable, and easily shared with appropriate security and yes, it would be nice if the reports themselves could become, like the assay protocols, version controlled, searchable documents residing in an appropriately indexed relational database. These are just the basic requirements. 

Version Control Software 299 VBScript/JavaScript for Applications 299... 

To keep control of your SAS programs you should learn about and invest in version control software. There are many commercial and free (RCS or CVS) version control software solutions available that do an excellent job of maintaining the integrity of your SAS programs. You can also integrate your version control software solution into your SAS program editor. 

External Documents e.g. Regulations, note document and version control ... 

The virtual SWISS-PROT entries have a far-reaching effect on TrEMBL. For example, the virtual entry for the Rubisco (ribulose-bisphosphate carboxylase) large chain affects 3300 TrEMBL entries. Therefore a system has been developed to decompose these virtual entries into rules that are stored in a relational database with proper version control features. 

Since the report is in itself a snapshot of comphance at a given period of time, it should be updated periodically. A complete revahdation is not necessary, but many sites find that an annual review of the vahdation report is helpful. Occasional specific events, such as upgrades of programs or replacement of hardware, may trigger partial or complete retesting. Finally, complex systems tend to evolve, so a review to confirm that version control procedures are appropriately followed is recommended on a regular (at least annual) basis. 

Record Management Describe the format, numbering sequence, revision, version control, and storage of the validation documentation. 

Since networks change frequently, maintaining these diagrams with documented version control is important. A good recommendation is to have procedures in place for regular review of these diagrams (e.g., quarterly). 

The changes and version control section will include information concerning purpose, responsibilities, and testing. Changes in the operating system and/or in Excel (e.g., new version and other significant changes in the spreadsheet) have to be documented, reviewed, and approved. The documentation will include ... 

All other validation sections, such as Design, Test, Security, Documentation for User and Training, Changes and Version Control, Archiving, Periodic Review, and Review and Approval, can be taken from the content uniformity example described earlier in the chapter. 

The methodology and records for design and development of system source code (operating system level), including version control and management and access availability. 

The procedures used to design and develop project-specific application software, including version control and management, the documentation provided, and backup copy availability. 

Software release Master copy and backup Version control Software replication Problem reporting/resolution Fault notification to customers... 

Only upon the successful completion of the integration testing and documentation review should product release be authorized. Once an application software program is released, it should be placed under formal configuration/ version control, and any revisions must follow the requirements of a change control procedure. 

Version control of software source and application code. 

Instructions are version controlled and need to go through a formal approval process before they can be used. When working with instructions in electronic format, the audit trails should start when the instruction is official approved. 

Version controls for the PLC program must be implemented and rigidly enforced. Revisions to the program must be reviewed in detail and thoroughly tested before implemention in the PLC. The various versions must be clearly identified so that there can be no doubt as to what logic is provided by each version of the program. 

Data is archived under SCCS version control and all data sets contain a tail section giving attribution and update history. A number of ADAS data sub-directories have a year number, such as 89 associated with the name. The year number is often used in ADAS to give the year of introduction of a new approximation and is not necessarily the year of production. Thus 89 in the adfll data format denotes the baseline parametric form of stage to stage recombination and ionization data widely used in fusion laboratories. 96 denotes the much higher precision generalized collisional-radiative data which is valid at all densities and is metastable resolved. 

---