"We Are Prisoners in Our Own Homes": Connecting the Environment, Gender-Based Violence and Sexual and Reproductive Health Rights to Sport for Development and Peace in Nicaragua

York University Librarie

Structural factoring approach for analyzing stochastic networks

The problem of finding the distribution of the shortest path length through a stochastic network is investigated. A general algorithm for determining the exact distribution of the shortest path length is developed based on the concept of conditional factoring, in which a directed, stochastic network is decomposed into an equivalent set of smaller, generally less complex subnetworks. Several network constructs are identified and exploited to reduce significantly the computational effort required to solve a network problem relative to complete enumeration. This algorithm can be applied to two important classes of stochastic path problems: determining the critical path distribution for acyclic networks and the exact two-terminal reliability for probabilistic networks. Computational experience with the algorithm was encouraging and allowed the exact solution of networks that have been previously analyzed only by approximation techniques

Device for testing continuity and/or short circuits in a cable

A device for testing current paths is attachable to a conductor. The device automatically checks the current paths of the conductor for continuity of a center conductor, continuity of a shield and a short circuit between the shield and the center conductor. The device includes a pair of connectors and a circuit to provide for testing of the conductive paths of the cable. The pair of connectors electrically connects the conductive paths of a cable to be tested with the circuit paths of the circuit. The circuit paths in the circuit include indicators to simultaneously indicate the results of the testing

Mending the Gap, An Effort to Aid the Transfer of Formal Methods Technology

Formal methods can be applied to many of the development and verification activities required for civil avionics software. RTCA/DO-178B, Software Considerations in Airborne Systems and Equipment Certification, gives a brief description of using formal methods as an alternate method of compliance with the objectives of that standard. Despite this, the avionics industry at large has been hesitant to adopt formal methods, with few developers have actually used formal methods for certification credit. Why is this so, given the volume of evidence of the benefits of formal methods? This presentation will explore some of the challenges to using formal methods in a certification context and describe the effort by the Formal Methods Subgroup of RTCA SC-205/EUROCAE WG-71 to develop guidance to make the use of formal methods a recognized approach

Certification

Objective 1: Provide regulators with a methodology for development of airworthiness requirements for certification of UAS. a) Rationale: a comprehensive methodology does not currently exist to support development of regulation for certification of UAS. Regulation is essential to enable routine access to the NAS. b) Approach: 1) assess existing approaches and classification schemes for deriving acceptable means of compliance to airworthiness requirements. 2) investigate a service-based approach to classification of UAS. 3) conduct comparative analysis of different methodologies. 4) work with FAA to determine best approach and conduct case study. 5) participate in regulatory/standards organizations developing safety and performance requirements for UAS. Objective 2: Provide regulators and industry with hazard and risk-related data to support criteria for UAS type design. a) Rationale: There is presently little UAS specific data (incident, accident, and reliability), especially in a civil context, to support risk assessment and development of standards and regulation. b) Approach: Identify gaps in existing data, provide measured data as needed, and formulate recommendations by: 1) evaluating UAS incident/accident data collection efforts and determining additional support necessary for regulation. 2) assessing UAS-specific hazards and risks. 3) evaluating need for reliability data for UAS-unique systems, components and subsystem, and determining additional measurement requirements. 4) developing guidance and best practices for UAS type design

GCS programmer's manual

A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities

Software verification plan for GCS

This verification plan is written as part of an experiment designed to study the fundamental characteristics of the software failure process. The experiment will be conducted using several implementations of software that were produced according to industry-standard guidelines, namely the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, Software Consideration in Airborne Systems and Equipment Certification, for the development of flight software. This plan fulfills the DO-178A requirements for providing instructions on the testing of each implementation of software. The plan details the verification activities to be performed at each phase in the development process, contains a step by step description of the testing procedures, and discusses all of the tools used throughout the verification process

The relationship between oxidised LDL, endothelial progenitor cells and coronary endothelial function in patients with CHD

Objective The balance between coronary endothelial dysfunction and repair is influenced by many protective and deleterious factors circulating in the blood. We studied the relationship between oxidised low-density lipoprotein (oxLDL), circulating endothelial progenitor cells (EPCs) and coronary endothelial function in patients with stable coronary heart disease (CHD). Methods 33 patients with stable CHD were studied. Plasma oxLDL was measured using ELISA, coronary endothelial function was assessed using intracoronary acetylcholine infusion and EPCs were quantified using flow cytometry for CD34+/KDR+ cells. Results Plasma oxLDL correlated positively with the number of EPCs in the blood (r=0.46, p=0.02). There was a positive correlation between the number of circulating EPCs and coronary endothelial function (r=0.42, p=0.04). There was no significant correlation between oxLDL and coronary endothelial function. Conclusions Plasma levels of oxLDL are associated with increased circulating EPCs in the blood of patients with CHD, which may reflect a host-repair response to endothelial injury. Patients with stable CHD had a high prevalence of coronary endothelial dysfunction, which was associated with lower numbers of circulating EPCs, suggesting a mechanistic link between endothelial dysfunction and the pathogenesis of atherosclerosis

Guidance for Using Formal Methods in a Certification Context

This paper discusses some of the challenges to using formal methods in a certification context and describes the effort by the Formal Methods Subgroup of RTCA SC-205/EUROCAE WG-71 to propose guidance to make the use of formal methods a recognized approach. This guidance, expected to take the form of a Formal Methods Technical Supplement to DO-178C/ED-12C, is described, including the activities that are needed when using formal methods, new or modified objectives with respect to the core DO-178C/ED-12C document, and evidence needed for meeting those objectives