IndexOverviewGeneral DescriptionProduct OverviewProduct FeaturesConstraintsAssumptions and DependenciesExternal InterfaceRequirementsUser InterfacesSoftware InterfacesThis section provides a scope description and overview of everything that is included in this SRS document. Additionally, the purpose of this document is 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 for the “Tahal” device. It will outline 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 whiteboard with a mobile application that helps users travel based on the specified location. The mobile application is only available to people who have the “Tahal” card. Users can provide the location they would like to visit. This information will serve as the basis for the search results and the “Tahal” tab will automatically take users to the defined location via a user-selected route without any manual effort. The user can also change the route later by commanding the “Tahal” Assistant. Additionally, the software requires both Internet connection and GPS connection to retrieve and view results. The device has the ability to make turns, instant response to obstacles, speed control. Say no to plagiarism. Get a tailor-made essay on "Why Violent Video Games Shouldn't Be Banned"? Get an Original Essay Overview This document includes three parts. The second provides an overview of the functionality and interaction of the system. This part also mentions the system's constraints and assumptions about the product. The third part provides the requirements specification in detailed terms and a description of the different interfaces of the system. General Description This section will provide an overview of the entire system. The system will be explained in its context to show how it works and present its basic functionality. 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 application will be used to search for locations; set the routes' while the board will be used for real movement such as skateboarding and as a whole will constitute an automated board. The mobile application will need to communicate with a GPS application within the mobile phone, which in turn communicates with a physical GPS device to find the user's location. GPS will provide the mobile application with the locations of both the user and the final destination and the route between them. Product Features With the mobile application, users will be able to search for visiting places. The search result will appear in a map view. The map view will show each location as a pin on the map, as well as your location. Constraints The mobile application is bound by the system interface to the GPS navigation system within the mobile phone. Since there are multiple GPS systems and multiple manufacturers, the interface will most likely not be the same for each of them. Furthermore, there may be a difference between the browsing features provided by each of them. The Internet connection also represents a constraint for the application. Since the application retrieves data from the database over the Internet, it is essential that an Internet connection is available for the application to work. Assumptions and Dependencies An assumption about the product is that it will always be used on mobile phones withsufficient performance. If the phone does not have sufficient hardware resources for the application, for example users may have allocated them to other applications, there may be scenarios where the application does not work as expected or even works at all. Another hypothesis is that the GPS components in all phones work the same way. If the phones have different interfaces for GPS, the application must be specifically adapted to each interface and this would mean that integration with GPS would have different requirements than what is indicated in these specifications. Specific requirements This section contains all the features and quality requirements of the system. Provides a detailed description of the system and all its features. External Interface RequirementsThis section provides a detailed description of all system inputs and outputs. It also provides a description of the hardware, software, and communications interfaces and provides basic user interface prototypes. User Interfaces A first-time user of the mobile application must register to use the "Tahal" application, which is only possible with an assigned PIN number to avoid unauthorized access. A user can search for the location using the search bar. The map view shows each location via a pin, you can zoom in to check available routes to follow your desired location. Hardware Interfaces The hardware component of the system is the board which may conventionally look like a skateboard but works without any manual effort and all with the use of the GPS device which connects to both the mobile phone and the device which feeds the data into the processor. Next the processor controls the motor and turns the wheel to move forward, in turn, adjusts the speed. Software interfaces The mobile application communicates with the GPS application to obtain geographical information on where the user is located and its visual representation, and with the database in order to obtain information on the indicated position. Functional Requirements This section includes requirements that specify all the fundamental actions of the software system. User Class 1 - The UserFunctional Requirement 1.1 TITLE: Download mobile application.DESCRIPTION: A user must be able to add the application via a shared link. Functional Requirement 1.2 TITLE: User Registration - Application DESCRIPTION: Given that a user has downloaded the mobile application, the user should be able to register via the application using a certain PIN number. Functional Requirement 1.3 TITLE: Application - Search DESCRIPTION: Given that a user is logged in to the mobile application, the user should be able to search for locations. A user should be able to select the desired route options. Functional Requirement 1.4 TITLE: Mobile application: Search results in a map view DESCRIPTION: Search results can be displayed on a map. Relevant information is shown on the map based on the user's location and movement status. A specific placeholder will represent the intended location. Another will represent the user's location. Functional Requirement 1.5 TITLE: Mobile Application - Navigation DESCRIPTION: When a selection is made, the final position must be sent to the mobile phone's GPS navigation program. The user should then be directed to the destination. Performance Requirements The requirements in this section provide a detailed specification of the quality of user interaction. Featured Search Features TITLE: Featured Search Features DESCRIPTION: The search feature