Kursledare: Rand Waltzman
The project is a big part of the course. You will be working on it during all 3 periods. The project will be done in several phases. The first phase is the Requirements Analysis which you will complete during Period 2.
You will work in groups of 4 persons. Smaller or larger groups can be approved only
in extremely exceptional circumstances
which will be decided on a case by case basis by
1. Form a group yourselves.
2. Request to be placed in a group.
I must hear from you no later than Friday, November 4, 1200. You must either:
1. Send me a list of the 4 members of your group. In this case, a single e-mail message containing the names of all group members will be sufficient.
2. Request to be placed in a group.
The header of this e-mail message must be: 2D1363 Group Request. I have a filter on my mail and if the header is not exactly as specified, I will not get it. If I have not heard from you by the date stated, I will assume that you are not interested in the course and you will be dropped and unable to continue. Exceptions to this will be made only in extreme cases (severe illness, a death in the family, etc.).
Each group will be able to choose their own project – up to a point. Your group can:
1. Submit a project proposal. In this case, I (Rand) must approve. Some negotiation between me and the group might be required. For your convenience, I have included a list of suggested projects. You are, however, not obligated to use any of them – they are just suggestions.
2. Choose from the following group of projects that I have arranged in advance. These projects have been contributed by several research groups here at KTH and involve interacting with the group of your choice and learning something about the research they are doing. The choices are limited and so (possibly) is the number of groups that can do a given project. In case there are more groups who want to do a certain project than the contributors are willing to allow, decisions will be made by lottery. The projects are:
1. The Ultimate RoboLook (Organizational meeting 25/11/2005 at Teknikringen 14, plan 3, rum 304)
2. Graphical Interface for Creating Compounded Components in CURE (Organizational meeting 25/11/2005 at Teknikringen 14, plan 3, rum 304)
3. The Infomat Interface - A Document Clustering Exploration Interface (Organizational meeting on 23/11/2005 in NADA seminar room 4523)
4. 3D Visualisering av Aktiviteten i Neuronnät (Organizational meeting 25/11/2005 in NADA seminar room 4523)
5. A System for the Design and running of Psychophysical Tests (Organizational meeting on 30/11/2005 in Room E53.)
The meetings will be held from 1500-1700 (yes, same time as my lectures which will take place as scheduled – in fact, just to be completely clear, “1500” means that the actual start time is 1515). The locations will be announced shortly.
In terms of the size and scope of the project, keep in mind the following. I expect each member of the team to spend approximately 100 hours on implementation and testing. If you look at the schedule, that is spread over approximately 8 weeks. That is a total of 400 – 500 person hours of work depending on whether you have 4 or 5 people in your group. Note that this does not count the time you spend in requirements analysis and design – it is the actual implementation and testing of code. I leave it to you to estimate how much you can get done in that amount of time.
Project Deliverables and Events
NOTE ABOUT LATE PROJECT DELIVERABLES: If you do not turn in all necessary project documentation in completed form by the stated deadlines, there will be a late penalty to pay. Each group begins with 25 points (note that these 25 points are for Part A of the course – you will start out with a fresh number – as yet unspecified - of points at the beginning of Part B). You will be charged 5 penalty points for each day (i.e., 24 hour period) any of the required project deliverables are late. The late period begins one minute after the stated deadline. This means you will be charged 5 points if I receive your work anytime during the following 24 hours. One minute after that period you will be charged another 5 points, etc. These charges are cumulative over the duration of Part A of the course (i.e., it is not 25 points per deliverable, but 25 points over the whole of Part A). When you reach 0 points, you fail the course.
1. Due Date: 18/11/2005, 1200 hours (use e-mail subject header “2D1363 RDT Group X” where X is your group number)
Requirements Document Template (RDT)
The RDT is an abstract outline of the Requirements Document (RD) that you will produce for your projects. The RD is the final project deliverable for Part A of the course. The RDT shows the various sections that you expect your document to contain with descriptions of each one. This template should be usable in any project. It represents the way you have decided that you would like to organize your work and will serve as a guideline for your group. I have provided several samples of RDTs (Sample 1, Sample 2, Sample 3, and Sample 4). Study them carefully and put together one of your own. There is also plenty of good general guidance to be found in your text. You may use any material that you find in these samples or the text for your own RDT. As an extreme case, you might simply choose to use one of them as is. That is entirely up to you. But one requirement that I insist on for your RDT is the inclusion of Use Cases. However, these may have any format that you choose as long they are clear.
Set up the RDT in a way that makes sense to you since you will be expected to use it as your guide to doing your project requirements analysis and fill in all the sections. You will be free to make changes to it once you have been assigned a project and start your actual requirements analysis. However, each such change must be documented. You must provide a reason for each section or subsection of your original RDT that you delete as well as each section or subsection that you add. This change documentation will be included in a separate deliverable.
It will also help if you have a look at some samples of completed RDs. Feel free to find your own. I have included a few here for your convenience and to get you started.
2. Due Date: 25/11/2005, 1200 hours (use e-mail subject header “2D1363 PSS Group X” where X is your group number)
Project Selection Statement (PSS)
If you want to propose a project of your own, the PSS is a short paragraph describing what you would like to do. If you would like to do one of the arranged projects, simply state which one you want to do. In that case, please give a first and second choice (there might be restrictions on the number of groups allowed to work on a given project depending on the preferences of the project sponsor).
3. Due Date: 9/12/2005, 1200 hours (use e-mail subject header “2D1363 POD Group X” where X is your group number)
Project Overview Document (POD)
You will find a description of the POD here.
4. Due Date: 9/12/2005, 1200 hours (use e-mail subject header “2D1363 RDWP Group X” where X is your group number)
Requirements Document Work Plan (RDWP)
You will find a description of the RDWP here.
5. Due Date: 3/2/2006, 1200 hours (use e-mail subject header “2D1363 RD Group X” where X is your group number)
6. 13/2 – 17/2/2006
Requirements review meetings. Sign up sheets will be available 3/2/2006.
7. Due Date: 7/4/2006, 1200 hours (use e-mail subject header “2D1363 DD Group X” where X is your group number)
Design Document (DD)
You will find a description of the DD here.
8. Due Date: 7/4/2006, 1200 hours (use e-mail subject header “2D1363 IP Group X” where X is your group number)
Implementation Plan (IP)
You will find a description of the IP here.
9. 18/4 – 21/4/2006
Design and Implementation Plan review meetings. Sign up sheets will be available 4/4/2006.
10. 22/5 – 26/5/2006
Demos and Final Report (Final Report will be handed in at the Demo). Sign up sheets will be available about one week
You will find a description of the required manual and final report here.
Upp till Nadas kurser.