- User Guide - Administrator Guide - Help Desk Guide 3 wks Mon 9/12/16 Mon 10/3/16 24,49,50 Technical Writer 59 Review documentation 2 days Tue 10/4/16 Wed 10/5/16 58 Project Team 60 Incorporate feedback 1 day Thu 10/6/16 Thu 10/6/16 59 Technical Writer 61 Develop System Documentation: - System Architecture - Database Schema - Code Documentation 3 wks Thu 10/6/16 Wed 11/2/16 24,26,49,50 Technical Writer

1. 27/05/2016
https://ashford.waypointoutcomes.com/assessment/7521/preview
https://ashford.waypointoutcomes.com/assessment/7521/preview
1/3
Description:
Total Possible Score: 10.00
Distinguished - Thoroughly and accurately describes the externa
l factors which affect the international operations at UPS.
Proficient - Describes the external factors which affect the inter
national operations at UPS. Minor details are missing or inaccur
ate.
Basic - Somewhat describes the external factors which affect th
e international operations at UPS. Relevant details are missing
and/or inaccurate.
Below Expectations - Attempts to describe the external factors
which affect the international operations at UPS; however,
significant details are missing and inaccurate.
Non-Performance - The description of the external factors whic
h affect the international operations at UPS is either nonexistent
or
lacks the components described in the assignment instructions.
Distinguished - Thoroughly and accurately describes how the ex
ternal factors cause UPS to adjust its operations.

2. Proficient - Describes how the external factors cause UPS to adj
ust its operations, but minor details are missing or inaccurate.
Basic - Briefly describes how the external factors cause UPS to
adjust its operations, but relevant details are missing and/or
inaccurate.
Below Expectations - Minimally describes how the external fact
ors cause UPS to adjust its operations and significant details are
missing and inaccurate.
Non-Performance - The description of how the external factors
cause UPS to adjust its operations is either nonexistent or lacks
the
components described in the assignment instructions.
Distinguished - Clearly and comprehensively discusses the input
s, processing, and outputs of UPS tracking system.
Proficient - Discusses the inputs, processing, and outputs of UP
S tracking system. Minor details are missing or unclear.
Basic - Partially discusses the inputs, processing, and outputs of
UPS tracking system. Relevant details are missing and/or
unclear.
Below Expectations - Attempts to discuss the inputs, processing
, and outputs of UPS tracking system; however, significant detai
ls
are missing and unclear.
Non-Performance - The discussion of the inputs, processing, an
d outputs of UPS tracking system is either nonexistent or lacks t
he
components described in the assignment instructions.

3. Distinguished - Accurately examines the technologies which are
used by UPS and illustrates how these technologies are related
to
the business model and business objectives of UPS.
Proficient - Examines the technologies which are used by UPS a
nd illustrates how these technologies are related to the business
model and business objectives of UPS. Minor details are missin
g or inaccurate.
Basic - Briefly examines the technologies which are used by UP
S and illustrates how these technologies are related to the
business model and business objectives of UPS. Relevant details
are missing and/or inaccurate.
Below Expectations - Minimally examines the technologies whi
ch are used by UPS and illustrates how the technologies are rela
ted
to the business model and business objectives of UPS. Significa
nt details are missing and inaccurate.
Non-Performance - The examination of the technologies which a
re used by UPS and illustration of how these technologies are
related to the business model and business objectives of UPS is
either nonexistent or lacks the components described in the
assignment instructions.
INF220.W1A1.11.2014
Describes the External Factors Which Affect the International O
perations at
UPS
Total: 1.80

4. Explains How the External Factors Cause UPS to Adjust its Ope
rations Total: 1.80
Discusses the Inputs, Processing, and Outputs of UPS Tracking
System Total: 1.80
Examines the Technologies Which are Used by UPS and Illustra
tes How These
Technologies are Related to the Business Model and Business O
bjectives of
UPS
Total: 1.80
Identifies the Problems That UPS’s Information Systems Need t
o Solve Total: 1.80
27/05/2016
https://ashford.waypointoutcomes.com/assessment/7521/preview
https://ashford.waypointoutcomes.com/assessment/7521/preview
2/3
Distinguished - Accurately and completely identifies the proble
ms that UPS’s information systems need to solve.
Proficient - Identifies the problems that UPS’s information syst
ems need to solve, but minor details are missing or inaccurate.
Basic - Briefly identifies the problems that UPS’s information s
ystems need to solve, but relevant details are missing and/or
inaccurate.
Below Expectations - Minimally identifies the problems that UP

5. S’s information systems need to solve and significant details are
missing and inaccurate.
Non-Performance - The identification of the problems that UPS’
s information systems need to solve is either nonexistent or lack
s
the components described in the assignment instructions.
Distinguished - Distinguishes probable implications of the text f
or contexts, perspectives, or issues outside the assigned task or
beyond the author's explicit message.
Proficient - Uses the text and/or specific knowledge of the auth
or’s context to draw more intricate inferences about the author’s
message and approach.
Basic - Considers how textual features (e.g., sentence and parag
raph structure or tone) contribute to the author’s message. Draw
s
fundamental inferences about context and rationale of text.
Below Expectations - Inadequately captures vocabulary but mak
es an effort to paraphrase or summarize the information the text
communicates.
Non-Performance - The assignment is either nonexistent or lack
s the components described in the instructions.
Distinguished - Utilizes a format, language, or graph (or other v
isual representation) in ways that enhance comprehension, while
making clear the interdependence of language and meaning, tho
ught, and expression.
Proficient - Utilizes a format, language, or graph (or other visua
l representation) to correlate content and form, demonstrating a
n

6. awareness of purpose and audience.
Basic - Utilizes a format, language, or graph (or other visual rep
resentation) that correlates what is being communicated.
Below Expectations - Utilizes a format, language, or graph (or o
ther visual representation) that is appropriate, but may be
incomplete or contain inaccuracies.
Non-Performance - The assignment is either nonexistent or lack
s the components described in the instructions.
Distinguished - Accurately uses APA formatting consistently thr
oughout the paper, title page, and reference page.
Proficient - Exhibits APA formatting throughout the paper. How
ever, layout contains a few minor errors.
Basic - Exhibits limited knowledge of APA formatting througho
ut the paper. However, layout does not meet all APA requireme
nts.
Below Expectations - Fails to exhibit basic knowledge of APA f
ormatting. There are frequent errors, making the layout difficult
to
distinguish as APA.
Non-Performance - The assignment is either nonexistent or lack
s the components described in the instructions.
Distinguished - Displays meticulous comprehension and organiz
ation of syntax and mechanics, such as spelling and grammar.
Written work contains no errors and is very easy to understand.
Proficient - Displays comprehension and organization of syntax
and mechanics, such as spelling and grammar. Written work

7. contains only a few minor errors and is mostly easy to understan
d.
Basic - Displays basic comprehension of syntax and mechanics,
such as spelling and grammar. Written work contains a few erro
rs
which may slightly distract the reader.
Below Expectations - Fails to display basic comprehension of sy
ntax or mechanics, such as spelling and grammar. Written work
contains major errors which distract the reader.
Non-Performance - The assignment is either nonexistent or lack
s the components described in the instructions.
Distinguished - Uses more than the required number of scholarl
y sources, providing compelling evidence to support ideas. All
sources on the reference page are used and cited correctly withi
n the body of the assignment.
Proficient - Uses the required number of scholarly sources to su
pport ideas. All sources on the reference page are used and cited
Reading: Comprehension Total: 0.20
Integrative Learning: Integrated Communication Total: 0.30
Written Communication: APA Formatting Total: 0.13
Written Communication: Control of Syntax and Mechanics
Total: 0.13
Written Communication: Resource Requirement Total: 0.12

8. 27/05/2016
https://ashford.waypointoutcomes.com/assessment/7521/preview
https://ashford.waypointoutcomes.com/assessment/7521/preview
3/3
correctly within the body of the assignment.
Basic - Uses less than the required number of sources to support
ideas. Some sources may not be scholarly. Most sources on the
reference page are used within the body of the assignment. Citat
ions may not be formatted correctly.
Below Expectations - Uses an inadequate number of sources tha
t provide little or no support for ideas. Sources used may not be
scholarly. Most sources on the reference page are not used withi
n the body of the assignment. Citations are not formatted
correctly.
Non-Performance - The assignment is either nonexistent or lack
s the components described in the instructions.
Distinguished - The length of the paper is equivalent to the requ
ired number of correctly formatted pages.
Proficient - The length of the paper is nearly equivalent to the r
equired number of correctly formatted pages.
Basic - The length of the paper is equivalent to at least three qu
arters of the required number of correctly formatted pages.
Below Expectations - The length of the paper is equivalent to at
least one half of the required number of correctly formatted pag
es.

9. Non-Performance - The assignment is either nonexistent or lack
s the components described in the instructions.
Written Communication: Page Requirement Total: 0.12
Powered by
ID Task
Mode
Task Name Duration Start Finish Predecessors Resource Names
0 Riordan HR Integration
Software Development
122 days Mon
7/4/16
Tue
12/20/16
1 Scope 4 days Mon 7/4/16 Thu 7/7/16
2 Determine project scope 8 hrs Mon 7/4/16 Mon 7/4/16 Project
Manager
3 Secure project sponsorship 1 day Tue 7/5/16 Tue 7/5/16 2
Project Manager,Project Sponsor
4 Define preliminary resources 1 day Wed 7/6/16 Wed 7/6/16 3
Project Manager,Project Sponsor

10. 5 Secure core resources 1 day Thu 7/7/16 Thu 7/7/16 4 Project
Manager,Project Sponsor
6 Scope complete 0 days Thu 7/7/16 Thu 7/7/16 5
7 Analysis/Software
Requirements
14 days Fri 7/8/16 Wed
7/27/16
8 Conduct needs analysis 5 days Fri 7/8/16 Thu 7/14/16 6 HR
Manager,Project Manager
9 Draft preliminary software
specifications
3 days Fri 7/15/16 Tue 7/19/16 8 HR Manager,IT Admin,Project
Manager
10 Develop preliminary budget 2 days Wed
7/20/16
Thu 7/21/16 9 Project Manager
11 Review software
specifications/budget with
team
4 hrs Fri 7/22/16 Fri 7/22/16 10 Project Manager,Analyst
12 Incorporate feedback on
software specifications
1 day Fri 7/22/16 Mon
7/25/16

11. 11 Analyst
13 Develop delivery timeline 1 day Mon
7/25/16
Tue 7/26/16 12 Project Manager
14 Obtain approvals to proceed
(concept, timeline, budget)
4 hrs Tue 7/26/16 Tue 7/26/16 13 Project Sponsor,Project
Manager
15 Secure required resources 1 day Wed
7/27/16
Wed
7/27/16
14 Project Manager
Page 1
ID Task
Mode
Task Name Duration Start Finish Predecessors Resource Names
16 Analysis complete 0 days Wed
7/27/16
Wed

12. 7/27/16
15
17 Design 14.5 days Thu 7/28/16 Wed
8/17/16
18 Review preliminary software
specifications
2 days Thu 7/28/16 Fri 7/29/16 16 HR Manager
19 Develop functional
specifications
5 days Mon 8/1/16 Fri 8/5/16 18 Developer
20 Develop prototype based on
functional specifications
4 days Mon 8/8/16 Thu 8/11/16 19 Developer
21 Review functional
specifications
2 days Fri 8/12/16 Mon
8/15/16
20 Project Manager,HR Manager,IT
Manager
22 Incorporate feedback into
functional specifications
1 day Tue 8/16/16 Tue 8/16/16 21 Project Manager

13. 23 Obtain approval to proceed 4 hrs Wed
8/17/16
Wed
8/17/16
22 Project Manager,Project Sponsor
24 Design complete 0 days Wed
8/17/16
Wed
8/17/16
23
25 Development 48 days Wed
8/17/16
Mon
10/24/16
26 Review functional
specifications
1 day Wed
8/17/16
Thu 8/18/16 24 Developer
27 Identify modular/tiered
design parameters
1.5 days Thu 8/18/16 Wed
8/31/16

14. 26 Developer,Analyst
28 Assign development staff 1 day Wed
8/31/16
Thu 9/1/16 27 Developer
29 Develop code 15 days Thu 9/1/16 Thu 9/22/16 28 Developer
30 Developer testing (primary
debugging)
15 days Thu 9/22/16 Mon
10/24/16
29FS-75% Developer
31 Development complete 0 days Mon 10/24/16Mon 10/24/1630
32 Testing 73.5 days Fri 8/19/16 Wed
11/30/16
Page 2
ID Task
Mode
Task Name Duration Start Finish Predecessors Resource Names
33 Develop unit test plans using
product specifications
4 days Fri 8/19/16 Wed

15. 8/24/16
24 Testers,Developer
34 Develop integration test
plans using product
specifications
4 days Thu 8/25/16 Tue 8/30/16 24 Testers,Developer
35 Unit Testing 15 days Mon 10/24/16Mon 11/14/16
36 Review modular code 5 days Mon 10/24/16Mon
10/31/1633,31 Project Team
37 Test component modules
to product specifications
2 days Mon
10/31/16
Wed
11/2/16
31,36 Testers
38 Identify anomalies to
product specifications
3 days Wed
11/2/16
Mon
11/7/16
37 Project Team

16. 39 Modify code 3 days Mon
11/7/16
Thu
11/10/16
38 Project Team
40 Re-test modified code 2 days Thu
11/10/16
Mon
11/14/16
39 Project Team
41 Unit testing complete 0 days Mon 11/14/16Mon 11/14/1640
42 Integration Testing 12 days Mon
11/14/16
Wed
11/30/16
43 Test module integration 5 days Mon
11/14/16
Mon
11/21/16
41 Testers
44 Identify anomalies to
specifications

17. 2 days Mon
11/21/16
Wed
11/23/16
43 Testers
45 Modify code 3 days Wed
11/23/16
Mon
11/28/16
44 Testers
46 Re-test modified code 2 days Mon
11/28/16
Wed
11/30/16
45 Testers
47 Integration testing
complete
0 days Wed
11/30/16
Wed
11/30/16
46
48 Training 62.5 days Wed

18. 8/31/16
Fri 11/25/16
Page 3
ID Task
Mode
Task Name Duration Start Finish Predecessors Resource Names
49 Develop training
specifications for end users
3 days Wed
8/31/16
Fri 9/2/16 24 Trainers,HR Manager
50 Develop training
specifications for helpdesk
support staff
3 days Mon 9/5/16 Wed 9/7/16 24 Trainers
51 Identify training delivery
methodology (computer
based training, classroom,
etc.)
2 days Thu 9/8/16 Fri 9/9/16 24 Trainers
52 Develop training materials 3 wks Mon

19. 10/24/16
Mon
11/14/16
49,31,50,51 Trainers
53 Conduct training usability
study
4 days Mon
11/14/16
Fri 11/18/16 52 Trainers
54 Finalize training materials 3 days Fri 11/18/16 Wed
11/23/16
53 Trainers
55 Develop training delivery
mechanism
2 days Wed
11/23/16
Fri 11/25/16 54 Trainers
56 Training materials complete 0 days Fri 11/25/16 Fri 11/25/16
55
57 Documentation 50.5 days Mon
9/12/16
Mon
11/21/16

20. 58 Develop Help specification 2 days Mon
9/12/16
Wed
10/5/16
24 IT Admin,IT Manager
59 Develop Help system 3 wks Mon
10/24/16
Mon
11/14/16
58,29FS-50% Developer
60 Review Help documentation 3 days Mon
11/14/16
Thu
11/17/16
59 IT Manager
61 Incorporate Help
documentation feedback
2 days Thu
11/17/16
Mon
11/21/16
60 IT Admin,Project Team

21. 62 Develop user manuals
specifications
2 days Mon
9/12/16
Tue 9/13/16 24 Analyst,IT Admin
63 Develop user manuals 3 wks Wed
9/14/16
Tue 10/4/16 62,29FS-50% Analyst,IT Admin
Page 4
ID Task
Mode
Task Name Duration Start Finish Predecessors Resource Names
64 Review all user
documentation
2 days Wed
10/5/16
Thu 10/6/16 63 IT Manager
65 Incorporate user
documentation feedback
2 days Fri 10/7/16 Mon
10/10/16

22. 64
66 Documentation complete 0 days Mon
11/21/16
Mon
11/21/16
65,61
67 Pilot 96.5 days Thu 7/28/16 Fri 12/9/16
68 Identify test group 1 day Thu 7/28/16 Thu 7/28/16 16 Project
Manager
69 Develop software delivery
mechanism
1 day Fri 7/29/16 Fri 7/29/16 68 Deployment Team
70 Install/deploy software 1 day Wed
11/30/16
Thu 12/1/16 47,69,66,56 Deployment Team
71 Obtain user feedback 1 wk Thu 12/1/16 Thu 12/8/16 70
Deployment Team
72 Evaluate testing information 1 day Thu 12/8/16 Fri 12/9/16
71 Deployment Team
73 Pilot complete 0 days Fri 12/9/16 Fri 12/9/16 72
74 Deployment 4.5 days Fri 12/9/16 Thu
12/15/16

23. 75 Determine final deployment
strategy
1 day Fri 12/9/16 Mon
12/12/16
73 Project Team
76 Develop deployment
methodology
0.5 days Mon
12/12/16
Mon
12/12/16
75 Project Team
77 Secure deployment
resources
1 day Tue
12/13/16
Tue
12/13/16
76 Project Team
78 Train support staff 1 day Wed
12/14/16
Wed
12/14/16

24. 77 Project Team
79 Deploy software 1 day Thu
12/15/16
Thu
12/15/16
78 Project Team
80 Deployment complete 0 days Thu
12/15/16
Thu
12/15/16
79
Page 5
ID Task
Mode
Task Name Duration Start Finish Predecessors Resource Names
81 Post Implementation Review 3 days Fri 12/16/16 Tue
12/20/16
82 Document lessons learned 1 day Fri 12/16/16 Fri 12/16/16 80
Project Manager,Project Team
83 Distribute to team members 1 day Mon

25. 12/19/16
Mon
12/19/16
82 Project Manager
84 Create software
maintenance team
1 day Tue
12/20/16
Tue
12/20/16
83 Project Manager
85 Post implementation review
complete
0 days Tue
12/20/16
Tue
12/20/16
84
86 Software development
complete
0 days Tue
12/20/16
Tue

26. 12/20/16
85
Page 6