Software Requirements, Lab Reports of Software Engineering

1. Google Play Account: For hosting Android app. 2. Data API hosted on Call123.com domain (or Heroku.com) 3. OTP generation mechanism (Twilio or any other decided later) 4. Application would run on any Android v4+ device

Typology: Lab Reports

2019/2020

Uploaded on 04/18/2020

muhammed-tausif
muhammed-tausif 🇵🇰

1 document

1 / 1

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Requirement Specification
Document
Ca ll123 (A nd roid App )
Functional Requirements:
1. Google Play Account: For hosting Android app.
2. Data API hosted on Call123.com domain (or Heroku.com)
3. OTP generation mechanism (Twilio or any other decided later)
4. Application would run on any Android v4+ device
Non-Functional Requirements:
Users:
There are three users of this application:
1. Admin
2. Vender
3. User
Specification:
NO Specification Role
01 Generate OTP User
02 OTP would be received via SMS
03 Users would enter the OTP and create account User
04 Rider and Vender would be displayed with different colors
05 User can view Google Map on which nearest rider and
vender are displayed
06 User can view short name of Rider/Vender on the map
07
Use case diagram:
Dad

Partial preview of the text

Download Software Requirements and more Lab Reports Software Engineering in PDF only on Docsity!

Requirement Specification

Document

Call123 (Android App)

Functional Requirements:

  1. Google Play Account: For hosting Android app.
  2. Data API hosted on Call123.com domain (or Heroku.com)
  3. OTP generation mechanism (Twilio or any other decided later)
  4. Application would run on any Android v4+ device

Non-Functional Requirements:

Users:

There are three users of this application:

  1. Admin
  2. Vender
  3. User

Specification:

NO Specification Role 01 Generate OTP User 02 OTP would be received via SMS 03 Users would enter the OTP and create account User 04 Rider and Vender would be displayed with different colors 05 User can view Google Map on which nearest rider and vender are displayed 06 User can view short name of Rider/Vender on the map 07

Use case diagram:

Dad