NOTICE!• These materials are prepared only for the students enrolled in
the course Distributed Software Development (DSD) at the Department of Computer Science and Engineering, University of Mälardalen, Västerås, Sweden and at the Faculty of Electrical Engineering and Computing, University of Zagreb, Croatia (year 2009/2010).
• For all other purposes, authors’ written permission is needed!• The purpose of these materials is to help students in better
understanding of lectures in DSD and not their replacement!
Distributed Software Development
Final Presentation
The CourseScheduler team presents
Egle Samuleviciute
Overview
• Team – who did what
• Project – what has been achieved– Demo
• Effort and Statistics
• Experiences
• Special thanks and questions
2010-01-12 4
The CourseScheduler team
2010-01-12
The CourseScheduler team
Egle Samuleviciute
•Project leader •Communication with customer and supervisor•Endless meetings•Coordinating team work•Documentation
2010-01-12
The CourseScheduler team
Inderjeet Oberoi
•Database handling•Uncountable Stored Procedures•Testing•Documentation•Meetings•Requirement gathering
2010-01-12
The CourseScheduler team
Narendran Sivakumar
•Business Logic developer•Documentation•Presentation•Requirement analyst
2010-01-12
The CourseScheduler team
Ligaj Pradhan
•Documentation•Testing Guy•Database•Beta presentation
2010-01-12
The CourseScheduler team
Dario Vuljanić
•Frontend development involving scheduling•Lot of letters in documentation•Lots of lines of code•Best friend of Project Leader•Sleepless nights
2010-01-12
The CourseScheduler team
Zvonko Ivić
•Testing•Backend development•Database administration•Documentation•System administration•Many interesting meetings
2010-01-12
The CourseScheduler team
Kristian Poslek
•Visual design•Frontend development•Documentation•Lack of sleep
2010-01-12
Main goal was...
2010-01-12
Work done (1/2)
14
• Initial goal and requirements fulfilled
• Data management: courses, programs, users, rooms, academic year
• Constraint system
• Schedule generator
• Schedule proposals system
2010-01-12
Work done (2/2)
15
• Interactive schedule display
• System testing automated with selenium
• Code testing was automated with unit testing
• Extensive Acceptance test plan
• Testing was formal and effective process
2010-01-12
Demo
162010-01-12
17
Workload 1/2
2010-01-12
Workload 2/2
• Total: 1613 hours
• That is 94 hours per week
• That is 13,5 hours per week per member
2010-01-12
Project statistics
• >70 files in the project repository
• 23 Skype group meetings
• > 290 posts on Google group
• 8 meetings with the customer
• > 5270 files in the SVN repository
192010-01-12
Experiences 1/2• Try to always keep it cool – Kristian
• The course was great because we had experienced all the problems which come from doing a project that has project member geographically distant from one another - Zvonko
• Learning how not to be big boss inside the team, compromises, technical knowledge, cultural experiences and all that in English – Dario
• It was good but could have been better – Naren
2010-01-12
Experiences 2/2• It was more about communication than anything else
– Egle
• I experienced a realistic approach to software development in a distributed team with formal requirement engineering, design, implementation, integration, testing, documentation, presentation and above all co-ordination – Ligaj
• It was fun but could have been better - Inder
2010-01-12
Special thanks
22
Rikard Land(supervisor)
Ivica Crnković(customer)
2010-01-12
After working hard...
2010-01-12
… discovering other cultures...
2010-01-12
… having little fun..
2010-01-12
… it's time to celebrate!
2010-01-12
27
Questions
2010-01-12
Top Related