{"title":"Model-Based System Engineering and Software System Safety Workshop","authors":"Barry Hendrix, Saralyn Dwyer, D. West","doi":"10.56094/jss.v53i3.110","DOIUrl":"https://doi.org/10.56094/jss.v53i3.110","url":null,"abstract":"The G-48 System Safety Committee sponsored a Model-Based System Engineering (MBSE) and Software System Safety (SSS) workshop, hosted by A-P-T Research, Inc. (APT) in Huntsville, Alabama, on May 2-3, 2017. The idea of this workshop evolved at the 34th International System Safety Conference (ISSC) in Orlando, Florida, during presentations and a paper by Barry Hendrix, which noted that the MBSE needs to include more system safety and software system safety processes. An action recorded under urgent-need topics by International System Safety Society (ISSS) Fellow Dave West at the G-48 meeting in Orlando resulted in volunteers to host and coordinate the workshop. \u0000The MBSE SSS workshop consisted of a panel of seven subject matter experts. Approximately 40 attendees were present and more than 70 people viewed the workshop via a NASA live video streaming feed. The MBSE SSS panel consisted of Barry Hendrix, APT; Dr. Fayssal Safie, APT; Dr. Donna Havrisik, Government Agency System Engineering; Josh McNeil, AMRDEC Software Engineering Directorate (SED); David Arterburn, University of Alabama Huntsville; Joe Hale, NASA; and Paul Gill, NASA. Many attendees were from local Redstone Arsenal agencies, such as AMCOM, PEO Missiles & Space, and the Missile Defense Agency. Several contractors from companies within Cummings Research Park also attended. Special out-of-town guests included Peggy Rogers, U.S. Navy Software System Safety Technical Review Panel (SSTRP); Bob McAlister, U.S. Air Force; and Lynece Pfledderer, Lockheed Martin (LM), along with five other LM attendees from Texas, Florida and Connecticut.","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126506927","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"President's Message","authors":"Charles Muniak","doi":"10.56094/jss.v53i3.103","DOIUrl":"https://doi.org/10.56094/jss.v53i3.103","url":null,"abstract":"The recent International System Safety Conference (ISSC) in Albuquerque, New Mexico was a thought-provoking event. \u0000Professor Edward Gibson gave the first keynote address. He described the engineering programs at Arizona State University (ASU) and some possible relations with the system safety discipline. Members of the Executive Council (EC) had additional meetings with Dr. Gibson to explore including system safety concepts in the school’s engineering curriculum, as well as the relationship between ASU and the ISSS. \u0000One of the most venerable members of our Society, John Rankin, gave several presentations on hazard analysis. He also provided a viewing of the movie Fate is the Hunter and explained how it helped inspire him to invent Sneak Circuit Analysis. \u0000The Conference featured many excellent papers and tutorials. One that received a good deal of positive commentary was on the topic of “gamification” in teaching software safety analysis. The authors, Brian Connell and David Musgrave, have developed an entertaining and effective way to train on this topic.","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130797793","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Design-Based Safety","authors":"D. maccollum","doi":"10.56094/jss.v53i3.105","DOIUrl":"https://doi.org/10.56094/jss.v53i3.105","url":null,"abstract":"The prevention of unintended occurrences — usually identified as “accidents” that result in personal injury or damage — is usually considered as “safety.” The most common approach to safety focuses on behavior that attempts to prevent accidents from occurring with the involvement of users and operators. In many circumstances, this has been the only option to prevent accidents. \u0000Technology has provided us with many machines, and society relies more and more on complex equipment which now is entering an age of automation. Going forward, safe design will be the key to preventing accidents. The transition from behavior-based safety to design-based safety is not easy, as both the public and engineering professionals lack the wide scope and diversity of knowledge needed to ensure for safe design in complex systems. Traditionally, many designers and manufacturers have considered the cause of accidents to be the ineptness of users/operators. As more and more of the error-producing tasks become automated, the measuring of safe performance becomes an issue of reliability. The new concept of safety shifting from behavior-based to design-based safety now becomes a whole new ball game.","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"19 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116242852","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"TBD","authors":"Charles Hoes, Lee Flint","doi":"10.56094/jss.v53i3.106","DOIUrl":"https://doi.org/10.56094/jss.v53i3.106","url":null,"abstract":"During the past couple of years, I have been involved with things such as introducing system safety concepts into engineering courses. This, and other activities, has caused me to question what it is that makes the profession of system safety “special” — or at least different — from other approaches to achieving safety. My first reaction is that it is something you recognize when you see it. It usually takes only a quick review of a safety plan or effort to determine if it is a “system safety” effort. This isn’t always helpful when talking to those that haven’t “seen the light.” I wonder if there isn’t something fundamentally different between “traditional” safety (whatever that might be) and “system safety.”","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130487075","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Pushing the Boundaries of System Safety","authors":"Charles Muniak","doi":"10.56094/jss.v53i3.111","DOIUrl":"https://doi.org/10.56094/jss.v53i3.111","url":null,"abstract":"The 35th Annual ISSC was held August 21-25, 2017 in Albuquerque, New Mexico. This year’s theme was intended not only to redefine how system safety is applied in different domains, but to also reach into our past for lessons learned and go beyond our present thinking as we confront new challenges. It was intended to push the boundaries of the system of safety, as well as how we think about the safety of systems. \u0000Highlights of the 35th International System Safety Conference","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"2020 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121329492","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"System Safety in Healthcare","authors":"D. Raheja, M. Escano","doi":"10.56094/jss.v53i3.107","DOIUrl":"https://doi.org/10.56094/jss.v53i3.107","url":null,"abstract":"The objective of performing Failure Mode and Effects Analysis (FMEA) is to use sound risk management principles, coupled with innovative solutions that can assure high return on investment (ROI). Quality Guru Philip Crosby wrote in his book, Quality is Free, that quality is free if you do the right things at the right time. Essentially, the savings from avoiding fixes, process changes and lawsuits are much higher than the cost of doing things right. The principles of sound risk management, experienced by this paper’s co-author Dev Raheja as an international engineering management consultant over 30 years, include: \u0000 \u0000Identifying risks \u0000Assessing risks \u0000Mitigating risks \u0000Orchestrating risk management \u0000Aiming at high ROI without compromising safety \u0000","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129541929","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"How Safe is Safe Enough? Acceptable Safety Criteria From an Engineering and Legal Perspective","authors":"Martin Chizek","doi":"10.56094/jss.v53i3.108","DOIUrl":"https://doi.org/10.56094/jss.v53i3.108","url":null,"abstract":"Manufacturers have a vested interest in the safety of their customers, and in protecting their reputation for producing safe products. An additional incentive to produce safe products is avoiding liability when their product is involved in an accident or mishap that results in personal injury and/or property damage. While it is often said that one must never compromise on safety, the fact remains that any product must necessarily be a balance between the level of safety desired and the cost and performance impact of achieving that level of safety. The product manufacturer must make a determination: Is this product (or technology) acceptably safe within the context of current consumer expectations as well as the legal/regulatory framework? Is the residual risk tolerable? This paper presents a methodology to address those questions by reviewing the publicly available information of a recent automotive product liability case, and evaluating whether the product design met current legal and safety engineering best practices.","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"354 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132553276","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Defending Against Firmware Cyber Attacks on Safety-Critical Systems","authors":"Chris W. Johnson, Maria Evangelopoulou","doi":"10.56094/jss.v54i1.83","DOIUrl":"https://doi.org/10.56094/jss.v54i1.83","url":null,"abstract":"In the past, it was not possible to update the underlying software in many industrial control devices. Engineering teams had to “rip and replace” obsolete components. However, the ability to make firmware updates has provided significant benefits to companies who use Programmable Logic Controllers (PLCs), switches, gateways and bridges, as well as an array of smart sensor/actuators. While these updates — which include security patches when vulnerabilities are identified in existing devices — can be distributed by physical media, they are increasingly downloaded over Internet connections. These mechanisms pose a growing threat to the cyber security of safety-critical applications, which is illustrated by recent attacks on safety-related infrastructures across the Ukraine. This paper explains how malware can be distributed within firmware updates. Even when attackers cannot reverse engineer the code necessary to disguise their attack, they can undermine a device by forcing it into a constant upload cycle in which the firmware installation never terminates. In this paper, we present means of mitigating the risks of firmware attacks on safety-critical systems as part of wider initiatives to secure national critical infrastructures. Technical solutions, including firmware hashing, must be augmented by organizational measures to secure the supply chain within individual plants, across companies and throughout safety-related industries.","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"1 5","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134505963","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Organizational Problems: Potential Causes and Unintentional Consequences — Some Personal Views","authors":"Malcolm Jones","doi":"10.56094/jss.v53i2.92","DOIUrl":"https://doi.org/10.56094/jss.v53i2.92","url":null,"abstract":"It is not uncommon today for companies to suffer a range of program difficulties, which broadly lie under the headings of “lack of efficiency,” “schedules moving to the right,” “cost overruns” and “having to repair past poor decisions.” Although senior management may appear to be well aware of these problems and their consequences, inherent difficulties in rectifying these problems exist. Often, responses are more directed to corrective action and damage limitations rather than assessing what is wrong at a fundamental level. Of course, most — if not all — safety mishaps can be associated with technical or human faults. However, it is also generally accepted that these are not the root-cause reasons for mishaps but rather, a result of faults higher up in the organization’s structure.","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-07-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123609184","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Notes on Society History","authors":"Rex B. Gordon","doi":"10.56094/jss.v53i2.89","DOIUrl":"https://doi.org/10.56094/jss.v53i2.89","url":null,"abstract":"The word “esteemed” — “to be highly regarded with respect” — certainly describes Jerry Lederer, a friend and colleague that I had the privilege of spending many hours with during his retirement years prior to his passing in 2004 at the age of 102. He was extremely modest about his accomplishments, which are legendary in the fields of flight and aerospace safety.","PeriodicalId":250838,"journal":{"name":"Journal of System Safety","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-07-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129179415","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
