......

QHSE Manual Drake & Scull

DocumentName:
QHSE Ref. No. IMS/IT/SDP/10 Rev. 01
SOFTWARE DEVELOPMENT
POLICY Date: 31sl October 2009

~
-

' '

SOFTWARE DEVELOPMENT POLICY

Rev Date Revision Record

'-- 01 31/10/2009 First issue

Page 1 of 3

~
 QHSE Manual

Document Name:
QHSE Ref. No. IMS/IT/SDP/10 Rev. 01
SOFTWARE DEVELOPMENT
POLICY Date: 31st October 2009

1.0 PURPOSE

The purpose of this policy is to establish guidelines for software development at Drake & Scull
International. This policy will better allow Drake & Scull International to standardize the software
development, resulting in better resource utilization, a more consistent outcome, and a higher
quality software product delivered to end users.

2.0 SCOPE

All software developed by employees of Drake & Scull International using Drake & Scull
International’s resources are the property of Drake & Scull International. This also includes all
software developed using personal resources that was commissioned by Drake & Scull
International. This policy covers software development for the following types of applications:

• Internal departmental management software and report developments.

• Windows-based productivity suite add-ons for Word, Excel, Access, etc.
• Web applications and Intranet.
• Any application developed to automate regular processes.
• Any other application types.

3.0 DEFINITIONS

None

4.0 RESPONSIBILITY

Corporate IT Manager has all responsibility of this policy to ensure consistently, standardization of
high quality output.

5.0 PROCEDURE

5.1 Development Languages

The following programming, scripting, and coding types of languages can be used for
software development unless new techniques or languages are produced:

1. VB.net
2. ASP.net
3. PHP
4. HTML and JavaScript
5. C++ or Visual C++
6. Visual Basics and Access programming

5.2 The Coding Standard

The coding standard for the software development must not change and must follow the
same standard every time a need of development is needed. This will automate the coding
process and speed up the development cycle.

Page 2 of 3
 QHSE Manual

Document Name:
QHSE Ref. No. IMS/IT/SDP/10 Rev. 01
SOFTWARE DEVELOPMENT
POLICY Date: 31st October 2009

5.3 The Development Environment

The following integrated development environments (IDEs) should be used for all software
development projects. In situations where development is being done using personal
resources, a compatible IDE must be used that does not negatively impact or hinder the
development process in any way.
• A source Code editor
• A Compiler or Interpreter
• Build automation tools
• A Debugger

5.4 Reuse Policy

Software reuse covers more than just source code. Application development considers the
following software development cycle as candidates for reuse:

1. Project Plans. .
2. Architecture.
3. Requirements Models and Specifications.
4. Designs.
5. Source Code.
6. User and Technical Documentation.
7. Data.

5.5 Licensing

Software developed for Drake & Scull International should be licensed using the genuine
software product.

6.0 ATTACHMENTS

None

Page 3 of 3