In this course, groups of 6-8 students carry out a larger software development project for an external (i.e. from a company, organization or some other part of MDH) client. The project work includes establishing requirements, designing and implementing the system, and testing the result. Each part of the work is documented and presented to the other groups. The project groups are responsible for organizing and planning the work, and for the contacts with the clients. To help them, the groups have weekly meetings with the course assistants/teachers.
(Old news at the bottom of the page)
2016-02-03 Grading finished and individual grades reported. They should be visible i the student portal in a couple of days. Also, the summary of the course evaluation is available.
|Jan Carlson||Responsible teacher, examiner||U1-066a|
|Juraj Feljan||Course assistant||U1-050a|
2016-01-25 Don’t forget to fill out the course evaluation!
2016-01-25 Grading is ongoing. Still waiting for input from some of the clients!
2016-01-15 Three information items related to the remaining things to do:
2016-01-08 Final presentation schedule available on the presentations page.
2015-12-14 Added some information about the acceptance test to the deliverables page, including instruction how to write about it in the project report.
2015-12-10 Since the last weekly meeting is so close to Christmas, we have decided to make it optional. We are available for a meeting with the groups that want to, but it is ok if not all group members participate. For groups that decide not to have the meeting at all, we ask you to still prepare presentation slides with the usual information and put them in svn/git. In addition we want a short text (corresponding to what you normally talk about in the meeting that is maybe not explicitly shown in the presentation) addressing these things:
2015-12-01 A general hint for the weekly meetings: Try to present the previous and planned activities with a bit more details. Clearly show for each of the activities planned for the passed week if it is finished or not. Try to formulate implementation activities as well-defined features ("Implement name filtering") with clear boundaries rather than more general activities that can go on for several weeks ("work on GUI").
2015-11-16 Changed start time for the project presentations, since we are only five groups this year.
2015-11-14 Updated project group descriptions (still waiting for pictures from most grous).
2015-11-09 The SVN repositories should be ready now. Each group has access to a separate folder (https://v-subek.ita.mdh.se:8443/svn/dva313/2015/gN, where N is the group number). If you are new to SVN, spend some time learning the basics first. This free book could be useful. TortoiseSVN is a good svn client for Windows. For Mac, there are several svn clients, each with some pros and cons. The one most of our colleagues use is SCPlugin (SCToolbarButton), where svn functions are integrated in Finder. There are also svn clients that are run as separate programs, such as RapidSVN.
2015-11-09 We will provide a SVN repository for each group (in a couple of days). If you prefer to use Git, this is also fine but you have to set up your own repository (for example at Github) and provide us access to it.
2015-11-09 Added the project startup slides.
2015-11-09 Added information about weekly meetings, deliverables and presentations. Note that this is an initial version of the information, and it may be adjusted during the course.
015-10-28 Added the project list and sign-up form.
015-10-28 Added Course information slides from the information meeting today.
015-09-30 Note that all scheduled time is mandatory in this course (except the Important information on October 28). In particular, the first week is very crucial since the project work starts already the first Monday, and you will most likely have your first meetings with the customer in this week.
015-09-30 Since there were many questions about this last year, it might be good to write it here: In this course, the project groups are formed by the course staff, and not by the students. Before the course starts, we will provide some information about the available projects, and then students can indicate which projects they prefer. Based on this, and other factors, we will put the teams together.
2015-09-28 Course page created.