High-Level Design Document “Application Name”

Application Proposal:

“Name”

Author / Name + ID + email
Version
Created
Last Updated
Current Status

Table of Contents

Table of Contents

Introduction

1.1Overview

1.2The Market

1.2.1Users

1.2.2Needs

1.2.3Competition

1.3Design Goals and Non-Goals

1.3.1Goals

1.3.2Non-Goals

1.4Dependencies

1.5Assumptions and Design Constraints List

1.6Issues List (Risks)

2Application Design

2.1Features and functionalities

2.2Screens – Functionality and Flow

2.2.1Screens Functionality

2.2.2Screens Flows

3Logical Architecture

3.1Application Context

Introduction

1.1Overview

Provide a high level description of the application

1.2The Market

Describe the target market –

1.2.1Users

Describe who the planned users of the applications are, the users can be defined in many ways, for example –

■Gender

■Age

■Location

■Drivers

■Sport fans

■Sick

■….

1.2.2Needs

Describe WHY the users will use the application –

■What are the needs which the application will address?

■How the needs are answered today?

■Why the application will give a better answer to the needs?

1.2.3Competition

Are there other applications that might compete, trying to address the same users or needs?

1.3Design Goals and Non-Goals

1.3.1Goals

Provide a short overview (up to 2 pages) of the capabilities of the application and the services it provides. Potential issues to be covered include:

■Major services, capabilities and functionality of the application

■Typical usage

1.3.2Non-Goals

Describe which need the application is not going to address and which functionality the application is not planned to have

1.4Dependencies

■Such as interaction with other systems (such as web services)

1.5Assumptions and Design Constraints List

1.6Issues List (Risks)

What are the issues & risks in developing the application and how you are going to address them?

2Application Design

2.1Features and functionalities

List of features and functionalities the application will support

For each a short description of what it supposed to do

(What it is doing not how it gets done)

2.2Screens – Functionality and Flow

2.2.1Screens Functionality

List of all the screens / pop-ups/ notifications and what is the functionality that will be supported in each

2.2.2Screens Flows

List of all the screens / pop-ups/ notifications and what is the flow between the screens

(What will happen when the application is dormant or tombstone?)

3Logical Architecture

3.1Application Context

Diagram of the architecture of the application and its interaction with external components