Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Myron Hecht

dblp:74/1055 · DBLP profile ↗
← Back
9ranked-venue papers
4as first author
0since 2021 · last 2019
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 4 · 1 first-authorSystems, architecture and hardware · 2 · 1 first-authorSecurity and privacy · 2 · 1 first-authorComputer networks · 1 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer architecture, parallel and distributed computing, and storage systems
2 papers
Hardware reliability and fault tolerance · 48% Distributed systems · 40% Embedded and real-time systems · 12%
Software engineering, system software, and programming languages
1 paper
Software testing · 100%

Topics — the 4 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Distributed systems
fault tolerance
0.011989
A Distributed Fault Tolerant Architecture for Nuclear Reactor Control and Safety Functions · RTSS 1989
Hardware reliability and fault tolerance
fault-tolerant architecture
0.011989
A Distributed Fault Tolerant Architecture for Nuclear Reactor Control and Safety Functions · RTSS 1989
Software testing
software reliability
0.011986
Software Reliability in the System Context · IEEE Trans. Software Eng. 1986
Hardware reliability and fault tolerance
reliability modeling
0.011986
Software Reliability in the System Context · IEEE Trans. Software Eng. 1986

Methods — techniques the papers use, named apart from their topics

systems approach · 0.0reliability modeling · 0.0failure modeling · 0.0redundancy · 0.0fault containment · 0.0
YearPublicationVenuePosition
2019 Automated Failure Modes and Effects Analysis using SysML for Industrial Computer Network Reliability and Cybersecurity
Myron Hecht, David Baum, Joseph Betser
IM1
2012 Defectivity profiling with dynamic COQUALMO: An explication and product quality retrospective
abstract
SUMMARY A software development organization's process trustworthiness can be enhanced through development project retrospectives or postmortems, which seek to produce lessons from mistakes and successes in the project performance. Tool support for such retrospectives is usually limited to qualitative analysis. A new model, Dynamic COQUALMO, offers quantitative support through a defectivity profile that can be calibrated to a project's actual profile of defects found over time. The model inputs can then be varied to represent alternative project decisions and conditions, providing a basis for estimating the effects of project improvements on product quality. This paper describes Dynamic COQUALMO and demonstrates its use in a project retrospective. Copyright © 2010 John Wiley & Sons, Ltd.
Dan X. Houston, Douglas J. Buettner, Myron Hecht
J. Softw. Evol. Process.3
2011 A Tool Set for Integrated Software and Hardware Dependability Analysis Using the Architecture Analysis and Design Language (AADL) and Error Model Annex
abstract
Cyberphysical (embedded) computer system availability and reliability can be modeled and assessed using the Architecture Analysis and Design Language (AADL) and its Error Model Annex. AADL can represent systems at multiple levels of abstraction. Therefore, analyses can be performed early and often throughout the development process thereby minimizing the cost and schedule impact of changes. We discuss how the AADL and its Error Model Annex can be used for automated generation of a reliability/dependability model. We then describe a tool set to graphically create AADL system architecture and error behavior files that are then transformed into Stochastic Petri Nets (SPN) and Stochastic Activity Network (SAN) representations and demonstrate its use using a generic satellite as an example.
Myron Hecht, Alexander Lam, Chris Vogl
ICECCS1
2008 Using an assurance case to support independent assessment of the transition to a new GPS ground control system
abstract
We describe a specific application of assurance cases to the problem of ensuring that a transition from a legacy system to its replacement will not compromise mission assurance objectives. The application in question was the transition of the Global Positioning System (GPS) to a new ground-control system. The transition, which took place over five days, required uninterrupted control of the GPS satellite constellation while control was transferred from a 1970s-era mainframe to a distributed architecture. We created an assurance case so that the procedural documentation we had could be restructured into a form amenable to analysis. The analysis concluded that there were no major hazards; this conclusion was validated by a successful transition.
Elisabeth A. Nguyen, William S. Greenwell, Myron Hecht
DSN3
2000 OFTT: A Fault Tolerance Middleware Toolkit for Process Monitoring and Control Windows NT Applications
abstract
Describes OFTT (OLE Fault Tolerance Technology), a fault tolerance middleware toolkit running on the Microsoft Windows NT operating system that provides the required fault tolerance for networked PCs in the context of industrial process monitoring and control applications. It is based on the Microsoft Component Object Model (COM) and consists of components that perform checkpoint-saving, failure detection, recovery and other fault tolerance functions. The ease with which this technology can be incorporated into an application represents the primary innovation. It is hoped that, by making fault tolerance more compatible with standard software architectures, more reliable PC-based monitoring and control systems can be built conveniently.
Myron Hecht, Xuegao An, Yutao He
DSN1
1995 Dependability assessment for decentralized systems
abstract
Conventional dependability measures, such as reliability or availability, assume that the equipment characterized by the measure is either operational or has failed. This dichotomy does not hold for decentralized or distributed systems because these can operate in modes in which partial or degraded service is furnished. Whether a specific degraded mode should be counted as "operational" or "failed" is a subjective decision, but this decision can make a large difference in the dependability assessment. Examples show that this affects not only numerical reporting, but also the selection of reliability improvements. A weighted averaging of the dependability measures obtained under various failure criteria is seen to be a workable method for reliability assessment that provides much more stable measures than can be obtained by selection of a single failure criterion.>
Herbert Hecht, Myron Hecht
ISADS2
1994 V&V in defense and commercial projects
abstract
Verification and validation activities in defense projects are compared with those in the nuclear power plant industry. A significant difference is that in most defense projects the V&V effort is funded directly by the sponsor whereas in the nuclear power industry the major responsibility for V&V resides with the developer. This may cause a shift in V&V emphasis from early life cycle stages (in defense) to later phases (in the nuclear power industry). The paper shows that there are sufficient similarities to make development of dual use technologies possible.>
Herbert Hecht, Myron Hecht
ISSRE2
1989 A Distributed Fault Tolerant Architecture for Nuclear Reactor Control and Safety Functions
abstract
A fault-tolerant architecture that provides tolerance to a broad scope of hardware, software, and communications faults is being developed. This architecture relies on widely available commercial operating systems, local area networks, and software standards. Thus development time is significantly shortened, and modularity allows for continuous and inexpensive system enhancement throughout the expected 20-year life. The fault-containment and parallel-processing capabilities of computers are exploited to provide a high-performance, high-availability network capable of tolerating a broad scope of hardware, software, and operating system faults. The system can tolerate all but one known (and avoidable) single fault, two known and avoidable dual faults, and it will detect all higher-order fault sequences and provide diagnostics to allow for rapid manual recovery.>
Myron Hecht, J. Agron, S. Hochhauser
RTSS1
1986 Software Reliability in the System Context
abstract
A systems approach to the analysis and control of software reliability is described which is intended to supplement conventional software reliability models which focus on program attributes under the control of the software professionals. A review of software reliability experience during the operations and maintenance (O&M) phase is presented. This is followed by a description of a basic failure model that supports a unified approach to software and hardware reliability and of the implications of that model for conventional software reliability approaches. Next, the effect of management activities on reliability is investigated, and an outline of a combined hardware/software reliability model suitable for the planning phase is presented.
Herbert Hecht, Myron Hecht
IEEE Trans. Software Eng.2