Knowledge representation and reasoning in the design of composite systems
- 1 June 1992
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 18 (6) , 470-482
- https://doi.org/10.1109/32.142870
Abstract
The design process that spans the gap between the requirements acquisition process and the implementation process, in which the basic architecture of a system is defined, and functions are allocated to software, hardware, and human agents. is studied. The authors call this process composite system design. The goal is an interactive model of composite system design incorporating deficiency-driven design, formal analysis, incremental design and rationalization, and design reuse. They discuss knowledge representations and reasoning techniques that support these goals for the product (composite system) that they are designing, and for the design process. To evaluate the model, the authors report on its use to reconstruct the design of two existing composite systems rationally.Keywords
This publication has 24 references indexed in Scilit:
- Negotiation behavior during requirement specificationPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- A logic of action for supporting goal-oriented elaborations of requirementsACM SIGSOFT Software Engineering Notes, 1989
- gIBIS: a hypertext tool for exploratory policy discussionACM Transactions on Information Systems, 1988
- Language support for the specification and development of composite systemsACM Transactions on Programming Languages and Systems, 1987
- Reachability trees for high-level petri netsTheoretical Computer Science, 1986
- A First Order Theory of Planning, Knowledge, and ActionPublished by Elsevier ,1986
- THE SYNTHESIS OF DIGITAL MACHINES WITH PROVABLE EPISTEMIC PROPERTIESPublished by Elsevier ,1986
- IMPLEMENTING SPECIFICATION FREEDOMS**This research was supported by Defense Advanced Research Projects Agency contract DAHC15 72 C0308. Views and conclusions contained in this document are those of the authors and should not be interpreted as representing the official opinion or policy of DARPA, the U.S. Government, or any other person or agency connected with them.Published by Elsevier ,1986
- Why are Design Derivations Hard to Replay?Published by Springer Nature ,1986
- Implementing specification freedomsScience of Computer Programming, 1982