Quality assurance program guidelines for application to and use by manufacturers of rail/guideway vehicles, buses, automatic train control systems, and their major subsystems

Guidelines are presented for a quality assurance system to be implemented by the manufacturer in support of designing, developing, fabricating, assembling, inspecting, testing, handling, and delivery of equipment being procured for use in public urban mass transit systems. The guidelines apply to this equipment when being procured for: (1) use in revenue service; (2) demonstration of systems that will be revenue producing or used by the public; (3) use as a prototype for follow-on operational/revenue producing equipment procurements; and (4) qualification tests

Guide for certifying pressure vessels and systems

This guide is intended to provide methodology and describe the intent of the Pressure Vessel and System (PV/S) Certification program. It is not meant to be a mandated document, but is intended to transmit a basic understanding of the PV/S program, and include examples. After the reader has familiarized himself with this publication, he should have a basic understanding of how to go about developing a PV/S certification program

Can Individual Code Reviews Improve Solo Programming on an Introductory Course?

Peer code reviews have been successfully applied to the teaching of programming and can be applied to solo programming. Collaborative approaches are currently popular and have been successfully applied though social interaction and assessment issues limit their application. It is believed that a checklist based individual code review can provide a framework which allows students to proofread their code prior to submission, improving performance. Pilot and follow-up studies were conducted at Swansea Metropolitan University and although the results are inconclusive some important observations are made with regards to the use of this technique. Further study into the effects of individual code reviews on student performance is recommended

Can using Fagan Inspections improve the quality of specification in 2011? A Case Study

In this paper, we explore why Fagan Inspections have become obsolete in the software industry, given the body of evidence which supports their use to improve the quality of software artefacts and the software development process. Since the late 1970’s, much has been written about how Fagan Inspections improve the quality of both processes and outputs of the software development process. The literature indicates that the Fagan Inspection technique can improve quality of software (or other software development artefacts) by a reduction in defects of 60 – 90%. However, recent literature suggests that inspection techniques in general and Fagan Inspections in particular, are no longer used. A study in 1998 found that respondents used inspections either irregularly or not at all. Teams often review artefacts informally, but believe that they are performing an inspection or formal review. The lack of rigour in the review process results in reduced benefits and more defects in the artefacts. To explore this situation, we conducted a case study with a local enterprise and we report on the early findings. These suggest that the introduction of Fagan Inspections may have a number of benefits before they have even been introduced fully, including recognition of flaws in the current development process, development of technical knowledge relating to the software process domain, and improved team relations and a ‘quality’ culture. In addition, the personnel using Fagan Inspection gain experience in the production of ‘quality’ artefacts

Investigating Effective Inspection of Object-Oriented Code

Since the development of software inspection over twenty-five years ago it has become established as an effective means of detecting defects. Inspections were originally developed at a time when the procedural paradigm was dominant but, with the Object- Oriented (OO) paradigm growing in influence and use, there now exists a lack of guidance on how to apply inspections to OO systems. Object-oriented and procedural languages differ not only in their syntax but also in a number of more profound ways - the encapsulation of data and associated functionality, the common use of inheritance, and the concepts of polymorphism and dynamic binding. These factors influence the way that modules (classes) are created in OO systems, which in turn influences the way that OO systems are structured and execute. Failure to take this into account may hinder the application of inspections to OO code. This thesis shows that the way in which the objectoriented paradigm distributes related functionality can have a serious impact on code inspection and, to address this problem, it develops and empirically evaluates three code reading techniques

Software Formal Inspections Guidebook

The Software Formal Inspections Guidebook is designed to support the inspection process of software developed by and for NASA. This document provides information on how to implement a recommended and proven method for conducting formal inspections of NASA software. This Guidebook is a companion document to NASA Standard 2202-93, Software Formal Inspections Standard, approved April 1993, which provides the rules, procedures, and specific requirements for conducting software formal inspections. Application of the Formal Inspections Standard is optional to NASA program or project management. In cases where program or project management decide to use the formal inspections method, this Guidebook provides additional information on how to establish and implement the process. The goal of the formal inspections process as documented in the above-mentioned Standard and this Guidebook is to provide a framework and model for an inspection process that will enable the detection and elimination of defects as early as possible in the software life cycle. An ancillary aspect of the formal inspection process incorporates the collection and analysis of inspection data to effect continual improvement in the inspection process and the quality of the software subjected to the process

Process Time Refinement for Reusable Launch Vehicle Regeneration Modeling

To sustain operational effectiveness, the Air Force has invested in the research and development of space-based technologies. Certain ongoing spacelift research efforts are focused on developing operationally responsive Reusable Military Launch Vehicles (RMLV) capable of launching payloads into orbit within hours of a tasking notification. Previous Air Force Research Laboratory-sponsored AFIT studies have resulted in the development of the MILEPOST discrete-event simulation model. This model has enabled the ability to analyze the impacts to responsiveness and manpower requirements given different RMLV design alternatives. The focus of this thesis is to improve the fidelity of the MILEPOST model by developing parametric models of simulation process times in terms of certain influential factors which affect maintenance task times. Based on MILEPOST process modules, the research developed a Work Unit Code (WUC) structure, providing the means to document key maintenance tasks which are required during the regeneration of the vehicle. Additionally, the research determined that significant parametric relationships exist between task times and certain influential vehicle design and human factors. Incorporated into the MILEPOST model, the identified prediction expressions provide a more precise evaluation of RMLV design alternatives

Ready To Roll: Southeastern Pennsylvania's Regional Electric Vehicle Action Plan

On-road internal combustion engine (ICE) vehicles are responsible for nearly one-third of energy use and one-quarter of greenhouse gas (GHG) emissions in southeastern Pennsylvania.1 Electric vehicles (EVs), including plug-in hybrid electric vehicles (PHEVs) and all-electric vehicles (AEVs), present an opportunity to serve a significant portion of the region's mobility needs while simultaneously reducing energy use, petroleum dependence, fueling costs, and GHG emissions. As a national leader in EV readiness, the region can serve as an example for other efforts around the country."Ready to Roll! Southeastern Pennsylvania's Regional EV Action Plan (Ready to Roll!)" is a comprehensive, regionally coordinated approach to introducing EVs and electric vehicle supply equipment (EVSE) into the five counties of southeastern Pennsylvania (Bucks, Chester, Delaware, Montgomery, and Philadelphia). This plan is the product of a partnership between the Delaware Valley Regional Planning Commission (DVRPC), the City of Philadelphia, PECO Energy Company (PECO; the region's electricity provider), and Greater Philadelphia Clean Cities (GPCC). Additionally, ICF International provided assistance to DVRPC with the preparation of this plan. The plan incorporates feedback from key regional stakeholders, national best practices, and research to assess the southeastern Pennsylvania EV market, identify current market barriers, and develop strategies to facilitate vehicle and infrastructure deployment