Object oriented development of engineering software using CLIPS

Engineering applications involve numeric complexity and manipulations of a large amount of data. Traditionally, numeric computation has been the concern in developing an engineering software. As engineering application software became larger and more complex, management of resources such as data, rather than the numeric complexity, has become the major software design problem. Object oriented design and implementation methodologies can improve the reliability, flexibility, and maintainability of the resulting software; however, some tasks are better solved with the traditional procedural paradigm. The C Language Integrated Production System (CLIPS), with deffunction and defgeneric constructs, supports the procedural paradigm. The natural blending of object oriented and procedural paradigms has been cited as the reason for the popularity of the C++ language. The CLIPS Object Oriented Language's (COOL) object oriented features are more versatile than C++'s. A software design methodology based on object oriented and procedural approaches appropriate for engineering software, and to be implemented in CLIPS was outlined. A method for sensor placement for Space Station Freedom is being implemented in COOL as a sample problem

Weighted Class Complexity: A Measure of Complexity for Object Oriented System

Software complexity metrics are used to predict critical information about reliability and maintainability of software systems. Object oriented software development requires a different approach to software complexity metrics. In this paper, we propose a metric to compute the structural and cognitive complexity of class by associating a weight to the class, called as Weighted Class Complexity (WCC). On the contrary, of the other metrics used for object oriented systems, proposed metric calculates the complexity of a class due to methods and attributes in terms of cognitive weight. The proposed metric has been demonstrated with OO examples. The theoretical and practical evaluations based on the information theory have shown that the proposed metric is on ratio scale and satisfies most of the parameters required by the measurement theor

Object-oriented software quality through data scope complexity measurement

[[abstract]]Software metrics is a necessary step for software reliability and quality, and software metrics of traditional procedure-oriented programming are fairly mature and have various methodologies and tools available for use. Object-oriented programming has recently became popular. However, traditional procedure-oriented software metrics are not appropriate for the development of object-oriented software. Some research into object-oriented software metrics has been proposed, but these articles focus on only one metric that measures a specific characteristic of the object-oriented software. The authors propose a new metric methodology, the data scope complexity, for object-oriented software based on the data scope of a program. The data scope complexity can show complexities of multiple features of object-oriented programming at the same time. They also quantify and compare object-oriented programming with procedure-oriented programming[[conferencetype]]國際[[conferencedate]]19971012~19971015[[booktype]]紙本[[iscallforpapers]]Y[[conferencelocation]]Orlando, FL, US

Using a Combination of Measurement Tools to Extract Metrics from Open Source Projects

Software measurement can play a major role in ensuring the quality and reliability of software products. The measurement activities require appropriate tools to collect relevant metric data. Currently, there are several such tools available for software measurement. The main objective of this paper is to provide some guidelines in using a combination of multiple measurement tools especially for products built using object-oriented techniques and languages. In this paper, we highlight three tools for collecting metric data, in our case from several Java-based open source projects. Our research is currently based on the work of Card and Glass, who argue that design complexity measures (data complexity and structural complexity) are indicators/predictors of procedural/cyclomatic complexity (decision counts) and errors (discovered from system tests). Their work was centered on structured design and our work is with object-oriented designs and the metrics we use parallel those of Card and Glass, being, Henry and Kafura's Information Flow Metrics, McCabe's Cyclomatic Complexity, and Chidamber and Kemerer Object-oriented Metrics

Improving a data-acquisition software system with abstract data type components

Abstract data types and object-oriented design are active research areas in computer science and software engineering. Much of the interest is aimed at new software development. Abstract data type packages developed for a discontinued software project were used to improve a real-time data-acquisition system under maintenance. The result saved effort and contributed to a significant improvement in the performance, maintainability, and reliability of the Goldstone Solar System Radar Data Acquisition System

Formal Transformations from Graphically-Based Object-Oriented Representations to Theory-Based Specifications

Formal software specification has long been touted as a way to increase the quality and reliability of software; however, it remains an intricate, manually intensive activity. An alternative to using formal specifications is to use graphically-based, semi-formal specifications such as those used in many object-oriented specification methodologies. While semi-formal specifications are generally easier to develop and understand, they lack the rigor and precision of formal specification techniques. The basic premise of this investigation is that formal software specifications can be constructed using correctness preserving transformations from graphically-based object-oriented representations. In this investigation, object-oriented specifications defined using Rumbaugh\u27s Object Modeling Technique (OMT) were translated into algebraic specifications. To ensure the correct translation of graphically-based OMT specifications into their algebraic counterparts, a formal semantics for interpreting OMT specifications was derived and an algebraic model of object-orientation was developed. This model defines how object-oriented concepts are represented algebraically using an object-oriented algebraic specification language O-SLANG. O-SLANG combines basic algebraic specification constructs with category theory operations to capture internal object class structure as well as relationships between classes. Next, formal transformations from OMT specifications to O-SLANG specifications were defined and the feasibility of automating these transformations was demonstrated by the development of a proof-of-concept system

White-Box Testing Framework for Object-Oriented Programming based on Message Sequence Specification

Software is a crucial element in the functionality of devices and industry. Likewise, the operation of an enterprise or organization depends largely on the reliability of the software systems used for supporting the business process or particular tasks. The quality of software has become the most important factor in determining the success of products or enterprises. In order to accomplish a quality software product several methodologies, techniques, and frameworks have been developed, each of them tailored to specific areas or characteristics of the software under review. This paper presents a white-box testing framework for Object- Oriented Programming based on Message Sequence Specification. In the context of an object-oriented program, our framework can be used to test the correct order in which the methods of a class are invoked by its clients. The implementation of the framework is based on aspect-oriented programming.XV Workshop Ingeniería de Software (WIS)Red de Universidades con Carreras en Informática (RedUNCI

White-Box Testing Framework for Object-Oriented Programming based on Message Sequence Specification

Software is a crucial element in the functionality of devices and industry. Likewise, the operation of an enterprise or organization depends largely on the reliability of the software systems used for supporting the business process or particular tasks. The quality of software has become the most important factor in determining the success of products or enterprises. In order to accomplish a quality software product several methodologies, techniques, and frameworks have been developed, each of them tailored to specific areas or characteristics of the software under review. This paper presents a white-box testing framework for Object- Oriented Programming based on Message Sequence Specification. In the context of an object-oriented program, our framework can be used to test the correct order in which the methods of a class are invoked by its clients. The implementation of the framework is based on aspect-oriented programming.XV Workshop Ingeniería de Software (WIS)Red de Universidades con Carreras en Informática (RedUNCI

An integrated approach to system design, reliability, and diagnosis

The requirement for ultradependability of computer systems in future avionics and space applications necessitates a top-down, integrated systems engineering approach for design, implementation, testing, and operation. The functional analyses of hardware and software systems must be combined by models that are flexible enough to represent their interactions and behavior. The information contained in these models must be accessible throughout all phases of the system life cycle in order to maintain consistency and accuracy in design and operational decisions. One approach being taken by researchers at Ames Research Center is the creation of an object-oriented environment that integrates information about system components required in the reliability evaluation with behavioral information useful for diagnostic algorithms. Procedures have been developed at Ames that perform reliability evaluations during design and failure diagnoses during system operation. These procedures utilize information from a central source, structured as object-oriented fault trees. Fault trees were selected because they are a flexible model widely used in aerospace applications and because they give a concise, structured representation of system behavior. The utility of this integrated environment for aerospace applications in light of our experiences during its development and use is described. The techniques for reliability evaluation and failure diagnosis are discussed, and current extensions of the environment and areas requiring further development are summarized