SECTION $1$: OBJECTIVE $/$ SCOPE

PROBLEM

You work for a local project management company that specializes in helping start$-$up

companies and entrepreneurs manage new and existing projects. Projects range from new

websites, desktop and mobile applications, advertisement, and marketing. The company needs a

new tool to help its employees and customers manage tasks and has hired you to create their

website. You have already chosen the MEAN stack environment for the website and elected to

use Swagger for documenting the API's.

Out of Scope

Authorization $($i$.$e$.,$ roles$)$

Updating the text of a task

Assigning tasks to team members

Reporting

Security

Employees must be signed in to view the task management page. The landing page, about,

contact, and $404$ pages do not require authentication.

Requested Completion Date

Nodebucket should fully built, tested, and deployed by the end of wee five $(5).$

SECTION $1$: INTRODUCTION

$1\mathrm{.}1.$ Purpose

$[$Provide a brief overview of the application and its purpose$]$

$1\mathrm{.}2.$ Terminology

$[$Identify the technical terms used in this document; list the name and a brief definition in a table or

matrix$]$

$1\mathrm{.}3.$ User Personas

$[$Identify the core users of the proposed solution$]$

$1\mathrm{.}4.$ User Stories

$[$Identify the user stories, based on the above personas$]$

$1\mathrm{.}5.$ Work Estimations

$[$Given the above user stories, identify the appropriate story points$/$time estimations$]$

SECTION $2$: PROCESS DESIGN

$2\mathrm{.}1.$ Sitemap

$[$Create a sitemap for the proposed website$]$

$2\mathrm{.}2.$ Prototypes

$[$Make sure the prototypes cover every page$/$dialog$/$message in the proposed solution$)$

$2\mathrm{.}3.$ ORD $($Object Relational Diagram$($s$)$

$[$Create an ORD based on the proposed business rules$]$

$2\mathrm{.}4.$ NoSQL Data Structure

$[$Covert the above NoSQL Document Diagram into a NoSQL Data Structure $($JSON data$)]$SECTION $3$: FUNCTIONAL DESIGN

$3\mathrm{.}1.$ Overview of the Design

$[$This section will cover what you are envisioning the system will do$,$ specifically any minimum $/$

maximum value of a field, navigation, error handling, and logging$.$ If there are exceptions,

explain how they are handled and under what circumstances they will be generated$/$thrown$]$

$3\mathrm{.}2.$ Functional Design

$[$This section is a list of the design definitions for the requirements in the BRD$]$

$3\mathrm{.}3.$ Feedback$/$Comments

$[$This section is for any addition comments$/$feedback that will help business and other team

members better understand the solution you built$]$