# Context-Based Model for Browsing the Web Through Voice
## 4 Model Requirements and Architecture  
The specification of requirements was carried out based on the related work, as well as on the ISO IEEE 29148-2018 and ISO 9241-11 standards mentioned above. As a result, six main functions to be covered by the model were defined:  
1. Continuously listening to and understanding the user voice requests and responses;
2. Finding relevant web content based on the user's query and its context;
3. Enabling web browsing through voice commands, including interacting with objects such as buttons and checkboxes, selecting text or multimedia, and scrolling between sections;
4. Presenting relevant web content or information audibly and visually;
5. Managing the user's context and browsing history logging;
6. Facilitating interaction primarily through voice, with additional support for on-screen gestures and a virtual keyboard. Figure 1: Research methodology. Therefore, ten functional requirements and three non-functional requirements were defined, highlighted for their significance, and listed in Tables 3 and 4, respectively. Non-functional requirements concern the usability criteria [38] defined as the degree to which a product can be used by specific users to achieve specific objectives with effectiveness, efficiency, and satisfaction in a specific context of use. Considering these requirements, the structural model was established. As shown in Figure 2, the context-based model for web browsing via voice consists of ten components are described below:  
* Multi-modal User Interface: it is responsible for presenting notifications, results, and available actions in audible or graphical form. In addition, it allows user interaction primarily through voice with standby and active listening. It also supports interaction via touch gestures on the screen, and text input through a virtual keyboard;
* Natural Language Translator: it analyzes the validity of user requests, detects the underlying intent, and extracts relevant data from the lexical units in order to establish parameters associated with that intent. Depending on the user's activity (profiling or \begin{table}
\begin{tabular}{l c} \hline
**ID** & **Description** \\ \hline UR01 & Proper volume adjustment for effective interaction \\ UR02 & Readability of application responses \\ UR03 & Voice-activation at any time \\ \hline \end{tabular}
\end{table} 
Table 4: Usability requirements. Figure 2: Components of the context-based model for browsing the Web using voice. browsing), the results generated by this component (intent and parameters) are sent to the User Context Manager, Query Generator or Operations component;
* Operations: this component is responsible for managing the execution of events in other components of the model based on the intent and parameters provided by the Natural Language Translator. Its main functions include managing voice-driven browsing, coordinating the presentation of results through the Multi-modal User Interface, and maintaining data communication with the Response Generator;
* User Context Manager: it creates the user profile by means of a questionnaire. From the answers provided, it extracts context descriptor terms and stores them in the User Context table. In addition, it generates and performs updates to the General Set of URLs table based on the navigation history;
* Query Generator: it builds a query to search for content on the Web based on the user's request and context. Each query is composed of a set of words from the user's request, context descriptor terms, search operators, and filters.