and Cultural Table of Contents Revision History... ii Document Approval... iii 1.0 Overview... 1 1.1 Outline... 1 1.2 Detailed Description... 1 1.3 Purpose... 1 1.4 In Scope... 1 1.5 Out of Scope... 1 2.0 Ministry Toolsets... 2 3.0 Server... 3 4.0 Standard Operating... 3 4.1 Standard Client s... 3 4.2 Mobile Client s... 3 5.0 Database... 4 6.0 Software Configuration Management (SCM)... 4 7.0 Reasons for ADE standards... 4 8.0 Government and Ministry IM/IT Standards... 5 9.0 Contravening these standards... 6
Revision History Ministry of Community, Sport, and Cultural Date Harvest Version Section Description Author 06-JUL-2004 1 All Final Draft DE 08-JUL-2004 3 All Proof-reading updates DE 22-JUL-2004 4 All Updated with feedback from DWS group DE 17-AUG-2004 5, 6 1.2, 1.3, 2.0 Updated with feedback from DWS group 02-JUN-2006 7,8,9 All Updates to Ministry naming DE 05 JUN 2006 10 All Document Rename FV 06 DEC 2006 11 2.0 Updates DE 06 SEP 2007 12 3 Updates, reflecting server upgrades FV 22 OCT 2008 13 2 Updates FV 14 May 2009 14 2,4 Updates FV 18 May 2011 15 All Updates for.net 4, C#, SQL Server RG 29 OCT 2012 16 2 Updates for Kentico BP 30 OCT 2012 17 All Updates for Kamloops BP 30 OCT 2012 18 All Ministry Name changes, updates to Oracle database version 30 NOV 2012 19 All Merging existing documentation into current and updating various sections 05 FEB 2013 20 2 Clarification on Kentico BP 9 JAN 2014 21 1,2,3,4,5,6 Updated Visual Studio and Kentico versions Updated SQL Server and Browser Versions Updated Server and Client s Updated SCM Standards Updated Unit Test requirements General Wording Changes 19 MAR 2015 22 2 Updates to.net 4.5.2 Fixed formatting on Kentico requirement DE KW BP BP BP
and Cultural Document Approval Signature Date Print Name Title
and Cultural 1.0 Overview 1.1 Outline This document will outline the for use by the Ministry of Community, Sport and Cultural (CSCD), the Skill Training (and Responsible for Labour) (JTST), and the Ministry of Investment and Trade (MIT), collectively referred to as the Ministry. 1.2 Detailed Description The will describe the acceptable tools, environments and methodologies for use by developers working for the Ministry. These standards apply to both internal and external developers working on new applications, as well as enhancements to existing applications. 1.3 Purpose This document is part of the Ministry s standards documentation project to clearly document all of the Ministry s development standards. The standards documentation will provide developers with information regarding the Ministry s environments and processes, to ensure that deliverables are compatible with the Ministry s support infrastructure. 1.4 In Scope The following items are in scope for this document: languages tools Database environments Server environments Desktop environments Software Configuration Management (SCM) The reasons for having an 1.5 Out of Scope The following items are out of scope for this document: Coding practices architecture standards Last Modified: 3/19/2015 1 of 6
and Cultural 2.0 Ministry Toolsets The following toolsets are standard for the Ministry: Visual Studio 2013 Using C# (for both client/server and ASP.NET applications) and the.net framework version 4.5.2 o Unit tests must be built using Visual Studio Unit Test Project o Load tests must be built using Visual Studio s Web Performance Tests AllFusion Harvest Change Manager 7.1 the Ministry s master System Configuration Management repository o s and projects under the umbrella of Labour applications use Team Foundation Server (TFS) 2010 Ministry s JIRA environment used for management of bugs and issues o s and projects under the umbrella of Labour applications use Team Foundation Server (TFS) 2010 Kentico the Ministry s Content Management System (CMS) o Version: Enterprise Marketing Solution 8.1 NOTE: Must use the Portal page templates Relational Database Management System (RDMS): o Oracle 11g R2 Oracle Designer 10g will be used as the main repository for data management (i.e. logical DB design, Physical DB design, server-side code, DDL, etc ) Oracle 11g R2 PL/SQL procedures/packages should be used for database server components.net database connections should use the Microsoft.NET Data Provider for Oracle. ODBC database connection should use the Microsoft ODBC for Oracle driver. NOTE: If Oracle specific data types are required, then the Oracle Data Provider for.net or Oracle ODBC driver may be used. Read-only ODBC connections MUST use the Oracle ODBC driver. o Microsoft SQL Server Standard Edition 2014 Visual Studio 2013 Database Project for code management Using SQL Server Data Tools (SSDT) Microsoft.NET Data Provider for SQL Server SQL Server Integration Services (SSIS) used for: large volume data loads importing data into existing data sets SQL Server Reporting Services for reports SAP Crystal Reports developer version for Visual Studio o For internal use only. External applications which provide reports through SAP Crystal Reports require extra licensing. o http://scn.sap.com/docs/doc-21990 An Office 2010 compatible format (Word 2007 SP1+) for letter/mail merges HTML 4.01 Web Browsers o For internal audience projects ONLY: Internet Explorer 8/9/10/11 o Public applications must be compatible with, in functionality and be reasonably similar in layout, the following browsers: Internet Explorer 8/9/10/11 Last Modified: 3/19/2015 2 of 6
and Cultural Safari 3+ Firefox 3.5+ Chrome 20+. NOTE: If you wish to use any additional tools, or 3 rd party controls, Ministry approval is required. 3.0 Server Our web servers are running the Windows 2008 R2 operating system with Internet Services 7.5 (IIS 7.5). The Oracle 11g client, Microsoft Data Access Components (MDAC) 2.6 Service Pack 1 (or higher), and Microsoft MVC 4 Framework, are installed on the Ministry web servers which host non-static sites. All Oracle database servers are running Sun Solaris 10; All Microsoft SQL Server database servers are running Windows Server Enterprise 2008 R2; see section 5.0 for further information. All Desktop Terminal Service (DTS) Servers are running Windows 2003 with Service Pack 1 and Citrix Presentation Server. For further information regarding the exact configuration of the DTS servers, please contact the Ministry IS Operations Manager. 4.0 Standard Operating 4.1 Standard Client s Ministry employees are issued a BC Government standard personal computer. Approximately 90% of users are issued Windows-based PC s The remainder of users are issued Apple hardware running OS X Windows Users BC Government standard-issue computers fall into a standard refresh cycle. The current refresh cycle is Upgrade 3.0 (U3.0): o Windows 7 o Internet Explorer 8/9/11 o Microsoft Office 2010 o 4GB RAM o 22 16:10 (1680x1050) LCD or 23 (1920x1080) LCD monitor Apple Users Apple products have only recently been approved for use within the BC Government desktop environment and as a result the standards aren t as clearly defined. The below specifications should be considered a reference-point only. o Mac OS X 10.6 (Snow Leopard) o Microsoft Office 2011 o Safari 5 4.2 Mobile Client s Within the ministry, a wide range of mobile devices are deployed with varying capabilities. These include: RIM Blackberry and Playbook Last Modified: 3/19/2015 3 of 6
and Cultural o Supports version 4.5.0 (Curve or newer) Apple iphone 4 and ipad o Supports version 4.2.1 (iphone 3G or newer) o icloud is disabled on ios 5 devices 5.0 Database The Ministry currently supports two database environments. The appropriate RDBMS will be determined during the RFP stage of a project: Oracle 11g R2 (version 11.2.0.4) Enterprise Edition is the preferred, and default, Ministry standard for relational databases. Oracle Standard Edition is available if required Where a business or technical reason requires, Microsoft SQL Server Standard Edition 2014 is the alternative RDBMS. s and projects under the umbrella of Labour applications use SQL Server 2014 as the preferred standard for relational databases. Oracle Standard Edition is available if required. 6.0 Software Configuration Management (SCM) All project deliverables are to be managed through the Ministry s SCM methodology, which is available from the Ministry Change Manager. All developers will be required to connect to the Ministry AllFusion Harvest SCM repository. Non-database related deliverables such as code and documentation, will be managed and versioned within the Ministry s AllFusion Harvest change management repository. Oracle database deliverables will be created and versioned within the Ministry Oracle Designer 10g SCM repository. SQL Server database deliverables will be created and versioned in Harvest using the toolsets described in Section 2. s and projects under the umbrella of Labour applications have the following exceptions to this standard: All developers will be required to connect to the Team Foundation Server 2010 repository. Non-database related deliverables such as code and documentation, will be managed and versioned within the Team Foundation Server 2010 repository. SQL Server database deliverables will be created and versioned in Team Foundation Server 2010 using the toolsets described in Section 2. 7.0 Reasons for ADE standards The following have been defined as the reasons for having a Ministry ADE standard: They maintain the current investments in application development skills. Consistent with the line of business applications being developed within CSCD and JTST. They ensure consistency within the Ministry s application ecosystem. s can be developed using.net (either client or web-based) without sacrificing maintainability or performance, when compared with other ADEs..NET programming resources are readily available from the private sector. Oracle Designer is the government standard for process and data modeling, as well as for database design. Using Oracle RDBMS allows for leveraging of existing internal and external DBA resources. Last Modified: 3/19/2015 4 of 6
and Cultural AllFusion Harvest has been selected as the best value system configuration management tool. It has a good level of support, government-use price discounts, and high level of flexibility and functionality. 8.0 Government and Ministry IM/IT Standards The Contractor will be required to adhere to the Province s applicable Management and Technology standards in carrying out the services under the Contract. A standard is a specific statement of the rules and constraints governing the naming, contents, and operations of software and hardware. There are two types of standards, Government and Ministry, applicable to the services under the Contract. The Contractor will be responsible for adhering to the policies and procedures outlined in Government and Ministry Standards. This includes the Ministry SCM Methodology Guide, Source Material Management Policies and Procedures, Web Standards, as well as Oracle Designer standards. This includes development and/or transfer of all code in the Ministry s Oracle Repository and the Ministry s source code repository. The Ministry will conduct Quality Assurance (QA) and design reviews of the deliverables, in accordance with the SDLC standards of the Ministry. Government and Ministry IM/IT standards may be updated at any time. The Contractor is required to keep up-to-date with the applicable standards in effect during delivery of the services under the Contract to ensure adherence to the most current one(s). Under certain and appropriate circumstances exemption from individual policies or standards may be granted by the OCIO or MCIO. Any requests for policy or standards exemption should be raised with the Ministry and will require approval in writing. Last Modified: 3/19/2015 5 of 6
and Cultural Government IM/IT Standards Applicable Government CIO (Chief Officer) standards and policies can be obtained from the following site: http://www.cio.gov.bc.ca/ Government information security policy: http://www.cio.gov.bc.ca/local/cio/standards/documents/standards/standards_manual.pdf Ministry IM/IT Standards Ministry standards (including this document) can be obtained from the following site: http://www.cscd.gov.bc.ca/isbstandards 9.0 Contravening these standards If a developer wishes to contravene these standards, a written proposal must be submitted to the Ministry System. Managerial sign-off must be attained prior to developing using non-standard technologies. Last Modified: 3/19/2015 6 of 6