Annual Report

This section offers a scope description and overview of every little thing integrated in this SRS document. Also, the objective for this document is described and a list of abbreviations and definitions is offered. Objective The objective of this document is to give a detailed description of the specifications for the “Tahal” device. It will illustrate the purpose and full declaration for the development of method. It will also explain system constraints, interface and interactions with other external applications. Scope “Tahal” is an automated board with a mobile application which helps users to travel primarily based on their specified location. The mobile application is available only to people owning the “Tahal” board. Users can give the location they would like to pay a visit to. This details will act as the bases for the search final results and “Tahal” board will take customers automatically to defined place across a user selected path with out any manual work. The user can also adjust the path later by commanding “Tahal” Assistant. Furthermore, the application wants each Web and GPS connection to fetch and display benefits. The device has the capability of taking turns, instantaneous response to obstacles, speed handle.

Overview

This document consists of three components. The second one offers an overview of the program functionality and method interaction. This element also mentions the system constraints and assumptions about the product. The third element provides the specifications specification in detailed terms and a description of the diverse method interfaces.

All round description

This section will give an overview of the entire technique. The technique will be explained in its context to show how the system performs and introduce the simple functionality of it. The constraints and assumptions for the technique will be also presented.

Solution point of view

Figure 1 Block Diagram This method will consist of two parts: 1 mobile application and 1 board. The mobile application will be used to search areas set path’ while the board will be used for actual movement like skateboard and as a whole it will make an automated board. The mobile application will want to communicate to a GPS application inside the mobile telephone, which in turn communicates with a physical GPS device to find the location of the user. The GPS will give the mobile application with places of both the user and the final location and the path in between them.

Solution functions

With the mobile application, the customers will be in a position to search for visiting places. The outcome of the search will be viewed in a map view. The map view will show every location as a pin on the map as effectively as the user’s personal location.

Constraints

The mobile application is constrained by the technique interface to the GPS navigation system within the mobile phone. Since there are numerous technique and multiple GPS makers, the interface will most most likely not be the exact same for every single one of them. Also, there may be a difference between what navigation features every single of them provide. The World wide web connection is also a constraint for the application. Given that the application fetches information from the database more than the Internet, it is crucial that there is an Net connection for the application to function.

Assumptions and dependencies

One particular assumption about the solution is that it will often be utilised on mobile phones that have enough efficiency. If the telephone does not have enough hardware sources offered for the application, for instance the users may possibly have allocated them with other applications, there might be scenarios exactly where the application does not work as intended or even at all. One more assumption is that the GPS elements in all phones function in the identical way. If the phones have various interfaces to the GPS, the application need to be specifically adjusted to every single interface and that would mean the integration with the GPS would have distinct specifications than what is stated in this specification.

Distinct specifications This section contains all of the functional and top quality requirements of the technique. It provides a detailed description of the program and all its characteristics.

External interface Specifications

This section provides a detailed description of all inputs into and outputs from the system. It also offers a description of the hardware, software program and communication interfaces and supplies simple prototypes of the user interface.

User interfaces

A initial-time user of the mobile application needs to register for using “Tahal” application which is only attainable with a pin quantity assigned to avoid unauthorised access. A user can search for the location employing the search bar. The map view shows each and every place by a pin, you can zoom into to check the obtainable paths to stick to your preferred place. Hardware interfaces The hardware component of the program is the board which may conventionally appear like a skateboard but operates with out any manual effort all with the use of GPS device which connects to each mobile phone and the device that feeds the information in the processor. Thereafter processor controls the motor and rotates the wheel to move forward take turns adjust speed.

Computer software interfaces

The mobile application communicates with the GPS application in order to get geographical details about exactly where the user is positioned and the visual representation of it, and with the database in order to get the data about the pointed place. Functional requirements This section consists of the specifications that specify all the basic actions of the computer software method. User Class 1 – The User

Functional requirement

1.1 TITLE: Download mobile application.

DESCRIPTION: A user must be capable to add the application by way of a shared link. Functional requirement 1.2 TITLE: User registration -Application DESCRIPTION: Provided that a user has downloaded the mobile application, then the user ought to be in a position to register by way of the application employing a given pin quantity.

Functional requirement

1.three TITLE: Application – Search DESCRIPTION: Offered that a user is logged in to the mobile application, then the user must be capable to search for places. A user should be able to choose desired path choices.

Functional requirement

1.four TITLE: Mobile application – Search outcome in a map view DESCRIPTION: Search benefits can be viewed on a map. On the map, the relevant information according to the user’s position and movement status are shown. A certain pin will represent destined location. Another will represent user location.

Functional requirement

1.5 TITLE: Mobile application – Navigation DESCRIPTION: When a selection is produced, the final location need to be sent to the mobile phone’s GPS-navigation program. The user need to then be navigated to the destination. Performance specifications The requirements in this section supply a detailed specification of top quality of the user interaction

Prominent search function TITLE: Prominent search feature DESCRIPTION: The search feature should be prominent and simple to uncover for the user.

Usage of the result in the map view TITLE: Usage of the outcome in the map view DESCRIPTION: The outcomes displayed in the map view must be user friendly and effortless to comprehend. Choosing a pin on the map should only take one click. Method dependability TITLE: System Dependability DESCRIPTION: The fault tolerance of the system. If the system goes into some fault, it ought to slow down and quit in response to fault.

Protected travel selection TITLE: Safe travel choice DESCRIPTION: The board must be capable of responding to instant obstacles. Speed Control TITLE: Speed Handle DESCRIPTION: The user need to be capable of controlling the speed from user interface. Prioritization and Release Strategy and Software program Models Software program Models In order to get a view of how to divide the needs and what requirements ought to be greatest suited prototype model is best opted for creating of this device. Prioritization and Release Strategy

1st a prototype will be made to verify the implementation of the functionality. Right after effective testing of object response, speed limits a human sized riding board will be created and henceforth that as well will be tested at different speeds on distinct course paths. After satisfying test results the board will be released as a total project. Figure 2 Functionality Diagram