Search results

The purpose of this paper is to evaluate the reliability of individual software components in terms of the probability that each software component performs its intended functionality successfully. The overall software system reliability is evaluated.

This paper incorporates the reliability behavior of component‐based software system using Markov process.

It is found that the component‐based software system reliability increases as the component reliability increases.

This paper explores new directions in evaluating the reliability of component‐based software systems for software reliability and offers practical help to researchers and software industries in reliable software development. The proposed software simulation technique will act as a tool for the software quality assurance team for evaluating the reliability of component‐based software systems.

The flexibility of an automated manufacturing system (AMS) is largely determined by the architecture of its supervisory software. The AMS supervisory software should be compatible enough to allow re‐configuration, maintenance, and upgrading to be done at a reasonable cost, so as to prolong the life span of the AMS, and to maintain its value and success. In this connection, the application of software engineering methodologies is to introduce better management of AMS software development, with a view to providing some structure and formality to express, analyse, and produce them. This paper presents an object‐oriented methodology to address the task of AMS supervisory software development. The effectiveness of the methodology is examined in an extensive case study of the development of the supervisory software for a flexible manufacturing cell (FMC) that contains a robot and an AGV.

This study proposes targeted modernization of the Department of Defense (DoD's) Joint Forces Ammunition Logistics information system by implementing the optimized innovative information technology open architecture design and integrating Radio Frequency Identification Device data technologies and real-time optimization and control mechanisms as the critical technology components of the solution. The innovative information technology, which pursues the focused logistics, will be deployed in 36 months at the estimated cost of $568 million in constant dollars. We estimate that the Systems, Applications, Products (SAP)-based enterprise integration solution that the Army currently pursues will cost another $1.5 billion through the year 2014; however, it is unlikely to deliver the intended technical capabilities.

Two aspects of the selection and evaluation of software packages are reviewed: the strategy for evaluation and selection, and criteria that might be applied in selection. The evaluation and selection of a software package should be approached as a project. Appropriate strategies for the selection and evaluation of software packages can be based on information systems methodologies. The main stages in the project are: definition of objectives, evaluation of options, definition, selection and design, implementation and evaluation and maintenance. A system requirements specification is an important document in this process. Software selection must be guided by appropriate criteria. General criteria are cost, lifetime and life history, originator, supplier, support, maintenance, technical considerations and compatibility, ease of use, interfaces and integration. In addition specific criteria must be developed for specific categories of packages. A checklist of criteria for database packages is given.

The following bibliography focuses mainly on programs which can run on IBM microcomputers and compatibles under the operating system PC DOS/MS DOS, and which can be used in online information and documentation work. They fall into the following categories:

The purpose of this paper is to introduce a novel approach of designing, specifying, and describing the behavior of software systems in a way that helps to predict their reliability from the reliability of the components and their interactions.

Design imperatives and relevant mathematical documentation techniques for improved reliability predictability of software systems are identified.

The design approach, which is named design for reliability predictability (DRP), integrates design for change, precise behavioral documentation and structure based reliability prediction to achieve improved reliability predictability of software systems. The specification and documentation approach builds upon precise behavioral specification of interfaces using the trace function method (TFM) and introduces a number of structure functions or connection documents. These functions capture both the static and dynamic behavior of component‐based software systems and are used as a basis for a novel document driven structure based reliability predication model.

Decades of research effort have been spent in software design, mathematical/formal specification and description and reliability prediction of software systems. However, there has been little convergence among these three areas. This paper brings a new direction where the three research areas are unified to create a new design paradigm.

This paper aims to describe an effort to provide for a robust and secure software development paradigm intended to support DevSecOps in a naval aviation enterprise (NAE) software support activity (SSA), with said paradigm supporting strong traceability and provability concerning the SSA’s output product, known as an operational flight program (OFP). Through a secure development environment (SDE), each critical software development function performed on said OFP during its development has a corresponding record represented on a blockchain.

An SDE is implemented as a virtual machine or container incorporating software development tools that are modified to support blockchain transactions. Each critical software development function, e.g. editing, compiling, linking, generates a blockchain transaction message with associated information embedded in the output of a said function that, together, can be used to prove integrity and support traceability. An attestation process is used to provide proof that the toolchain containing SDE is not subject to unauthorized modification at the time said critical function is performed.

Blockchain methods are shown to be a viable approach for supporting exhaustive traceability and strong provability of development system integrity for mission-critical software produced by an NAE SSA for NAE embedded systems software.

A blockchain-based authentication approach that could be implemented at the OFP point-of-load would provide for fine-grain authentication of all OFP software components, with each component or module having its own proof-of-integrity (including the integrity of the used development tools) over its entire development history.

Many SSAs have established control procedures for development such as check-out/check-in. This does not prove the SSA output software is secure. For one thing, a build system does not necessarily enforce procedures in a way that is determinable from the output. Furthermore, the SSA toolchain itself could be attacked. The approach described in this paper enforces security policy and embeds information into the output of every development function that can be cross-referenced to blockchain transaction records for provability and traceability that only trusted tools, free from unauthorized modifications, are used in software development. A key original concept of this approach is that it treats assigned developer time as a transferable digital currency.

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.

The approach is done through an interpretive case study of a small Canadian manufacturer that has adopted an open source ERP system.

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.

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).

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.

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.

The purpose of this paper is to enable real estate managers to identify and evaluate appropriate information technology (IT) solutions from the array of options available.

The authors explain the main components of IT solutions and provide a systematic approach for evaluating, selecting, and maintaining a cost‐effective IT solution, empowering corporate real estate managers to make informed IT decisions.

Corporate real estate managers can use a systematic approach to evaluating hardware and software options to select a solution that better serves business needs.

Corporate real estate managers can use the models in this paper to change how they approach the selection of IT solutions for their business.

The paper fills a void by providing IT assistance specifically for corporate real estate managers using business rather than technical language.