Maintainability and Maintenance—A Case Study on Mission Critical Aircraft and Engine Components

2003 ◽  
pp. 377-398
Author(s):  
U. Dinesh Kumar ◽  
John Crocker
Keyword(s):  
Mission Critical ◽  
Engine Components

How Do I Assess Our Cyber Risk?

2021 ◽  
pp. 41-57
Author(s):  
Gregory Falco ◽  
Eric Rosenbach
Keyword(s):  
Communication Networks ◽  
Impact Analysis ◽  
Critical Systems ◽  
Safety Critical ◽  
Safety Critical Systems ◽  
Mission Critical ◽  
Delivery Networks ◽  
Cyber Risk ◽  
Digital Assets

The question “How do I assess our cyber risk?” addresses how to identify and characterize cyber risk unique to an organization’s critical systems, networks, and data. The chapter begins with a case study about a cyberattack on Ukraine’s electric grid. It details risk assessment for three types of critical systems: mission-critical systems, business-critical systems, and safety-critical systems. It explains the three types of networks critical to many organizations: business and administrative networks, operational and service delivery networks, and communication networks. In outlining the “CIA triad,” it shows how cyber risk can be characterized as a confidentiality, integrity, or availability issue relating to digital assets. Further, it describes how to assess the importance of different digital assets and how to prioritize them using a business impact analysis (BIA). The chapter concludes with real-world Embedded Endurance strategy lessons Rosenbach gained in Saudi Arabia in the wake of one of the world’s most destructive cyberattacks.

The Launch of Web-based Collaborative Decision Support at NASA

2008 ◽  
pp. 113-125
Author(s):  
Irma Becerra-Fernandez ◽  
Matha Del Alto ◽  
Helen Stewart
Keyword(s):  
Knowledge Management ◽  
Decision Support ◽  
Decision Makers ◽  
Web Based ◽  
Management Platform ◽  
Individual Person ◽  
Mission Critical ◽  
Multiple Domains ◽  
Collaborative Decision

Today, organizations rely on decision makers to make mission-critical decisions that are based on input from multiple domains. The ideal decision maker has a profound understanding of specific domains coupled with the experience that allows him or her to act quickly and decisively on the information. Daily, decision makers face problems and failures that are too difficult for any individual person to solve; therefore, teams are now required who share their knowledge in spontaneous collaborations. Since requisite expertise may not all reside in the same organization, nor be geographically colocated, virtual networked teams are needed. This chapter presents a case study describing the development and use of Postdoc, the first Web-based collaborative and knowledge management platform deployed at NASA.

Migrating mission-critical applications in federated cloud: a case study

2018 ◽  
Vol 12 (4) ◽  
pp. 379
Author(s):  
Alba Amato ◽  
Rocco Aversa ◽  
Massimo Ficco ◽  
Salvatore Venticinque
Keyword(s):  
Mission Critical

scholarly journals Multi-View Software Architecture Design: Case Study of a Mission-Critical Defense System

2015 ◽  
Vol 8 (4) ◽  
pp. 12 ◽  
Author(s):  
Kadir Alpaslan Demir
Keyword(s):  
Software Architecture ◽  
Case Studies ◽  
System Development ◽  
Architecture Design ◽  
Defense System ◽  
Architectural Style ◽  
Quality Requirements ◽  
Mission Critical ◽  
Software Architecture Design

As the use of software intensive systems increase in our daily lives, the systems are getting larger and larger every day. A significant portion of these software systems in use are medium to large in size and complexity. Most of them are also becoming a part of a system of systems. In addition to satisfying of a set of functional requirements, the users expect a certain level of quality in these systems. Quality requirements are also referred as nonfunctional requirements. Adequate satisfaction of quality requirements can be achieved via a careful software architecture design. Since the quality requirements are multi-faceted, the software architects have to consider many diverse aspects and provide a software architecture solution that can optimally satisfy both functional and nonfunctional requirements. Therefore, such a solution requires a multi-view software architecture design as the result of a careful systematic system development effort. Research reports with detailed case studies are helpful in bridging the gap between academia and industry. Research studies including a carefully designed real-world sample case studies will help practitioners and engineers to understand the theoretical concepts and apply the novel research findings in their practices. Therefore, in this study, we explain the systematic multi-view software architecture design with the help of a detailed mission-critical defense system development case study. The mission critical system in the case study is a Mine Neutralization System for navy mine hunting ships. In the study, we explain the multi-view software system architecture design step by step starting with identifying the system context, requirements, constraints, and quality expectations. We further outline the strategies, techniques, designs, and rationales used to satisfy a diverse set of requirements with a particular software architecture pattern. In addition, we introduce a novel architectural style named as a star-controller architectural style. We explain the use of the style with a related discussion.

scholarly journals Metamorphic Testing Integer Overflow Faults of Mission Critical Program: A Case Study

2013 ◽  
Vol 2013 ◽  
pp. 1-6 ◽  
Author(s):  
Zhanwei Hui ◽  
Song Huang ◽  
Zhengping Ren ◽  
Yi Yao
Keyword(s):  
Collision Avoidance ◽  
Traditional Method ◽  
Property Testing ◽  
Testing Methods ◽  
Metamorphic Testing ◽  
Testing Method ◽  
Safety Property ◽  
Mission Critical ◽  
Collision Avoidance System

For mission critical programs, integer overflow is one of the most dangerous faults. Different testing methods provide several effective ways to detect the defect. However, it is hard to validate the testing outputs, because the oracle of testing is not always available or too expensive to get, unless the program throws an exception obviously. In the present study, the authors conduct a case study, where the authors apply a metamorphic testing (MT) method to detect the integer overflow defect and alleviate the oracle problem in testing critical program of Traffic Collision Avoidance System (TCAS). Experimental results show that, in revealing typical integer mutations, compared with traditional safety property testing method, MT with a novel symbolic metamorphic relation is more effective than the traditional method in some cases.

Risk of adopting mission-critical OSS applications: an interpretive case study

2014 ◽  
Vol 34 (4) ◽  
pp. 477-512 ◽  
Author(s):  
Placide Poba-Nzaou ◽  
Louis Raymond ◽  
Bruno Fabi
Keyword(s):  
Risk Management ◽  
Open Source ◽  
Resource Planning ◽  
Adoption Process ◽  
Content Type ◽  
It Risk Management ◽  
Interpretive Case Study ◽  
Mission Critical ◽  
It Risk

Purpose – This study aims to explore the process of open source software (OSS) adoption in small- and medium-sized enterprises (SMEs), and more specifically open source enterprise resource planning (ERP) as a “mission critical” OSS application in manufacturing. It also addresses the fundamental issue of ERP risk management that shapes this process. Design/methodology/approach – The approach is done through an interpretive case study of a small Canadian manufacturer that has adopted an open source ERP system. Findings – Interpreted in the light of the IT risk management, OSS and packaged application adoption literatures, results indicate that the small manufacturer successfully managed the adoption process in a rather intuitive manner, based on one guiding principle and nine practices. In analyzing the data, diffusion of innovation theory appeared to fit rather well with the situation observed and to offer rich insights to explain the mission-critical OSS adoption process. Research limitations/implications – A single case study of successful IT adoption should be eventually counterbalanced by future cases considered to be partial or total failures, using a wider multiple case study approach for comparative purposes. And this should include alternative theoretical interpretations and more detailed empirical work on the extent to which the distinctive features of OSS make its adoption more or less risk-laden. This initial effort should also be followed by further research on mission-critical OSS adoption in contexts other than SMEs (e.g. healthcare organizations) and other than ERP (e.g. customer-relationship management). Practical implications – This research confirms that open source is a credible alternative for SMEs that decide willingly or under external pressure to adopt a mission-critical system such as ERP. Moreover, it suggests that a high level of formalization is not always necessary. Originality/value – The authors argue that rich insights into the dynamics of the mission-critical OSS adoption process can be obtained by framing this process within an IT risk management context.

scholarly journals Quality specification and metrication, results from a case-study in a mission-critical software domain

2010 ◽  
Vol 18 (4) ◽  
pp. 469-490 ◽  
Author(s):  
Jos J. M. Trienekens ◽  
Rob J. Kusters ◽  
Dennis C. Brussel
Keyword(s):  
Mission Critical
Sign in / Sign up

Export Citation Format

Share Document