Project Management Example

Server Query Management System for ABC Corp.

Prepared By

Sarmed Rahman

Moin Uddin

Ziauddin

Md. Al-Mokabbir Billah 2012-3-96-005

Jaki Shahrier Kanak 2012-3-96-011

Project Management Example

Prepared By

Sarmed Rahman

Moin Uddin 2012-1-96-005

Ziauddin 2012-3-96-001

Md. Al-Mokabbir Billah 2012-3-96-005

Jaki Shahrier Kanak 2012-3-96-011

Background

•ABC Corp has 10 offices distributed globally

•Each local server serves the local branch

•The address of every remote server has been statically mapped in the local server

• The local server directly connects to the remote server and initiates the query

•The local-remote Server communication is done across a routed WAN link.

Current Topology (Addressing)•The address of every remote server has been statically mapped in the local server

Server A Entries (Addressing):

Server B -> B.B.B.B:3306Server C -> C.C.C.C:3306Server D -> D.D.D.D:3306….….Server J -> J.J.J.J:3306

•Similar Entries in all Servers

Limitations

Fully Meshed Scalability is difficult Change management is difficult Risk of interception of information in

transit

MOV

• A central Request Management Server will be placed

• This server will have the addresses of all other Servers

• For all offices, this Server will be acting as a request Gateway for all remote requests

Team Hierarchy

COOMr. A

Project Office

Networking Stream

Software Stream

General IT

Project Manager Mr. X

1. Sarmed Rahman2. Mokabbir Billah3. Team Member 14. Team Member 2

1. Moin Uddin2. Zia Uddin3. Zaki Kanak4. Team Member 15. Team Member 2

1. Mr. Y

Schedule

Budget (Project)

Task Days Req Variable Cost Fixed Cost Misc

Conceptualize and Initialize Project 3 0.00 40,000.00 900

Develop Charter and Plan 17 0.00 226,666.67 5100

Analysis 8 160,000.00 106,666.67 2400

Design 7 140,000.00 93,333.33 2100

Construction 15 300,000.00 200,000.00 4500

Testing 7 140,000.00 93,333.33 2100

Implementation 7 140,000.00 93,333.33 2100

Close Project 6 0.00 80,000.00 1800

Evaluate Project Success 4 0.00 53,333.33 1200

Sub-Total   880,000.00 986,666.67 22,200.00

TOTAL   1,888,866.67

Challenges

Authentication and encryption issues Geo-location of the central server Load in the WAN link of branches and

central datacenter Connectivity issues – VPN vs. Routed,

IPLC, link redundancy

Challenges(Continued) Clustering/load balance requirements

and techniques Platform interoperability e.g. MySQL,

Oracle, MS-SQL Modification of existing system in

running environment VPS vs. Dedicated Server

Learning Cycle

Facts Assumptions Questions

There are database servers

Multiple branches

Inter-branch communication needed

Every branch office has a high speed Internet connection

All the servers are using same database platform e.g. MySQL

The datacenter will be placed in X, which is more or less in a center position geographically

24x7 Redundant Power, Cooling, Surveillance, Limited Access

Is there any provider in country X who will be able to provide a world class datacenter services?

Learning Cycle (Continued)

Facts Assumptions Questions

Dedicated Server will be used instead of VPS

VPN will be used, IPLC too costly

3 redundant WAN Links

Backup policies (weekly)

Is backing up of data within the scope?

Clustering technology will be used

Piranha LVS will be able to meet the requirements.

The customer does not have digital certificates

How will the digital certificates be installed?

High Level Design

• A central Request Management Server will be placed

• This server will have the addresses of all other Servers

• For all offices, this Server will be acting as a request Gateway for all remote requests

Current Topology (Addressing)

• The addresses of all of the Servers will be mapped only in the Request Management Server

• All other Servers will be using this Request Management Server as a Gateway of Request

Addressing Entries

Request Management Server Server A -> A.A.A.A:3306Server B -> B.B.B.B:3306Server C -> C.C.C.C:3306Server D -> D.D.D.D:3306Server E -> E.E.E.E:3306Server F -> F.F.F.F:3306Server G -> G.G.G.G:3306Server H -> H.H.H.H:3306Server I -> I.I.I.I:3306Server J -> J.J.J.J:3306

All Servers:

Request Gateway: M.M.M.M:1234

High Level Design (Continued) Authentication:

Private-Public pre shared keys Pre-shared passwords Digital certificates

Geo-Location: The Server will be placed in county X. The co-location will be provided by QWE Inc. The co-location has

24x7 power supply with redundant power connections

24x7 cooling, surveillance, access to authorized personnel only

High Level Design (Continued) Network:

VPN will be used, IPLC is too expensive Site will have 3 different WAN links

Clustering: 3 Servers Cluster Highly available with load balancer

Server Hardware: All Servers will have dedicated hardware

High Level Design (Continued) Backup Policy

The Server will not store any database records

All configuration files will be backed up every week

Backup files will be stored in a remote location

Security

VPN tunnel will ensure that all data in transit cannot be accessed

Public-private pre shared keys will ensure any server-server communication can not be accessed by employees

Strong passwords (random generated) will be enforced

Digital certificates will ensure the authenticity of the sender-receiver

Flow of Request (Local)

• Local queries are server by local Server

Flow of Request (Remote)

• Remote queries are forwarded by request management server

Thank you