Scribd
Upload
100 views3 pages

Guide Mobile App URD

This document outlines the user requirements for a new mobile application. It specifies that the application is intended for external users to solve a specific problem. The document defines the scope, user needs, assumptions, functional and nonfunctional requirements for the app. It provides details on the intended audience, features, interactions and specifications needed for the mobile application to function properly.

Uploaded by

Gabbie Solero
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100 views3 pages

Guide Mobile App URD

This document outlines the user requirements for a new mobile application. It specifies that the application is intended for external users to solve a specific problem. The document defines the scope, user needs, assumptions, functional and nonfunctional requirements for the app. It provides details on the intended audience, features, interactions and specifications needed for the mobile application to function properly.

Uploaded by

Gabbie Solero
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

TITLE: <YOUR TITLE>

PREPARED BY: <NAME OF GROUP MEMBERS>

DATE: (Date of Submission)


<NAME OF YOUR MOBILE APPLICATION>
USER REQUIREMENTS DOCUMENT

1. INTRODUCTION

1.1. PURPOSE
Set the expectations for the outcome of your mobile application.

1.2. INTENDED AUDIENCE


Who is the software for? Who is the end-user? Will the software be used
internally at a company or externally?

1.3. INTENDED USE


What is the software for? What problem is it solving?

1.4. SCOPE
Explain the scope of the software. What are the main goals and objectives?
How do they relate to the company’/organization/sector’s goals?

1.5. DEFINITION AND ACRONYMS


Provide an overview of any definitions the reader should understand before
reading on.

2. OVERALL DESCRIPTION
Describe what you are building and for who.

2.1. USER NEEDS


Explain the user needs for this software. This is where you specify the use
cases along with the actors involved within that use case.

2.2. ASSUMPTIONS AND DEPENDENCIES


What assumptions are you making that could cause an error in your approach?
Are there any assumptions you’re making with the URD that could turn out to be false?
Also note in here if your mobile application is dependent on any external factors – this
might include software components you’re reusing from another mobile application.

3. SYSTEM FEATURES AND REQUIREMENTS

3.1. FUNCTIONAL REQUIREMENTS


Outline tasks users want to perform within your mobile app and list possible
user–app interactions. Based on this data, you can derive the core functionality your
app must provide to enable these interactions to happen.

3.2. EXTERNAL INTERFACE REQUIREMENTS


Are there any UX and UI requirements that you must keep in mind as you build?
List the hardware and software specifications of your mobile application here.

3.3. SYSTEM FEATURES


What features are required for your mobile application to even work? List and
define the features that will make your mobile application work. Include sitemaps
and/or wireframes of your mobile app.
3.4. NONFUNCTIONAL REQUIREMENTS
Gather users’ expectations related to your mobile app’s level of performance,
security, usability, and so forth.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy