DD1363, Mjukvarukonstruktion

Aktuell kursomgång: period 2-4 07/08

Kursledare: Rand Waltzman
Datorpostadress(er): rand@nada.kth.se

Project Information

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.  I have provided a few suggestions for projects for your convenience.

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.

Each deliverable (except item 1 below) must be a pdf file.  It must contain a cover page (i.e., the first page) with nothing but the following information centered on the page using one line per item:

1.      Project Title

2.      Group Number (“Group X”)

3.      Name (one line for each member of the group)

If the title page is not in this format or is missing, the document will be rejected and you will be penalized.

NOTE:  All work must be written in English.

Project Deliverables and Events

1.  Due Date:  2/11/2007, 1800 hours (use e-mail subject header “MVK Group Assignment”)

This is where you suggest a project group.  You will be with this group until the end of the course, so choose as wisely as you can.  The group must contain 4 or 5 members.   I will not accept less than 4 or more than 5.  4 is the ideal number.  Your e-mail should contain the name and e-mail address of each member of your group.  You will also designate a group coordinator.  For the responsibilities of the group coordinator, see the description of the GMP plan (item 2 below).  Once I receive this message, I will assign your group a number which you will use in all future correspondence.

I expect you to make every effort possible to find a group to join.  I likewise expect groups that do not have the minimum 4 members required to be open minded about accepting another student into your group.  If you absolutely can’t find a group to join, then e-mail me and I will assign you to a group.

2.  Due Date:  9/11/2007, 1800 hours (use e-mail subject header “DD1363 GMP Group X” where X is your group number).

Group Management Plan (GMP)
You will find a description of the GMP here.

3.  Due Date: 13/11/2007, 1800 hours (use e-mail subject header “DD1363 POD Group X”)

Project Overview Document (POD)
You will find a description of the POD here.

4.  Due Date:  13/11/2007, 1800 hours (use e-mail subject header “DD1363 RDWS Group X”)

            Requirements Document Work Schedule (RDWS)
            You will find a description of the RDWS here.

5.  Due Date:  20/11/2007, 1800 hours (use e-mail subject header “DD1363 POD Reviews” – no group number required since you will do this assignment individually).

You will review the Project Overview Documents for 3 other groups.  These reviews will not be anonymous – you must stand for what you say.  You will be provided with a review form to be filled out for each POD that you review.  You will then send a copy of each review to the respective project coordinators of the PODs you review and one copy of all three reviews to me.  You will find details here.

6.  Due Date:  27/11/2007, 1800 hours (use e-mail subject header “DD1363 Use Cases Group X”)

You will turn in a complete description of the functional and non-functional requirements for your project as well as a complete set of use cases. 

7.  Due Date:  4/12/2007, 1800 hours (use e-mail subject header “DD1363 Use Case Reviews” – no group number is required since you will do this assignment individually).

You will review the requirements and use cases for 2 other groups.  As in the POD reviews, these reviews will not be anonymous.  You will be provided with a review form to be filled out for each set of requirements and use cases that you review.  You will then send a copy of each review to the respective project coordinators and one copy of all three reviews to me.  You will find details here.

8.  Due Date:  4/1/2008, 1800 hours (use e-mail subject header “DD1363 RD Group X”)

            Requirements Document (RD)
            You will find a description of the RD here.

9.  Have a Merry Christmas and a Happy New Year!!!

WELCOME BACK!!

During the next part of the course you will produce your Design Document (DD).  You will find a complete description of this document here.  You will produce this document one piece at a time, hand it in for peer review, rewrite it and move on to the next piece according to the following schedule.  Note that each section is to be done and handed in as a group effort.

Each review specified is to be done and handed in individually as well as sent to the relevant group leader (whose names you will find here).  For each review assignment, you will review the relevant sections of the group whose number is 1 more than that of the group that you are in unless (a) your group number is 14 in which case you will review the sections for Group 16 or (b) your group number is 24 in which case you will review the section for Group 1.  For the purpose of each review, you are writing from a designer’s point of view – particularly a designer who was not involved in the requirements analysis.  Thoroughly review and discuss each section with regards to clarity and completeness, i.e. do you think that the requirements are accurately reflected and completely covered.  Be sure to give specific examples of any problems that you find.

All assignments are due at 1800 hours on the day specified.  The assignment is evident from the e-mail header.

10.  28/1/2008.  “DD1363 DD Sec. 2.2-2.3 Group X”.  Sections available here for review.

11.  4/2/2008.  “DD1363 DD Sec. 2.2-2.3 Review”

12.  4/2/2008.  “DD1363 DD Sec. 4 Group X”.  Sections available here for review.

13.  11/2/2008.  “DD1363 DD Sec. 2.2-2.3 Rewrite Group X”

14.  11/2/2008.  “DD1363 DD Sec. 4 Review”

15.  11/2/2008.  “DD1363 DD Sec. 5.1-5.4 Group X”.  Sections available here for review.

16.  18/2/2008.  “DD1363 DD Sec. 4 Rewrite Group X”

17.  18/2/2008.  “DD1363 DD Sec. 5.1-5.4 Review”

18.  18/2/2008.  “DD1363 DD Sec. 5.5-5.6 Group X”.  Sections available here for review.

19.  25/2/2008.  “DD1363 DD Sec. 5.1-5.4 Rewrite Group X”

20.  25/2/2008.  “DD1363 DD Sec. 5.5-5.6 Review”

21.  25/2/2008.  “DD1363 DD Sec. 6 Group X”.  Section available here for review.

22.  3/3/2008.  “DD 1363 DD Sec. 5.5-5.6 Rewrite Group X”

23.  3/3/2008.  “DD 1363 DD Sec. 6 Review”

24.  10/3/2008.  “DD 1363 DD Group X”

25.  28/3/2008.   “DD1363 IP Group X”

Implementation Plan (IP)          
You will find a description of the IP here.
The next deliverable is a progress report (see next item).  Since you will have to justify any revisions you make to this initial IP, you would be wise to keep good change records as you go along.  It will make the progress report a lot easier to write.

26.  11/4/2008.  “DD 1363 RD Review”.  Documents available here for review. 

Now that you have the experience of writing a complete DD based on your own RD, you will have a good basis for reviewing the RD of another group.  Remember that this is an individual assignment.  Write from the point of view of the designer who was not involved in the requirements process.  What you need to analyze and discuss is whether you think you could have produced a good design that reflects the requirements as stated in the RD.  Was the RD clear and complete enough for you to do your job.  Be sure to give specific examples of any problems you find.  This report should be 2 – 5 pages.

27.  18/4/2008.  “DD 1363 IPR Group X”

Implementation Progress Report (IPR) 
The purpose of this report is to show how well you are keeping to the schedule provided in the IP.  If any adjustments have been made to the IP, then you must include a revised IP that reflects your current reality together with an explanation of what changes were made from the original and why - so be sure to keep good records of any changes that you make.

28.  9/5/2008.  “DD 1363 FD Group X”

Final Documentation (FD)
There are three parts to the FD:  (1) The user manual for your system, (2) a 10 – 20 page Power Point presentation for your final project, and  (3) a one to two page description of your experience with the project from beginning to end.

29.  12 – 15/5/2008.  Final presentations.  These will be public.

30.  23/5/2008.  “DD1363 DD Review”

Now that you have the experience of implementing a complete system based on your own DD, you will have a good basis for reviewing the DD of another group.  Remember that this is an individual assignment.  Write from the point of view of the implementer who was not involved in the design process.  What you need to analyze and discuss is whether you think you could have produced a good implementation that reflects the design as stated in the DD.  Was the DD clear and complete enough for you to do your job.  Be sure to give specific examples of any problems you find.  This report should be 2 – 5 pages.

 

 

^Upp till Nadas kurser.

Sidansvarig: <rand@nada.kth.se>
Tekniskt stöd: <webmaster@nada.kth.se>