Abstract

Design patterns are widely used in various areas of computer science, the most notable example being software engineering. They have been introduced also for supporting the encoding of automated planning knowledge models, but up till now, with little success.In this paper, we investigate the merits of design patterns, as an example of the broader class of reusable abstractions, in the automated planning context; particularly, we aim at drawing attention to their potential usefulness for the explainability of domain-independent planning systems. Further, we argue that to foster the use of design patterns, there is a need for a centralised repository, and we describe the functionalities that such repository should provide to support knowledge engineers.

Highlights

  • In domainindependent planning there is a decoupling between the planning logic, that is embodied in the planning engine, and the domain knowledge, that comes under the form of knowledge models

  • Studies on Knowledge Engineering for Planning and Scheduling (KEPS) have led to the creation of several tools and techniques to support the design of domain knowledge structures, and the use of planners for real-world problems [15, 10]

  • We point to the fact that design patterns can play a significant role for supporting the explainability of the behaviour of a planning system

Read more

Summary

Beyond Knowledge Encoding

We would like to highlight the important role that reusable abstractions, and design patterns can play for AI planning knowledge models, beside the support for knowledge encoding and acquisition. In the XAIP field, the knowledge model is more and more regarded as a source of knowledge that can explain the behaviour of the planning system [24, 11]. This is because, during the knowledge engineering process of encoding specifications into an appropriate planning knowledge model a number of design decisions have to be made. Design patterns can provide a valuable and well-defined mean for supporting explanations This is because, when design patterns are implemented in a planning model, the design pattern description becomes a valuable source of additional knowledge, that is not encoded in the model. Additional sources of domain-specific knowledge can be sought via ontologies or similar structures [24]

Example
Conclusion

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.