Functional Requirements of the Ask.Ng App.
Autor: preet • June 5, 2015 • Term Paper • 2,830 Words (12 Pages) • 947 Views
Introduction
Purpose
The purpose of this document is to capture the functional requirements of the Ask.ng app. This document was created to ensure that all our requirements in the app are captured and understood by the developers prior to the start of development.
Intended Audience and Reading Suggestions
The intended audience for this document is the application developer who will build the application.
Project Scope
This project is to build a mobile app that will allow users to ask any question, anytime, anywhere. The application is designed to connect people and businesses specific to their immediate cities in Nigeria.
The software being used for development is the Blackberry, Nokia Asha, Apple and Android development kits.
Overall Description
Product Features
This application will allow users to be able to ask questions that are broadcast to other users of the app, follow questions, view answers and report questions that violate a common use policy.
Operating Environment
The software will run on the iOS, Android, Nokia Asha and Blackberry 10 platforms.
Design and Implementation Constraints
The database that is used across all three platforms must be the same, to allow of easy synchronization of information across all three platforms.
Assumptions and Dependencies
Users will need to be able to download the apps from all 3 app stores.
Functional Requirements
Session Management – Registration & Profiles Ask, View, Follow, Report:
FR-1: After installing the Application from the App store the user will be asked to register with a valid email address that allows notifications to be sent to them in the event they chose to follow a question (same applies for business registrations). Users can also register with their existing Facebook or Twitter accounts. The application shall also have the usual password reset, password forgotten protocols including allowing admin to reset for users where need be.
FR-2: User names should be created in the same format as twitter (i.e. @Michael) and businesses can register with their business name (i.e. @GarmetCare_Drycleaners).
FR-3: On the registration screen the user will be asked if they want to register as an individual or as a business. The difference between the two registrations is the business registration screen should include a call to action asking the business if they would like to register to receive alerts when certain key words are typed into the application. There should be an option to take you to a tutorial screen that will explain how the key words work. (This also allows us specifically target business inboxes for marketing of keywords)
...