Real-time software methodologies: Are they suitable for developing Manufacturing control software?

Computer-Integrated Manufacturing (CIM) systems may be classified as real-time systems. Hence, the applicability of methodologies that are developed for specifying, designing, implementing, testing, and evolving real-time software is investigated in this article.Peer Reviewedhttp://deepblue.lib.umich.edu/bitstream/2027.42/45553/1/10696_2005_Article_BF01358949.pd

Developing control and integration software for flexible manufacturing systems

The slow growth of computer-integrated manufacturing is attributed to the complexity of designing and implementing their control and integration software. This article expands on a methodology for designing and implementing this software that was introduced in [16]. The goal of this methodology is to build flexible and resuable control and integration software for computer-integrated manufacturing systems. It hinges upon the concepts of software/hardware components, their assemblages, a distributed common language environment, formal models, and generic controllers. Major sources of flexibility are obtained by decoupling process plan models from the model of the factory floor and by using a generic controller. Reusability is achieved by building selfcontained software/hardware components with general, possibly parametrized, interfaces. The interplay between simulated and actual hardware internals of software/hardware components is used as the basis of a testing strategy that performs off-line simulation followed by on-line testing.Peer Reviewedhttp://deepblue.lib.umich.edu/bitstream/2027.42/43095/1/10952_2005_Article_BF02265064.pd

Developing manufacturing control software: A survey and critique

The complexity and diversity of manufacturing software and the need to adapt this software to the frequent changes in the production requirements necessitate the use of a systematic approach to developing this software. The software life-cycle model (Royce, 1970) that consists of specifying the requirements of a software system, designing, implementing, testing, and evolving this software can be followed when developing large portions of manufacturing software. However, the presence of hardware devices in these systems and the high costs of acquiring and operating hardware devices further complicate the manufacturing software development process and require that the functionality of this software be extended to incorporate simulation and prototyping.Peer Reviewedhttp://deepblue.lib.umich.edu/bitstream/2027.42/45542/1/10696_2005_Article_BF01328739.pd

Software design methodologies : a survey

http://deepblue.lib.umich.edu/bitstream/2027.42/4077/5/ang8668.0001.001.pdfhttp://deepblue.lib.umich.edu/bitstream/2027.42/4077/4/ang8668.0001.001.tx

In-Process Evaluation for Software Inspection and Test

Abstract-The goal of software inspection and test is to reduce the expected cost of software failure over the life of a product. This paper extends the use of defect higgers, the eventsthat cause defects to be discovered, to help evaluate the effectiveness of inspections and test scenarios. In the case of inspections, the defect trigger is defined as a set of values that associate the shills of the inspector with the discovered defect. Similarly, for test scenarios, the defect trigger values embody the deferring strategies being used in creating these scenarios. The usefulness of triggers in evaluating the effectiveness of software inspections and tests is demonstrated by evaluating the inspection and test activities of some software products. These evaluations are used to point to both deficiencies in inspection and test strategies and to progress made in improving such strategies. The trigger distribution of the entire inspection or test series may then be used to highlight areas for further investigation, with the aim of improving the design, implementation, and test processes. Index Terms-Software development process, software inspec-tion, software reliability, software testing