Because of the quick innovative headway and the advancement of the idea of chatbots; and the time and exertion, they can save. Many specific systems have arisen to embrace chatbot creation and advancement. By depending on computerized reasoning, the chatbot has coordinated AI inside it, and it has become more far reaching and more extensive for different mechanical fields. Along these lines, we are making a chatbot for the college. The task intends to construct a chatbot to work with the most common way of getting to data connected with understudies’ requests towards affirmation, enlistment, and data in regards to the college. The inspiration for this task is that there is no college level identical from past graduation projects, as this project basically focuses on all Misr worldwide University understudies and non-Egyptian understudies, and other Egyptian understudies. In an end, it lies in addressing incessant and normal inquiries by individuals and giving the response to these inquiries whenever the client needs.
The purpose of this document is to offer a complete software design description (SDD) of our system’s architecture and design (MIU-Chatbot). It’s also necessary for communicating with stakeholders during the design process. It will provide the team with a thorough explanation of the system architecture and design, as well as a review of the requirements and a general overview of the system.
The goal of this SDD is to encourage the software development by giving a fully described system design. There isn’t only specified information for the design and development of the system, but also there is critical information regarding the system that is being developed.
The Chatbot system’s architecture will be detailed in the SDD. The introduction is the first portion of the document; it discusses the purpose of our work, scope, overview, intended audience, reference material, and definitions and acronyms. The overview, scope, aims, and timing of the system will be discussed in the second section. The system design ideas are described in the third section. It consists of the following items: (context, use case, composition, logic, patterns use, algorithm, interaction, and interface viewpoint). The Data Design part, on the other hand, contains data, datasets, and database design descriptions. User interface and screen graphics are included in the fifth section, Human Interface Design. Finally, in the sixth section, there is a requirements matrix, which is a table that summarise the functions and state of the system.
1.4 Intended audience
Team members of the project are responsible for this document, which will be used to keep track of the project. Students, alumni, parents and any user are among the stakeholders who could profit from this approach.