1 / 25

NOTICE!

NOTICE!.

lamond
Download Presentation

NOTICE!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 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!

  2. Distributed Software Development

  3. WikiPres@MdH Final Release

  4. Overview • Project Overview • Project Demo • Process followed • Effort analysis • Experiences

  5. WikiPres Overview Importing slides and adding comments Adding, editing and deleting slides Supported format: ODP, PDF, PPT User edits the contents User imports ODP File User exports the contents to ODP file Importing ODP files and adding user’s comments for each slide Editing the contents of slide and exporting it to ODP file

  6. Distributed Development Customer Satish Co-developer and plan Rahi – Developer, PHP expert Romik - developer and integrator Asad - Testing and documentation Irfan – Testing and documentation Hussain - Tester and project management

  7. Integration through SVN Irfan – Testing and documentation Satish - Developer Asad – Testing and documentation Rahi – Developer Local Repository Local Repository Local Repository Local Repository Same folder structure as in server Local Repository Hussan- Developer and coordinator Romik - Developer and integration SVN Server

  8. The process model Team meeting - Requirement analysis High Level Design WIKIPRES Application Module 1 Module 2 Module 3 Module 4 Coding Iterative Waterfall Model Testing Integration

  9. Exciting Features

  10. Value Adds Add and delete presentation PDF PPT ODP Multiple File support Options for inserting slides Manage User Rights Slide Navigation

  11. Effort Analysis

  12. EFFORT SPENT Parser development during Beta Release Hours Spent per week Hours spent per week HOLIDAYS

  13. Milestones, assumption and task (MAT) • Import functionality (Alpha) • Adding Comments (Alpha) • Parser for editing slide (Beta) • Adding new Slide (Final) • Adding/Deleting new presentation (Major value add) (Final) • Testing

  14. Milestone Assumption Tasks Assumption • One person in team is sick all the time. This was done to mitigate risk. • No one will work in holidays • Each one will share their knowledge with team members.

  15. Milestone Assumption Tasks Task • To study the features of Mediawiki and share this knowledge among team members • Divide the components of Wikipres among different team members based on their expertise • Integrate the work of team members and check in to Tortoise SVN.

  16. Experiences – Cultural Differences

  17. Experiences Party Harder Work Hard

  18. Experiences Informal meeting helped in cordial relations among team members. It not only helped in discussing the problems offline but also increased the productivity of team.

  19. Experiences - Trips

  20. Experiences Sleepless nights but great achievements

  21. Problems in project • Because of assignments from other subjects it was difficult to distribute work equally • Few functionalities needed to sit in pair and develop. (Eg: parser)

  22. Learning and Take Away • Do risk analysis well in advance • Pair programming is a healthier approach. • Most critical module in project should be identified first • Never be egoistic with team members especially when working in distributed environment.

  23. Thank You 25

More Related