Sheet1[Project Name]0Gantt ChartSecurity Network UpgradeTeam BToday's Date:9/5/16Monday(vertical red line)
Jon: Work Breakdown Structure
Level 1: 1, 2, 3, ...
Level 2: 1.1, 1.2, 1.3, ...
Level 3: 1.1.1, 1.1.2, 1.1.3, …
The WBS is automatically entered, but the formulas are different for different levels.Project Lead:Team B
Jon: Duration (Calendar Days)
Enter the number of calendar days for the given task. Refer to the Working Days column or use a calendar to determine the corresponding working days. The duration is from the beginning of the Start date to the ending of the End Date.
When the duration is calculated, it is calculated as End Date minus the Start Date plus 1 day, so that a task starting and ending on the same day has a duration of 1 day.
Jon: Percent Complete
Update the status of this task by entering the percent complete (between 0% and 100%).
Jon: Working Days
Counts the number of working days using the NETWORKDAYS() formula, which excludes weekends. When planning work based upon the number of working days, adjust the Duration until the desired # of working days is reached.
Jon: Calendar Days Complete
This column is calculated by multiplying the Duration by the %Complete and rounding down to the nearest integer.
Jon: Calendar Days Remaining
This column is calculated by subtracting the Days Complete from the Duration.Start Date:9/5/16Monday[42]First Day of Week (Mon=2):212/29/1412/30/1412/31/141/1/151/2/151/3/151/4/151/5/151/6/151/7/151/8/151/9/151/10/151/11/151/12/151/13/151/14/151/15/151/16/151/17/151/18/151/19/151/20/151/21/151/22/151/23/151/24/151/25/151/26/151/27/151/28/151/29/151/30/151/31/152/1/152/2/152/3/152/4/152/5/152/6/152/7/152/8/152/9/152/10/152/11/152/12/152/13/152/14/152/15/152/16/152/17/152/18/152/19/152/20/152/21/152/22/152/23/152/24/152/25/152/26/152/27/152/28/153/1/153/2/153/3/153/4/153/5/153/6/153/7/153/8/153/9/153/10/153/11/153/12/153/13/153/14/153/15/153/16/153/17/153/18/153/19/153/20/153/21/153/22/153/23/153/24/153/25/153/26/153/27/153/28/153/29/153/30/153/31/154/1/154/2/154/3/154/4/154/5/154/6/154/7/154/8/154/9/154/10/154/11/154/12/154/13/154/14/154/15/154/16/154/17/154/18/154/19/154/20/154/21/154/22/154/23/154/24/154/25/154/26/154/27/154/28/154/29/154/30/155/1/155/2/155/3/155/4/155/5/155/6/155/7/155/8/155/9/155/10/155/11/155/12/155/13/155/14/155/15/155/16/155/17/155/18/155/19/155/20/155/21/155/22/155/23/155/24/155/25/155/26/155/27/155/28/155/29/155/30/155/31/156/1/156/2/156/3/156/4/156/5/156/6/156/7/156/8/156/9/156/10/156/11/156/12/156/13/156/14/156/15/156/16/156/17/156/18/156/19/156/20/156/21/156/22/156/23/156/24/156/25/156/26/156/27/156/28/156/29/156/30/157/1/157/2/157/3/157/4/157/5/157/6/157/7/157/8/157/9/157/10/157/11/157/12/157/13/157/14/157/15/157/16/157/17/157/18/157/19/157/20/157/21/157/22/157/23/157/24/157/25/157/26/157/27/157/28/157/29/157/30/157/31/158/1/158/2/158/3/158/4/158/5/158/6/158/7/158/8/158/9/158/10/158/11/158/12/158/13/158/14/158/15/158/16/158/17/158/18/158/19/158/20/158/21/15.
1. Sheet1[Project Name]0Gantt ChartSecurity Network
UpgradeTeam BToday's Date:9/5/16Monday(vertical red line)
Jon: Work Breakdown Structure
Level 1: 1, 2, 3, ...
Level 2: 1.1, 1.2, 1.3, ...
Level 3: 1.1.1, 1.1.2, 1.1.3, …
The WBS is automatically entered, but the formulas are
different for different levels.Project Lead:Team B
Jon: Duration (Calendar Days)
Enter the number of calendar days for the given task. Refer to
the Working Days column or use a calendar to determine the
corresponding working days. The duration is from the beginning
of the Start date to the ending of the End Date.
When the duration is calculated, it is calculated as End Date
minus the Start Date plus 1 day, so that a task starting and
ending on the same day has a duration of 1 day.
Jon: Percent Complete
Update the status of this task by entering the percent complete
(between 0% and 100%).
Jon: Working Days
Counts the number of working days using the
NETWORKDAYS() formula, which excludes weekends. When
planning work based upon the number of working days, adjust
the Duration until the desired # of working days is reached.
Jon: Calendar Days Complete
This column is calculated by multiplying the Duration by the
%Complete and rounding down to the nearest integer.
3. B9/5/169/17/16130%1301312Meet and Create ScheduleTeam
B9/5/169/6/1620%21132Meet and Create Schedule2.1Office
Managers Meeting for
Discussion9/5/169/5/1610%1112.12.2Create and Submit
Security Upgrade9/6/169/6/1610%1012.22.3Approve
schedule9/6/169/6/1610%1012.33Receive New Security
SoftwareTeam B9/7/169/10/16450%4043Receive New Securty
Software3.1Purchase New
Software9/7/169/7/16150%1013.13.2Ensure Hardware is
sufficient9/7/169/7/16150%1013.23.3Purchase
Accessories9/8/169/8/16150%1013.33.4Prepare for Hardwasre
installation9/9/169/10/1622023.44Back Up DataTeam
B9/11/169/13/1630%3034Back Up Data4.1Back Up shared
Drives & Files9/11/169/11/1610%1014.14.2Back Up User
Data9/12/169/12/1610%1014.24.3Ensure Back Up Was
Successful9/13/169/13/1610%1014.35Install and configureTeam
B9/14/169/17/1640%4045Install and configure5.1Set Up
Security Software9/14/169/14/1610%1015.15.2Set Up
Firewals9/15/169/15/1610%1015.25.3Create Passwords and
Acces Rules9/16/169/16/1610%1015.35.4Individual Security
Settings9/17/169/17/1610%1015.4FinalNetwork Upgrade
ReadyFinal
Running head: PROJECT CHARTER
1
Project Schedule
Learning Team B: Project Schedule
Ali Mbil, Gerald Merten, Jose Murguia, Lilia Nevarez, Ronalyn
Reyes
4. CMGT/410
September 5, 2016
Seth Chaikin
Project Details
Project Name
Orao Media Technologies
Project Type
Music Industry Production Software
Project Start Date
September 5, 2016
Project End Date
September 27, 2016
Project Sponsor
Media Technologies
Primary Driver
Production
Secondary Driver
Quality Assurance
Division
Music
Project Manager/Dept
Team B
5. Overview
This document defines the high level requirements for Orao
Media Technologies. It will be used as the basis for the
following activities:
· Creating solution designs, assigning the appropriate software
· Developing test plans, test scripts, and test cases, utilizing
Mojave as an internal secure data line
· Determining project completion refreshing consumer’s server
operating system and hardware.
· Assessing project success
Role
Functionality
Sub Functionality/Budget
NFR/Client-Server Database System
Consumer
Add production cart
With login 30%
Performance / CRM
Consumer
logout
Without login
30%
Usability/ CRM
Consumer
Add production cart
With login
30%
Performance/ CRM
Admin
logout
Without login
40%
Compatability/CRM
6. Admin
40%
Security/ CRM
Admin
Add production cart
40%
Usability/CRM
consumer
Add production cart
30%
Compatability/CRM
Admin
logout
40%
Performance/CRM
Admin
logout
40%
Security/CRM
Admin
Add production cart
40%
Usability/CRM
Consumer
logout
30%
Performance/CRM
Actor Name
Actor Type
Access Type needed
7. Comments
Member 1
|_| Stakeholder
|_| Primary Actor
|_| Supporting Actor
|_| Create |_| Print
|_| Read |_| Export
|_| Update |_| Others
|_| Delete
Internal Secure Data Line/Mojave
Member 2
|_| Stakeholder
|_| Primary Actor
|_| Supporting Actor
|_| Create |_| Print
|_| Read |_| Export
|_| Update |_| Others
|_| Delete
Internal Secure Data Line/Mojave
Member 3
|_| Stakeholder
|_| Primary Actor
|_| Supporting Actor
|_| Create |_| Print
|_| Read |_| Export
|_| Update |_| Others
|_| Delete
Internal Secure Data Line/Mojave
Member 4
|_| Stakeholder
|_| Primary Actor
|_| Supporting Actor
|_| Create |_| Print
|_| Read |_| Export
|_| Update |_| Others
|_| Delete
8. Internal Secure Data Line/Mojave
Project Scope
An analysis of the current network will need to be completed to
further understand the process. The scope of the project is the
design and implementation of the resources necessary for a new
and secured system. The new system will require several
resources for successful implementation. Hence, the current
system and operations must be maintained, while ensuring that
client data is intact.
Phases:
I. Assessment
II. Development
III. Implementation
IV. Maintenance and support
Assumptions
· Funds for the upgrade will be available prior to project
mobilization.
· Personnel will be available to complete assigned tasks
Constraints
· Adjustments or changes to security and data protocols
· Training personnel on new upgrades and policies
· Budget Limitations
· Disruption to business operations
9. Risks
· Breach of security during data migration from old to new
system network
· There might be project overlap which may impair timeline
· The above bullet points may require outsourcing that may put
the company to security vulnerability since there’s limited
control to their network system