1. Project Management presented by Aaron Molloy - Jimmy Kenny - Taras Voloshyn Newspaper Delivery System

2. Introduction Newspaper Delivery System System Overview Printing Summary Reports Billing Information Geographical Information Customer specific settings Web based application

3. Introduction Why a Web Application ? Our skillsets are in the area of web development. Better for casual users(i.e. newsagents) Greater accessibility. Offsite hosting

4. Hardware Requirements 3 PCs Printer Internet Connection Source Control Server (i.e. Git)

5. Software requirements Eclipse with J-Unit plugin shall be used to develop and test the project. MySQL shall be used to develop the database required for the project. Google Maps integration shall be used to find out where customers are located. PHP, Xampp, JavaScript, AJAX/JSON, HTML and CSS shall be used in the web development side of the project.

6. Software requirements Microsoft Office Excel shall be used to organize and input users billing information. Microsoft Office Word shall be used to write up the requirements document. GIT shall be used to manage the changes to the project.

7. Risk Analysis 5 Probability Measures CategoryProbability MeasureProbability Meaning Very Low1 0% to 20% chance of occurrence Low2 21% to 40% chance of occurrence Average3 41% to 60% chance of occurrence High4 61% to 80% chance of occurrence Very High5 81% to 100% chance of occurrence

8. Risk Analysis 5 Consequence Measurements Consequence MeasureConsequence Meaning 1Insignificant 2Tolerable 3Serious 4Critical 5Catastrophic

9. Risk Analysis 17 Risks identified altogether Risk Exposure = Probability x Consequence Main risks identified: Requirements change Data loss System performance Development time underestimated Budget concerns

10. Risk Analysis Risk No.Risk Description Probability (P) (of Occurrence) Consequence (C) (of Occurrence) Risk Exposure (RE) P x C Plan (Avoidance / Mitigate) 1 Development time underestimated 236 Allow for contingency. 2 Requirements change 5210 Analyse the impact of the new requirements on entire project and discuss with customer of necessary. 3 Hardware failure 144 Have access to spare parts. 4 Data loss 3515 Do regular backups. 5 Staff illness 224 Ensure that staff understand each others tasks. Reasign tasks between remaining members fo a team. 6 Budget cuts 155 Explain to customer why cuts in costing would have a detrimental effect on development process. 7 Underestimation of resources 236 Understand hardware capabilities for given requirements. 8 Misunderstanding of the requirements 3412 Plan interview well so all the requirement are understood correctly. 9 Poor project planning 236 Review project plan at regular intervals. 10 Lack of skills or knowledge 236 Ensure adequate training of team members. 11 Incorrect hardware requirements 3412 Test hardware requirements e.g. Test server under high load 12 Change in client management during the project 133 Make sure that contract cover this risk. 13 Data theft 248 Ensure adequate security measures are taken e.g. strong firewalls, virus protection etc. 14 System doesn’t perform to expectations 339 Understand requirements fully. Ensure hardware and software resources are of high specification. 15 Budget overrun 339 On-going reviews of project spend 16 Requirements inadequate 248 Interact with customer to make sure requirements are sound 17 Design of system inadequate 248 Read and understand requirements fully. Make sure designer has appropriate skill level.

11. Work Breakdown Structure Top down approach V-model used Why V-model ? Testing is important in this system Sensitive user data Dealing with money Newspaper Delivery System Requirements In-house Preparation High Level Design Unit/Module Design Implementation Unit Testing Integration Testing System Testing User Acceptance Test In-house analysis Project Monitoring

12. Work Breakdown Structure Requirements User Req. Interviews Prepare questions Organize time InterviewReq. Analysis Design of UAT cases System Req. System req. meeting Req. Analysis Design of system test cases

13. Work Breakdown Structure Unit/Module Design Design printing module and test cases Design summary module and test cases Design billing module and test cases Design customer settings module and test cases Design geo info module and test cases Design of Database

14. Project Scheduling Structure based V-model 130 days (including 10 days contingency) Testing phases allocated more time

15. Project Scheduling We had both, concurrent and sequential tasks Implementation and Unit testing were concurrent tasks

16. Project Scheduling Where’s the Critical Path ? Concurrent tasks run over the same period of time No divergent path One path through the project

17. Milestones and Deliverables Milestones Requirements Elicitation and User Acceptance Test Requirements Analysis and System Testing High Level Design and Integration Testing Unit/Module Design and Unit/Module Testing Implementation

18. Milestones and Deliverables Deliverables Deliverables are the work products we will give the client for evaluation. The deliverables are as follows: Project Plan Requirements Document Design Document Executable Code Modules Integrated Modules for testing User Manual

19. Monitoring and Reporting Throughout the course of the project we will implement Monitoring and Reporting mechanisms as follows Weekly Informal Team Meetings Evaluate project status and issues to be addressed Formal report created at each Milestone Submitted to Project Manager. Details what was done during phase Highlight any actual or potential problems Formal meeting with the Project Manager Follow-up meetings may be required. Report accompanies each Deliverable Formal meeting arranged with Client Discuss issues arising Follow-up meetings may be required.

20. Summary Learning Outcomes Risk Analysis Work Breakdown Structure Project Scheduling Critical Path Milestones and Deliverables Monitoring and Reporting Teamwork