HART Technologies Process Overview

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Software Quality Assurance Plan
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Software Quality Assurance Plan
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
Stepan Potiyenko ISS Sr.SW Developer.
Software Configuration Management (SCM)
Configuration Management
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Configuration Management
Software Engineering Institute Capability Maturity Model (CMM)
CSSE 375 Software Construction and Evolution: Configuration Management
Effective Methods for Software and Systems Integration
SE-02 CONFIGURATION MANAGEMENT Today we talk about Software Configuration Management (SCM for short): - What? - Why? - How?
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Introduction to Software Quality Assurance (SQA)
Cybersecurity: Engineering a Secure Information Technology Organization, 1st Edition Chapter 7 Software Supporting Processes and Software Reuse.
Software Configuration Management
From Research Prototype to Production
Software Configuration Management (SCM)
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
1 Configuration Management “The Cookbook Approach”
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
How To Build a Testing Project 1 Onyx Gabriel Rodriguez.
Georgia Institute of Technology CS 4320 Fall 2003.
© Mahindra Satyam 2009 Configuration Management QMS Training.
Software Engineering 2003 Jyrki Nummenmaa 1 CONFIGURATION MANAGEMENT Today we talk about Software Configuration Management (SCM for short): -
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
Software Configuration Management (SCM). Product Developer Disciplines One view of the world is that there are three types of activities are required.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 29 Slide 1 Configuration management.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
Software Configuration Management (SCM) Source: Pressman, R., Software Engineering: A Practitioner ’ s Approach. Boston: McGraw Hill, Inc., 2005; Ghezzi,
Maintaining and Sustaining System Integrity Configuration Management for Transportation Management Systems Configuration management (CM) describes a series.
Configuration Management- Basic Concepts. Agenda  Configuration Management process Overview  Process Stages  Planning & Setup  Control  Audit  Case.
Software Configuration Management n Art of coordinating SW development to minimize confusion n Software quality assurance (umbrella) activity n Set of.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Configuration Control (Aliases: change control, change management )
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
Configuration & Build Management. Why Software Configuration Management ? The problem: Multiple people have to work on software that is changing More.
Anytime, Anywhere Access Benefits Functionality Work Order Administration Dispatch Work Order Work Order Details New Work Order Additional Functionality.
Certified Software Tester How To Build a Testing Project, Part 1.
Collaborating for Quality through the Project Quality Plan Matthew Conlon ESS ACCSYS QA/QC Quality Learning & Planning.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Software Configuration Management (SCM)
Configuration Management
Software Configuration Management
Software Project Configuration Management
Software Quality Control and Quality Assurance: Introduction
Software Configuration Management (SCM)
Chapter 11: Software Configuration Management
Software Configuration Management
Software and Systems Integration
Software Planning Guidelines
Configuration Management
Software Configuration Management
Release Management Release Management.
CMMI – Staged Representation
Engineering Processes
Lockheed Martin Canada’s SMB Mentoring Program
Chapter 11: Software Configuration Management
Chapter # 6 Software Configuration Management
Engineering Processes
Configuration Management
Configuration Management
Software Reviews.
DRAFT ISO 10007:2017 Revision Overview Quality management – Guidelines for configuration management ISO/TC176 TG 01.
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

HART Technologies Process Overview February 2, 2005

HART Processes HART Technologies has established a set of processes and procedures to use in our everyday business to ensure reliable and quality products are delivered to our customers. An top level graphical overview and description of the processes are provided in this presentation.

HART Processes Graphical Overview HT Policies Quality Assurance Admin Engineering Forms Finance Eng Admin InfoSec CM Eng Security HW Security SW SE

HART Processes Overview Administrative Finance (FIN) Information Security (IS) Security (SEC) Engineering Engineering (ENG) Configuration Management (CM) Hardware (HW) Software (SW) Systems Engineering (SE) Quality Assurance (QA) Forms/Templates Standard HART forms

Administrative Finance Property Tracking – track company and customer assets Accounting – defines overall accounting process Accounting system – defines process using QuickBooks System Information Security – Acceptable use of Computer Equipment Email Policy Information Sensitivity Password Remote Access VPN Wireless Access Security – defines our security procedures to safeguard classified materials Security Training and Briefings

Engineering (ENG) This process will define the top level engineering process, discuss process management, development team structure, technical practices, and provide a concurrent engineering implementation guideline. Project Planning – Plan work/tasks Project Control – Defines how we manage tasks/project Peer Review – Internal Reviews Review – Formal reviews and Audits Action Items – establishes process for recording, tracking and correcting all items Measure – Measurement Criteria Trade – Trade-off Process Training – Project Training Needs

Configuration Management Process (CM) The Configuration Management process (CM) is referenced from the top level Engineering process (ENG). The process addresses the tasks of Configuration Identification (CI), Configuration Control (CC), Configuration Status Accounting (CSA), and Configuration Audits (CA) and defines what tasks must be performed Configuration Management Plan (CMP) Configuration Control - Configuration Identification Configuration Control Board (CCB) Audits Build Directive Change Request Process GFE/Cots Reference Configuration Status Accounting

Hardware Engineering (HW) The Hardware Development process (HW) is referenced from the top level Engineering process (ENG) and encompasses those activities necessary to perform hardware development and testing including; hardware requirement analysis, preliminary design, detailed design, hardware build, hardware integration and check out, hardware qualification testing and product support. Preliminary Design Detailed Design Build Data Design Prototype – Simulation/Prototyping Build – Defines activities required throughout process Build.SAT – Subassemblies processes – ensures subassemblies are ready for use in system Integration – verifies HW assemblies/subassemblies meet electrical/mechanical requirements Development Plans and Requirements Analysis – Updates HW development plan generated during proposal Product Support – supports required changes to product Qualification Testing – verifies HW Assemblies/subassemblies meet specified requirements

System Engineering (SE) The Systems Engineering process (SE) is referenced from the top level Engineering process (ENG) and governs all systems engineering efforts within Engineering. This process describes tasks to develop, coordinate, support, and report on the system-wide technical aspects of projects performed within the Engineering organization System Engineering Plan System Design – system analysis System Integration Technical coordination Requirements Requirements Traceability Matrix (Reference) Verification – verifies system level requirements

Software Development Process (SW) The Software Development process (SW) is referenced from the top level Engineering process (ENG) encompasses those activities necessary to perform software development and testing including; software requirement analysis, architectural design, detailed design, coding, software component testing, software integration and testing, and software qualification testing. Architecture Design Critical computer Resource Estimation Software Development Resource Estimation Software Change Control Coding Coding in C++ Coding in VB6 Coding Evaluation Software Component Testing Detailed Design Integration and Testing Software Qualification Testing Software Corrective Actions Software Requirements Analysis Life Cycle Model Description Size Estimating Guidelines Software Development File Software Development Plan

Quality Assurance The Quality Assurance process (QA) defines our polices for ensuring quality products and services are provided to our customers. Ethics Policy - The purpose for this ethics policy is to establish a culture of openness, trust and integrity in business practices Quality Program Software Design/ Development Phase - process by which software products and activities are evaluated for compliance to project plans and contractual requirements and the results reported to the appropriate management.

Forms/Templates HART Forms and Templates referenced in our processes and used to conduct business at HART include: Admin Timesheets Business Expense Reports Travel Expense Reports Fax Cover Sheets HART Letterhead BOM – Pack List BOM – Product Release Engineering Program Plan Template Program Schedule Template Software Development Plan Template Configuration Mgmt Plan Template Security Visit Authorization Letter Security Clearance Justification Form

Process Management All processes are located on //ht-server/HART Policies & Process (W: Drive) in html format: Changes to process will be managed via the Change Control process using the Change Request forms on the HART database.