4
 9 2.2. Proposed System Architecture Main Marathon Web Server Social Marathon Server Facebook Authenticat ion and Post Servers Desktop Event App FB Access Token FB Auth Participant Internet Browser  Internet Browser Redirect to registration page  Access landing page Send data to Google  Analytics  Access Back Office App Chameleon SDK Register to the marathon Post Image and Text to FB Wall during Event 1 2 3 4 5  2.3. Software and Hardware Minimum Specifications Function Deployment Type RAM Processor HDD Capacity Operating System Web Server Production 8GB Intel Xeon 64 bit 200 GB Linux/Windows Server 2013 Laptop/PC Production 4GB Intel Core i3 500GB SATA Window 8

The Proposal 1

Embed Size (px)

Citation preview

Page 1: The Proposal 1

7/26/2019 The Proposal 1

http://slidepdf.com/reader/full/the-proposal-1 1/4

  9

2.2. 

Proposed System Architecture

Main Marathon Web Server Social Marathon Server 

Facebook Authentication

and Post Servers

Desktop Event App

FB Access

Token

FB Auth

Participant

InternetBrowser    Internet

Browser 

Redirect to

registration page

 Access landing

page

Send data to Google

 Analytics

 Access Back Office App

Chameleon SDK

Register to the marathon

Post Image and Text

to FB Wall during

Event

1

2

3

4

5

 

2.3.  Software and Hardware Minimum Specifications

Function Deployment

Type

RAM Processor HDD

Capacity

Operating

System

Web Server Production 8GB Intel Xeon 64

bit

200 GB Linux/Windows

Server 2013

Laptop/PC Production 4GB Intel Core i3 500GB SATA Window 8

Page 2: The Proposal 1

7/26/2019 The Proposal 1

http://slidepdf.com/reader/full/the-proposal-1 2/4

  10

3. Deliverables

3.1.  Project Governance Approach

3.1.1. 

Communication Plan

A formal process will be employed to facilitate communication during the project. There will

be two key vehicles for providing this communication: a weekly status report and bi-weekly

status meeting.

Bi-weekly Meetings will be held to review overall status, the engagement schedule and

open issues noted in the status report.

3.1.2.  Issue/Risk Management Procedure

The following general procedure will be used by the project team to manage project issues

and risks:

  Identify, classify (i.e., determine what is, and is not an issue), and document

  Assess impact and prioritize

  Assign responsibility

  Monitor and report progress

  Communicate issue resolution

  A mutually agreed upon issue escalation process will be defined at the outset of the

project.

3.1.3. 

Change Management ProcessDuring the engagement, either party may request in writing additions, deletions, or

modifications to the services described in the SOW (“change”). We shall have no obligation

to commence work in connection with any change until the estimated fee and schedule

impact of the change is agreed upon in a written Change Request Form.

Page 3: The Proposal 1

7/26/2019 The Proposal 1

http://slidepdf.com/reader/full/the-proposal-1 3/4

  11

3.2. 

Project Timeline

The number of resources work on the project:

Project Manager/System Analyst : 1

Developer : 2

Graphics Designer : 1

Quality Assurance : 1Total : 4

Page 4: The Proposal 1

7/26/2019 The Proposal 1

http://slidepdf.com/reader/full/the-proposal-1 4/4

  12

4. Project ost

Terms & Condition:

  Total Price does not include VAT 10%

  The Duration of the work is 60 days start from the kick of meeting 

4.1. 

Payment Terms100% payments should be done after UAT sign-off.