1 / 19

NOTICE!

This notice provides an update on the progress of the Distributed Software Development Course, including documentation evolution and testing status.

herrera
Télécharger la présentation

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 2006/2007). • 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. Selected Topics in Software Engineering -Distributed Software Development

  3. CourseBuilder Standalone Team CourseBuilderStandalone ApplicationProject Status Report 2

  4. CourseBuilder – Standalonein action

  5. Past Documentation • Documents already used and filled: - Project description - Requirements definition - Design description - Week reports - Minutes of meeting

  6. NEW Documentation • Currently working on new documents • Acceptance Test Plan • Installation Manual • User Manual (Maybe, still not working on it) • Technical Documentation • Final Project Report

  7. NEW Documentation Evolution • Working on first parts • Waiting for program to be more evolved • Publication

  8. Publication • We keep on adding documentation through the website • Not final versions • Probably some will be modified

  9. Testing (1) • We started our testing part  • The testing will be done in NUnit which is similar to the JUnit. • There will be approximately 30 testing classes • The testing will be rigorous and address the most critical parts to avoid any catastrophe

  10. Testing (2) • Last week we are immersed with Learning NUnit. • So the progress was slow but we will soon gather pace and complete the task well before milestone.

  11. Project status

  12. General project status • On track

  13. General project statusin Gantt chart

  14. Statistics #1 (time) • Typically, about 20-30 hours per week are spent for the communication

  15. Statistics #2 (money) • Decreased forecasted project costs • This is the status collected in the end of week W49

  16. Statistics #3 (communication) • Average of 1.5 group meetings per week • About 300 e-mails • (ca. 100 in past 14 days)

  17. Expiriences • We expirienced CVS conflicts • Accidental • Fixing somebody else’s bugs • We shifted some project roles

  18. Future plans • Make new application build (few more bugfixes) • Visit customer and discuss GUI and application behaviour • Coding and much testing • Working on the documentation

  19. Any questions?

More Related