Previously developed software

In this paper, a software component is considered to be an entity that has a predefined and specified bormdary and which is atomic, in the sense that we do not have the option to split the component into sub-components. We make no special assumptions whether the component is available in binary format or as source code. The context we are interested in is essentially an Off-The-Shelf (OTS) situation where we have access to previously developed software (PDS) components which we want to combine, possibly in... 

Only Limited Variability Languages (LVL) are allowed for the application software according lEC 62061 and if previously developed software library functions are used in the design, their suitability in satisfying the specification of requirements for software safety shall be justified. 

Much of the thinking behind lEC 61508 and DEF STAN 00-55 seems to be targeted at real-time, embedded software. Modem safety-related software can be an application mnning on a standard desktop operating system, it can be previously developed software re-used in a new application, it can be part of a complex system-of-systems Demonstrating the safety of these types of system introduces new issues, which 61508 and 00-55 do not address. 

Components sourced from other companies that use Previously Developed Software (PDS) This issue most often arises due to the purchase of sensors and actuators which have embedded software - the so-called Smart Sensor problem. The difficulty here is that the pedigree of the PDS may be unknown, or the quality control system used by the supplier company may be considered inadequate, or else the supplier company may be reluctant to divulge information about the software because they consider it threatens their Intellectual Property (IP). Acronym alert Software-based devices can also be known as COTS devices - since they use Commercial Off The Shelf software, as opposed to bespoke software. Software whose origins are unknown can be called SOUP - Software Of Unknown Provenance. 

The literature on the response surface methodology and the design of experiments is quite extensive and the reader is referred to the hterature for a more in-depth discussion. The intent here is to demonstrate how the previously developed software can be used in this type of analysis. This example has also illustrated the use of the actv[] table as input to nlstsqQ for eliminating flic use of particular parameters from a least squares data fitting analysis. 

Contributors to HEEP could be research institutions who are already involved in activities on hydrogen production, and previous developers of DEEP and other related software. The IAEA is contracting some recognised experts to assist in all stages of HEEP development. 

Software developed and validated by the user should also be revalidated by the user. Principally, software redevelopment and testing should follow the same procedure as for newly developed software. Procedures should include information on who authorizes changes, who executes the changes, and who can finally release the changed version. Compared to new software, the amount of testing can be reduced through intensive reuse of previously developed test hies and test procedures. 

By and large, software development in CAMD has not kept pace with new hardware developments. Several reasons for this can be imagined. As mentioned previously, CAMD software and methodology usually originates in a university setting, and most often in a chemistry group. Chemists are usually not computer science... 

In modern reactor analysis, the calculations previously outlined are performed on computer codes specially written for the purpose. For most actual operating reactors, these computer codes are proprietary to the reactor vendors (or, in some cases, the utilities that own the reactor) and are not generally available to outside analysts. However, there are computer codes available from Reactor Safety Information Computational Center (RSICC), the computer code distribution center at the Oak Ridge National Laboratory, which can be used for reactor analysis. For the most part, the available computer codes are those that were developed at the various national laboratories (Oak Ridge National Laboratory [ORNL], Los Alamos National Laboratory [LANL], Argonne National Laboratory [ANL]), although some university and privately developed software is also available. 

Safety standards acknowledge the economic need to employ previously developed systems, functions and components [12] [13] [14] [15]. In civil aerospace for example, systems may be reused across different aircraft types, without the need for additional assessment, provided that evidence of similar design, installation, application and operation can be produced [15]. Otherwise, the safety assessment process should be performed to examine the impact of the reusable systems on the aircraft functions. Also in civil aerospace, particularly for airborne software, the American Federal Aviation Administration (FAA) created an Advisory Circular (AC), offering means to satisfy the requirements of the aerospace software guidance DO-178B regarding the use of reusable software components [16]. 

The techniques presented here are intended to be easy to implement with pencil and paper. As such, they may not be the best, although they are very likely the most economical. The use of recently developed software programs is gaining acceptance, some of these programs able to do very sophisticated data manipulation and plotting. As mentioned previously, the advice or direction of a professional statistician is always to be considered, especially for very complex problems. 

A recent extension of this simulation package has been recently reported by Franco [2, 41, 43], called MS LIBER-T (Multiscale Simulator of Lithium Ion Batteries and Electrochemical Reactor Technologies). This model constitutes a breakthrough compared to the previously developed simulation package MEMEPhys penalized by its dependence on commercial software toolboxes and solvers such as Simulink. MS LlBER-T is coded on an independent C/Pyth(Mi language basis, highly flexible and portable (it can eventually be coupled to... 

Well-developed software should be described by comprehensive, intelligible documentation throughout the development process. It should include, inter alia, references to design methods, software tools employed and details of test plans together with results. Software maintainability has already been discussed and the documentation should also be maintained to respond to changes in the software and previous versions destroyed. 

Previously developed application software library modules should be used where... 

The datafitO code segment is another useful illustration of how previously developed code segments and functions can be combined in new and very useful ways. The datafitO function combines in a very short code segment the interpolation function of Chapter 6 with the nonlinear least squares data fitting routine nlstsqO of the previous section of this chapter. The result is another very useful and practical software application. In subsequent chapters many other applications of the code segments already developed will be seen. 

The effect of gate location on process consistency during the injection molding of an automotive bumper is analyzed in this paper. The analyses were performed using Moldflow Plastic Insight version 6.0 and multivariable optimization software based on Data Envelopment Analysis (DEA) previously developed by our group [3, 4, 5]. 

---