DOCSLIB.ORG

Configuration Management Plan

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Configuration Management Plan Configuration Management Plan CONFIGURATION MANAGEMENT PLAN Version 5-00 Document Control Number 1000-00000 2018-09-11 Woods Hole Oceanographic Institution Woods Hole Road, Woods Hole, MA. www.whoi.edu in Cooperation with University of Washington Oregon State University Rutgers University 1 Configuration Management Plan Document Control Sheet Version Date Description Originator 1-0 Jun 16, 2006 Initial integration S. Williams 2-0 Oct 15, 2007 Complete Revision A. Ferlaino 2-1 Oct 30, 2007 Threshold Update A. Ferlaino 2-2 Oct 30, 2007 Threshold Update S. Williams 2-3 Nov 13, 2007 Terminology A. Ferlaino 2-4 Nov 16, 2007 Comment Updates A. Ferlaino 2-5 Jan – 2008 Major update SE group 2-56 Apr 29, 2008 Revision A. Ferlaino 2-64 May 28, 2008 Revision Chapters 5-6 A. Ferlaino 2-66 May 28, 2008 Clerical Corrections A. Ferlaino 2-70 Jun 9, 2008 Formal Review Comment Update A. Ferlaino 2-71 Jun 20, 2008 Section 2.6 Changes A. Ferlaino 2-73 Jun 27, 2008 Formatting A. Ferlaino 2-74 Aug 11, 2008 Document Properties A. Ferlaino 2-75 Aug 25, 2008 Version formatting, section 1-7 A. Ferlaino change to convention 2-76 Sep 22, 2008 Clerical Correction A. Ferlaino 2-77 Oct 6, 2008 Collaboration Tools, update of A. Ferlaino, P. Yeung naming conventions, inclusion of attachment B2, correction to CCB 2-78 Oct 9, 2008 Formatting, clerical corrections L. Snow 2-79 Oct 10, 2008 Mike Harrington directed RCA A. Ferlaino example changes, Section 1 2-81 Oct 22, 2008 1.8.2 graphic, 1.8.4, 5.3.1, 5.3.3 A. Ferlaino text 2-82 Jan 22, 2009 Section 6.5, Appendix A-2: E. Griffin Change OOI CCB Chairperson to OOI Program Director. Move OOI Project Director to OOI CCB Members list. 1.5, 1.6, 3.4.5, 3.4.10, 3.5.2.1, 3.5.2.2, 3.5.2.3: copy edits 2-83 Jan 26, 2009 Section 7.3.2 text added re: Risk L. Brasseur Management Board 2-84 Jan 30, 2009 Appendix A-1, minor title A. Ferlaino description edits. 2-85 Oct 29, 2009 Updated pre baseline A. Ferlaino, B. Bergen, M. Goodnight 2-86 Nov 15, 2009 NSF Directed changes to CCB A. Ferlaino membership and address change in OL management structure. Update of tools references including Alfresco structure. Variant impact changes. 2-87 Nov 19, 2009 1.2 R&RA Scope, Scope in A. Ferlaino naming convention 2-88 Nov 20, 2009 CCB Lien update A. Ferlaino, ECR # 1300-00030 2-89 May 25, 2010 Section 1.9 updates K. Carr, ECR # 1300-00075 corresponding to B2 table 2 Configuration Management Plan updates 2-90 Sept 2, 2010 Major Update for CCB E. Chapman, ECR#1300-00090 2-91 Oct 10, 2010 Edits to Sec 6.3, 6.4, and 7.2 E. Chapman, ECR#1300-00090 based on CCB feedback. 2-92 Feb 7, 2011 Edits to 3.4.10 and Section 5. E. Chapman 3-00 Feb. 18, 2011 Major Update, edits to Sections E. Griffin, ECR #1300-00126 1.7.1, 1.7.2, 1.9, 2.11.2, 3.0, 3.5.2.2, 4.2.1, 7.0, 7.1, Appendices 3-01 June 9, 2011 Edits and clarifications to E. Griffin, E. Chapman Sections 1.6, 1.7, 1.8, 2.7, 6.2.3, 6.4, 6.5, 7.3.2, 7.4, 7.5, and Appendix A-1 3-02 June 15, 2011 Clarified drawing title block E. Chapman statement in 2.7 3-03 July 14, 2011 Updates to Sections 1.8.1, 7.4, E. Griffin, ECR #1300-00179 removal of Appendix A-1, administrative changes. 3-04 August 5, Updates to Sections 6.4, 7.2, 7.3, G. Settle and E. Griffin, ECR 2011 7.5, and 7.6; changed position #1300-00192 titles to reflect actuals used in the PMO throughout the document. 3-05 Oct. 20, 2011 Edits to sections 1.8, 3.5, 6.2, 7.2, E. Griffin 7.5 3-06 Oct. 21, 2011 Addition to 1.4; minor word G. Settle changes, copy edits 3-07 Oct 21, 2011 Section 6.2.4; additional edits to E. Griffin, A. Ferlaino, E. sections 6.2.1, 6.2.2, 6.4, 7.1, Chapman 7.1.3, 7.3.1, 7.5 3-08 Nov 15, 2011 Resolving liens ECR 1300-00192 E. Griffin 3-09 Nov 29, 2011 Resolving liens ECR 1300-00192 E. Griffin 3-10 Dec 1, 2011 Edits to Sections 2.9, 2.10, 2.11 E. Griffin 3-11 Dec 6, 2011 Resolving liens ECR 1300-00192 E. Griffin 3-12 Dec 9, 2011 Formatting E. Griffin, ECR #1300-00192 3-13 Dec 23, 2011 Administrative edit on Document E. Griffin Control Sheet 3-14 Mar 9, 2012 Updates to Sections 1.5, 1.10 E. Griffin 3-15 Mar 13, 2012 Updates to Sections 3.4, 3.5, 6.3, E. Griffin 6.4 3-16 Mar 28, 2012 Working off liens E. Griffin, ECR #1300-00237 3-17 Mar 30, 2012 Completion of liens E. Griffin, ECR #1300-00237 3-18 Dec 14, 2012 Completion of NSF Liens E. Chapman, ECR #1300- 00237 3-19 Dec 21, 2012 Formatting, copy edits E. Griffin 3-20 Mar 19, 2013 Administrative updates, E. Griffin corrections to Sections 1.7.2, 1.8.1, 6.2.1, 6.4, 6.5, 7.3.1. 3-21 April 3, 2013 Updates to Sections 4.5.1.3, 7.3.1 K. Carr, ECR #1300-00356 3-22 April 9, 2013 Changed language in 7.3.1 per K. Carr, ECR #1300-00356 comment on ECR 1300-00356 3-23 Aug 8, 2013 Administrative change. As-Build E. Chapman TDP due as part of Commissioning not Acceptance. 3-24 Oct 28, 2013 Updates to CI CM section. T. Cowles 3 Configuration Management Plan 3-25 Jan 7, 2014 Admin Change- clarify language E. Chapman in 6.2.1.e and 6.2.2.d 4-01 Oct. 15, 2014 Major Update for Transition to P. Matthias, S. White O&M 4-02 May 12, 2015 Finalize for End of Construction D. Penn 4-03 May 19, 2015 Addition of CGSN and Cabled S. Banahan Array CMP documentation 4-04 May 19, 2015 Addition of Cabled Array S. Banahan document and software instructions. 4-05 Oct 02, 2015 Various Updates needed for the J. Pisciotta O & M phase. 4-05 Dec 11, 2015 Various Updates needed for the J. Pisciotta O & M Redmine. 4-05 April 1, 2016 Additional Updates needed for the J. Pisciotta O & M Redmine changes. 5-00 Sept. 11, 2018 Refresh for OOI 2.0, with input P. Matthias from all IOs. 4 Configuration Management Plan Table of Contents: 1 Configuration Management System Structure ............................................................................... 8 1.1 Purpose .................................................................................................................................. 8 1.2 Scope ...................................................................................................................................... 8 1.3 Configuration Process ............................................................................................................ 8 1.3.1 Drawing Standard ........................................................................................................... 8 1.3.2 Software Versioning and Configuration Process ............................................................ 8 1.3.3 Implementing Organization Documentation Assurance Process ................................... 9 1.3.4 Implementing Organization Configuration Management Process .................................. 9 1.4 Responsibility & Authority ....................................................................................................... 9 1.5 Configuration Controlled Documents .................................................................................... 11 1.6 File Formats and Applications .............................................................................................. 11 1.7 File Naming Conventions (Non-Controlled) .......................................................................... 12 1.7.1 Terms and Definitions ................................................................................................... 12 1.8 File Numbering Conventions (Controlled) ............................................................................ 12 1.8.1 Series Number .............................................................................................................. 12 1.8.2 Sequence Number ........................................................................................................ 13 1.8.3 Control Assignment Validation Criteria ......................................................................... 14 1.8.4 Controlled Files Outside of the DMS ............................................................................ 14 1.9 Other Naming Conventions .................................................................................................. 14 1.9.1 Observatory - Instrument Name ................................................................................... 14 1.10 Technical Data Baselines ..................................................................................................... 14 2 Document and Information Types ................................................................................................. 15 2.1 Hardware and Software Documentation............................................................................... 15 2.2 Document (Drawing) List ...................................................................................................... 15 2.3 Procurement Documentation ................................................................................................ 16 2.4 Source Control Document / Vendor Item Drawing ............................................................... 16 2.5 Specifications ........................................................................................................................ 16 2.6 Hardware Parts Lists and Bills of Material ............................................................................ 16 2.7 Hardware Assembly Drawings ............................................................................................. 16 2.8 Hardware Assembly Procedures .......................................................................................... 16 2.9 Hardware Configuration Database ......................................................................................
Load more

Recommended publications
  • Rhetorical Code Studies Revised Pages
    Revised Pages rhetorical code studies Revised Pages Sweetland Digital rhetoric collaborative Series Editors: Anne Ruggles Gere, University of Michigan Naomi Silver, University of Michigan The Sweetland Digital Rhetoric Collaborative Book Series publishes texts that investigate the multiliteracies of digitally mediated spaces both within academia as well as other contexts. Rhetorical Code Studies: Discovering Arguments in and around Code Kevin Brock Developing Writers in Higher Education: A Longitudinal Study Anne Ruggles Gere, Editor Sites of Translation: What Multilinguals Can Teach Us about Digital Writing and Rhetoric Laura Gonzales Rhizcomics: Rhetoric, Technology, and New Media Composition Jason Helms Making Space: Writing, Instruction, Infrastrucure, and Multiliteracies James P. Purdy and Dànielle Nicole DeVoss, Editors Digital Samaritans: Rhetorical Delivery and Engagement in the Digital Humanities Jim Ridolfo diGitalculturebooks, an imprint of the University of Michigan Press, is dedicated to publishing work in new media studies and the emerging field of digital humanities. Revised Pages Rhetorical Code Studies discovering arguments in and around code Kevin Brock University of Michigan Press ann arbor Revised Pages Copyright © 2019 by Kevin Brock Some rights reserved This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Note to users: A Creative Commons license is only valid when it is applied by the person or entity that holds rights to the licensed work. Works may contain components (e.g., photo- graphs, illustrations, or quotations) to which the rightsholder in the work cannot apply the license. It is ultimately your responsibility to independently evaluate the copyright status of any work or component part of a work you use, in light of your intended use.
    [Show full text]
  • Managing the Configuration of Information Systems with a Focus on Security
    MANAGING THE CONFIGURATION OF INFORMATION SYSTEMS WITH A FOCUS ON SECURITY Shirley Radack, Editor Computer Security Division Information Technology Laboratory National Institute of Standards and Technology U.S. Department of Commerce Organizations have to make frequent changes to their information systems in order to implement new and updated hardware and software components, correct software flaws and other errors, address new security threats, and adapt to changing business objectives. These constant changes result in adjustments being made to the configuration of information systems; these activities could have an impact on the security of the systems and operations. In developing information systems, organizations employ many components that can be interconnected in different arrangements to meet the organization’s business, mission, and information security needs. To protect information systems and information, organizations need techniques for the secure configuration, operation, and management of system components, including mainframes, workstations, servers, networks, operating systems, middleware, and applications, and for the management and control of risks to systems and information. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) has issued a new guide to help organizations develop a well-defined process for managing and controlling secure system configurations, and for managing risks in information systems. NIST Special Publication 800-128, Guide to Security- Focused
    [Show full text]
  • Travstar1 V10.01.02-XXXX XXX
    Travstar1 v10.01.02-XXXX_XXX Fiscal Systems, Inc. 4946 Research Drive Huntsville, AL 35805 Office: (256) 772-8920 Help Desk: (800) 838-4549, Option 3 www.fis-cal.com Document Version History Version Description Approved Date 1.0 Initial Release for Version 9.00 KDS 15 JUL 09 1.1 Changed Patch and Update Instructions KDS 11 NOV 09 Annual Review 1.2 KDS 22 APR 10 Corrected Typographical Errors 1.3 Annual Review KDS 12 JUL 11 Annual Review Verified reference web links are valid 1.4 KDS 10 AUG 12 Updated web link on qualified QSAs Updated web link for PCI wireless guidelines Annual Review 12 JUN 13 1.5 Verified reference web links are valid KDS Added Log Review Instructions Annual Review 1.6 KDS 16 JUN 14 Verified reference web links are valid Annual Review Verified reference web links are valid 1.7 Updated Business Address NBJ 30 MAR 15 Updated Secure Access Control Added detailed Log Review Setup Instructions 1.8 Added Software Versioning Methodology NBJ 14 OCT 15 Added Required Ports/Services 1.9 Modified Log review Setup Instructions NBJ 19 OCT 15 Added Centralized Logging Updated Required Ports/Services 2.0 Updated Secure Remote Updates NBJ 02 FEB 16 Updated Auditing and Centralized Logging 2.1 Updated Software Versioning Methodology NBJ 17 Feb 16 Full Certification 2.2 BTH 5 May 17 Updated Software Versioning Methodology Updated Introduction Updated Remote Access to “Multi-factor” 2.3 Revised Version number BTH 22 JUN 17 Updated “Travstar1 POS” to just “Travstar1 ” for clarity. Minor wording changes throughout for clarity Adjusted Wording of PCI-DSS requirements to match PCI-DSS 3.2 Updated network connections to clearly define 2.4 BTH 02 AUG 17 every connection Updated references to stored cardholder data to state that it is only stored during preauthorization.
    [Show full text]
  • Business Rule Based Configuration Management and Software System Implementation Using Decision Tables
    Business Rule Based Configuration Management and Software System Implementation Using Decision Tables Olegas Vasilecas, Aidas Smaizys Vilnius Gediminas Technical University, Sauletekio av. 11, LT-10223 Vilnius, Lithuania [email protected], [email protected] Abstract. Deployment and customization of the software in different information systems of separate organizations challenge large requirement conformity, project and specification management, design and architecture complexity, code integration, compatibility and interoperability issues, frequently causing the need of reengineering through the entire all the system development lifecycle. The paper proposes new business rule based method of information system configuration management and automated way of configuration implementation into the final software system code. 1 Introduction Business systems are functioning according to business rules in specific business domain. Due to dynamic of its nature, business environment is changing frequently according to internal and external influences such as changes in law, new competition etc. [1]. However Business rules (BR) of particular problem domain are similar in several organizations but they are never applied the same way even they depend on the same legal regulations. Production and implementation of such a software system into the large amount of slightly different information systems of separate organizations challenge large requirement conformity, project and specification management, design and architecture complexity,
    [Show full text]
  • ITIL Asset and Configuration Management in the Cloud
    ITIL Asset and Configuration Management in the Cloud January 2017 © 2017, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. Contents Introduction 1 What Is ITIL? 1 AWS Cloud Adoption Framework 2 Asset and Configuration Management in the Cloud 3 Asset and Configuration Management and AWS CAF 5 Impact on Financial Management 5 Creating a Configuration Management Database 6 Managing the Configuration Lifecycle in the Cloud 8 Conclusion 9 Contributors 10 Abstract Cloud initiatives require more than just the right technology. They also must be supported by organizational changes, such as people and process changes. This paper is intended for IT service management (ITSM) professionals who are supporting a hybrid cloud environment that leverages AWS. It outlines best practices for asset and configuration management, a key area in the IT Infrastructure Library (ITIL), on the AWS cloud platform.
    [Show full text]
  • Book of Abstracts
    The Association for Literary and Lingustic Computing The Association for Computers and the Humanities Society for Digital Humanities — Société pour l’étude des médias interactifs Digital Humanities 2008 The 20th Joint International Conference of the Association for Literary and Linguistic Computing, and the Association for Computers and the Humanities and The 1st Joint International Conference of the Association for Literary and Linguistic Computing, the Association for Computers and the Humanities, and the Society for Digital Humanities — Société pour l’étude des médias interactifs University of Oulu, Finland 24 – 29 June, 2008 Conference Abstracts International Programme Committee • Espen Ore, National Library of Norway, Chair • Jean Anderson, University of Glasgow, UK • John Nerbonne, University of Groningen, The Netherlands • Stephen Ramsay, University of Nebraska, USA • Thomas Rommel, International Univ. Bremen, Germany • Susan Schreibman, University of Maryland, USA • Paul Spence, King’s College London, UK • Melissa Terras, University College London, UK • Claire Warwick, University College London, UK, Vice Chair Local organizers • Lisa Lena Opas-Hänninen, English Philology • Riikka Mikkola, English Philology • Mikko Jokelainen, English Philology • Ilkka Juuso, Electrical and Information Engineering • Toni Saranpää, English Philology • Tapio Seppänen, Electrical and Information Engineering • Raili Saarela, Congress Services Edited by • Lisa Lena Opas-Hänninen • Mikko Jokelainen • Ilkka Juuso • Tapio Seppänen ISBN: 978-951-42-8838-8 Published by English Philology University of Oulu Cover design: Ilkka Juuso, University of Oulu © 2008 University of Oulu and the authors. _____________________________________________________________________________Digital Humanities 2008 Introduction On behalf of the local organizers I am delighted to welcome you to the 25th Joint International Conference of the Association for Literary and Linguistic Computing (ALLC) and the Association for Computers and the Humanities (ACH) at the University of Oulu.
    [Show full text]
  • Software Project Monitoring and Control
    Module 12 Software Project Monitoring and Control Version 2 CSE IIT, Kharagpur Lesson 31 Risk Management and Software Configuration Management Version 2 CSE IIT, Kharagpur Specific Instructional Objectives At the end of this lesson the student would be able to: • Identify the main categories of risks which can affect a software project. • Explain how to assess a project risk. • Identify the main strategies to plan for risk containment. • Explain what risk leverage is. • Explain how to handle the risk of schedule slippage. • Explain what is meant by configuration of a software product. • Differentiate among release, version and revision of a software product. • Explain the necessity of software configuration management. • Identify the principal activities of software configuration management. • Identify the activities carried out during configuration identification. • Identify the activities carried out during configuration control. • Identify the popular configuration management tools. Risk management A software project can be affected by a large variety of risks. In order to be able to systematically identify the important risks which might affect a software project, it is necessary to categorize risks into different classes. The project manager can then examine which risks from each class are relevant to the project. There are three main categories of risks which can affect a software project: Project risks. Project risks concern varies forms of budgetary, schedule, personnel, resource, and customer-related problems. An important project risk is schedule slippage. Since, software is intangible, it is very difficult to monitor and control a software project. It is very difficult to control something which cannot be seen. For any manufacturing project, such as manufacturing of cars, the project manager can see the product taking shape.
    [Show full text]
  • Quality Assurance and Configuration Management
    Quality Assurance and Configuration Management Energy, Climate, & Sandia National Laboratories implements quality assurance and configuration Infrastructure Security systems essential to the control and traceability of modeling used to demonstrate regulatory compliance. Introduction agencies, including, most significantly, the U.S. Nuclear Regulatory Commission Sandia National Laboratories has a long and the U.S. Environmental Protection history of involvement in significant Agency, as well as various federal, state, national programs directed at solving and other organizations. Among more the national problem of managing the notable successes of this work has been disposal of various forms of nuclear the adaptation of quality assurance wastes. These involvements include to activities sponsored largely by the significant responsibility on the Waste U.S. Department of Energy involved Isolation Pilot Plant (WIPP), the Yucca in the characterization, selection, and Mountain Site Characterization Project performance analyses associated with (YMP), the Hanford Tank Waste programs involving nuclear waste Remediation System (TWRS), and management. Quality assurance the Greater Confinement Disposal requirements originated from a need to (GCD) programs. In addition, control and assure the quality of nuclear Sandia has also played major roles power plant design, construction, and in nuclear waste transportation, operations; modifying these concepts and in several environmental for application to scientific investigation remediation and restoration and characterization activities was a programs, including those at Fernald, necessary and beneficial effort that Ohio, and Hanford, Washington. has proven successful for nuclear waste A key to the success of our activities management. on these programs, particularly for Decades of experience under the WIPP, YMP, TWRS, and GCD, was the scrutiny of independent audits, development and application of quality identifying quality deficiencies, and assurance for program activities.
    [Show full text]
  • Service Asset and Configuration Management (SACM/CMDB) Process
    Service Transition SERVICE ASSET AND CONFIGURATION MANAGEMENT PROCESS VERSION: 4.3 REVISION DATE: February 23, 2017 Service Transition USER GUIDE Service Asset and Configuration Management Process 4.3 | 02/23/2017 Contents Section 1. Introduction ......................................................................................... 1 1.1 Purpose .............................................................................................. 1 1.2 Goal .................................................................................................... 1 1.3 Overview ............................................................................................ 1 1.4 Key Relationships with other processes ........................................ 2 1.5 Definitions .......................................................................................... 2 Section 2. Roles and Responsibilities .................................................................. 4 2.1 Process Owner/Configuration Manager ......................................... 4 2.2 Configuration Item Class Owner ..................................................... 4 2.3 Configuration Item Class Administrator ......................................... 4 2.4 Configuration Item Company Administrator .................................. 5 2.5 IT Service Continuity Management (ITSCM) Role......................... 5 2.6 IT Staff ................................................................................................ 5 2.7 ITSM Product Manager ....................................................................
    [Show full text]
  • Component Evolution and Versioning State of the Art
    ACM SIGSOFT Software Engineering Notes Page 1 January 2005 Volume 30 Number 1 Component Evolution and Versioning State of the Art Alexander Stuckenholz FernUniversitat¨ in Hagen Lehrgebiet fur¨ Datenverarbeitungstechnik Universitatsstrasse¨ 27, 58084 Hagen, Germany [email protected] October 26, 2004 Abstract the kind of information about the running system as well as the lifecycle of the component in which the mechanisms are applied. Emerging component-based software development architectures The most frequently used technology in this area is versioning. promise better re-use of software components, greater flexibility, Versioning mechanisms are typically used to distinguish evolv- scalability and higher quality of services. But like any other piece ing software artifacts over time. As we will show in section 4 on of software too, software components are hardly perfect, when be- page 4, these mechanisms play an important role in component ing created. Problems and bugs have to be fixed and new features based software development too. need to be added. This paper presents an overview of current versioning mecha- This paper analyzes the problem of component evolution and nisms and substitutability checks in the area of component based the incompatibilities which result during component upgrades. software development. In a comparison, these systems will be We present the state of the art in component versioning and com- evaluated against their usability in the case of component up- pare the different methods in component models, frameworks and grades. Here we come to the conclusions that the available so- programming languages. Special attention is put on the automa- lutions are not sufficient to reduce version conflicts in component tion of processes and tool support in this area.
    [Show full text]
  • Chrome, Edge, and Firefox Integration
    Blue Prism 7.0 Chrome, Edge, and Firefox Integration Document Revision: 1.0 Blue Prism 7.0 | Chrome, Edge, and Firefox Integration Trademarks and Copyright Trademarks and Copyright The information contained in this document is the proprietary and confidential information of Blue Prism Limited and should not be disclosed to a third-party without the written consent of an authorized Blue Prism representative. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying without the written permission of Blue Prism Limited. © Blue Prism Limited, 2001 – 2021 © “Blue Prism”, the “Blue Prism” logo and Prism device are either trademarks or registered trademarks of Blue Prism Limited and its affiliates. All Rights Reserved. All trademarks are hereby acknowledged and are used to the benefit of their respective owners. Blue Prism is not responsible for the content of external websites referenced by this document. Blue Prism Limited, 2 Cinnamon Park, Crab Lane, Warrington, WA2 0XP, United Kingdom. Registered in England: Reg. No. 4260035. Tel: +44 370 879 3000. Web: www.blueprism.com Commercial in Confidence Page ii Blue Prism 7.0 | Chrome, Edge, and Firefox Integration Contents Contents TrademarksContents and Copyright iiiii Chrome, Edge, and Firefox integration 4 Browser extension compatibility 4 Chrome browser extension 5 Prerequisites 5 Install the Chrome browser extension using the Blue Prism installer 6 Install from the Bluecommand Prism line installer 67 Install the
    [Show full text]
  • 2. Configuration Management
    Computer Science and Software Engineering University of Wisconsin - Platteville 2. Configuration Management Yan Shi SE 3730 / CS 5730 Lecture Notes Outline . What is configuration management? — Identification — Change control — Status accounting — Audit and review . CM techniques and practices — lock-modify-unlock — copy-modify-merge — RCS — branching — deltas . CM tools Why is CM needed? . ``This worked yesterday and doesn't work now.” What happened? . ``The user manual says to do this, but when I do it, something different happens.'' Which is correct, the manual or the code? Why was one changed? . ``The code changes that I made last week are no longer in the code.” What happened to the fix? Who changed the code and Why? . ``The listing doesn't match what the program does!'' Which is correct? . ``Did the bug get fixed in this copy, too?'' Why is CM needed? . Control the changes — Versions of documents need to be combined to form a product, or configuration — With many people working on many files, inconsistencies can occur . Required for testing — We must know and control what source was used to produce a software system in order to know what is being tested — We need to be able to build and rebuild a software system reliably . Reduce the quality cost — https://www.youtube.com/watch?v=Ij1yDpfZI8Q CM CONCEPTS AND COMPONENTS What is Configuration Management? . Software CM is a discipline for managing the evolution of software systems throughout all stages of the software life cycle. SCM is a component of SQA system. — Infrastructure component — Organizational framework . SQA teams are often required to take the responsibility of managing the CM system.
    [Show full text]