High Level Solution Architecture Design

and Requirements Package:

SHUBER Project

Interactive Partners LLC

Group 2: Eli Lerner, Atamai Tuiolosega, Hao Zhang

Document Date: v1.0_04/12/2018

Table of Contents

Table of Contents 1

1. Introduction 3
1.1 Document Purpose 3
1.3 Audience 3
1.4 Business Background 3
1.5 Minimum Viable Product 4
1.6 Project Goals 4
1.7 Project Scope of Work 5
1.7.1 Statement of Purpose 5
1.7.2 Work Breakdown Structure 5
1.7.3 Deliverables 6

2. Project Requirements 6
2.1 Business Requirements 6
2.2 Functional Requirements 8
2.2 Non-Functional Requirements 9
2.3 Risk Log 10
2.4 Risk Assessment Matrix 10

3. Functional Specification 12
3.1 Shuber Experience Overview / MVP Extended 12
3.2 Shuber Subscription Rules 12
3.2.1 Credit / Shoe Accessibility 12
3.2.2 Cost and Credits by Plan 13

4. Solution Design 13
4.1 Solution Overview 13
4.2 Business Intelligence Tools 13
4.2.1 Option 1 (Top Recommendation): IBM Watson 13
4.2.2 Option 2: Google Analytics 14
4.2.3 Option 3: Tableau 14
4.3 Data Storage 14
4.3.1 Option 1 (Top Recommendation): Amazon S3 14
4.3.2 Option 2: DropBox 14
4.3.3 Option 3: OneDrive 14
4.4 Platform Hosting 14

1
 4.4.1 Option 1 (Top Recommendation): Shopify Plus 14
4.4.2 Option 2: GoDaddy 15
4.4.3 Option 3: HostGator 15
4.5 Development Vendor Proposal 15
4.5.1 Web Development 15
4.5.2 iOS + Android Development 15
4.6 Project Management 15

5. Technical Design 16
5.1 Use Case Diagram 16
5.2 Data Flow Diagram 18
5.3 Interaction Scenarios / Activity Diagrams 18
5.3.1 User Logs in to Account 19
5.3.2 User Creates Account 20
5.3.3 User Browses Shoe Inventory 21
5.3.4 User Rents Shoes 23
5.3.5 User Provides Payment 23
5.3.6 User Ships Shoes Back 25
5.4 High Level Class Diagram 27
5.5 State Chart: Shoes Status 28
5.6 Wireframe Flow Diagram 29
5.7 Problem Scenarios 30
5.7.1 Scenario 1 30
5.7.2 Scenario 2 30

6. Implementation Plan 30
6.1 Proposed Rollout Schedule (January - December 2018) 30
6.2 Timeline 32

7. Budget Allocation 32
7.1 Assets Cost 32
7.2 Service Cost 33

8. Ongoing Support 33

9. Points of Contact / Stakeholder Analysis Matrix 34

2
1. Introduction

1.1 Document Purpose

The ultimate purpose of this document is to describe the high level solution design for potential
architecture solutions for the SHUBER project.

The key objectives of this document is to:

● Describe the main design components of the solution in sufficient detail in relation to
○ The business design
○ The functional (technical) design

The initial sections provide the context for the solution by describing the business drive and
associated background information. We then will show how our proposed solution fits with the
desired outcome by fleshing out the functional and technical specifications that we’ve
determined during our engagement with Shuber.

1.3 Audience
The intended viewers of this document are as follows:

● Project sponsor + stakeholders

● Potential user population
● IS3500 Spring 2018 Students

1.4 Business Background

Taken from the​ IS3500 Case Study description.

Michelle has an affection for shoes. Even though she has well over 120 pairs of shoes ranging
from casual to fancy, she still enjoys shopping for new footwear whenever she can. Her Premier
status at DSW hints at the fact that she may have an addiction, as her husband pointed out.
Unfortunately, she cannot afford many of the shoes that she really likes and that fit her well.
Footwear by fashion designers such as Christian Louboutin don't come cheap; a pair can easily
run $2,000 and up. On top of that, she only has a few occasions to wear high-end shoes and
fashion designs.

3
She knows that she is not the only one with that conundrum. Many of her friends feel the same
way -- of course, they solve the problem by borrowing from Michelle's extensive collection. So,
after many sleepless nights, she decided to do something about that. Why not rent out her
footwear -- kind of like the Uber or Lyft of shoes, she thought to herself? In fact, why not buy
footwear in common sizes and offer them to women on a rental or perhaps even a subscription
basis. Wouldn't it be great to get a new pair of shoes every week or maybe every couple of
weeks, wear them a couple of times, and then simply return them. Michelle is certain that this
would make a great business. Who knows, maybe adding accessories and jewelry might be a
possible expansion path. And after she has made millions she can buy all the Miu Miu, Gucci,
Walter Steiger, Jimmy Choo, Louis Vuitton, and Christian Louboutin shows she ever wanted.

A business like that requires a great user experience: simple, clean, and uncluttered. A good
website complemented with great apps for iPad, iOS, and Android would be key, in her opinion.
She's shopped for a while at fashion discounters such as MyHabit and knows what attracts her.
Clearly, she needs to do more research and understand the needs of users and their
requirements much better. Once she understands the requirements better, she feels that
outsourcing would be the best way to get up and running quickly -- in fact, the first iteration
doesn't have to do everything. Releasing the website and apps incrementally might make the
most sense. While the development of the website and eventually the apps are under way, she
can focus on financing her inventory, buying the shoes, and finding a way to properly store and
care for them -- tight security would be key.

Jeff Greenberg, her serial entrepreneur neighbor who's built a few companies with great web
presence, recommended she hire the local design and analysis firm Interactive Partners LLC.
Jeff is confident that they can help her flush out the requirements, build a good specification of
her website, and help her communicate the requirements specification to an outsourcing
partner. While she'd rather hire a local consulting firm, she knows that she might have to
engage offshore resources and is pleased that Interactive Partners knows how to build
specifications that are thorough, detailed, and understandable by offshore programmers.

1.5 Minimum Viable Product

A ​website​, ​iOS mobile app​, and ​Android mobile app​ that handles shoe rentals based on a
monthly subscription that is fully implemented by the end of 2018.

1.6 Project Goals

Ultimate goals of the project are:

● Establish a strong user base

● Minimize cost/stay within budget

4
 ● Create a flexible platform

● Maintain responsiveness

● Ensure a low risk implementation

● Stay within time constraints

1.7 Project Scope of Work

1.7.1 Statement of Purpose

The ultimate purpose of Interactive Partners LLC’s engagement is to ​assist with the design
and analysis of the Shuber business​ as well as help ​discover the business, functional,
and non-functional requirements​ that the project will have. Interactive Partners LLC will also
assist with the ​platform specifications and screen prototypes.

1.7.2 Work Breakdown Structure

1.7.3 Deliverables
Interactive Partners LLC will produce the following deliverables during their engagement with
the Shuber project:

5
 1. Solution Architecture Proposal + Requirements Package
2. Web Screen Prototypes
3. Mobile Screen Prototypes

2. Project Requirements
Below are the ​business​,​ functional​, and ​non-functional business requirements​ for this
project as well as the ​risk log​ and associated ​risk assessment matrix.

2.1 Business Requirements

Priority Number Type Requirement Post-Condition

Level Requirement

High BREQ-0010 Business This product will require the following Roles are fulfilled.
employee roles:
● Customer Service
● Marketing
● Shoe-gathering / Research
● Legal
● Business Development
(Outsourced, On-shore)
● Web + Mobile Development
(Outsourced, On-shore)

High BREQ-0020 Business The ideal budget is $250,000. Capital spent on

project is
<=$250,000.

Medium BREQ-0030 Business Target users will be “ladies attending The user
events throughout the year: demographics
executives, prom, weddings, derived from the
birthdays, xmas”. business intelligence
tools used on the
Shuber platform
match the described
target users after the

6
 go-live dates.

Medium BREQ-0040 Business The client has no interest in or The development

experience with offshore companies used are
development companies and would On-shore or
like to use nearshore companies that Near-shore.
have been suggested by the partner.
(Mexico and Argentina).

Medium BREQ-0050 Business The product will be initially offered in The Shuber
the local neighborhood, and then platforms are rolled
regionally by the end of the year, and out locally,
then nationally by the end of next regionally, and then
year, and eventually internationally nationally by the end
(within 2 years). of 2019, and
internationally by
2020.

Medium BREQ-0060 Business The client plans to keep their own Shuber keeps their
inventory, but eventually wants to inventory initially, but
have enough volume that they can then grows their
offer any shoe, but not necessarily shoe inventory and
have it in stock until there is an offering according to
actual order. the trends derived
from their BI tools
used on the site.

Medium BREQ-0070 Business The intended initial shoe inventory The initial shoe
size is 250 pairs of shoes to start inventory is 250
with, and then expanding that to pairs of shoes and
2,500 pairs of shoes by the end of then is expanded to
the year. 2,500 pairs by the
end of 2018.

Low BREQ-0080 Business Similar platform designs to consider The finalized Shuber
will be: platform design
● Uber mirrors the
● Lyft mentioned
● Airbnb applications.
● Zipcar

Low BREQ-0090 Business This product will be initially promoted The product will be
via Instagram and Facebook. successfully

7
 promoted via the
mentioned social
media platforms.

2.2 Functional Requirements

Priority Number Type Requirement

Level

High FREQ-0010 Functional The product will be offered on the following

platforms:
● Website
● Mobile App(iOS & Android)

High FREQ-0020 Functional The platforms will be cloud-based.

Medium FREQ-0030 Functional Customer support for the product will be handled via
email and phone and will be provided in-house in
order to ensure the best turnaround time and overall
experience.

Medium FREQ-0040 Functional The users will be prompted to create an account

before being able to use the service the product will
provide.

Medium FREQ-0050 Functional The user will have to provide the following
information upon account creation:
● Email
● First Name
● Last Name
● Phone
● Address
● Card details for deposits and payment

Low FREQ-0060 Functional The user will have to provide the following
information upon account creation:
● Would like Paypal
● Would like Integration with other
social media accounts, potential to

8
 provide discounts for each share, like,
repost, etc.

Low FREQ-0070 Functional The structure of the subscription packages and plans
will be offered as following:
● Monthly
● Weekly
● # of rentals
● Price

Low FREQ-0080 Functional The client plans to communicate with their users via
Instagram and Facebook initially, however there is
the eventual desire to integrate an onsite messaging
system.

2.2 Non-Functional Requirements

Priority Number Type Requirement

Level

High NREQ_0010 Non-Functional Shuber should use Business Intelligence tools to

capture data trends and use them to improve the
product.

High NREQ_0020 Non-Functional The Shuber platform will need to use a cloud-based
data storage solution.

High NREQ_0030 Non-Functional User should be able to view search results no longer
than 5 seconds after they’ve made the initial search.

High NREQ_0040 Non-Functional User should be able to use the Shuber platform at
any time of the day.

High NREQ_0050 Non-Functional Product functionality should be consistent across

Web and Mobile platforms.

9
2.3 Risk Log

Risk Risk Risk Description Status Comments

Level Number

High R_0010 No determination on security, OPEN Shuber will have to handle

privacy policy, or terms of this.
service/use handling.

Medium R_0020 No determination on how to PENDING IP LLC provides data

store customer information. storage options for Shuber.

Medium R_0030 No determination on platform PENDING IP LLC provides platform

hosting. hosting options for Shuber.

Medium R_0040 No determination on business PENDING IP LLC provides business

intelligence tools. intelligence tool options for
Shuber.

High R_0050 No determination on shipping PENDING IP LLC suggests process by

process. which Shuber can handle
shoe return shipments.

Low R_0060 Contracted development team OPEN TBD

cannot deliver product on time.

Low R_0070 Contracted services have OPEN TBD

system outage.

Low R_0080 Shuber project is over-budget. OPEN TBD

Low R_0090 Shuber platforms are not used OPEN TBD

enough to maintain business.

2.4 Risk Assessment Matrix

Risk Risk Description Likelihood Impact Risk Score Management

10
Number of Strategy
Occurrence

R_0010 No determination 0.3 5 15 TRANSFER

on security, privacy
policy, or terms of
service/use
handling.

R_0020 No determination 0.1 8 8 TRANSFER

on how to store
customer
information.

R_0030 No determination 0.05 8 4 AVOID

on platform
hosting.

R_0040 No determination 0.1 8 8 TRANSFER

on business
intelligence tools.

R_0050 No determination 0.1 8 8 TRANSFER

on shipping
process.

R_0060 Contracted 0.3 5 15 MITIGATE

development team
cannot deliver
product on time.

R_0070 Contracted 0.1 8 8 TRANSFER

services have
system outage.

R_0080 Shuber project is 0.3 3 9 MITIGATE

over-budget.

R_0090 Shuber platforms 0.3 8 24 AVOID

are not used
enough to maintain
business.

11
3. Functional Specification

3.1 Shuber Experience Overview / MVP Extended

1. Users should be able to ​create an account ​and ​select a subscription plan​ for the
Shuber system. Guiding principle: Less is more, only take the info that is needed.

2. Users should be able to ​login seamlessly to the Shuber website/mobile application.

3. Users should be able to ​browse the Shuber product inventory ​and​ filter according to
location, time availability, price, and type of shoe.

4. Users should be able to ​rent whatever selected shoes they desire,​ and ​receive the
selected shoes by the time they specified.

5. Users should be able to ​easily provide payment information for their accounts​, and
receive timely confirmations for received payments for orders.

6. Users should be able to ​easily ship back shoes​ by ​utilizing the prepaid shipping
labels either provided in the original shipment to them, or provided on their online
Shuber account.

7. Users should be able to ​easily rate and leave feedback​ on their Shuber orders.

3.2 Shuber Subscription Rules

3.2.1 Credit / Shoe Accessibility

Cost Credits

Shoes <​ $100 1

$100 ​< Shoes < ​$250 2

$250 ​< Shoes <​ $500 3

$500 ​< Shoes 4

12
3.2.2 Cost and Credits by Plan

Plan Bronze Silver Gold Platinum

Cost $20 $35 $50 $75

Credits 2 3 5 8

4. Solution Design

4.1 Solution Overview

Below, the team at Interactive Partners LLC has put together a list of proposals for the following
solution elements:

● Business Intelligence Tools

● Data Storage
● Platform Hosting
● Development Teams

The final solution design is ultimately up for determination by the Shuber stakeholders, however
our top recommendations are indicated.

4.2 Business Intelligence Tools

4.2.1 Option 1 (Top Recommendation)​: ​IBM Watson

Interactive Partners LLC recommends Shuber use ​IBM Watson​ because it is an easy to use
Business Intelligence tool that seamlessly takes unstructured data and uses its “Watson AI” to
discover trends a business wouldn’t normally see itself. The tool also suggests ways that a
business can improve and it’s incredibly powerful analytics engine and is shaping how
businesses utilize machine learning and artificial intelligence.

13
4.2.2 Option 2:​ ​Google Analytics

Google Analytics ​is a top-tier solution for both website and mobile application data analysis. It is
completely free, which is a huge draw for many smaller businesses. The biggest drawback is
the lack of quality customer support, but ultimately it is a powerful tool and a great option for
Shuber.

4.2.3 Option 3: Tableau

Tableau Desktop​ is another great BI tool solution because of its intuitive design and widespread
use across businesses everywhere. It is defined as a self-service business intelligence tool and
is renowned for its massive collection of data visualizations and connectors.

4.3 Data Storage

4.3.1 Option 1 (Top Recommendation): Amazon S3

Interactive Partners LLC recommends Shuber use ​Amazon S3’s cloud storage solution​ because
it is an incredibly easy to use web interface with flexible pricing and storage options. It is backed
by Amazon, an industry-standard, and is known for its high configurability and reliability.

4.3.2 Option 2​:​ DropBox

Another reputable name in terms of cloud-based data storage, ​DropBox​ is a great option that
supports all operating systems. The biggest downside is cost, however its ease of use and
reliability make it a solid option for Shuber.

4.3.3 Option 3: OneDrive

OneDrive​ is a good option for Shuber because it can be seamlessly integrated with Microsoft
Office 365 Business accounts- an industry standard in the business world. It is relatively cheap,
and will ultimately do the job.

4.4 Platform Hosting

4.4.1 Option 1​ ​(Top Recommendation): Shopify Plus

14
Interactive Partners LLC recommends Shuber use the ​Shopify web-hosting platform​ because it
offers domain services as well as ecommerce site platform development templates. Shopify is
very intuitive to use and handles all of the ecommerce functionality (payments, security,
shipping, etc.). Shopify provides professional templates at low costs and is a great solution for a
small business like Shuber.

4.4.2 Option 2:​ ​GoDaddy

GoDaddy​, another great web-hosting platform solution, is known for their excellent customer
service which would be very useful for a fledgling company like Shuber. GoDaddy offers lots of
features and flexible website-building tools, which makes it a great option.

4.4.3 Option 3:​ ​HostGator

HostGator​ is known for its quality cloud and VPS server packages for small businesses. It’s
reliable, has great site-building software, and ultimately provides a very solid service for a very
reasonable price.

4.5 Development Vendor Proposal

4.5.1 Web Development

This design decision is ultimately up to the Shuber stakeholders, however Interactive Partners
LLC proposes Shuber use an Onshore development team, specifically the ​Third and Grove firm
based in Boston. The scope of the project does not require a ton of technical skill and Third and
Grove is known for their familiarity and expertise with the Shopify platform. The firm is reputable
and has a good track record with new eCommerce businesses.

4.5.2 iOS + Android Development

Interactive Partners LLC proposes Shuber use an Onshore development team, specifically the
Snappii firm​ based in New Hampshire, due to the fact that the front-end of the applications have
been mapped out, and the firm is known for a quick turnaround due to their extensive portfolio of
projects with different businesses. With the rollout timeline proposed in this document, there
would be more than enough time for the app development team to analyze the finalized Shuber
web platform designed by Third and Grove and complete mobile applications.

4.6 Project Management

15
Interactive Partners LLC proposes Shuber use a ​contracted project manager and business
analyst​ from either our firm, IP LLC, or another firm. It’s important that there’s a separation of
tasks/interests, so IP LLC would highly suggest a ​third party to help manage Third and
Grove’s work and Snappii’s work.​ The appointed project manager would help coordinate
between Third and Grove, Snappii, and the Shuber stakeholders to make sure that business
requirements are being met and the overall Shuber implementation runs smoothly and
effectively.

5. Technical Design

5.1 Use Case Diagram

Use Cases:
● User Logs In
● User Creates Account
● User Selects Subscription Plan
● User Browses Shoe Inventory
● User Rents Shoes
● User Ships Shoes Back

16
17
5.2 Data Flow Diagram

5.3 Interaction Scenarios / Activity Diagrams

Below are the interaction scenarios for each use case a user will have for the Shuber website.

18
5.3.1 User Logs in to Account

Actors:​ Shuber user

Pre-conditions:​ Shuber user has an account and wants to log in.

Narrative:
1. <Process Start> User navigates to the Shuber main page and searches for shoes
2. User clicks on upper right “Log in” button
3. System loads “Login” page, where user is prompted to fill in the following test
boxes:
a. Email Address
b. Password
4. User clicks “Login” button {V.1}
5. User is brought back to “Shoe Browsing” Page and is logged in <Process End>

Variation:
V.1: User can not login the account
1. System shows the password is not correct
2. System shows the account is not exist

Post-conditions: ​System shows “Shoe Browsing” Page, and user status is logged in.

19
5.3.2 User Creates Account

Actors:​ Shuber user

Pre-conditions:​ Shuber user does not have an account and would like to create one.

Narrative:
1. <Process Start> User navigates to the Shuber main page and searches for shoes
2. User clicks on upper right “Sign Up” button
3. System loads “New Account” page, where user is prompted to fill in the following
text boxes:
a. First Name
b. Last Name
c. Email address
d. Password
e. Confirm Password
4. User clicks “Next” button at the bottom of the screen {V.1}
5. System loads “Account HomePage” <Process End>
Variation:
V.1: User can not create the account

20
 1. System shows the Email address is already registered.

Post-conditions: ​System shows the “Account HomePage” and user can login with new account

5.3.3 User Browses Shoe Inventory

Actors:​ Shuber user

Pre-conditions:​ Shuber user wants to view the Shuber shoe inventory.

Narrative:
21
 1. <Process Start> User navigates to the Shuber main page
2. User enters the Brand or Type of shoe they’re looking for
3. User enters the dates for when they will need to borrow the shoes
4. User enters the location they want to browse in
5. User selects the “Search” button, which brings the user to the “Shoe Browsing page”
<Process End> {V.1}

Variation:
V.1: User can not find the shoes they are looking for
1. System shows that the shoes is not found

Post-conditions: ​User can see the result showing on the “Shoe Browsing page”

22
5.3.4 User Rents Shoes

Actors:​ Shuber user

Pre-conditions:​ Shuber user has an account, has browsed the shoe inventory and wants to
rent.

Narrative:
1. <Process Start> User selects a product from the “Shoe Browsing Page”
2. User is brought to the “View Product Page”
3. User reviews details/reviews of product
4. User clicks “Add to Cart” button <Process End> {V.1}

Variation:
V.1: User fails to add the shoes to cart
1. The shoes had just been rented

Post-conditions: ​Shoes are added to cart, and user can view it in the “Cart” page

5.3.5 User Provides Payment

Actors:​ Shuber user

23
Pre-conditions:​ Shuber user has an account, has selected a shoe to rent, and now needs to
pay for their selected shoes.

Narrative:
1. <Process Start> User navigates to “Cart” page
2. User reviews product(s) summary
3. User selects “Checkout” button
4. User is brought to “Payment” page
5. User has option to enter new payment details or select their default payment method
6. User enters shipping address
7. User selects “Place Order” button {V.1}
8. User is presented with “Confirmation” Page <Process End>

Variation:
V.1: Order can not be placed
1. User did not fill all the information requirements
2. The payment is failed

Post-conditions: ​The system shows the “Confirmation” Page, and the order status update as
placed

24
5.3.6 User Ships Shoes Back

Actors:​ Shuber user

Pre-conditions:​ Shuber user has an account, is currently rented out shoes and now needs to
send them back.
Narrative:

1. <Process Start> User needs to ship back shoes

2. User either uses prepaid shipping label from box to place on box and ship back
a. Alternative: User prints prepaid shipping label from Shuber account
3. Shipping carrier [UPS, DHL, Fedex, etc.] ships box back to Shuber headquarters
4. Shuber receives shipment <Process End> {V.1}

25
Variation:
V.1: Shuber does not receive package
1. Shipping carrier failed
2. User did not ship back the shoes

Post-conditions: ​The shoes are received

26
5.4 High Level Class Diagram

27
5.5 State Chart: Shoes Status

28
5.6 Wireframe Flow Diagram
Mobile Wireframe Flow

29
5.7 Problem Scenarios

5.7.1 Scenario 1

Mary’s husband is being honored at his law firm for being a stellar employee. The black-tie
event is at the Ritz-Carlton and ​Mary will have to wear fancy shoes, which she doesn’t own
herself. She doesn’t want to buy brand new pair since she knows she’ll only wear them to
this event and maybe a few others in the future.

5.7.2 Scenario 2

Christina​ is a young, fun-loving journalist who ​likes to go out and wear the latest and
greatest fashion.​ She especially has an affinity for Jimmy Choo heels. Unfortunately, ​her
salary doesn’t allow her to buy all the shoes she wants to wear, so she often has to
borrow from friends.

6. Implementation Plan

6.1 Proposed Rollout Schedule (January - December 2018)

Jan 2 - April 12:​ Definition of Project Scope + Gathering Requirements

During this time, Interactive Partners LLC will assist Shuber with defining the scope of the
ultimate project as well as gather requirements

● Deliverables:
○ Solution Architecture Proposal and Requirements Package
○ Web Screen Prototypes
○ Mobile Screen Prototypes

April 12 - Aug 1:​ Platform Development + Training

During this time, Shuber will work with the chosen development team [see 4 For suggested
development firms as well as associated platform hosting, data storage, and BI tools]

● Deliverables:
○ Shuber Website

30
 ○ Shuber Mobile Application(s)
■ iOS
■ Android

July 1: ​Web Go-Live Date

● Shuber Website deployed

Aug 1:​ Mobile Go-Live Date

● Shuber Mobile Applications deployed

Aug 1 - Nov 1: ​Platform Refinement + Promotion

During this time, Shuber will work with their development team and their chosen analytics tool to
further improve the Shuber product post go-live dates as well as improve the marketing to
attract more users from the target audience

● Deliverables:
○ Improved Shuber Website
○ Improved Shuber Mobile Application(s)
■ iOS
■ Android

Nov 1 - Jan 1:​ Platform Extension (Implement the next business feature)

● During this time, Shuber’s development team will start to implement new features that
the stakeholders see fit for the overall business vision depending on the success of the
product(s)

● Deliverables:
○ To be determined

31
6.2 Timeline

7. Budget Allocation
The total estimated cost of the proposed service vendors and developers are ​$121,794​ for the
2018 fiscal year, with ​$3,330 going towards asset costs ​and ​$118,464 going towards
services costs.

This is ​$128,206 under the initial given budget​ by the Shuber stakeholders.

Below is the breakdown of the budget.

7.1 Assets Cost

Solution Asset Vendor Months of Use Estimated Price

Platform Hosting Shopify 6 $1800 [$300 per

month]

Data Storage Amazon S3 6 $1,350 [~$225 per

month]

Business Intelligence IBM Watson 6 $180 [$30 per month]

Estimated Total Asset Cost: ​$3,330

32
7.2 Service Cost

Service Vendor Roles Estimated Estimated Price

Effort Hours

Web Third and Grove 2-4 Developers 588 $58,800

Development [Business Days [~$50 per hour]
in engagement x
4 working hours
per day]

Android/iOS Snappii 3 Developers N/A - $7,500

App Subscription [Depends on
Development Based flat fees usage]

Project Interactive 1 Project Manager 567 $23,814

Management Partners LLC [Business Days [$42 per hour]
in engagement x
3 working hours
per day]

Business Interactive 1 Business Analyst 567 $28,350

Consulting Partners LLC [Business Days [$50 per hour]
in engagement x
3 working hours
per day]

Estimated Total Service Cost:​ ​$118,464

8. Ongoing Support
Interactive Partners LLC proposes Shuber keep their Project Manager and Business Analyst
representatives to ensure that the project progresses smoothly. If Shuber agrees to this,
Interactive Partners LLC will assign ​one of their representatives​ to stay on to oversee the
work of their employees through the end of 2018 to assist with business consulting. This
document serves as a high-level guide to hand-off to another firm, however ​the value of an
on-call consultant​ who is familiar with the business intent is unparalleled and ​would help
ensure the overall success of the Shuber business.

33
 Ongoing support plans with other vendors will have to be negotiated with the respective
vendor’s representatives.

9. Points of Contact / Stakeholder Analysis Matrix

Impact /
Contact Person + Company Stakeholder Role What is important to the stakeholder?
Influence

Eli Lerner
lerner.el@husky.neu.edu Project Manager /
Screen Prototype High Manage project, develop screen prototypes that meet requirements.
(617) 519-2051 Designer
Interactive Partners LLC

Atamai Tuiolosega
tuiolosega.a@husky.neu.edu Project Manager /
High Manage project, gather requirements for overall solution design.
(617) 668-5207 Business Analyst
Interactive Partners LLC

Hao Zhang
zhang.hao7@husky.neu.edu Business Process
High Document technical designs, create corresponding UML diagrams.
(617) 220-7962 Developer
Interactive Partners LLC

Michelle Schuster
michelle_shoes@gmail.com
CEO / Founder High Oversee the full implementation of the Shuber business idea.
(925) 230-8467
Shuber

Jeff Greenberg
greenberg.j@gmail.com CTO / Business
Technology Medium Oversee the technical design choices for the Shuber business.
(952) 460-4410 Consultant
Shuber

34