1. Public Advice Traveling Help DSD Course – Project final Presentation School of Innovation, Design and Engineering Malardalen University Jan 15 th, 2008 12015-09-07

2. Contents Introduction Project final Presentation Team Members Project Analysis Development Model Milestones Architectural decisions Risk Management Effort Metrics Financial Metrics Communication Requirement Compliance Testing Project Experiences Score Approach Demo 22015-09-07

3. Project Analysis – Development Model Requirement, Design and implementation were in parallel rather sequential. Individual working with short meetings. Responsibilities and roles Conclusion: Helped in multi tasking and proper initial planning Reorganized ourselves to long working under same roof. Faster problem solving Conclusion: Experienced better implementation phase RUP Agile 3

4. Project Analysis - Milestones Most tasks were on time. Implementation and testing were delayed by 1 week. Prototype development should be complete before implementa- tion starts to avoid delay. Conclusion 4

5. Project Analysis – Architectural Decisions As a result of our research into requirements we were guided on how to make decisions as to our system architecture. 5 Software selection L.A.M.P GoogleMaps API Project Architecture User Interface Layer (UIL) Business Object Layer (BOL) Data Access Layer (DAL)

6. Project Analysis - Risk Management Risk Analysis 1.Time shortage 2.Competence in technology 3.Key resource leaving the team 4.Miscommunication 5.Design Flaw 6.Database server crash 7.SVN server crash 8.Choose of wrong technology 9.Installation problem 10.Server unavailability Conclusion Many of the risks were fore seen. Lack of competence in technology created installation problem 6

7. Project Analysis - Effort Metrics Conclusion Equal work distribution through out the software development weeks. Work Distribution among team members was equal except for holidays. Weekly effort metrics Person effort metrics 7

8. Financial metrics & Communication 82015-09-07 CostHours Actual25780 $1289 Estimated38500 $1925 The cost well within the budget. Estimated as 25hrs/week. Actual should be 20hrs/week. Miscommunication was regarded as one of the risks. But did not prove so. 241 messages, 65 files uploaded to btwmdh@googlegroups.com.btwmdh@googlegroups.com All barriers of cultural differences were broken to work as a team. Financial metrics Communication

9. Project Analysis – Requirement Compliance 9 Total number of requirements 13 Number of requirements implemented 10 Requirements partially fulfilled 02 Requirements not fulfilled 0 Requirements dropped01 Dropped tasks Integration of management Partially Implemented Add advice types Conflict management

10. Project Testing 102015-09-07 Requirements Testing

11. Project Experiences 112015-09-07 Positive Experiences Communication Planning design Cultural differences Team Work Real distributed environment Equal workload through all weeks of development Possible improvements Technical improvements Documentation Time management Better risk analysis Early prototype development Time allocation for testing

12. Score Approach 122015-09-07 Communication with Customer Score Supervisior recommended to find potential user From Common people requirement are collected on basis of Survey and Interview by feedback

13. Score Approach 132015-09-07 Problem solving approach in Requirement Engineering Analysis Search and Conclude (ASC) approach to review problems It contains simple steps that are based on reviewing problems in peers ASC (Analysis, Search and Conclude)

14. Score Approach 142015-09-07 Additional requirements PATH advice management system Adding Advice features such as Bar, Road information according to user. Problem faced in writing the SCORE Report Ambigious about expectation of Steering Group about SCORE Report No previous Experience of Writing Score Report for International Conference At the Beginning Lack Team work when only 2 member working on Score report Learning from Score Report Able to Analyze and find ASC approach Team work comes handy in all phase of software life cycle.

15. 152015-09-07

16. Thank you & Any Questions ? 16