Merge Algorithm
TQA Project Plan
To develop a system that takes in three elements: a base
version of a file and two modified versions of the file; the program should
then output a resultant file that is a best approximation of the non-destructive
merge of the modified versions.
John A. Preston
IT Department
CCSU
(770) 960-4354
|
Name |
csu# |
Phone
Number |
Role |
|
Jocelyn
Rampy |
13672 |
770-365-0684 |
Project
Manager |
|
Victoria
Nguyen |
19947 |
404-849-2574 |
Tester |
|
Ian
Gualdoni |
10522 |
678-592-9776 |
Webmaster |
|
Nathan
Buffington |
12107 |
770-584-0688 |
Developer |
|
Resource |
When
needed |
Justification |
Number |
|
Visual
Basic |
Entire
semester |
for
development & testing |
2 Copies |
|
Visual
Studio 6.0 |
Entire
semester |
for
development help |
5 copies |
|
Microsoft
Word |
Entire
semester |
for
documentation |
5 copies |
|
Laptops/PC |
Testing Period |
For testing |
4 |
|
Switch |
Testing Period |
For testing |
1 |
|
Patch
Cable |
Testing Period |
For testing |
4 |
Week1
|
Task |
Who |
Time
Estimate |
|
1 |
All |
12(4, 4, 4, 4) |
|
1.1 |
Buffington |
2 |
|
1.2 |
Buffington |
2 |
|
Meetings |
All |
4 |
|
Create
Requirements document |
Rampy,Nguyen |
4(3,1) |
|
Review
requirements document |
All |
4(1, 1, 1, 1) |
|
Documents
Management |
Rampy |
3 |
|
Website
Management |
Gualdoni |
5 |
|
Project
Research |
All |
8(2, 2, 2, 2) |
Week2
|
Task |
Who |
Time
Estimate |
|
1 |
All |
8(4,
4, 4, 4) |
|
1.1;
1.2 |
Buffington, Gualdoni |
4(2, 2) |
|
2 |
Buffington |
6 |
|
Meetings |
All |
4(1, 1, 1, 1) |
|
Create
Project Plan |
Rampy,
Nguyen |
8(6,2) |
|
Review
Project Plan |
All |
4(1, 1, 1, 1) |
|
Documents
Management |
Rampy |
3 |
|
Website
Management |
Gualdoni |
6 |
|
Project
Research |
All |
8(2, 2, 2, 2) |
|
Development
of Merge Program |
Buffington |
4 |
Week3
|
Task |
Who |
Time
Estimate |
|
2 |
Buffington |
5 |
|
3.1,
3.1.2, 3.1.3 |
Buffington, Gualdoni |
4(2, 2) |
|
Meetings |
All |
4(1,
1, 1, 1) |
|
Create
Testing Plan |
Nguyen,
Rampy |
8(4,4) |
|
Review
Testing Plan |
All |
4(1,
1, 1, 1) |
|
Documents
Management |
Rampy,
Nguyen |
4(2, 2) |
|
Website
Management |
Gualdoni |
5 |
|
Project
Research |
All |
8 |
|
Development
of Merge Program |
Buffington |
4 |
Week4
|
Task |
Who |
Time
Estimate |
|
3.1,
3.1.2, 3.1.3 |
Buffington |
5 |
|
3.4 |
Rampy, Nguyen |
4(2, 2) |
|
4 |
Buffington, Gualdoni |
4(2, 2) |
|
Meetings |
All |
4(1,
1, 1, 1) |
|
Documents
Management |
Rampy,
Nguyen |
6(3,
3) |
|
Website
Management |
Gualdoni |
6 |
|
Project
Research |
All |
8(2, 2, 2, 2) |
|
Development
of Merge Program |
Buffington |
4 |
|
Testing
Merge Program |
Nguyen,
Rampy |
4(2, 2) |
Week5
|
Task |
Who |
Time
Estimate |
|
3.3,
3.3.1 |
Buffington |
5 |
|
3.4 |
Buffington, Gualdoni |
4(2, 2) |
|
4 |
All |
4(1, 1, 1, 1) |
|
Meetings |
All |
4(1, 1, 1, 1) |
|
Documents
Management |
Rampy,
Nguyen |
4(2, 2) |
|
Website
Management |
Gualdoni |
5 |
|
Project
Research |
All |
8(2, 2, 2, 2) |
|
Development
of Merge Program |
Buffington |
4 |
|
Testing
Merge Program |
Nguyen,
Rampy |
6(3, 3) |
Week6
|
Task |
Who |
Time
Estimate |
|
3.3, 3.4,
4 |
Buffington, Gualdoni |
9(6, 3) |
|
5 |
Buffington, Gualdoni |
4(2, 2) |
|
Meetings |
All |
8(2, 2, 2, 2) |
|
Create
Demo1 |
Rampy,
Nguyen |
6(3, 3) |
|
Review
Demo1 |
All |
4(1, 1, 1, 1) |
|
Documents
Management |
Rampy |
3 |
|
Website
Management |
Gualdoni |
5 |
|
Project
Research |
All |
8(2, 2, 2, 2) |
|
Development
of Merge Program |
Buffington |
4 |
|
Testing
Merge Program |
Nguyen,
Rampy |
6(3, 3) |
Week7
|
Task |
Who |
Time
Estimate |
|
3.4 |
Buffington, Gualdoni |
8(6, 2) |
|
4 |
Buffington, Gualdoni |
4(2, 2) |
|
5 |
Buffington |
2 |
|
Meetings |
All |
8(2, 2, 2, 2) |
|
Create
Final Demo |
Rampy,Nguyen |
8(5, 3) |
|
Review All Documents |
All |
8(2, 2, 2, 2) |
|
Documents
Management |
Rampy |
4 |
|
Website
Management |
Gualdoni |
6 |
|
Project
Research |
All |
8(2, 2, 2, 2) |
|
Development
of Merge Program |
Buffington |
4 |
|
Testing
Merge Program |
Nguyen,
Rampy |
8(5, 3) |
Week8
|
Task |
Who |
Time
Estimate |
|
4,
5, 6 |
Buffington, Gualdoni |
10(6, 4) |
|
Meetings |
All |
8(2, 2, 2, 2) |
|
Create
Final Demo |
Rampy,Nguyen |
10(6, 4) |
|
Website
Management |
Gualdoni |
6 |
|
Project
Research |
All |
8(2, 2, 2, 2) |
|
Development
of Merge Program |
Buffington |
4 |
|
Testing
Merge Program |
Nguyen,
Rampy |
8(6, 4) |
Week9
|
Task |
Who |
Time
Estimate |
|
5,
6, 6.1 |
Buffington, Gualdoni |
8(5, 3) |
|
Edit
Final Demo |
Rampy, Ngyuen |
8(5,
3) |
|
Review
Final Demo |
All |
8(2, 2, 2, 2) |
|
Meetings |
All |
8(2, 2, 2, 2) |
|
Documents
Management |
Rampy |
4 |
|
Website
Management |
Gualdoni |
6 |
|
Project
Research |
All |
8(2, 2, 2, 2) |
|
Development
of Merge Program |
Buffington |
6 |
|
Test of
Merge Program |
Nguyen,
Rampy |
8(5, 3) |
Week10
|
Task |
Who |
Time
Estimate |
|
6,
6.1 |
Buffington, Gualdoni |
10(6, 4) |
|
Review
Final Changes |
All |
12(3, 3, 3, 3) |
|
Review/Edit
Final Demo |
Rampy, Nguyen |
8(4, 4) |
|
Meetings |
All |
8(2,
2, 2, 2) |
|
Documents
Management |
Rampy |
5 |
|
Website
Management |
Gualdoni |
6 |
|
Project
Research |
All |
8(2, 2, 2, 2) |
|
Development
of Merge Program |
Buffington |
6 |
|
Testing
Final Changes to Merge Program |
Nguyen,
Rampy |
8(5, 3) |
Week11
|
Task |
Who |
Time
Estimate |
|
Final
Task Completion |
Buffington, Gualdoni |
8(5, 3) |
|
Edit
Final Demo |
Rampy, Nguyen |
8(4, 4) |
|
Review
Final Demo |
All |
8(2, 2, 2, 2) |
|
Meetings |
All |
8(2, 2, 2, 2) |
|
Website
Management |
Gualdoni |
6 |
|
Development
of Merge Program |
Buffington |
6 |
|
Documents
Management |
Rampy,
Nguyen |
6(3, 3) |
|
Project
Research |
All |
8 |
|
Development
of Merge Program |
Buffington |
6 |
|
Final
Testing of Merge Program |
Nguyen,
Rampy |
6 |
|
Week |
|
|||||||||||
|
Member |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
TOTAL |
|
Rampy |
13 |
17 |
10 |
10 |
9 |
14 |
18 |
14 |
18 |
19 |
11 |
153 |
|
Nguyen |
8 |
9 |
10 |
10 |
9 |
11 |
14 |
14 |
14 |
16 |
11 |
126 |
|
Gualdoni |
12 |
16 |
11 |
11 |
11 |
15 |
16 |
14 |
15 |
17 |
13 |
151 |
|
Buffington |
11 |
20 |
15 |
14 |
15 |
17 |
20 |
14 |
17 |
19 |
15 |
177 |
|
TOTAL |
44 |
62 |
46 |
45 |
44 |
57 |
68 |
56 |
64 |
71 |
50 |
607 |
Description
|
Probability |
Impact |
Severity |
|
Customer changes
requirements |
9 |
9 |
81 |
|
Insufficient
Research |
4 |
9 |
36 |
|
Hard drive failure |
3 |
10 |
30 |
|
Loss communication
with customer |
2 |
10 |
20 |
|
Lack communication
between members |
2 |
7 |
14 |
|
Loss of team
member |
1 |
8 |
8 |
|
Description |
Mitigation
Strategies |
Preventative
Plans |
|
|
|
|
|
Customer
changes requirements |
Project
needs to be changed to fit the need or desire of customer |
Meet
with customer on regular basis |
|
Insufficient
Research |
Having
a team meeting |
Make
sure everyone researching what they should be researching |
|
Hard
drive failure |
Use
the backup copy |
Make
regular backup and distribute to other team members |
|
Loss
communication with customer |
Slow
down development until communication has been restored |
Get
in touch with customer right away |
|
Lack
communication between members |
Keep
on informing what's going on with the project |
Have
regular team meetings |
|
Loss
of team member |
Each
team member must work extra hard to make up |
Pray
that it won't happen!! |