VALIDATION OF ANSYS FINITE ELEMENT ANALYSIS SOFTWARE

This document provides a record of the verification and Validation of the ANSYS Version 7.0 software that is installed on selected CH2M HILL computers. The issues addressed include: Software verification, installation, validation, configuration management and error reporting. The ANSYS{reg_sign} computer program is a large scale multi-purpose finite element program which may be used for solving several classes of engineering analysis. The analysis capabilities of ANSYS Full Mechanical Version 7.0 installed on selected CH2M Hill Hanford Group (CH2M HILL) Intel processor based computers include the ability to solve static and dynamic structural analyses, steady-state and transient heat transfer problems, mode-frequency and buckling eigenvalue problems, static or time-varying magnetic analyses and various types of field and coupled-field applications. The program contains many special features which allow nonlinearities or secondary effects to be included in the solution, such as plasticity, large strain, hyperelasticity, creep, swelling, large deflections, contact, stress stiffening, temperature dependency, material anisotropy, and thermal radiation. The ANSYS program has been in commercial use since 1970, and has been used extensively in the aerospace, automotive, construction, electronic, energy services, manufacturing, nuclear, plastics, oil and steel industries.

Software Configuration Management

A brief introduction describes the characteristics of configuration management and outlines the key issues of knowledge and control of content, along with the targets developed for configuration management. Software, as a relatively new discipline, is still evolving standard techniques. The special properties of software which cause difficulty in configuration management are discussed. The theme moves to the planning of configuration management in order to support the reliability program. While many organisations consider con-figuration management at the end of development, the reasoning and recommendations (based on experience) are given for applying configuration management during the entire development and life of a project. The paper shows how to implement software configuration management and describes the method used in YARD. It concentrates on the view of the system by all users, and the impact on the ability to send software to customers with confidence, keep track of reported defects, and trace the effect of modifications on all issued software. The software configuration control system is the foundation on which all reporting systems must be based. It is an entirely different matter accumulating and analysing failure reports on some object like a pressure transducer, the configuration control for which is easily identified, than a large software-based system undergoing continual evolution and correction. The use of computers to maintain configuration control discipline on software is essential and, in our experience, works.

A description is given of the authors experience with software development and configuration management during the development and use of the Cronus distributed operating system. Cronus establishes a computing environment in which it is possible to perform software development for a heterogeneous set of computers, issue periodic software upgrades for each supported type of computer, and provide support for the software after upgrades have been installed. The author has designed a software source control system to manage the introduction of new versions of software modules and have established a configuration management plan to control the distribution of software to the varied set of supported computer types through a master-host-relay-host-destination-host approach. In discussing release support, the author pays special attention to the bug report manager, a distributed Cronus service designed to manage reports of problems in the Cronus system. >

Fault or failure of software contained in medical devices will seriously endanger users and should be considered to reduce risk. In software development process, the risk analysis and risk control are very important for software contained in medical devices. In order to promote the quality of software contained in medical devices, a website is designed to provide the operating procedure of software contained in medical devices in this paper. The configuration management of software with operation procedure is managed by website based relational database developed by PHP and MySQL. Software process model, V-mode, is applied to guide software development process and used to promote the reliability of software. Moreover, fault tree analysis and failure mode and effects analysis are used to achieve risk analysis and risk control. The risk of software contained in medical devices can be effectively reduced. Therefore, software verification and validation is also integrated to verify and validate the function of software. Integrated Cephalometric Analysis System had been used to show that proposed approach is feasible.KeywordsSoftware contained in medical devicessoftware verification and validationV-modelfault tree analysisfailure mode and effects analysis

Software productivity and quality improvement through software configuration management is based on organized and consistent change management. In change management, artifact identified as configuration item should be able to provide its changed history to the members in group and the members should be able to trace the changes made for the corresponding artifact. General software configuration management systems provide tracing information for artifacts only within the configuration management system, and it does not go further to changes that occur within individual working environment. This paper provides a solution that helps tracing changes that occur not only in configuration management, but also individual artifact’s changes through the integration of configuration management system and individual working environment. A revised version in configuration management system is connected to the artifact version of the working environment by the tagging technique, and traceability can be managed more effectively by sharing the tracing information.

Chapter 17 - Integrating SysML into a Systems Development Environment

The verification and validation of CFD software is of utmost importance for the reliability and hence for the success of CFD technology in industry. This paper discusses the relative importance, key elements, and some examples of: • Verification of numerical models and computer software; • Validation of solutions against benchmark data; and • Calibration of the models and analysis process. Out of these, the main emphasis is placed on verification. This is in light of the growing generality and complexity of CFD software (in response to continuously increasing expectations in industry). Finally, three key success factors for effective utilization of CFD technology are pointed out. These are: 1) Verifications and Validation of software; 2) Skills of the Users; and 3) Vision, and commitment of the manager (s).

When dealing with hundreds of components, keeping track of version changes and various dependency constraints imposed on the system, Software configuration management (SCM) can be defined as the control of the evolution of complex software systems. In recent years, researchers have argued that using ontology to represent and drive knowledge infrastructure of software projects provides procedural knowledge. The advantages of using ontology for SCM are immense and cover various aspects of software development and evolution. In this paper, key challenges must be face for designing and implementing SCM is summarized. One of them is the limited capability on interoperating in different SCM tools. An ontology-based reference knowledge model base for SCM is presented. The reference model allows depicting complex relations between concepts and services operating in configuration management.

The Software Configuration Management (SCM) of the Space Launch Initiative (SLI) Advanced Engineering Environment (AEE) products is performed in a distributed environment-meaning the activities performed during the project lifecycle are across numerous NASA Centers, facilities, organizations, colleges and industry. SCM is the glue that holds the project and products together-especially in a distributed environment. It identifies, controls, accounts, and verified the details of the products; the schedule of activities; the assigned responsibilities; and the required resources, including staff, tools, and computer facilities. Data/document management (DM) captures and conveys the SCM and project efforts. SCM and DM are integrally linked; hence, Software Configuration and Data Management (SCDM). This paper discusses one team's challenges in implementing SCDM in a distributed environment. The distributed nature of the project introduces new opportunities for moving SCDM to the next level of usefulness in today's high-tech development arena. The lessons learned from the implementation of distributed SCDM in support of the SLI AEE Project provide valuable information for future implementations of SCM and DM.

Models for Implementation of Software Configuration Management

Modeling product characteristics is well known to software configuration management (SCM). Modeling process characteristics is relatively new to SCM. Combining process modeling and SCM enhances the current capabilities of SCM. The paper presents product and process models suitable for SCM. The outlined approach, Concert provides building blocks for developing project specific models. Concert's models are described by entity relationship diagrams. In addition, Concert uses the predicate calculus to express model restrictions. Concert offers a seamless integration of product and process modeling. The paper presents a process model for software maintenance that is based on change requests. Such a model helps SCM to recognize the course of a software project early, thus SCM need not determine the development history of a software ex post. The paper describes a tool to manage the presented models and their instances.

Purpose – The purpose of this paper is to present the findings of Phase 1 of the research and to identify Australian agile software development organizations having such coexistence of agile and software configuration management (SCM) practices. This study employed “organization size” variable to study the phenomenon and used theory of Lean Thinking as a lens to analyse implementation variations of agile and SCM practices. Design/methodology/approach – For this study, the research design was comprised of three phases. In Phase 1, a quantitative study using an online survey was performed to answer RQ using various statistical techniques. In Phase 2, an initial conceptual model based on a literature review was developed, and then a qualitative study was performed using one longitudinal case study. In Phase 3, another online survey was performed using various parametric statistical techniques to validate and generalize the findings of Phase 1 and 2 and the proposed SLAM traceability model. The scope of this paper is to discuss only Phase 1 and its associated findings. Findings – The results of the analysis indicated that organizations, regardless of their size, frequently use agile practices for their software development operations. On the other hand, larger organizations use SCM practices comparatively more than medium and small organizations. However, traces of customized SCM process were found in most of the respondent (large, medium, and small) organizations, which indicates the coexistence of agile and SCM practices. Research limitations/implications – As there is no known listing or database available for such specialized criteria, a non-probabilistic sampling method was used, in the sense that the selection of members of the sample was arbitrary and subjective instead of a non-random selection from the pool of all agile practitioners in the field. Originality/value – By using the quantitative method approach, this study aims to generate empirical evidence to contribute to the body of knowledge in the relevant areas. On the practical side, this research can also provide support to IT businesses in general, and software development organizations in particular, with the streamlining of the internal operational environment for the facilitation of an adaptable process and the resulting coexistence of value-added agile and SCM practices.

Short development life cycles, the importance of time-to-market and fast changes in technology influence the requirements engineering process. Requirements are exposed to changes during the entire development life cycle, and decisions related to requirements and system design are moving toward developers. For this reason it is important to keep requirement changes under control during the entire development process. This control can be achieved by utilizing Configuration Management (CM) functions and in particular Change Management. This paper describes a model for managing requirements using CM functions. A requirements specification is defined as an hierarchic structure, in which elements of the structure are isolated requirements designated Requirements Specification Items. Having items under version control it is possible to get a better overview of the requirements change process. In the implementation phase, requirement items are associated with Change Requests which define implementations to be introduced in the system. When using Change Requests as links between requirements and the implemented functions we achieve a greater awareness of requirements and a better overview over the requirement process. Furthermore it provides a foundation for reuse of requirements when new systems are built.

The conventional Software Configuration Management (SCM) tools have shown their weakness in large and complex software systems with the development of modern software. This paper provides a better SCM tool with high availability to facilitate software development process. A novel approach named Quality of Service (QoS)-based SCM (QSCM) is presented, which introduces QoS guarantee techniques at the application level to web-based SCM system in order to improve SCM system?s performance. QSCM classifies users together with SCM activities and treats with requests according to their priority. When the server is overloaded, it stops treatment with new requests so that to avoid from crash. The work described here is a first step towards this goal.