Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section Configuration Management Ernest Williams.

Slides:



Advertisements
Similar presentations
.NET Technology. Introduction Overview of.NET What.NET means for Developers, Users and Businesses Two.NET Research Projects:.NET Generics AsmL.
Advertisements

Configuration Management
An open source QA stack testing tools for agile teams Presented by Aaron Evans
Web Development Engineering Processes Introduction to Web Development Outsourcing Processes.
The “Lifecycle” of Software. Chapter 5. Alternatives to the Waterfall Model The “Waterfall” model can mislead: boundaries between phases are not always.
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
Configuration management. Reasons for software configuration management  it facilitates the ability to communicate  status of documents, coding, changes.
Requirements Analysis 5. 1 CASE b505.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis CASE Computer.
E. M. Saleski FAC 11/11/08 Configuration Control of PPS FAC Review November 2008 E. Michael Saleski Controls Dept Safety.
CSC 395 – Software Engineering Lecture 25: SCM –or– Expecting Change From Everything But Vending Machines.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Introduction to Software Testing
EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 1 DataGrid Quality Assurance Gabriel Zaquine Quality Engineer - WP12 – CS-SI.
Software Configuration Management
Software Configuration Management
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
Final Design and Implementation
Terri Lahey EPICS Collaboration Meeting June June 2006 LCLS Network & Support Planning Terri Lahey.
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
Effective Methods for Software and Systems Integration
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
Configuration Management System
NUAGA May 22,  IT Specialist, Utah Department of Technology Services (DTS)  Assigned to Department of Alcoholic Beverage Control  PCI Professional.
1 CSE 403 System Testing and Test Plans These lecture slides are copyright (C) Marty Stepp, They may not be rehosted, sold, or modified without expressed.
Research infrastructure and knowledge management Eric Maryniak.
Module CC3002 Post Implementation Issues Lecture for Week 6 AY 2013 Spring.
Article: Source Code Review Systems Author: Jason Remillard Presenter: Joe Borosky Class: Principles and Applications of Software Design Date: 11/2/2005.
Software Testing Life Cycle
CCSM Software Engineering Coordination Plan Tony Craig SEWG Meeting Feb 14-15, 2002 NCAR.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Rational Unified Process Fundamentals Module 4: Disciplines II.
COMP-14: Automating your deployments using ANT Gary S Clink Business Consultant.
Understand Application Lifecycle Management
From Creation to Dissemination A Case Study in the Library of Congress’s use Open Source Software DLF Spring Forum Corey Keith
Configuration Management (managing change). Starter Questions... Which is more important?  stability  progress Why is change potentially dangerous?
Requirements Verification & Validation Requirements Engineering & Project Management.
May 29 th, 2003 Curtis Anderson Sivaprasad Padisetty.
ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA.
1 SEG4912 University of Ottawa by Jason Kealey Software Engineering Capstone Project Tools and Technologies.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Access Grid and the Mbone media tools Sumover Workshop November 28, 2005 Thomas D. Uram
1 Software Configuration Management (SCM) and Software Reuse Presented By: Edmund Leng (HT052446J) Choo Zhi Min (HT052430X)
Software Testing and Maintenance 1 Code Review  Introduction  How to Conduct Code Review  Practical Tips  Tool Support  Summary.
CSCI 521 Final Exam Review. Why Establish a Standard Process? It is nearly impossible to have a high quality product without a high quality process. Standard.
MIS 7003 MBA Core Course in MIS Professor Akhilesh Bajaj The University of Tulsa Introduction to S/W Engineering © All slides in this presentation Akhilesh.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
TMS - Cooperation partner of TÜV SÜD EFFECTIVE SERVICE MANAGEMENT based on ISO/IEC & ISO/IEC
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Jefferson Lab Report Karen S. White 11/14/00. Overview  Status of Jefferson Lab Control System  Work In Progress  Transitioning to Operations.
IT323 - Software Engineering 2 1 Tutorial 4.  List the main benefits of software reuse 2.
JRA1 Meeting – 09/02/ Software Configuration Management and Integration EGEE is proposed as a project funded by the European Union under contract.
Parasoft : Improving Productivity in IT Organizations David McCaw.
SG Software Configuration Management And CVS scmGalaxy Author: Rajesh Kumar
Using COTS Hardware with EPICS Through LabVIEW – A Status Report EPICS Collaboration Meeting Fall 2011.
Building Enterprise Applications Using Visual Studio®
Configuration Management
Software Project Configuration Management
CompTIA Server+ Certification (Exam SK0-004)
Accelerator Reliability and Software
Configuration Management
Software Configuration Management
Maintaining software solutions
LEVEL OF TESTING J.ALFRED DANIEL, AP/CSE.
Chapter 7 –Implementation Issues
ONAP Architecture Principle Review
Software Configuration Management
Presentation transcript:

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section Configuration Management Ernest Williams

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section OUTLINE Introduction Scope Software Development and Deployment Standards CVS/Subversion + Relational Database System Monitoring/Maintenance EPICS IOC Software and Extensions

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section Introduction In order to meet the reliability and availability requirements placed on the control system; a solid configuration management system is needed. Configuration management also supports the long term maintenance and security of control systems. Configuration management applies to: Hardware Software Documentation (e.g. procedures and drawings) Plan to hire a Database Software Architect and Engineer

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section SCOPE The Focus in this talk is on Software Configuration Management

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section Software Configuration Management (Wiki-Pedia) Configuration identification - What code are we working with? Configuration control - Controlling the release of a product and its changes. Status accounting - Recording and reporting the status of components. Review - Ensuring completeness and consistency among components. Build managementBuild management - Managing the process and tools used for builds. Process management - Ensuring adherence to the organization's development process. Environment management - Managing the software and hardware that host our system. Teamwork - Facilitate team interactions related to the process. Defect tracking - Making sure every defect has traceability back to the source

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section Software Development Multi-user Server/Workstation environment (e.g. linux) Software development standards/guidelines will provide some consistency and lead to code maintainability. Use common frameworks and software tools Compiler/build environment must be kept in synch with production server. Test, test, test on development server Build/Construct reusable test harness for software components. Use debugging tools: gdb, valgrind, purify, etc… Practice software version control using such as CVS or Subversion:. Development of shared IOC software modules such as EPICS IOC device/driver support should undergo small informal software design reviews. Internal/External peer review ) Software Development

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section Software Deployment Multi-user Server/Workstation environment (e.g. linux) Strong software release procedures/standards. Production releases for deployment should be tagged and/or marked with a clear versioning scheme. The version and all dependencies could be captured in a relational database. Mark/Embed all shared libraries with some version string or tag. Create/Implement a reliable and sound “roll-back” scheme. Develop a deployment checklist (manual/automated) Test on the production side before turning over to operations

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section CVS/Subversion + Relational Database What do we need to capture in an RDB? Location of software documentation Author’s information address, phone number, etc… Release/Version versus machine operating period Version numbers associated with an IOC but maintained with different versioning software or methods Examples: FPGA code, LabView, MATLAB A relational database can tie all of this together and produce useful reports. We are planning to join the IRMIS Collaboration.

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section System Monitoring/Maintenance Configuration management also means keeping tabs on the status of what is running on our systems. Is caRepeater running? Who is monitoring that? Does someone get paged if it is down? What about iocLogServer or some other important service that our software relies on? Configuration management means bug tracking and resolution. What about patch management? Investigating some options now. Bugzilla Mantis RequestTracker (RT) Again, we should integrate this in with a relational database to help us monitor/maintain our systems

Ernest L. Williams Jr. FAC November 2008 Control Systems Software Section Concerns/Issues Many disparate Database systems here at SLAC. Critical Database servers outside the control system network could reduce availability. Hardware configuration management requires a solid plan for developing/releasing drawings, firmware, etc… Need to hire Database Engineer/Architect