Work breakdown structure of some ATM software is given below in list form:

TASK Duration Predecessor

Requirement Analysis
1.1. Describe system architecture	20 days
1.2. Interview	12 days
1.3. Define and develop sw requirements	14 days
1.4. Define Interface Requirements	14 days
1.5. Prioritize and Integrate Requirements	11 days	1.3
1.6. System Security Analysis	22 days	1.2
1.7. Software Quality & Risk Analysis	14 days	1.5
1.8. Create Requirements Analysis Report	22 days	1.6 & 1.7
System Designing 2.1. Perform Architectural Designing	21 days	1.8
2.2. Design interfaces	21 days	1.4
2.3. Develop algorithms	12 days	2.1 & 2.2
2.4. Design test cases	12 days	2.3
2.5. Perform Detailed Design	8 days	2.1 & 2.2 & 2.3
2.6. Create Software Design specification	24 days	2.5
Implementation 3.1. Create Test Data	19 days	2.6
3.2. Create Source Code	19 days	2.6
3.3. Generate Object Code	30 days	3.2
3.4. Plan Integration	7 days	2.1, 2.2
3.5. Perform integration	9 days	3.3., 3.4
3.6. Document Object Model	10 days	3.5
Testing 4.1. Unit Testing	14 days	3.1, 3.2
4.2. Integration Testing	22 days	3.5
4.3. System Testing	13 days	4.2
4.4. Provide Feedback to Programmers	14 days	4.3
Operation & Maintenance 5.1. Final checks and verification	28 days	4.4
5.2. Perform Preventative Maintenance	1 day	5.1
5.3. Documentation & User Manual	17 days	1.8 & 2.6
5.4. Distribute software	5 days	5.1 & 5.2
5.5. Install Software	12 days	5.3& 5.4
5.6. Training	8 days	5.3 & 5.5
5.7. Perform Adaptive Maintenance	9 days	5.5

Using the above WBS,

-Create the Gantt chart for the project.

-How long will it take to complete this project? You may ignore inconsistencies in estimations.

-Name two of the critical tasks.

-Assuming that every person in the team is multi-functional, roughly how many people are required?

Please use Microsoft Excel