Mapping the design information representation terrain

Webster, Dallas

doi:10.1109/2.16186

Cited by 46 publications

(17 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As a result, having a clear model of CE projects is fundamental to the effective management of these projects. Such models should capture data "effectively so that it can be interpreted and used" at an appropriate level of processable expressiveness, "the degree to which a mechanism supports machine understanding or semantic interpretation" [5].…”

Section: Information Modelingmentioning

confidence: 99%

Information Modeling for Rapid Prototyping in a Risk Management System

Khoo¹,

Zhou²,

Kayis

2008

2008 International Conference on Computational Intelligence for Modelling Control &Amp; Automation

View full text Add to dashboard Cite

Constantly evolving business requirements and the large amounts of data involved in concurrent engineering projects are challenges that managers face in managing project risks. This paper proposes an information modeling approach that can be used for the construction of risk models and lessons learnt. Using these models, rapid prototypes can be developed and deployed within a web-based risk management system. The availability of the prototypes allowed early and regular validations of analysis results with actual costing data from case studies that resulted in the improvement of the system's accuracies.

show abstract

Section: Information Modelingmentioning

confidence: 99%

Information Modeling for Rapid Prototyping in a Risk Management System

Khoo¹,

Zhou²,

Kayis

2008

2008 International Conference on Computational Intelligence for Modelling Control &Amp; Automation

View full text Add to dashboard Cite

show abstract

“…Specification languages are extensively used in modeling the structural and behavioral properties of real-time embedded software systems (Charr 1987;Kelly 1987;Webster 1987). RSL (Alford 1977), ESML (Ward 1988), PAISLey (Zave and Schell 1986), PSDL (Luqi, Burzins and Yeh 1988) and RT-ASLAN (Auernheimer and Kemmerer 1986) are examples of such languages.…”

Section: Using Formal Modelsmentioning

confidence: 99%

A specification language for planning and fault recovery in manufacturing systems

Chaar

Volz

1993

Int J Flex Manuf Syst

View full text Add to dashboard Cite

Abstract. This paper presents the syntax and semantics of a component-oriented rule-based language for specifying the formal models of manufacturing systems. A model captures the state of a component of the system in a set of first-order logic predicates, and it captures the semantics of the operations performed by this component in a set of rules that determine the preconditions and postconditions of an operation. The models are then used to plan the sequence of operations of each class of jobs to be manufactured by these systems. A plan-oriented fault detection and correction strategy is proposed. This strategy can automatically handle any combination of faults that may occur when monitoring the operations of manufacturing systems. A fault-tree is consulted prior to executing the scheduled operations of a plan, and the faults that affect the execution of these operations are handled subsequently. Resuming the original cyclic schedule is attempted, whenever feasible. As a proof of concept, a prototype implementation of both the main constructs of the component-oriented rule-based language and the planning and fault-recovery algorithms presented in this paper have been completed. This prototype is implemented on a Unix-based system in the Ada programming language. The specification of a manufacturing system is first expressed in the proposed language. These statements are then translated into Ada code. This code is next compiled by a Verdix Ada compiler and is executed in order to create and populate the model data structure of the system. A detailed plan of execution and a set of fault-recovery plans may then be derived for a job to be manufactured on this system.

show abstract

“…(For further discussion, interested readers may refer to [8,10,24,27,31,35,36,44].) Information hiding is important for ensuring reliability and modifiability of software systems by reducing interdependencies between software components.…”

Section: Encapsulationmentioning

confidence: 99%

A knowledge-based system for Ada® software development

Tsai

Sheu

1991

Journal of Systems Integration

View full text Add to dashboard Cite

Abstract. In this article, we present a knowledge-based system using the concept of knowledge representation and data abstraction to support Ada ~ software development. This article uses logic-based specification with objectoriented features to facilitate Ada software development. The Ada source code will be obtained through knowledgebased transformation. This system includes a frame-and-rule-oriented requirements language (FRORL), a predominance/particular methodology, and a knowledge base. FRORL uses frame representations for object-oriented modeling, applies production rules for specifying actions and constraints of real world domains, and provides a set of abstract mechanisms for the practical description of abstract relations. The predominance/particular methodology is used to support Ada software developers in performing object-oriented modeling of application domains. The knowledge base provides rules for specification checking, prototype validation, and transformation of specifications into Ada code. A real problem is given to illustrate the system.

show abstract

Mapping the design information representation terrain

Cited by 46 publications

References 5 publications

Information Modeling for Rapid Prototyping in a Risk Management System

Information Modeling for Rapid Prototyping in a Risk Management System

A specification language for planning and fault recovery in manufacturing systems

A knowledge-based system for Ada® software development

Contact Info

Product

Resources

About