Information Technology Policy
Information Technology PolicyApplication DevelopmentITP l@pa.gov1.Effective DateFebruary 22, 2017SupersedesNoneScheduled ReviewApril 2019PurposeEstablishes enterprise-wide standards and guidance for application developmentmethodologies.2.ScopeThis Information Technology Policy (ITP) applies to all departments, boards, commissions andcouncils under the Governor’s jurisdiction. Agencies not under the Governor’s jurisdiction arestrongly encouraged to follow this ITP.3.Objective 4.Provide a uniform approach to application development;Enhance and promote standardization;Reduce training costs and facilitate enhanced support services by having the samelanguages in use throughout state government;Achieve substantial savings in person/time support costs over a period of time by reducingthe number of languages supported; andDecrease time to production for applications.PolicyNew application development projects that require the use of an application developmentlanguage, integrated development environments (IDE), web development frameworks, andforms development tools are to use the current application development standards as definedin section 6 of this ITP.Major revisions to existing application development projects that are not using the currentstandards will be reviewed as part of the ITP-PRO001 IT Procurement Review Process todetermine if the investment warrants a change in standards at that time.Agencies implementing forms solutions are to incorporate usability testing as part ofapplication quality assurance. Usability testing is to assess the form solutions ability to: Provide good quality information to usersGather good quality information from usersReduce processing costsIncrease user satisfactionAgencies implementing forms solutions are to comply with ITP-ACC001 InformationTechnology Accessibility Policy.Agencies implementing form solutions are to assess the level of security and privacyassociated with the data in the form. Forms solutions requiring authentication and
ITP-SFT009 Application Developmentauthorization services are to comply with ITP-SEC014 Identity Protection and AccessManagement (IPAM) Architectural Standard.All IT projects related to application development are subject to review prior to inception forcompliance with this standard through the Procurement Review Process (See ITP-PRO001).5.StandardsCurrent Standards for Application Development Languages(These technologies meet the requirements of the current architecture and are recommended for use.)TechnologyPlatformsTechnology ClassificationC#Windows/.NETCurrentVisual rrentSwiftApple (iOS)CurrentObjective CApple (iOS)CurrentContain Standards for Application Development Languages(These technologies no longer meet the requirements of the current architecture and are notrecommended for use. They are to be phased out over time. No date has been set for theirdiscontinuance.)TechnologyC (all versions)AllPlatformsTechnology ClassificationContainC (all versions)AllContainPowerBuilder (all versions)AllContainCOBOL (all variants andversions)AllContainFortran (all variants andversions)AllContainEntire X (all versions)AllContainNatural (all versions)AllContainSpectrum (all versions)AllContainPL/IAllContainUnisys COBOL (all versions)AllContainOracle Forms (all versions)AllContainPage 2 of 6
ITP-SFT009 Application DevelopmentTechnologyPython (all versions)AllPlatformsTechnology ClassificationContainPERCobol (all versions)AllContainMicrosoft J# (all versions)AllContainEmerging / Research for Application Development Languages(Emerging technologies have the potential to become current standards. At the present time, they areto be used only in pilot or test environments where they can be evaluated. Use of these technologiesis restricted to a limited production mode, and requires approval of a waiver request. Researchtechnologies are less widely accepted and time will determine if they will become a standard.)TechnologyPlatformsTechnology ClassificationCurrent Standards for Integrated Development Environments(These technologies meet the requirements of the current architecture and are recommended for use.)TechnologyPlatformsTechnology ClassificationMicrosoft Visual Studio TeamServices (VSTS)Microsoft Visual Studio.NETAllCurrentWindowsCurrentMicrosoft Team FoundationServer (all Editions)IBM Rational ApplicationDeveloper for lCurrentXcodeApple (iOS)CurrentContain Standards for Integrated Development Environments(These technologies no longer meet the requirements of the current architecture and are notrecommended for use. They are to be phased out over time. No date has been set for logyClassification--Emerging / Research for Integrated Development Environments(Emerging technologies have the potential to become current standards. At the present time, they areto be used only in pilot or test environments where they can be evaluated. Use of these technologiesis restricted to a limited production mode, and requires approval of a waiver request. Researchtechnologies are less widely accepted and time will determine if they will become a standard.)Technology--Platforms--Technology Classification--Page 3 of 6
ITP-SFT009 Application DevelopmentCurrent Standards for Web Development Frameworks(These technologies meet the requirements of the current architecture and are recommended for use.)TechnologyPlatformsTechnology ClassificationMicrosoft .NET Framework4.5.2WindowsCurrentMicrosoft .NET Framework4.6 / 4.6.1 / 4.6.2WindowsCurrentJava EE (current vendorsupport version)AllCurrentJ2SE (current vendorsupport version)AllCurrentContain Standards for Web Development Frameworks(These technologies no longer meet the requirements of the current architecture and are notrecommended for use. They are to be phased out over time. No date has been set for theirdiscontinuance.)TechnologyJ2EE 7.0PlatformsAllTechnology ClassificationContainEmerging / Research for Web Development Frameworks(Emerging technologies have the potential to become current standards. At the present time, they areto be used only in pilot or test environments where they can be evaluated. Use of these technologiesis restricted to a limited production mode, and requires approval of a waiver request. Researchtechnologies are less widely accepted and time will determine if they will become a standard.)TechnologyMicrosoft .NET Framework4.7 / 4.7.1PlatformsWindowsTechnology ClassificationEmergingMicrosoft .NET Core 1.xWindowsEmergingMicrosoft .NET Core 2.0WindowsResearchJava EE 8AllEmergingJava EE 9AllResearchCurrent Standards for Forms Development Tools(These technologies meet the requirements of the current architecture and are recommended for use.)TechnologySAP Interactive Forms byAdobe1PlatformsAllTechnology ClassificationCurrentPage 4 of 6
ITP-SFT009 Application DevelopmentAdobe LiveCycle EnterpriseSuite1AllCurrentThis standard is for use within Integrated Enterprise SystemsContain Standards for Forms Development Tools(These technologies no longer meet the requirements of the current architecture and are notrecommended for use. They are to be phased out over time. No date has been set for theirdiscontinuance.)TechnologyPlatformsTechnology Classification------Emerging / Research for Forms Development Tools(Emerging technologies have the potential to become current standards. At the present time, they areto be used only in pilot or test environments where they can be evaluated. Use of these technologiesis restricted to a limited production mode, and requires approval of a waiver request. Researchtechnologies are less widely accepted and time will determine if they will become a standard.)Technology--6.Platforms--Technology Classification--ResponsibilitiesCommonwealth agencies must adhere to all policy and standards outlined in this ITP.7.Related ITPs/Other ReferencesDefinitions of associated terms of this policy are published on the Office of Administration’spublic portal: ommonwealth policies, including Executive Orders, Management Directives, and IT Policiesare published on the Office of Administration’s public .aspx Management Directive 205.34 Commonwealth of Pennsylvania Information TechnologyAcceptable Use Policy8. ITP-ACC001 IT Accessibility Policy ITP-SEC005 Commonwealth Application Certification and Accreditation ITP-SEC014 Identity Protection and Access Management (IPAM) Architectural Standard ITP-SFT000 Software Development Life Cycle (SDLC) Policy) ITP-SYM006 Desktop and Server Software Patching PolicyAuthorityExecutive Order 2016-06, Enterprise Information Technology GovernancePage 5 of 6
ITP-SFT009 Application Development9. Publication Version ControlIt is the user’s responsibility to ensure they have the latest version of this publication, whichappears on https://itcentral.pa.gov for Commonwealth personnel and on the Office ofAdministration public portal: http://www.oa.pa.gov/Policies/Pages/default.aspx. Questionsregarding this publication are to be directed to RA-ITCentral@pa.gov.10.Exemption from This PolicyIn the event an agency chooses to seek an exemption, for reasons such as the need tocomply with requirements for a federally mandated system, a request for waiver may besubmitted via the Commonwealth of PA Procurement and Architectural Review (COPPAR)process. Requests are to be entered into the COPPAR Tool located athttp://coppar.oa.pa.gov/. Agency CIO approval is required.This chart contains a history of this publication’s 27/2018Purpose of RevisionBase DocumentMoved to Software domain from Application, including ITP numberchangeMerged ITP-APP011 Application Development Languages, ITP-APP013Integrated Development Environments, ITP-APP015 Web DevelopmentFrameworks, ITP-APP021 Forms Development Tools into ITPAdded References sectionAdded Apple Swift language to App Dev Language Current StandardAdded Apple Xcode to IDE Current StandardRemoved Microsoft Visual Studio 2005 from Contain (Retire)Revised Web Development Framework standardsMoved ITP Definitions to Policy GlossaryPage 6 of 6
Microsoft Visual Studio.NET Windows Current Microsoft Team Foundation Server (all Editions) Windows Current IBM Rational Application Developer for WebSphere Software All Current Eclipse All Current Xcode Apple (iOS) Current Contain Standards for Integrated Development Environments (These technologies no longer meet the requirements of the .
Toys and Technology Policy Science Policy End of Day Policy Substitute Policy Sick Policy Co-Op Closure Policy Events Outside of Co-op Volunteer Responsibilities Cooperative Policy Age group Coordinator . 3 Lead & Co-Teaching Policy Co-Teaching Policy Class Assistant
address-family ipv6 unicast network . 2001:468::/48 route-policy EX1 redistribute connected route-policy EX2 neighbor 2001:db8::1 route-policy EXAMPLE1 in route-policy EXAMPLE2 out vrf FOO address-family ipv6 unicast import route-policy EXAMPLE1 export route-policy EXAMPLE2 Single-policy at attachment point Attach a policy at:
This Guideline presents a methodology for Information Technology (IT) security audits suitable for supporting the requirements of the Commonwealth of Virginia (COV) Information Technology Security Policy (ITRM Policy SEC500-02), the Information Technology Security Standard (ITRM Standard SEC501-01), and the Information Technology Security Audit
April 2018 Name of Policy Child protection and Safeguarding Policy, Education Scotland – Inclusion and Equality Description of Policy Policy Number Policy Status New Revision of Existing Policy Withdrawal of Policy Scottish Government Adopted Author Monica McGeever, Lead Officer Safeguarding Owner and business area Inclusion and Equality
Allocations and Development Management Plan Policy Listing Policy Ref Chapter / Policy Title PAGE NO. Chapter 1 Sustainable Communities and Development Principles 9 Policy SC 1 Presumption in Favour of Sustainable Development 12 Chapter 2 Environment 14 Policy EN1 Design Principles 15 Policy EN2 Amenity Protection 17 Policy EN3 Demolition in Conservation Areas 20 Policy EN4 Heritage Assets 21 .
Jun 06, 2019 · Policy Review Checklist Policy Template All policies should be in the current Policy Template. Yes, in the current Policy Template No, needs to be put into current Policy Template Check footer for policy tile and approval date Policy Title Expresses t
Subject: Proposed modifications to the Federal PKI Common Policy Framework Certificate Policy Date: April 13, 2021-----Title: Federal PKI Key Recovery Policy Consolidation into Common Policy Version and Date of Certificate Policy Requested to be changed: X.509 Certificate Policy for the Federal PKI Common Policy Framework Version 2.0, September .
INFORMATION TECHNOLOGY AND OUTSOURCING LIABILITY POLICY . Your Information Technology Liability Insurance Policy is issued on a CLAIMS MADE basis. Please note that this proposal form is being completed by the PROPOSER on behalf of all Insureds (as defined in the policy).
