Table of ContentsOverviewGeneral DescriptionProduct OutlookProduct FeaturesConstraintsAssumptions and DependenciesExternal InterfaceRequirementsUser InterfacesSoftware InterfacesThis section gives a scope description and overview of everything included in this SRS document. The purpose of this document is also described and a list of abbreviations and definitions is provided. Purpose The purpose of this document is to provide a detailed description of the requirements relating to the “Tahal” device. It will illustrate the purpose and complete statement for the development of the system. It will also explain the system constraints, interface and interactions with other external applications. Scope “Tahal” is an automated board with a mobile application that helps users travel based on the specified location. The mobile application is only accessible to people with the “Tahal” board. Users can indicate the location they want to visit. This information will serve as the basis for search results and the “Tahal” board will automatically take users to a defined location on a user-selected path without any manual effort. The user can also change the path later by commanding the “Tahal” Wizard. Additionally, the software needs an Internet connection and GPS to retrieve and display results. The device has the ability to take turns, instantly react to obstacles, control speed. Say no to plagiarism. Get a tailor-made essay on “Why Violent Video Games Should Not Be Banned”?Get Original EssayOverviewThis paper has three parts. The second provides an overview of system functionality and system interaction. This part also mentions system constraints and assumptions about the product. The third part provides the specification of requirements in detailed terms and a description of the different interfaces of the system. General DescriptionThis section will give an overview of the entire system. The system will be explained in context to show how it works and present its basic functionalities. The constraints and assumptions of the system will also be presented. Product Perspective Figure 1 Block diagram This system will consist of two parts: a mobile application and a card. The mobile app will be used to search for locations; define paths” while the board will be used for real movement like skateboarding and as a whole it will constitute an automated board. The mobile application will need to communicate with a GPS application built into the mobile phone, which in turn will communicate with a physical GPS device to find the user's location. The GPS will provide the mobile application with the locations of the user and the final destination as well as the path between them. Product Features With the mobile app, users will be able to search for tour locations. The search result will be displayed in map form. The map view will display each location as a pin on the map along with the user's location.ConstraintsThe mobile application is limited by the system interface of the mobile phone's GPS navigation system. Since there are several system and GPS manufacturers, the interface will likely not be the same for each of them. Additionally, there may be a difference between the navigation features offered by each of them. The Internet connection is also a constraint for the application. Since the application retrieves data from the database via the Internet, it is essential that there is an Internet connection for the application to work.Assumptions and Dependencies One assumption about the product is that it will always be used on sufficiently capable mobile phones. If the phone does not have enough hardware resources available for the application, for example if users have allocated them to other applications, the application may not work as expected, or at all. Another hypothesis is that the GPS components in all phones work the same way. If phones have different interfaces with GPS, the application must be specifically tailored to each interface, which means that integration with GPS would have different requirements than those stated in this specification. Specific Requirements This section contains all functional features. and system quality requirements. It gives a detailed description of the system and all its features.External Interface RequirementsThis section provides a detailed description of all inputs and outputs of the system. It also gives a description of the hardware, software and communication interfaces and provides basic prototypes of the user interface. User Interfaces A new user of the mobile application must register to use the "Tahal" application, this which is only possible with an assigned PIN code. to prevent unauthorized access. A user can search the location using the search bar. The map view shows each location by a pin, you can zoom in to check the available paths to follow the desired location. Hardware Interfaces The hardware component of the system is the board which may classically resemble a skateboard but operates without any manual effort through the use of a GPS device which connects to both the mobile phone and the device which feeds the data into the processor. Then the processor controls the motor and rotates the wheel to move forward, taking turns adjusting the speed.Software InterfacesThe mobile application communicates with the GPS application in order to obtain geographical information about the location of the user and its visual representation, as well as with the database in order to obtain information about the pointed location. Functional Requirements This section includes requirements that specify all fundamental actions of the software system. User Class 1 - The User Functional Requirement 1.1 TITLE: Download the mobile application. DESCRIPTION: A user must be able to add the application via a shared link. Functional Requirement 1.2 TITLE: User Registration - APP DESCRIPTION: Given that a user has downloaded the mobile application, the user must then be able to register through the application using an identification number given personnel. Functional Requirement 1.3 TITLE: Application - Search DESCRIPTION: Given that a user is logged in to the mobile application, the user must then be able to search for locations. A user should be able to select the desired path options. Functional Requirement 1.4 TITLE: Mobile Application - Search Result in a Map View DESCRIPTION: Search results can be viewed on a map. On the map, relevant information based on the user's location and travel status is displayed. A specific pin will represent the intended location. Another will represent the user's location.Functional Requirement1.5 TITLE: Mobile Application - Navigation DESCRIPTION: When a selection is made, the final location must be sent to the mobile phone's GPS navigation program. The user must then be directed