Version / Status / Date / Page
1.0 / Commercial in Confidence / 08-Aug-2006 / 3 of 5
Environmental Naming Convention SOP
Document No: / SOP_0105Prepared by: / David Brown
Date: / 09-Aug-2006
Version: / 1.0
Document Approval
David Brown / Author
Document Control
Version / Author / Date / Description1.0 / David Brown / 08-Aug-2006 / Version 1
Table of Contents
1 Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definition 4
1.4 Responsibility 4
1.5 References 4
2 Environment Naming Convention 5
1 Introduction
1.1 Purpose
To establish the requirement for environment (platform) naming conventions.
1.2 Scope
Department/Section: IT Group
Naming conventions will be created for objects used in the environment where validated software applications are developed.
1.3 Definition
Environment - A collection of hardware, software, network communications and procedures that work together to provide a discrete type of computer service. There may be one or more environments on a physical platform (e.g. test, pilot, production). An environment has unique features and characteristics that dictate how they are administered in similar, yet diverse manners. Examples of platforms are Windows 2003 Server, Linux, and Solaris.
Validation Group – the group responsible for ensuring that computer systems are implemented and maintained in a validated state.
IT Group – the group responsible for development, operation, and maintenance of computer systems.
1.4 Responsibility
The responsibilities for preparation and approval of naming conventions are defined in SOP SOP_0100 "Implementation Life Cycle". It is the responsibility of management of Operational Support and Validation to ensure that this procedure is followed.
1.5 References
Document ID / TitleSOP_0100 / Implementation Lifecycle SOP
2 Environment Naming Convention
Naming conventions for each environment should be unique and appropriate to its characteristics. Naming conventions for characteristics that are common across environments should be consistent.
Within each environment, there must be naming conventions that apply to any application or data structure within the environment. The following naming conventions must be established:
q Application Names, both at the system level and subsystem level
q Libraries and storage structures or facilities
q High level executables such as jobs, tasks or scheduled events
q Low level executables such as object modules, transactions and linkage members
q Program and Report names
q Permanent and temporary File names
q Database objects (tables, views, indexes, fields)
Hidden text