TY - JOUR
T1 - Rule-based systems formalized within a software architectural style
AU - Gamble, R. F.
AU - Stiger, P. R.
AU - Plant, R. T.
N1 - Funding Information:
This research is sponsored in part by the AFOSR (F49620-98-1-0217). The US Govt. is authorized to reproduce and distribute reprints for governmental purposes not withstanding any copyright violation therein. The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied of the AFOSR or the US Govt.
Copyright:
Copyright 2017 Elsevier B.V., All rights reserved.
PY - 1999/4
Y1 - 1999/4
N2 - This article considers the utilization of architectural styles in the formal design of knowledge-based systems. The formal model of a style is an approach to systems modeling that allows software developers to understand and prove properties about the system design in terms of its components, connectors, configurations, and constraints. This allows commonality of design to be easily understood and captured, leading to a better understanding of the role that an architectural abstraction would have in another complex system, embedded context, or system integration. In this article, a formal rule-based architectural style is presented in detail using the Z notation. The benefits of depicting the rule-based system as an architectural style include reusability, understandability, and the allowance for formal software analysis and integration techniques. The ability to define the rule-based architectural style in this way, illustrates the power, clarity, and flexibility of this specification form over traditional formal specification approaches. In addition, it extends current verification approaches for knowledge-based systems beyond the knowledge base only.
AB - This article considers the utilization of architectural styles in the formal design of knowledge-based systems. The formal model of a style is an approach to systems modeling that allows software developers to understand and prove properties about the system design in terms of its components, connectors, configurations, and constraints. This allows commonality of design to be easily understood and captured, leading to a better understanding of the role that an architectural abstraction would have in another complex system, embedded context, or system integration. In this article, a formal rule-based architectural style is presented in detail using the Z notation. The benefits of depicting the rule-based system as an architectural style include reusability, understandability, and the allowance for formal software analysis and integration techniques. The ability to define the rule-based architectural style in this way, illustrates the power, clarity, and flexibility of this specification form over traditional formal specification approaches. In addition, it extends current verification approaches for knowledge-based systems beyond the knowledge base only.
UR - http://www.scopus.com/inward/record.url?scp=0032626098&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=0032626098&partnerID=8YFLogxK
U2 - 10.1016/S0950-7051(99)00004-0
DO - 10.1016/S0950-7051(99)00004-0
M3 - Article
AN - SCOPUS:0032626098
VL - 12
SP - 13
EP - 26
JO - Knowledge-Based Systems
JF - Knowledge-Based Systems
SN - 0950-7051
IS - 1
ER -