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

Public Advice Traveling Help

DSD Course – Project final Presentation

School of Innovation, Design and Engineering Malardalen University

Jan 15th, 2008

104/19/23

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

204/19/23

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

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

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)

Project Analysis - Risk Management

05

101520253035404550

1 2 3 4 5 6 7 8 9 10

Risk Analysis

1. Time shortage2. Competence in technology3. Key resource leaving the

team4. Miscommunication5. Design Flaw6. Database server crash7. SVN server crash8. Choose of wrong technology9. Installation problem10. Server unavailability

Conclusion

• Many of the risks were fore seen.• Lack of competence in technology created installation problem

6

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

Financial metrics & Communication

804/19/23

Cost Hours

Actual 25780 $ 1289

Estimated 38500 $ 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 [email protected].• All barriers of cultural differences were broken to work as a team.

Financial metrics

Communication

Project Analysis – Requirement Compliance

9

Total number of requirements 13

Number of requirements implemented 10

Requirements partially fulfilled 02

Requirements not fulfilled 0

Requirements dropped 01

Dropped tasks• Integration of management

Partially Implemented• Add advice types• Conflict management

Project Testing

1004/19/23

Requirements Testing

Project Experiences

1104/19/23

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

Score Approach

1204/19/23

Communication with Customer• Score Supervisior recommended to find potential user• From Common people requirement are collected on basis of Survey and Interview by feedback

Score Approach

1304/19/23

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)

Score Approach

1404/19/23

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.

1504/19/23

Thank you&

Any Questions?

16