Business Requirements Document

To compile all the business requirements of a product into a single document, I created a summary of the business goals, customer needs, and stakeholder concerns. Regarding the product being built, this document is crucial for aligning company stakeholders and keeping everyone on the same page. It specifically focuses on what needs to be accomplished, rather than how to accomplish it—something usually covered in a System Requirements or Product Requirements document.

Looking back on it now, I'd make the wireframing part longer though. I would have to do first low fidelity, then testing, iterating, having meetings with everyone about it, and then repeat everything through mid-fidelity and high fidelity.

Executive Summary

This document details the problems that the product is trying to solve by logically listing high-level business requirements in relation to customers’ needs. Our responsive web app is aimed to help people who are engaged with the rising sport of stand up paddling with weather forecasts in water and air condition details. Extra features, like social media-based route planning and additional blog contents, are also proposed to make the part of the design.

Target Audience

Our app’s target users are sports enthusiasts, from those who want to start and try the sport without any previous experience on boards, to advanced level wild water lovers and paddle yogis.

The minimum age demographic is at least 16, who can swim. Under this age, it is less likely to be that much interested in the sport to download an expert app. The upper age range is around 55, as anyone who is older than this, might have concerns about doing sport and also maybe health problems can cause issues here.

Competition

Main competitors are Paddle Logger, Go Paddling, Windy, Paddle Monster, iOverlander, RiverApp and Weesurf. However not the weather forecasts are the main feature of all of them, these can be our app’s extra features’ competitors.

Risk/Opportunity

Regarding the necessity of a weather app in daily life, we can assume that almost everyone has one on his/her phone. Competing with this occurrence makes it hard to make people change their habits and convince them with having a specific one for SUPing.

We have a great opportunity with building this app because there is no specified weather app for SUP which offer weather-based extra content like what to wear, what kind of paddle to use, buy or rent etc.

Conclusion

In spite of the significant risk mention above, we have a high possibility to succeed by such a (well) specialised app, which can provide interesting and exciting content, going beyond boring and average weather apps.

S.M.A.R.T Business Objectives

• Design a competitive responsive web app that offers specific, SUP related content with a weather forecast as its main feature. Measuring regarding needed features will take place as user surveys. Time phase: 2-3 months after starting the project
  

• Gain 800-1000 new users worldwide in 2-3 months after launching the app
  

• Get into contract-based business cooperation with 5 sport related blogs regarding the SUP specified blog posts providing feature in 1-2 months after starting the project

Scope

The basic pieces of the project are:

• Create a clean and beautiful design that makes the content easily understandable and the app quickly manageable
  

• Gain 5 blogpost provider business partners
  

• Google Map integration
  

• Official weather forecast database integration

Functional Requirements

• Onboarding page

• Language settings

• Profile customisation options

• Real-time water and air forecasts

• Route-planner with downloadable offline content

• Saved favourite location/track list

• Location follower for tracking

• Smartwatch options

• Planned route sharing for other users to join

• Notifications

• Blog post provider page based on the user’s experience level

• Connecting with other users

• Route experience reports

Delivery Schedule

Week 1 - 2

Problem statement, competitive analysis, user survey

Week 3 - 4

Evaluation of user survey, creating personas, user stories and flows

Week 5 - 6

Low and high fidelity prototypes

Week 7 - 8

Basic responsive application framework and navigation

Week 9 - 10

Implementing external blog posts & Google Maps Usable prototype and testing Finalising the user interface

Week 11 - 12

Final user testing & finalising the app

Week 13 - 14

Launch of applications Feedback monitoring