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

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 2003/2004).
• 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 Plan
4
Building a course

• Hard job
• Long time process

• Simple?
• Easy?
• Fast?

NO
5
Why use CourseBuilder? (1)

• Managing different course versions
• Various course types
• Online
• Classic
• Mixed

6
Why use CourseBuilder? (2)

• Defining
• Objectives (Bloom Taxonomy is important)
• Topics
• Activities
• Resources
• Dependencies
• Placing topics and activities to calendar, with
  real dates

7
Why use CourseBuilder? (3)

• Workload analysis based on
• Number of students in the course
• Number of students in groups
• Number of teaching stuff
• Various reports
• Course syllabus
• Activity list
• Workload analysis
• Users
• Resources needed

8
Other advantages

• Adding one chapter in your course from another
  course it becomes just a click with
  CourseBuilder
• Planning optimal workload for students and
  teachers
• Automatic checking dependencies

9
Who will make it possible?

• Students from Zagreb
• Tomislav Sukser manager, coding, documentation
• Tvrtko Bedekovic coding, CVS, GUI
• Dragan Juric coding, GUI
• Students from Västerås
• Diego Laga-Ramon vice manager, coding, XML,
  docs.
• Daniel Bartolome-Estacho CVS, documentation
• Alejandro Sainz-Julian XML, documentation
• Sreedhar Danturthi coding, CVS, documentation

10
Communication

• Skype and other IM software
• Chat
• Calls
• Video Calls
• Live meetings (when possible)
• Using CVS and good in-code documentation

11
Technologies in use

• Microsoft .NET 2.0
• Visual Studio 2005 Professional (C)
• XML
• CVS (both for coding and as CourseBuilder
  database)

12
Time guidelines
13
Possible delays in the project

• Find design errors during code time.
• Wrong version handling.
• Problems of communication between Croatia-Sweden.
• Different workload between members 'cause other
  courses.

14
4 Milestones

• 2006-11-16, Project Plan delivered
• Work on the design of the software
• 2006-11-23, Design Report delivered
• Start of implementation
• 2006-11-30, Revised Design Report delivered (if
  necessary)
• Core of the software ready and main GUI
• 2007-01-25, Final Project Report, Design
  documentation, the code, the questionnaire

15
5 Presentations

• 2006-11-09 Project Plan presentation
• Starting work on the design of software
• 2006-11-16 Project Design presentation
• Soon start of implementation
• 2006-11-30 Project Current state presentation
• Core of the software ready and main GUI
• 2006-12-14 Project Current state presentation
• Most of functionalitions
• Starting work on details
• 2007-01-18 Final presentation
• Project written, tested, documented, and finally,
  presented ?

16
Any questions?