See enhanced version of this (https://www.slideshare.net/ujjwaltrivedi/prd-template-for-product-managers). A sample product requirement document draft for mobile apps. It can also be used for quick wireframing and estimates of any kind of software. It should generally be a useful tool for business analysts, product managers, pre sales consultants. It is modern, complete and agile.

1. Mobile Product
Requirements and Estimates
3/19/2012
Whatever Company
Ujjwal Vijendra Trivedi

2. <Company Name/Logo> Internal Use Only
Table of Contents
1. Objective ......................................................................................................................... 2
2. Client Requirements........................................................................................................ 2
3. Analysis........................................................................................................................... 3
4. Target Users .................................................................................................................... 3
5. Non Functional Requirements ........................................................................................ 4
5.1 Security ................................................................................................................. 4
5.2 Performance .......................................................................................................... 4
5.3 Scalability ............................................................................................................. 4
5.4 Internationalization ............................................................................................... 4
5.5 Orientation ............................................................................................................ 4
6. Functional Requirements ................................................................................................ 5
6.1 Application brief ................................................................................................... 5
6.2 Application flow (Wireframes and Use Cases) .................................................... 5
9. Reference Screenshots .................................................................................................... 6
10. Project Estimates ........................................................................................................... 7
1

3. <Company Name/Logo> Internal Use Only
1. Objective
This document provides understanding of the client’s requirements for the creation of new smart
phone app for whatsoever purpose. It also categorizes the scope into smaller feature modules for
ease of visualization, estimation and creating wireframes.
2. Client Requirements
This is a list of requirements shared by the client on email/call and brief commentary after high
level analysis of the same.
Client Specifications Comments
Secure Login Token based/https/Captcha/Social etc.
2

4. <Company Name/Logo> Internal Use Only
3. Analysis
Which applications were analyzed? What features should be added, modified, removed
for better usability/performance/security/acceptance.
4. Target Users
Class of users, Work profile of users, Age groups, Gender bias (if any)
3

5. <Company Name/Logo> Internal Use Only
5. Non Functional Requirements
5.1 Security
Encryption required?
5.2 Performance
Standard/Real time
5.3 Scalability
Expansion plans and Scalability requirement – Low/Medium/High
5.4 Internationalization
Languages? Locale?
5.5 Orientation
Landscape/Portrait/Both
4

6. <Company Name/Logo> Internal Use Only
6. Functional Requirements
6.1 Application brief
Add highlights of application from engineering/marketing perspective.
6.2 Application flow (Wireframes and Use Cases)
- 6.2.1 Icon
asdf
- 6.2.2 Splash Screen
asdf
- 6.2.3 Home screen
asdf
- 6.2.4 Screen1
asdf
- 6.2.5 Screen2
asdf
- 6.2.6 Screen3
asdf
- 6.2.7 Settings screen
asdf
- 6.2.8 About Screen
Asdf
o About text
asdf
o Emailing text
asdf
5

7. <Company Name/Logo> Internal Use Only
9. Reference Screenshots
Following screenshots are attached, illustrating the functional modules listed above, for reference
only. They do NOT indicate exact UI or functionality of mobile app.
Login Screen
6

8. <Company Name/Logo> Internal Use Only
10. Project Estimates
The effort estimates as per the given scope in attached document is discussed in
this section. These estimates are also based on assumptions stated in the
document.
Following is the module wise categorization of features for pure development
estimates on all mobile platforms. These efforts include only coding and do not
include efforts for designing, managing, testing the app:
Development Estimates (in Person Days)
Features Platforms iOS Android Windows Blackberry Symbian J2ME
Phone 7
Registration
User profile
Login
Verify availability of
Delivery to user’s
location
Ordering and
payment
UI
Menu and Pricing
Order Tracking
Store locator
Offers
Complaints and
Feedback
Total
Further adding overheads to the development estimates:
7

9. <Company Name/Logo> Internal Use Only
Business Analysis – requirement gathering and documentation a%
Design/UI creation – Creating design assets b%
QA – Testing for functionality, usability, performance c%
Project Management – managing the team and taking care of
Information Security, Business Continuity Plan, Traceability matrix, d%
Project Plan, Release Management etc.
Total e%
Business analysis will be partly common for all platforms X% of maximum effort:
NN Person days
Based on the aforementioned overheads the total effort estimates per platform
will be as follows
Complete Effort Estimates (in Person Days)
Windows
Platforms  iOS Android Blackberry Symbian J2ME
Phone 7
Total
Final Effort estimates are NNN Person – Days.
Final Cost is USD NNNNNN.
8