Conformance 101. February FACE is a Trademark of The Open Group
|
|
- Lillian Mason
- 8 years ago
- Views:
Transcription
1 Conformance 101 February 2016 FACE is a Trademark of The Open Group
2 Purpose of this Presentation Overview of the FACE Conformance Program and Related Policies and Procedures Audience: New members of the FACE Consortium New participants in the Conformance Subcommittee Other interested parties 2
3 What is FACE Conformance? FACE Conformance is the assessment of a Software Item, known as a Unit of Conformance (UoC), to the applicable Conformance Requirements contained in the FACE Technical Standard Those Applicable Requirements are determined based on the segment and profile selected in the design of the particular UoC Verification of Conformance is conducted utilizing automated test tools and inspection of design and test documents The specific requirements, method of verification, and associated verification evidence is detailed in the Conformance Verification Matrix (CVM) 3
4 What can be Certified as FACE Conformant? Certification is for Units of Conformance (UoC) or UoC Packages Defined on next slide There is No compliance ; things are either certified conformant or not. No FACE certification for entire systems Systems can be comprised completely of Certified UoCs or a mix of Certified UoCs and other software No FACE certification for independent libraries, runtimes, frameworks These can be included in a certification of a larger set 4
5 What is a Unit of Conformance (UoC)? A Unit of Portability (UoP) is Items that fit completely within one of the FACE Architecture portable segments Platform Specific Segment Transport Services Segment Portable Component Segment A Unit of Conformance (UoC) is Items that fit completely within one of the five FACE Architecture segments Platform Specific Segment (also a UoP) Transport Services Segment (also a UoP) Portable Component Segment Operating System Segment (also a UoP) (is not a UoP) I/O Services (is not a UoP) 5
6 What is a Unit of Conformance Package? A Unit of Conformance (UoC) Package is A Collection of UoCs meeting the FACE Standard definition of packages Same Partition Allowable Segments 6
7 What are UoC variants? UoC Variants are versions of a UoC generated to a specific set of functionality and target environment from the same UoC source code. UoC Variants which conform to the Technical Standard may be certified and listed together on a single Conformance Certificate. If the Software Supplier is submitting UoC variants, conformance evidence must detail the conformant variants and their differences. 7
8 Conformance Processes FACE Verification is the act of determining the conformance of an implementation to specification requirements. Verification is handled through an entity known as a Verification Authority (VA), a technical expert on the FACE Technical Standard and Verification process and approved by the FACE Consortium Steering Committee FACE Certification is the process of applying for a FACE Conformance Certificate once verification has successfully been completed. Certification is processed through the FACE Certification Authority (CA) FACE Registration is the process of listing FACE Certified UoCs in a public listing of FACE Certified UoCs known as the FACE Registry. The FACE Registry is accessed from the FACE Landing Page 8
9 Conformance Program and Processes Software Supplier Initiate Verification Initiate Certification Initiate Registration FACE Verification FACE Certification FACE Registration FACE Verification Authority (VA) FACE Certification Authority (CA) FACE Library Administrator (LA) 9
10 Driving Factors Software Supplier is in control Software Supplier initiates the steps No listing of UoCs in process Software Supplier provides information for the Registry (the public listing) FACE Registry does not contain a way to download; Software Supplier must be contacted Software Supplier IP is protected 10
11 Driving Factors No Functional or Performance Testing Interfaces are tested Other Verification Evidence is inspected (evaluated) Functional Testing is assumed as part of other development processes and is not required for FACE Conformance 11
12 Driving Factors Certification is for Portable Software structure The source code and design are certified conformant to the FACE Technical Standard One instance of the object code, compiled for the test environment, is tested for conformance to the FACE APIs and data model Recompiling to a different target does not cause a loss of FACE Certification 12
13 Roles Software Supplier: The Software Supplier is anyone providing software (UoC) to be certified. This may include the original software developer, an integrator, or another entity wishing to certify software developed from another party. 13 FACE Verification Authority: A FACE Verification Authority (VA) is one of several organizations approved by the FACE Consortium to evaluate software against the FACE Technical Standard. The VA is an expert on the FACE technical standard and verification process. The VA conducts or witnesses conduct of the For-the-Record Test, utilizing an approved Conformance Test Tool, and inspects the Verification Evidence.
14 Roles FACE Certification Authority: The FACE Certification Authority (CA) is the singular organization approved by the FACE Consortium that can provide a FACE Conformance Certificate FACE Library Administrator: The FACE Library Administrator manages a listing of FACE Certified UoCs known as the FACE Registry FACE Trademark Licensor: The FACE Trademark Licensor issues the FACE Conformance Certification Trademark for Certified Units of Conformance and Certified Unit of Conformance Packages 14
15 Conformance OV-2 Cer+fica+on Package So9ware Supplier Conformance Cer+ficate Conformance Authori+es Cer+fica+on Authority (CA) Registra+on Shared Data Model Library Administrator Verifica+on Results Package SW Verifica+on Package ITAR SDM Snapshot Registry Verifica+on Authority (VA) Consor+um Documents Tools Public SDM Snapshot Reference Repository Verifica+on Reten+on Repository Verifica+on Results Package Library Repository Requirements Library Repository Requirements and Procedures Documents Consor+um Documents Cer+ficate ID Cer+fica+on Reten+on Repository Library Repository Requirements 15
16 Key FACE References Technical Standard Requirements for the FACE Architecture Conformance Verification Matrix Guidance and Verification Methods Conformance Policy Policy for certification of UoCs Conformance Certification Guide Guidance on the Policy and Program 16
17 Software Supplier Provides The Unit of Conformance (UoC) for Verification Object code, supporting files, and verification evidence Supplied to the Verification Authority (VA) only All UoCs included in a UoC Package Conformance Statement Identification of the Unit of Conformance (UoC) How the Unit of Conformance (UoC) meets FACE Technical Standard requirements Registry Entry Description of the Unit of Conformance (UoC), associated conformant UoC variants, and UoC Package as applicable Contact Information for Obtaining the Certifed Unit of Conformance (UoC) or Certified UoC Package 17
18 VA Provides Verification Statement Indication that the UoC Passed Verification For each UoC comprising a UoC Package, as well for the UoC Package itself Failed Verification is communicated to the Software Supplier specifying what and why failure occurred 18
19 CA Provides Conformance Certificate Indication that the Unit of Conformance (UoC) Passed Certification For each UoC comprising a UoC Package, as well for the UoC Package itself Failed Certification is communicated to the Software Supplier with sufficient detail for the problems to be resolved 19
20 FACE Conformance Program Steps and Processes Software Supplier Conduct Preparation Initiate Verification Initiate Certification Initiate Registration FACE Verification FACE Certification FACE Registration FACE Verification Authority (VA) FACE Certification Authority (CA) FACE Library Administrator (LA) 20
21 Conformance Preparation FACE Conformance Tab FACE Landing Page FACE Reference Repository Software Supplier Supplier Obtains References and Tools FACE Technical Standard Reference Implementation Guide (RIG) Automated Tools, SDK, ITK Conformance Certification Users Guide Conformance Policy Verification Matrix Matrix Users Guide (MUG) Conformance Test Suite 21
22 FACE Library Overview FACE Library Infrastructure Library Administration FACE Consoritum information FACE Events Procurements Main Landing Page Manages conformance and registration workflow VA CoP Library Portal Listing of FACE Certified UoCs Searchable Metadata Registry PR/CR System Reference Repository Verification Retention Repositories Certification Retention Repository Product Repositories VA Site CA Site Vendors Site Problem reports and change requests for Consortium artifacts and tools Dev/Test Tools Business Guide Technical Standard Contract Guide Artifacts submitted for FACE conformance verification / certification Certified FACE Conformant Software and associated artifacts 22
23 Conformance Preparation Identify FACE Criteria Number of UoCs for each: o FACE Architecture Segment o Profile (General, Safety, Safety Extended or Security) o Supporting Libraries for UoC o Test Environment 23
24 Conformance Preparation Supplier provides Verification Evidence o A trace of the FACE requirements to specific documents supporting the requirements o Required for all items in the Tech Standard identified as needing inspection in the Conformance Verification Matrix (CVM) including applicable conditional requirements Verification Needed (Y or N) FACE Segment Technical Standard for the FACE Reference Architecture Edition 1.0 Verification Method Conformance Artifacts (DID or equivalent) N PSS Segment Requirements PSSS 9. All communication with the IOSS shall go through the I/O Services Interface. Test Test Suite SW Supplier Artifact Cross- Reference Verification Notes Conditional Reqs Y Y PSSS 10. Messages communicated through the I/O Services Interface shall be in the format defined in Section D.11. Inspection SDD Y PSSS 11. All components of the PSSS shall use the interface defined in Section 3.11, Section 3.12, or Section 3.13 to access the functions provided by the OSS. Test Inspection Test Suite SAD SDD Inspection is only of Java frameworks or Ada run-times. 24
25 Conformance Preparation Supplier Selects a Verification Authority o List of Approved VAs from the Landing Page o Meets supplier needs o Not limited to Internal Verification o Willing to perform verification for the UoC s applicable FACE Architecture segment, e.g., Operating System 25
26 Conformance Preparation Software Supplier FACE Trademark Licensor FACE Verification Authority (VA) FACE Certification Authority (CA) Supplier Establishes Legal Agreements Conformance Certification Trademark License Agreement with TM Licensor Verification Agreement with Selected VA Certification Agreement with CA 26
27 Conformance Verification Process Software Supplier Initiate Verification Select & Establish Contractual Relationship with VA FACE Verification Authority (VA) Develop SW Verification Package o Verification Agreement o Verification Evidence o Conformance Statement o SW Product Set 27
28 Conformance Verification Process SW Verification Package o Verification Agreement - defines the conformance verification services to be provided by the VA and acceptance by the SW Supplier to provide the required verification evidence and SW Product Set o Verification Evidence - supporting verification documentation submitted by the SW Supplier to provide evidence of FACE Conformance to the applicable conformance requirements of the Technical Standard that are not directly tested by the Test Suite. The verification evidence is organized to correlate with the specific conformance requirements and verification approach contained in the applicable segment of the Conformance Verification Matrix 28
29 Conformance Verification Process SW Verification Package (cont) 29 o Conformance Statement SW Supplier s response to a standard questionnaire, tailored to the appropriate Segment of the Technical Standard, structured to obtain precise identification of the software product and conformance evidence. It includes SW product description documentation to uniquely identify and configuration manage the SW product through the conformance process. The Conformance Statement identifies the specific edition of the Technical Standard against which the SW product is being certified, the applicable set of conformance requirements, the corresponding Conformance Verification Matrix version, and the version of Conformance Test Suite used for verification. If the Software Supplier is submitting UoC variants, a Conformance Statement must detail the conformant variants and their differences.
30 Conformance Verification Process SW Verification Package (cont) o SW Product Set Includes object code representing all source code compiled for the test environment, appropriate data model files, associated information for set-up with interfacing segments, and minimum computer operating environment requirements If verification will include UoC Variants, the Software Product Set must include multiple versions of the object code. The versions of object code files must be representative of all UoC Variants for which verification is sought. The Software Product Set must include an analysis of this coverage. 30
31 Conformance Verification Process Software Supplier Initiate Verification Inspect SW Verification Package FACE Verification FACE Verification Authority (VA) Evaluate the Verification Evidence Conduct/Witness FTR test using Approved Conformance Test Suite Issue Verification Statement Archive Data 31
32 Conduct/Witness the FTR Test Uses the Applicable Approved FACE Conformance Test Suite Witness means watching execution of the FTR test not inspection of test results or test report Evaluates the Object Code through Linking (not executing) the product code Evaluates the Data Model for Conformance (IDL in 1.0) Does no functional testing; only ensures the appropriate FACE APIs are present and correct 32
33 Evaluate the Verification Evidence Inspect the trace from Technical Standard to specific locations in Designs, Requirements, Test Procedures, Test Reports, etc. Ensures the product meets requirements not covered by the Conformance Test Suite (FTR Test) Verification Needed (Y or N) FACE Segment Technical Standard for the FACE Reference Architecture Edition 1.0 Verification Method Conformance Artifacts (DID or equivalent) N PSS Segment Requirements PSSS 9. All communication with the IOSS shall go through the I/O Services Interface. Test Test Suite SW Supplier Artifact Cross- Reference Verification Notes Conditional Reqs Y Y PSSS 10. Messages communicated through the I/O Services Interface shall be in the format defined in Section D.11. Inspection SDD Y PSSS 11. All components of the PSSS shall use the interface defined in Section 3.11, Section 3.12, or Section 3.13 to access the functions provided by the OSS. Test Inspection Test Suite SAD SDD Inspection is only of Java frameworks or Ada run-times. 33
34 Conformance Verification Process Software Supplier Initiate Verification FACE Verification Verification Results Pkg & SW Verification Pkg Verification Retention Repository FACE Verification Authority (VA) 34
35 Conformance Certification Process Software Supplier Initiate Certification Establish Contractual Relationship with CA Verification Results Package FACE Verification Authority (VA) FACE Certification Authority (CA) Submit Legal Agreements o Certification Agreement o Trademark License Agreement CA Requests Verification Result Package from VA 35
36 Conformance Certification Process Software Supplier Initiate Certification FACE Certification FACE Certification Authority (CA) Ensure legal agreements are in place (Certification Agreement and TMLA) Review Conformance and Verification Statements for completeness and correctness 36
37 Conformance Certification Process Software Supplier Initiate Certification FACE Certification Conformance Certificate, Conformance Statement, Verification Statement, TMLA Certification Retention Repository FACE Certification Authority (CA) 37
38 FACE Registration Process Software Supplier Initiate Registration Submit Product Description & Conformance Certificate ID to Library Administrator FACE Library Administrator (LA) 38
39 FACE Registration Process Software Supplier Initiate Registration Request & Receive conformation of Conformance Certificate from CA Populates FACE Registry with Product Description & Conformance Certificate Conformance Certificate ID FACE Certification Authority (CA) FACE Registration FACE Library Administrator (LA) 39
40 Conformance Program and Processes Software Supplier Initiate Verification Initiate Certification Initiate Registration FACE Verification FACE Certification FACE Registration FACE Verification Authority (VA) FACE Certification Authority (CA) FACE Library Administrator (LA) 40
41 Conformance Packages Verification Agreement Verification Evidence SW Product Set Conformance Statement Verification Statement Certification Agreement SW Verification Package X X X Verification Results Package Verification Retention Repository X X X Certification Package Certification Retention Repository X X X X X X X X X TMLA X X Conformance Certificate X X X 41
42 Other Conformance Topics Recertification/Modification of a Certified UoC PR Process Appeals Auditing 42
43 Recertification/Modification of a Certified UoC Section Type of Modification Verification Requirement Certification Requirement Conformance maintenance release Software modification Delta-verification Delta-verification Certification information update New certification release Renamed UoC None Certification information update Modification of FACE Registry information Other modifications None As determined by the VA Certification information update As determined by the CA 43
44 Recertification/Modification of a Certified UoC Conformance Maintenance Releases are the result of modifications made to the UoC because of conformance-related issues that arise following FACE Conformance Certification; for example, conformance-related problems that arise during systemlevel test and evaluation or later during the porting of the UoC. Regardless of whether the problem was due to an improper implementation of a Conformance Requirement or a problem with the Technical Standard, the problem solution required a modification to the UoC. The Software Supplier will provide an impact assessment report resulting from the modification to the Software Verification Package contents and resubmit the Software Verification Package with the changes incorporated. The VA will conduct an assessment on the report and updated submittal, determine whether further information or testing is required, evaluate any additional data or test results, and upon satisfactory results issue a delta-verification assessment report to the CA. The CA will re-issue the FACE Conformance Certificate. 44
45 Recertification/Modification of a Certified UoC Software Modification Releases are the result of any software changes made to the UoC not associated with a conformance maintenance release. The requirement for change could be due to Software Supplier market assessment or customer demand. For these changes, the Software Supplier must submit an impact report on the change(s) and submit a new Software Verification Package. The VA will determine the level of verification required. Upon successful conformance verification, the process will follow the certification process for new UoCs. 45
46 Recertification/Modification of a Certified UoC Renamed UoC If a FACE Certified UoC is to be renamed, with no change to the UoC, the Software Supplier may request such changes at any time by contacting the CA. The Software Supplier will be required to affirm to the CA that there has been no change other than name. Renaming a UoC will additionally require an update of FACE Registry information. Modification of FACE Registry Information If the Software Supplier wishes to modify information in the FACE Registry that has no impact on the conformance of the FACE Certified UoC such as contacts, UoC descriptive text, or other metadata the Software Supplier may request such changes at any time by contacting the LA. 46
47 Recertification/Modification of a Certified UoC Other Modifications Except where specifically stated in this document, any other variant of a FACE Certified UoC which is deemed by the CA to have a material effect on the conformance of the UoC to the Technical Standard constitutes a new UoC, which will be subject to the full conformance verification and certification processes. 47
48 Problem Reporting (PR) Process A Problem Report (PR) may be submitted against any problem encountered with the Technical Standard, FACE Conformance Test Suite(s), or conformance verification and certification processes that inhibit or will inhibit the conformance effort. The PR submitter will utilize the Consortium-wide Problem Report/Change Request (PR/ CR) process. 48
49 Problem Reporting (PR) Process The types of problems that may be reported include: Errors, conflicts, or ambiguities in the Technical Standard. Errors in the test suite(s) used to assess conformance with the specifications; specifically, in the FACE Conformance Test Suite(s), or other test suites referenced by the FACE Conformance Program (if any). Errors, conflicts, or ambiguities in the set-up requirements of the FACE Conformance Test Suite(s) may also be addressed through PRs. Errors, conflicts, or ambiguities in the conformance verification and certification processes; specifically, those related to the Registration process, legal agreements, and completion of the Software Verification Package (set of artifacts to support conformance verification). 49
50 Problem Reporting (PR) Process A submitter may file PRs to address issues that arise for any of these items. The identity of the submitter will be protected throughout this process. The PR is used specifically for the types of errors listed above which are inhibiting the conformance effort. For general questions on the conformance verification and certification processes, running the test suites, or other problems not covered above, the CA can provide information on obtaining further assistance. Issues not resolved through this assistance may be followed-up with a PR. 50
51 Problem Reporting and Approved Corrections Flow Submitter PR/CR Administrator Steering Committee FTG FACE CCB Product CCB Entry INITIATED INITIATED Triage More Information RETURNED REJECTED Provide Feedback Confirm Rejection REJECTED RECOMMEND REJECT Proposal PROPOSED Yes Satisfied No Rejected Approve Correction Schedule Proceed with New Information Publish Correction File Appeal No Satisfied Yes Proceed With Correction 51
52 Appeals Occasions that may give rise to an appeal include, but are not limited to, the following: The Software Supplier disagrees with the resolution of a Problem Report (PR). The Software Supplier disagrees with the CA s grounds for denying the award of certification or the removal of certification. The Software Supplier of a FACE Certified UoC disagrees with a formal notification from the CA of the need to rectify a nonconformance. The incidence of a UoC having been found to be nonconformant will be handled on a case-by-case basis under Conformance Maintenance Release policies. Appeal requests will be made to the Steering Committee in writing within 90 calendar days of issue occasion. 52
53 Appeals Submitter Steering Committee Request Appeal Appeal Granted Yes Appeal Accepted Changes Made No Appeal Denied No Changes Made 53
54 Audits The primary purpose of the audit is to ensure the overall integrity of the FACE Conformance Program and the software contained in FACE Product Repositories. An audit may be conducted on a Software Supplier, a VA, or the CA. Audits will be conducted or directed by the Steering Committee (SC) when deemed necessary. The SC designates an auditor to perform an audit. The auditor may request the applicable information from any of the following entities in order to conduct the audit: Software Supplier Verification Package and configurationmanaged records VA verification records CA certification records 54
55 55 Audits
Library Requirements
The Open Group Future Airborne Capability Environment (FACE ) Library Requirements Version 2.2 April 2015 Prepared by The Open Group FACE Consortium Business Working Group Library Subcommittee AMRDEC PR1201
More informationTOGAF Certification for People Training Course Accreditation Policy
TOGAF Certification for People Training Course Accreditation Policy January 2009 Version 1.0 Copyright, 2009, The Open Group All rights reserved. No part of this publication may be reproduced, stored in
More informationChapter 13 Configuration Management
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 13 Configuration Management Outline of the Lecture Purpose of Software Configuration Management (SCM)! Motivation: Why software
More informationConfiguration & Build Management
Object-Oriented Software Engineering Using UML, Patterns, and Java Configuration & Build Management Outline of the Lecture Purpose of Software Configuration Management (SCM) Some Terminology Software Configuration
More informationSoftware Configuration Management. Addendum zu Kapitel 13
Software Configuration Management Addendum zu Kapitel 13 Outline Purpose of Software Configuration Management (SCM) Motivation: Why software configuration management? Definition: What is software configuration
More informationSoftware Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201
PURCHASE ORDER ATTACHMENT Q-201A Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201 1. A qualified employee shall be selected by the Software Quality Manager
More informationChapter 13 Configuration Management
Chapter 13 Configuration Management Using UML, Patterns, and Java Object-Oriented Software Engineering Outline of the Lecture Purpose of Software Configuration Management (SCM)! Motivation: Why software
More informationNFC Forum Certification Policy
NFC Forum Certification Policy Rules and Procedures for the Certification Program NFC Forum TM Version 1.4 NFCForum-Certification-Program-Policy 2014-06-11 EFFECTIVE 1 JANUARY 2015 RESTRICTIONS ON USE
More informationPage 1. Outline of the Lecture. What is Software Configuration Management? Why Software Configuration Management?
Books: Software Configuration Management 1. B. Bruegge and A. H. Dutoit, Object-Oriented Software Engineering: Using UML, Patterns, and Java (Chapter 13) Outline of the Lecture Purpose of Software Configuration
More informationMNLARS Project Audit Checklist
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
More informationCHAPTER 7 Software Configuration Management
CHAPTER 7 Software Configuration Management ACRONYMS CCB CM FCA MTBF PCA SCCB SCI SCM SCMP SCR SCSA SEI/CMMI SQA SRS USNRC INTRODUCTION Configuration Control Board Configuration Management Functional Configuration
More informationNSI Policy Supplement for XML Retail Accounting Reports Certification/Verification. May 7, 2007 Revision 1.1
NSI Policy Supplement for XML Retail Accounting Reports Certification/Verification May 7, 2007 Revision 1.1 Table of Contents 1. Overview... 3 1.1 Introduction... 3 1.2 Scope... 3 1.2.1 Scope of certification
More informationAdobe Digital Publishing Security FAQ
Adobe Digital Publishing Suite Security FAQ Adobe Digital Publishing Security FAQ Table of contents DPS Security Overview Network Service Topology Folio ProducerService Network Diagram Fulfillment Server
More informationThe Benefits of Utilizing a Repository Manager
Sonatype Nexus TM Professional Whitepaper The Benefits of Utilizing a Repository Manager An Introduction to Sonatype Nexus TM Professional SONATYPE www.sonatype.com sales@sonatype.com +1 301-684-8080 12501
More informationAudit Management Software Solution
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 Scope of Work I. Scope of Solicitation II. Instructions to Offerors III. Scope of
More informationThe Open Group COE Platform Certification Program. Security Testing Procedures
The Open Group COE Platform Certification Program Security Testing Procedures Applicable to Posix and Linux Application Platform Compliance February 16, 2004 Revision 1.1 Table of Contents 1. Overview...
More informationTutorial: BlackBerry Object API Application Development. Sybase Unwired Platform 2.2 SP04
Tutorial: BlackBerry Object API Application Development Sybase Unwired Platform 2.2 SP04 DOCUMENT ID: DC01214-01-0224-01 LAST REVISED: May 2013 Copyright 2013 by Sybase, Inc. All rights reserved. This
More informationProject Management Guidelines
Project Management Guidelines 1. INTRODUCTION. This Appendix (Project Management Guidelines) sets forth the detailed Project Management Guidelines. 2. PROJECT MANAGEMENT PLAN POLICY AND GUIDELINES OVERVIEW.
More informationKofax Export Connector 8.3.0 for Microsoft SharePoint
Kofax Export Connector 8.3.0 for Microsoft SharePoint Administrator's Guide 2013-02-27 2013 Kofax, Inc., 15211 Laguna Canyon Road, Irvine, California 92618, U.S.A. All rights reserved. Use is subject to
More informationHP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Processes and Best Practices Guide
HP Service Manager Software Version: 9.34 For the supported Windows and UNIX operating systems Processes and Best Practices Guide Document Release Date: July 2014 Software Release Date: July 2014 Legal
More informationEnterprise Service Provisioning
Enterprise Service Provisioning ProPath Office of Information and Technology Table of Contents Enterprise Service Provisioning Process Map... 1 Process: Enterprise Service Provisioning... 2 Enterprise
More informationSoftware Configuration Management Plan
For Database Applications Document ID: Version: 2.0c Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 22 Copyright 2000-2005 Digital Publications LLC.
More informationMinnesota Health Insurance Exchange (MNHIX)
Minnesota Health Insurance Exchange (MNHIX) 1.2 Plan September 21st, 2012 Version: FINAL v.1.0 11/9/2012 2:58 PM Page 1 of 87 T A B L E O F C O N T E N T S 1 Introduction to the Plan... 12 2 Integration
More informationCA Service Desk Manager - Mobile Enabler 2.0
This Document is aimed at providing information about the (CA SDM) Mobile Enabler and mobile capabilities that is typically not available in the product documentation. This is a living document and will
More informationLeverage Your Procurement Workflows in Release 12. Cal Kondratiuk O2Works, LLC
Leverage Your Procurement Workflows in Release 12 Cal Kondratiuk O2Works, LLC Learning Objectives After this presentation, you will be able to: Understand workflows in Advanced Procurement Analyze and
More informationSelf Testing and Product Qualification Processes
GlobalPlatform Self Testing and Product Qualification Processes Version 1.2.1 Public Release May 2013 Document Reference: GPC_PRO_042 Recipients of this document are invited to submit, with their comments,
More informationCopyright 2014 Carnegie Mellon University The Cyber Resilience Review is based on the Cyber Resilience Evaluation Method and the CERT Resilience
Copyright 2014 Carnegie Mellon University The Cyber Resilience Review is based on the Cyber Resilience Evaluation Method and the CERT Resilience Management Model (CERT-RMM), both developed at Carnegie
More informationSoftware and Hardware Configuration Management
DOWNLOADED AND/OR HARD COPY UNCONTROLLED Verify that this is the correct version before use. AUTHORITY DATE Jeffrey Northey (original signature on file) IMS Manager 07/09/2014 Doug Dorrer (original signature
More informationThe Requirements Compliance Matrix columns are defined as follows:
1 DETAILED REQUIREMENTS AND REQUIREMENTS COMPLIANCE The following s Compliance Matrices present the detailed requirements for the P&I System. Completion of all matrices is required; proposals submitted
More informationThe Fulfillment of AS 9100 Rev C Requirements by EnterpriseIQ
The Fulfillment of AS 9100 Rev C Requirements by EnterpriseIQ Manufacturers have worked to meet the stringent requirements of AS9100 for decades; the recent introduction of Revision C has further expanded
More informationIBM Endpoint Manager Version 9.1. Patch Management for Red Hat Enterprise Linux User's Guide
IBM Endpoint Manager Version 9.1 Patch Management for Red Hat Enterprise Linux User's Guide IBM Endpoint Manager Version 9.1 Patch Management for Red Hat Enterprise Linux User's Guide Note Before using
More informationIntegrating ConnectWise Service Desk Ticketing with the Cisco OnPlus Portal
Integrating ConnectWise Service Desk Ticketing with the Cisco OnPlus Portal This Application Note explains how to configure ConnectWise PSA (Professional Service Automation) application settings and Cisco
More information074-8432-552 Page 1 of 7 Effective Date: 12/18/03 Software Supplier Process Requirements
Page 1 of 7 Software Supplier Process Requirements 1.0 QUALITY SYSTEM FRAMEWORK 1.1 QUALITY POLICY The Seller shall document and implement a quality program in the form of Quality manual or detailed Quality
More informationISO 9001: 2008 Construction Quality Management System Sample - Selected pages (not a complete plan)
ISO 9001: 2008 Construction Quality Management System Sample - Selected pages (not a complete plan) Part 1: Project-Specific Quality Plan Part 2: Company Quality Manual Part 3: Submittal Forms Part 4:
More informationCONTENTS. Preface. Acknowledgements. 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI"? 2 What the CMMI* is Not 3 What are Standards?
Preface Acknowledgements xi xiii 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI"? 2 What the CMMI* is Not 3 What are Standards? 3 2. Summaryof CMMI-SW 5 The CMM*-SW 5 CMMI--SW Continuous
More informationSIEBEL PUBLIC SECTOR 8.2.2
SIEBEL PUBLIC SECTOR 8.2.2 CAPABILITIES Comprehensive case management and policy management centered on the citizen Facilitates complex eligibility determinations and change of circumstance Automates and
More informationIntland s Medical Template
Intland s Medical Template Traceability Browser Risk Management & FMEA Medical Wiki Supports compliance with IEC 62304, FDA Title 21 CFR Part 11, ISO 14971, IEC 60601 and more INTLAND codebeamer ALM is
More informationMOVING THE CLINICAL ANALYTICAL ENVIRONMENT INTO THE CLOUD
MOVING THE CLINICAL ANALYTICAL ENVIRONMENT INTO THE CLOUD STIJN ROGIERS, SENIOR INDUSTRY CONSULTANT, LIFE SCIENCES/HEALTH CARE (EMEA/AP) SANDEEP JUNEJA CONSULTING MANAGER (SSOD) AGENDA Move towards cloud
More informationNorth American Electric Reliability Corporation. Compliance Monitoring and Enforcement Program. December 19, 2008
116-390 Village Boulevard Princeton, New Jersey 08540-5721 North American Electric Reliability Corporation Compliance Monitoring and Enforcement Program December 19, 2008 APPENDIX 4C TO THE RULES OF PROCEDURE
More informationRequirements Elaboration
Requirements Elaboration ProPath Office of Information and Technology Table of Contents Requirements Elaboration Process Maps... 1 Process: Requirements Elaboration... 4 Requirements Elaboration and Goals...
More informationIntegrity 10. Curriculum Guide
Integrity 10 Curriculum Guide Live Classroom Curriculum Guide Integrity 10 Workflows and Documents Administration Training Integrity 10 SCM Administration Training Integrity 10 SCM Basic User Training
More informationITSM Process Description
ITSM Process Description Office of Information Technology Incident Management 1 Table of Contents Table of Contents 1. Introduction 2. Incident Management Goals, Objectives, CSFs and KPIs 3. Incident Management
More informationSECTION 3: TMHP ELECTRONIC DATA INTERCHANGE (EDI) TEXAS MEDICAID PROVIDER PROCEDURES MANUAL: VOL. 1
SECTION 3: TMHP ELECTRONIC DATA INTERCHANGE (EDI) TEXAS MEDICAID PROVIDER PROCEDURES MANUAL: VOL. 1 AUGUST 2015 TEXAS MEDICAID PROVIDER PROCEDURES MANUAL: VOL. 1 AUGUST 2015 SECTION 3: TMHP ELECTRONIC
More informationTeam Collaboration, Version Management, Audit Trails
Team Collaboration, Version Management, Audit Trails Best Practices for Successful Project Delivery with VoiceObjects May 2008 www.voiceobjects.com 2 Team Collaboration, Version Management, Audit Trails
More informationCloud Security Alliance and Standards. Jim Reavis Executive Director March 2012
Cloud Security Alliance and Standards Jim Reavis Executive Director March 2012 About the CSA Global, not for profit, 501(c)6 organization Over 32,000 individual members, 120 corporate members, 60 chapters
More informationSoftware Contract and Compliance Review
Audit Report Report Number IT-AR-15-009 September 18, 2015 Software Contract and Compliance Review The software contract did not comply with all applicable standards and management did not ensure the supplier
More informationGeneral Conditions for the Certification of Management System
General Conditions for the Certification of Management System The National Standards Authority of Ireland, inc. (hereinafter referred to as NSAI) located at 20 Trafalgar Square Nashua, NH 03063 provides
More informationORACLE PROCESS MANUFACTURING QUALITY MANAGEMENT
ORACLE PROCESS MANUFACTURING QUALITY MANAGEMENT KEY FEATURES Automated stability study management Lot expiration handling and retesting Potency or variability management Quality holds during receiving
More informationCamar Aircraft Products Co. QUALITY MANUAL Revision D
QUALITY MANUAL Revision D Gujll'y Manual Introduction The purpose of this manual is to describe the Quality Assurance Program implemented by Camar Aircraft Products Co. (hereafter referred to as C.A.P.C.)
More informationContent Marketing Integration Workbook
Content Marketing Integration Workbook 730 Yale Avenue Swarthmore, PA 19081 www.raabassociatesinc.com info@raabassociatesinc.com Introduction Like the Molière character who is delighted to learn he has
More informationAppendix 2-A. Application and System Development Requirements
Appendix 2-A. Application and System Development Requirements Introduction AHRQ has set up a Distributed Systems Engineering Lab (DSEL) to support all internal development efforts and provide a facility
More informationVistaSG Help Desk Training Manual
VistaSG Help Desk Training Manual Providing Paperless Solutions to the Justice Community VistaSG Copyright 2010 vistasg.com vistasg Copyright 2010 VistaSG Software Inc. All rights reserved. You may not
More informationOptimizing Supplier Performance:
Optimizing Supplier Performance: Essential Factors to Consider When Implementing a Supplier Performance Management System by Bevin Lyon & Paul Leavoy CONTENTS Introduction..........................................................................................................
More informationProject QA and Collaboration Plan for <project name>
Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document. This template can be used at it is, or to complete and
More informationSoftware Quality Assurance Plan
For Database Applications Document ID: Version: 2.1a Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 54 Copyright 2000-2006 Digital Publications LLC.
More informationNexus Professional Whitepaper. Repository Management: Stages of Adoption
Sonatype Nexus Professional Whitepaper Repository Management: Stages of Adoption Adopting Repository Management Best Practices SONATYPE www.sonatype.com sales@sonatype.com +1 301-684-8080 12501 Prosperity
More informationSOFTWARE QUALITY MANAGEMENT THROUGH IMPLEMENTATION OF SOFTWARE STANDARDS
4 th Int. Conf. CiiT, Molika, Dec.11-14, 2003 61 SOFTWARE QUALITY MANAGEMENT THROUGH IMPLEMENTATION OF SOFTWARE STANDARDS S. Grceva, Z. Zdravev Faculty for Education Goce Delcev, University of Sts. Cyril
More informationInstalling and Administering VMware vsphere Update Manager
Installing and Administering VMware vsphere Update Manager Update 1 vsphere Update Manager 5.1 This document supports the version of each product listed and supports all subsequent versions until the document
More informationTraining Management System Requirements (TPCP)
Training Management System Requirements (TPCP) API PUBLICATION TM-1 THIRD EDITION, NOVEMBER 2009 EFFECTIVE DATE: MAY 1, 2010 Training Management System Requirements (TPCP) Training and Certification Programs
More informationU.S. DEPARTMENT OF THE INTERIOR OFFICE OF INSPECTOR GENERAL Verification of Previous Office of Inspector General Recommendations September 2009
U.S. DEPARTMENT OF THE INTERIOR OFFICE OF INSPECTOR GENERAL Verification of Previous Office of Inspector General Recommendations September 2009 ISD-EV-MOA-0002-2009 Contents Acronyms and Other Reference
More informationKit Rowley. Subject: Content type and workflow planning (SharePoint Server 2010) Attachments: image001.gif. Plan content types. Plan content types
Kit Rowley Subject: Content type and workflow planning (SharePoint Server 2010) Attachments: image001.gif Content type and workflow planning (SharePoint Server 2010) Published: May 12, 2010 This article
More informationEastern Illinois University EISE Configuration Management Plan
Eastern Illinois University EISE Configuration Management Prepared by: Bill Witsman Version: 10.0 Create Date: April 13, 2005 Approval Date: Last Revision Date: December 17, 2009 CM Analyst: Project Manager:
More informationCA Spectrum and CA Service Desk
CA Spectrum and CA Service Desk Integration Guide CA Spectrum 9.4 / CA Service Desk r12 and later This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter
More informationPURCHASE ORDER ATTACHMENT Q-202 SOFTWARE QUALITY SUBCONTRACTOR REQUIREMENTS TASK DESCRIPTIONS - PURCHASE CATEGORY "B"
PURCHASE ORDER ATTACHMENT Q-202 SOFTWARE QUALITY SUBCONTRACTOR REQUIREMENTS TASK DESCRIPTIONS - PURCHASE CATEGORY "B" 1 SOFTWARE QUALITY PROGRAM. This attachment establishes the software quality requirements
More informationDepartment of Administration Portfolio Management System 1.3 June 30, 2010
E 06/ 30/ 2010 EX AM PL 1. 3 06/ 28/ 2010 06/ 24/ 2010 06/ 23/ 2010 06/ 15/ 2010 06/ 18/ 2010 Portfolio System 1.3 June 30, 2010 Contents Section 1. Project Overview... 1 1.1 Project Description... 1 1.2
More informationHP Service Manager. Software Version: 9.40 For the supported Windows and Linux operating systems. Processes and Best Practices Guide (Codeless Mode)
HP Service Manager Software Version: 9.40 For the supported Windows and Linux operating systems Processes and Best Practices Guide (Codeless Mode) Document Release Date: December, 2014 Software Release
More informationFor more information please contact your local UL field representative
MARK INTEGRITY PROGRAM UL Mark Surveillance Requirements UL defines responsibilities, duties and requirements for both manufacturers and UL representatives involved with Follow-Up Services inspection programs
More informationproduct data and product development process. enterprise to organize, access, and control data related to its
Product Data Management (PDM) Dr. M Kasim A Jalil C25 335 Tel: 5534741 kasim@fkm.utm.my my http://www.fkm.utm.my/~kasim Product Data Management (PDM) PDM is a tool that helps manage product data and product
More informationGSA PRODUCT CERTIFICATION PROGRAM POLICY GUIDE RELEASE 5
GSA PRODUCT CERTIFICATION PROGRAM POLICY GUIDE RELEASE 5 Gaming Standards Association GSA Certification Authority Released: 2012/04/20 GAMINGSTANDARDS.COM GSA Product Certification Program Policy Guide
More informationIBM SECURITY QRADAR INCIDENT FORENSICS
IBM SECURITY QRADAR INCIDENT FORENSICS DELIVERING CLARITY TO CYBER SECURITY INVESTIGATIONS Gyenese Péter Channel Sales Leader, CEE IBM Security Systems 12014 IBM Corporation Harsh realities for many enterprise
More informationSupport Triage a Self-Help Guide for Facilities, Vendors and Support Staff
Support Triage a Self-Help Guide for Facilities, Vendors and Support Staff Document History Version Date Update Origin Written by.01 5/22/12 Initial Draft Kelly Llewellyn 1.0 6/3/2012 Initial Release with
More informationTechExcel. ITIL Process Guide. Sample Project for Incident Management, Change Management, and Problem Management. Certified
TechExcel ITIL Process Guide Sample Project for Incident Management, Management, and Problem Management. Certified Incident Management Red Arrows indicate that the transition is done automatically using
More informationContract and Vendor Management Guide
Contents 1. Guidelines for managing contracts and vendors... 2 1.1. Purpose and scope... 2 1.2. Introduction... 2 2. Contract and Vendor Management 2.1. Levels of management/segmentation... 3 2.2. Supplier
More informationSTORRE: Stirling Online Research Repository Policy for etheses
STORRE: Stirling Online Research Repository Policy for etheses Contents Content and Collection Policies Definition of Repository Structure Content Guidelines Submission Process Copyright and Licenses Metadata
More informationa) To achieve an effective Quality Assurance System complying with International Standard ISO9001 (Quality Systems).
FAT MEDIA QUALITY ASSURANCE STATEMENT NOTE 1: This is a CONTROLLED Document as are all quality system files on this server. Any documents appearing in paper form are not controlled and should be checked
More informationNotice of Clarification
U. S. ELECTION ASSISTANCE COMMISSION VOTING SYSTEM TESTING AND CERTIFICATION PROGRAM 1225 New York Avenue, NW, Suite 1100 Washington, DC. 20005 Notice of Clarification NOC 09-004: Development and Submission
More informationNetBeans IDE Field Guide
NetBeans IDE Field Guide Copyright 2005 Sun Microsystems, Inc. All rights reserved. Table of Contents Introduction to J2EE Development in NetBeans IDE...1 Configuring the IDE for J2EE Development...2 Getting
More informationOUTSOURCING STRATEGIES & RISKS FROM AN ISO 9001-2000 PERSPECTIVE. Amera-Veritas. Amera-Veritas. Experts in in Quality, Safety & Supply Chain Assurance
OUTSOURCING STRATEGIES & RISKS FROM AN ISO 9001-2000 PERSPECTIVE Amera-Veritas Amera-Veritas Experts in in Quality, Safety & Supply Chain Assurance TOPICS 1. Outsourcing - Requirements of ISO 9001:2000
More informationSmart Meters Programme Schedule 2.5. (Security Management Plan) (CSP South version)
Smart Meters Programme Schedule 2.5 (Security Management Plan) (CSP South version) Schedule 2.5 (Security Management Plan) (CSP South version) Amendment History Version Date Author Status v.1 Signature
More informationRecords Management and SharePoint 2013
Records Management and SharePoint 2013 SHAREPOINT MANAGEMENT, ARCHITECTURE AND DESIGN Bob Mixon Senior SharePoint Architect, Information Architect, Project Manager Copyright Protected by 2013, 2014. Bob
More informationMicroStrategy Course Catalog
MicroStrategy Course Catalog 1 microstrategy.com/education 3 MicroStrategy course matrix 4 MicroStrategy 9 8 MicroStrategy 10 table of contents MicroStrategy course matrix MICROSTRATEGY 9 MICROSTRATEGY
More informationIntroduction... 4. Purpose... 4 Scope... 4 Manitoba ehealth Change Management... 4 Icons... 4. RFC Procedures... 5
Remedy Change Management Version 3.0 Modified: 10/27/2015 Table of Contents Introduction... 4 Purpose... 4 Scope... 4 Manitoba ehealth Change Management... 4 Icons... 4 RFC Procedures... 5 Process Flow
More informationAdd Feedback Workflow
Add Feedback Workflow Add Feedback Collection workflow to a list or library The workflows included with SharePoint products are features that you can use to automate your business processes, making them
More informationAutomated Transportation Management System
- BOE/RL-93-52 Rev. 1 Automated Transportation Management System (ATMS) Configuration Management Plan /, MAR 2 2 1995 OSTI 1 United States Department of Energy Richland, Washington - Approved for Public
More informationExtending the value of CA Service Desk Manager with integration connectors SAP Solution Manager, MS System Center Operations Manager
Extending the value of CA Service Desk Manager with integration connectors SAP Solution Manager, MS System Center Operations Manager Christophe Trinquet Terms of This Presentation This presentation was
More informationCDX Vendor Conformance Process Version 1.0
CDX Vendor Conformance Process Version 1.0 03-March-2014 Version 1.0 Status: Draft CDX Conformance Process Page 1 of 25 Document Version Control Release Date Version Status / Comments 18-Jul-2013 0.01
More informationManaging Open Source Code Best Practices
Managing Open Source Code Best Practices September 24, 2008 Agenda Welcome and Introduction Eran Strod Open Source Best Practices Hal Hearst Questions & Answers Next Steps About Black Duck Software Accelerate
More informationRecording and Registration of Domain Names
CORNELL UNIVERSITY POLICY LIBRARY Recording and Registration of Domain Names POLICY 5.6 Technologies Chapter 6, Domain Names POLICY STATEMENT Cornell University requires the central recording of all domain
More informationSOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK
Office of Safety and Mission Assurance NASA-GB-9503 SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK AUGUST 1995 National Aeronautics and Space Administration Washington, D.C. 20546 PREFACE The growth in cost
More informationProject Plan for <project name>
Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document. This template can be used at it is, or to complete and
More informationBusiness Process Flowchart. Supplier Management. Packet Description. MAGIC Roles. MAGIC Flows. Help or Questions
Business Process Flowchart Supplier Management Packet Description The Supplier Management Packet describes how to handle errors, updates to attributes and organizational structures, and user account management.
More informationManaged Support Policy
TABLE OF CONTENTS 1. SERVICE DESCRIPTION 2 2. SUPPORT OPTIONS 2 3. SERVICE SUPPORT HOURS 3 4. MONITORING AND OUTAGES 3 5. SERVICE LEVEL AGREEMENT 4 6. PLANNED MAINTENANCE AND UPGRADES 5 7. TARGET UPTIME
More informationHSCIC Audit of Data Sharing Activities:
Directorate / Programme Data Dissemination Services Project Data Sharing Audits Status Approved Director Terry Hill Version 1.0 Owner Rob Shaw Version issue date 20/04/2016 HSCIC Audit of Data Sharing
More informationSpecialties Manufacturing. Talladega Castings & Machine Co., Inc. ISO 9001:2008. Quality Manual
Specialties Manufacturing Talladega Castings & Machine Co., Inc. ISO 9001:2008 This document is the property of TMS and may not be reproduced, wholly, or in part, without the express consent of TMS. Rev.
More informationORACLE QUALITY ORACLE DATA SHEET KEY FEATURES
ORACLE QUALITY KEY FEATURES Enterprise wide Quality Data Repository In-process Quality Integrated with manufacturing, logistics, maintenance and service modules in the Oracle E-Business Suite. Analysis
More informationCitrix Online, div. of Citrix Systems Inc. GoToAssist TM. Product Category: Knowledge Management/eSupport Validation Date: 2/22/2005
, div. of Citrix Systems Inc. GoToAssist TM Product Category: Knowledge Management/eSupport Validation Date: 2/22/2005 Product Abstract GoToAssist enables businesses to securely interact in real time with
More informationSafetyMAP Initial Level User Guide
SafetyMAP Initial Level User Guide Initial Level User Guide 4th Edition Introduction This User Guide has been produced to support SafetyMAP: Auditing Health and Safety Management Systems, 4 th Edition
More informationOPERATING PROCEDURE IT CHANGE MANAGEMENT PROCEDURES MANUAL. PREPARED BY: AEMO DOCUMENT NO: Enter Document ID VERSION NO: 6.
OPERATING PROCEDURE IT CHANGE MANAGEMENT PROCEDURES MANUAL PREPARED BY: AEMO DOCUMENT NO: Enter Document ID VERSION NO: 6.6 STATUS FINAL Approvals The undersigned have approved the release of Version 6.6
More informationQuality Management System Manual Revision L
This Page 1 of 35 of the Quality Management System Manual If issued as a controlled copy, the serial number of this copy is Quality Management System Manual Certified to AS9100 Revision C Printed copies
More information