The SHARP evolution: development of the Sierra Hotel Aviation reporting program from the deck plates

Due to constant changes in the military environment, operations tempo, resource limitations, and leadership directives, the fashion in which the military computes its training and readiness is constantly in flux. Previous readiness calculations were accomplished from simple two-dimensional models of qualifications by dates. With the increase of more sophisticated requirements, a new six-dimensional model of training and readiness was invented to compute and even predict future readiness levels, for aviation as outlined in the Training and Readiness Manual CNAP INST/CNAL INST 3500 Series. Due to the complex requirements of the new T & R Manual, a software tool was required to track post-flight data and compute aviation combat readiness. The T & R Manual is revised at irregular intervals by independent type wings, resulting in a constant requirement to re-develop existing readiness models and tracking programs. To fulfill this requirement, a team of Naval Aviators with a combination of software engineering expertise, military operations, and project management experience was created to develop a modular based rapid prototype application. This thesis will review the unique software development models utilized in rapid military application development, contrasting with existing application development models, and the utilization of non-traditional techniques to meet defense readiness requirements. This thesis will also review other readiness tracking systems to compare and contrast the ability to meet the diverse needs of fleet readiness models through efficient software development.http://archive.org/details/thesharpevolutio109459424U.S. Navy (U.S.N.) author.Approved for public release; distribution is unlimited

Realising the open virtual commissioning of modular automation systems

To address the challenges in the automotive industry posed by the need to rapidly manufacture more product variants, and the resultant need for more adaptable production systems, radical changes are now required in the way in which such systems are developed and implemented. In this context, two enabling approaches for achieving more agile manufacturing, namely modular automation systems and virtual commissioning, are briefly reviewed in this contribution. Ongoing research conducted at Loughborough University which aims to provide a modular approach to automation systems design coupled with a virtual engineering toolset for the (re)configuration of such manufacturing automation systems is reported. The problems faced in the virtual commissioning of modular automation systems are outlined. AutomationML - an emerging neutral data format which has potential to address integration problems is discussed. The paper proposes and illustrates a collaborative framework in which AutomationML is adopted for the data exchange and data representation of related models to enable efficient open virtual prototype construction and virtual commissioning of modular automation systems. A case study is provided to show how to create the data model based on AutomationML for describing a modular automation system

Civil aircraft advanced avionics architectures - an insight into saras avionics, present and future perspective

Traditionally, the avionics architectures being implemented are of federated nature, which means that each avionics function has its own independent, dedicated fault-tolerant computing resources. Federated architecture has great advantage of inherent fault containment and at the same time envelops a potential risk of massive use of resources resulting in increase in weight, looming, cost and maintenance as well. With the drastic advancement in the computer and software technologies, the aviation industry is gradually moving towards the use of Integrated Modular Avionics (IMA) for civil transport aircraft, potentially leading to multiple avionics functions housed in each hardware platform. Integrated Modular Avionics is the most important concept of avionics architecture for next generation aircrafts. SARAS avionics suite is purely federated with almost glass cockpit architecture complying to FAR25. The Avionics activities from the inception to execution are governed by the regulations and procedures under the review of Directorate General of Civil Aviation (DGCA). Every phase of avionics activity has got its own technically involvement to make the system perfect. In addition the flight data handling, monitoring and analysis is again a thrust area in the civil aviation industry leading to safety and reliability of the machine and the personnel involved. NAL has been in this area for more than two decades and continues to excel in these technologies

Supporting the automated generation of modular product line safety cases

Abstract The effective reuse of design assets in safety-critical Software Product Lines (SPL) would require the reuse of safety analyses of those assets in the variant contexts of certification of products derived from the SPL. This in turn requires the traceability of SPL variation across design, including variation in safety analysis and safety cases. In this paper, we propose a method and tool to support the automatic generation of modular SPL safety case architectures from the information provided by SPL feature modeling and model-based safety analysis. The Goal Structuring Notation (GSN) safety case modeling notation and its modular extensions supported by the D-Case Editor were used to implement the method in an automated tool support. The tool was used to generate a modular safety case for an automotive Hybrid Braking System SPL

An experience of modularity through design

We aim to utilise the experiences of a marine industry-based design team to determine the need for research into a modular design methodology in an industrial environment. In order to achieve this we couple the outcome of a current design project with the findings of a recent literature survey with the objectives of firstly, clarifying why a methodology is required and, secondly, defining the key elements which the methodology would have to realise or address. The potential benefits of modularity have long been recognised in the shipbuilding industry. Many shipbuilders adopt a 'module' approach to ship construction whereby the ship structure is separated into a number of large structural 'blocks' to ease manufacture and manoeuvrability during construction. However, as understanding of the capabilities of modularity as a design tool develops there is increased interest in capitalising on the differing life phase benefits of modularity such as reduced design costs and time, increased ease of maintenance, upgrade, re-use, redesign and standardisation across individual products and product families. This is especially pertinent in naval shipbuilding where the maintenance of a class of ship requires that all previously designed ships in that class must be of similar outfitting and must be able to interface with the new ship, in terms of propulsion, weapons, communications and electronics, and thus often require some form of retrofit. Therefore, many shipbuilders are moving from viewing modularity as a purely 'manufacturing' principle to a design centred principle. However, as noted by Chang and Ward 'none of the design theories or tools in the mechanical world serves as an articulate procedure for designers to follow in practising modular design'. Thus, despite the identification of a need to introduce modular principles at an earlier stage than detail design and construction, there is little aid in the form of tools, techniques and methodologies for designers in practice

Formal Reasoning Using an Iterative Approach with an Integrated Web IDE

This paper summarizes our experience in communicating the elements of reasoning about correctness, and the central role of formal specifications in reasoning about modular, component-based software using a language and an integrated Web IDE designed for the purpose. Our experience in using such an IDE, supported by a 'push-button' verifying compiler in a classroom setting, reveals the highly iterative process learners use to arrive at suitably specified, automatically provable code. We explain how the IDE facilitates reasoning at each step of this process by providing human readable verification conditions (VCs) and feedback from an integrated prover that clearly indicates unprovable VCs to help identify obstacles to completing proofs. The paper discusses the IDE's usage in verified software development using several examples drawn from actual classroom lectures and student assignments to illustrate principles of design-by-contract and the iterative process of creating and subsequently refining assertions, such as loop invariants in object-based code.Comment: In Proceedings F-IDE 2015, arXiv:1508.0338