Course Page for 2D1385 Software Development 2008, prutt08

Up to general course home page.

Take Home August Re-Exam (Omtentamen)

The take home re-exam (omtenta) for this course for Friday 29th August 2008 is here . Manuscripts must be handed in by 12.00 on Monday 1st September 2008.

Past Take Home Exams

Here is the take home exam (tenta) for 2008-05-14.

Here is the take home exam (omtenta) for 2007-09-14.

Here is the take home exam (tenta) for 2007-05-25. The model answers to this exam are available as a pdf file.

Here is the take home exam (omtenta) for 2006-07-22.

Here is the take home exam (tenta) for 2006-05-15. The model answers to this exam are available as a pdf file.

The 2005 Omtenta is posted here.

The 2005 tenta is posted here. The model answers to this exam are available as Powerpoint slides.

Latest News and FAQ

• 2008-06-03 My marking assistant has been sick for one week. So there is a delay with marking the scripts. I have made good progress myself, but am reliant on this help. Thanks for your patience.

  Students who need to demo remaining lab work can do so by following the link!
  
  

• 2008-04-14 Today in lectures, as announced last week in lectures, the class voted by a clear majority to hold the home-exam on Thursday 15th May 2008. This means the exam will start on Wednesday 14th at around 15.00 and finish on Friday 16th at around 12.00
  
  
• 2008-03-11 You *only* need the blå häftet if you *don't know* how to do graphics programming/GUI construction using Java. The correct title is "Javaintroduktion" and it costs 20 SEK at studentexpeditionen. There are only a few copies left but we can print more if needed.
  
• 2008-03-11 Please register yourself for the course as soon as possible if you have not already done so. We cannot register your lab redovisning without this. Recall that you must run "res checkin prutt08" inside a terminal window. Thanks!
  
• 2008-03-11 Here are some instructions for installing and running JUnit for unit testing Java programs.
  Step 1: Install JUnit

  1. First, download the latest version of JUnit, referred to below as junit.zip.

  2. Unix (bash)

     To install JUnit on Unix, follow these steps:

     1. Unzip the junit.zip distribution file to a directory referred to as $JUNIT_HOME.

     2. Add JUnit to the classpath:

        export CLASSPATH=$JUNIT_HOME/junit.jar

  3. Test the installation by using either the textual or graphical test runner to run the sample tests distributed with JUnit.

     Note: The sample tests are not contained in the junit.jar, but in the installation directory directly. Therefore, make sure that the JUnit installation directory is in the CLASSPATH.

     To use the textual test runner, type:

     java junit.textui.TestRunner junit.samples.AllTests

     To use the graphical test runner, type:

     java junit.swingui.TestRunner junit.samples.AllTests

     All the tests should pass with an "OK" (textual runner) or a green bar (graphical runner). If the tests don't pass, verify that junit.jar is in the CLASSPATH.

  
  
• 2007-03-06 For lab 1 it will *not* be necessary to submit a UML diagram, as the exercise is a bit too simple for this.
  
• 2007-03-06 For lab redovisning, it is desirable but not essential that both lab partners are present. This way you will both receive feedback about your work. If you cannot be present for some reason then at least send your lab partner along.
  

  ---

  References

  Java programming

  • Javaintroduktion, by Olle Bälter and Anna Redz. (aka. Blå häftet) A concise and cheap introduction to graphics and event handling. Available from CSCs studentexpedition. Price 20 SEK.
  • Java-tutorial
  • Java 2 Platform, Standard Edition v1.4 API
  • Search the API
  • Java-lexikon med enkel förklaring av ord
  • Swedish Java terminology by Stefan Nilsson

  Development Environments (Java IDE)

  • JUnit is a framework for writing test programs.
  • NetBeans
  • JEclipse
  • JBuilder
  • Bean Builder (Code generator)
  • Other links

  Design Patterns and UML

  • Here is one recommended online resource: the Portland pattern repository.
  • More information about patterns can also be found at the Hillside group pattern pages.
  • Pattern digest All the patterns in the world ;-).
  • JavaDoc important for creating easy to read and well structured programs.
  • UML provides may languages for modelling business models, companies, problems and program designs. The notation is summarised here by Allen Holub.
  • A UML tutorial
  • A gentle introduction to extreme programming.

  Components

  • An introduction to Java-beans and another.
  • Other tutorials to Java beans.

  Threads

  • Threads are important, amongst other things, for network communication and GUI construction.

  Network Communications

  • Java-sockets
  • Java RMI is a way for java objects on different computers to communicate with each other.
  • CORBA is a way for objects to communicate with each other over the internet, even when they are written in different languages.
    

  XML, XHTML, and other tutorials

  • w3-schools has excellent basic tutorials on XML, XHTML, SOAP, WAP, JavaScript, .NET, TCP/IP and a lot more.
    
  • The OSI 7 layer model has been the source of inspiration for many internet protocols.

  Other

  ---

  Registration

  For us to report your lab work and exam marks you *must* register yourself for this course. You can do this from a CSC Unix terminal by using the command res checkin prutt08.

  In order to receive your course points it is also necessary that your "kansli" has registered that this course belongs to your choice of courses. Check this with Ping if you are unsure!

  ---

  Course Evaluation

  We are happy to receive suggestions for improvements to this course. During term 4 a course evaluation questionnaire will be distributed.
  
  Course Evaluation for 2006 course evaluation.

  ---

  Literature

  Main Literature

  • Eric Braude: Software Design, Wiley, 2003. Recommended book for the course. However, note that there is no single book that covers the entire course. So the course lecture notes are also essential material. Use the links above for deeper knowledge about course subjects. The course book mainly concerns traditional development methods.
    

    Additional literature

  • Blå häftet, (blue book) A concise and cheap introduction to graphics and event handling. Available at CSCs studentexpedition. For those of you who don't know graphics and GUI construction, this book is *important*.

    Here are some other interesting books you might look at:

  • E Freeman and E Freeman: Head First Design Patterns, O'Reilly, 2004. ISBN 0-596-00712-4. An easy-to-read introduction. One of the few books on design patterns that actually teaches patterns instead of just cataloguing them. Ideal for beginners. to design patterns that emphasises how to use them successfully.
  • Robert C Martin: Agile software development, Prentice Hall, 2002. ISBN 0-13-597444-5. An entertaining and revolutionary book about object modelling and program development using extreme programming.
  • Deitel, Deitel, Santry: Advanced Java2 Platform, Prentice Hall, 2002, 2,075 kg. ISBN 0-13-089560-1. Content rich book, but something of a goldmine, includes CD with large amount of code.
  • Joshua Bloch: Effective Java, Addison Wesley, 2004. Useful for deepening your knowledge of Java.
  • Jan Skansholm: Java Direkt med Swing, Studentlitteratur, 2004, ISBN 9-14-403443-7. A good introductory book to learn graphics quickly.
  • The course material will be made available on the web. One can probably pass the course without buying any books.

  ---

  Timetable

  Vecka 11 - 23 2008 Kurs     DD2385     Programutvecklingsteknik      Vecka 13  2008   Måndag 24 mar   Tisdag 25 mar   Onsdag 26 mar   Torsdag 27 mar   Fredag 28 mar   Lördag 29 mar  08     09     10    10:00-12:00 Programutvecklingsteknik Ovn E32, E33, E34  11     12     13     14     15    15:00-17:00 Programutvecklingsteknik Frl V2  16     17     18       Vecka 14  2008   Måndag 31 mar   Tisdag 1 apr   Onsdag 2 apr   Torsdag 3 apr   Fredag 4 apr   Lördag 5 apr  08    08:00-10:00 Programutvecklingsteknik.b Lab 4V5Gro, 4V6Bru  09     10    10:00-12:00 Programutvecklingsteknik Frl V2  11     12     13    13:00-15:00 Programutvecklingsteknik Ovn L21, L22, L41  14     15    15:00-17:00 Programutvecklingsteknik.a Lab 4V2Rod, 4V5Gro 15:00-17:00 Programutvecklingsteknik Frl V2  16     17     18       Vecka 15  2008   Måndag 7 apr   Tisdag 8 apr   Onsdag 9 apr   Torsdag 10 apr   Fredag 11 apr   Lördag 12 apr  08    08:00-10:00 Programutvecklingsteknik.b Lab 4V5Gro, 4V6Bru  09     10    10:00-12:00 Programutvecklingsteknik Frl V2  11     12     13    13:00-15:00 Programutvecklingsteknik Ovn L21, L22, L41  14     15    15:00-17:00 Programutvecklingsteknik.a Lab 4V2Rod, 4V5Gro 15:00-17:00 Programutvecklingsteknik Frl V2  16     17     18       Vecka 16  2008   Måndag 14 apr   Tisdag 15 apr   Onsdag 16 apr   Torsdag 17 apr   Fredag 18 apr   Lördag 19 apr  08    08:00-10:00 Programutvecklingsteknik.b Lab 4V5Gro, 4V6Bru  09     10    10:00-12:00 Programutvecklingsteknik Frl V2  11     12     13    13:00-15:00 Programutvecklingsteknik Ovn L21, L22, L41  14     15    15:00-17:00 Programutvecklingsteknik.a Lab 4V2Rod, 4V5Gro 15:00-17:00 Programutvecklingsteknik Frl V2  16     17     18       Vecka 17  2008   Måndag 21 apr   Tisdag 22 apr   Onsdag 23 apr   Torsdag 24 apr   Fredag 25 apr   Lördag 26 apr  08    08:00-10:00 Programutvecklingsteknik.b Lab 4V5Gro, 4V6Bru  09     10    10:00-12:00 Programutvecklingsteknik Frl V2  11     12     13    13:00-15:00 Programutvecklingsteknik Ovn L21, L22, L41  14     15    15:00-17:00 Programutvecklingsteknik.a Lab 4V2Rod, 4V5Gro 15:00-17:00 Programutvecklingsteknik Frl V2  16     17     18       Vecka 18  2008   Måndag 28 apr   Tisdag 29 apr   Onsdag 30 apr   Torsdag 1 maj   Fredag 2 maj   Lördag 3 maj  08    08:00-10:00 Programutvecklingsteknik.b Lab 4V5Gro, 4V6Bru  09     10    10:00-12:00 Programutvecklingsteknik Frl V2  11     12     13     14     15    15:00-17:00 Programutvecklingsteknik.a Lab 4V2Rod, 4V5Gro  16     17     18       Vecka 19  2008   Måndag 5 maj   Tisdag 6 maj   Onsdag 7 maj   Torsdag 8 maj   Fredag 9 maj   Lördag 10 maj  08    08:00-10:00 Programutvecklingsteknik Frl V2 08:00-10:00 Programutvecklingsteknik.a Lab 4V5Gro, 4V6Bru  09     10    10:00-12:00 Programutvecklingsteknik.b Lab 4V5Gro, 4V6Bru  11     12     13     14     15    15:00-17:00 Programutvecklingsteknik Ovn E32, E33, E34 15:00-17:00 Programutvecklingsteknik Frl V2  16     17     18       Vecka 20  2008   Måndag 12 maj   Tisdag 13 maj   Onsdag 14 maj   Torsdag 15 maj   Fredag 16 maj   Lördag 17 maj  08    08:00-10:00 Programutvecklingsteknik.b Lab 4V5Gro, 4V6Bru  09     10     11     12     13     14     15    15:00-17:00 Programutvecklingsteknik.a Lab 4V2Rod, 4V5Gro  16     17     18

  ---

  Teachers

  The course leader is Karl Meinke <karlm(at)nada.kth.se>, telephone 08-7906337. Its easiest to meet me at the end of lecture periods or in the labs.

  
  
  

  ---

  Course Objectives

  Take a good look at the course objectives. Besides helping you understand the course from a student-centred point of view, you will also find them extremely helpful in giving guidance about what kind of questions can appear on the exam. This is particularly critical on a new course with no past exam papers.
  
  

  ---

  
  
  

  Course Contents

  Lectures

  • Lecture 1: (OH-slides in pdf) (OH-slides in powerpoint) Overview of the course, UML, use cases, simple sequence diagrams.
  • Lecture 2: (OH-slides in pdf) (OH-slides in powerpoint) Structured sequence diagrams. Class diagrams, inheritance, aggregation.
  • Lecture 3: (OH-slides in pdf) (OH-slides in powerpoint) Class diagrams (continued), associations, multiplicity etc. Mapping class diagrams to code. Object diagrams. Introduction to software architectures, MVC.
  • Lecture 4: (OH-slides in pdf) (OH-slides in powerpoint) Software architectures MVC, virtual machines, independent components, data centered, layered, ATAM.
  • Lecture 5: (OH-slides in pdf) (OH-slides in powerpoint) Patterns: singleton, facade, mediator, factory, observer, command.
  • Lecture 6: (OH-slides in pdf) (OH-slides in powerpoint) Software lifecycle models: waterfall, code-and-fix, spiral, rapid prototyping, extreme-programming, unified process, COTS.
  • Lecture 7: (OH-slides in pdf) (OH-slides in powerpoint) Goals of software design. Testing, JUnit.
  • Lecture 8: (OH-slides in pdf) (OH-slides in powerpoint) Java exceptions. Sockets.
  • Lecture 9: (OH-slides in pdf) (OH-slides in powerpoint) Threads. XML.
  • Lecture 10: (OH-slides in pdf) (OH-slides in powerpoint) Computer Law, Internet Programming, Javadoc, CORBA.
  • Lecture 11: (OH-slides in pdf) (OH-slides in powerpoint) OO Design Principles.
  • Lecture 12: (OH-slides in pdf) (OH-slides in powerpoint) Course Review.

  Exercises

  The exercises will be the same as last years exercises.

  	Namn	Datorpostadress
  Övningsgrupp 1	Karl Meinke	karlm(at)nada.kth.se
  Övningsgrupp 2	Joel Sjöstrand	joelgs(at)sbc.su.se
  Övningsgrupp 3	Mattias Kjellson	mkje(at)nada.kth.se

  Labs

  Please read the lab demonstration rules. for examination and make sure you are properly prepared to demonstrate *all* the required aspects of each lab before you ask a lab assistant for a demonstration time.

  There are five laboratory exercises. Solving all the basic exercises by the deadlines gives a C for the lab work. Solving each bonus problem by the deadline (bonus problems exist for all labs except lab 1) will give a B for the lab work. If you also successfully complete the extra lab exercise by its deadline, this will give an A for the lab work. If you don't successfully demonstrate all labs according to schedule you will receive at most a C for the lab work. The lab work is to be demonstrated according to the lab demonstration rules.. The extra laboratory exercise can be an extension of one of the basic lab exercises that you have chosen yourself, or a completely new exercise. Check with a lab assistant that your choice of work is appropriate to receive the extra point. To pass the lab component of the course, all labs must be demonstrated before the final demo occasion. We do not have the resources to examine individual student labs at random times, particularly near the end of term. Therefore it is important that you make use of the booked lab periods.

  To redovisa labs we will be using the queueing system SIMA. To use this software from a Unix terminal, type "module add sima". Then simply type "sm" to start the program. You should see a window pop up with various course names. Click on the course "prutt08". You should now see who is in the queue. Also you should be able to add yourself to the queue.

  Here you can find what do I have to redovisa and when? in pdf format, and for those on PCs the same checklist in Powerpoint.

  Lab	Demonstration Deadline
  Lab 1   Lab 1 - english	v.15 9 april 2008
  Lab 2   Lab 2 - english	v.16 16 april 2008
  Lab 3 and here!   Lab 3 - english and here!	v.17 23 april 2008
  Lab 4   Lab 4 - english	v.18 30 april 2008
  Lab 5   Lab 5 - english	v.19 9 may 2008
  Suggestions for extra lab work: swedish   english	v.20 14 may 2008

  ---

  Examination

  
  
  In 2008 I will again use a take-home exam (hemtenta) as the examination method. This means that the exam paper will be placed on this web page on a date and time to be agreed by the course participants. From the time that the exam is made available, students will have about 36 hours to complete a paper that should normally not take longer than 5 hours of continuous work.
  
  Only paper manuscripts can be submitted. *I do not accept electronic submission under any circumstances". Manuscripts may be typed on a computer and printed out on a printer, or they may be handwritten.
  
  Paper manuscripts should normally be handed in to studentexpeditionen. If students are unable to attend before the deadline, they may post their manuscript to the department. The submission date will be taken to be the date of posting (official stamp). *I repeat, it is not possible to submit electronically under any circumstances*.
  
  You will be able to sit the exam anywhere you wish (but there are no booked examination rooms).
  
  Your exam work must be your own. You are not allowed to collaborate with any other student on the course, or anyone outside the course. You are however allowed to use books and/or the internet as long as you cite any work which is not your own to its correct source.
  
  The subject matter of the questions will be very similar to the exercises used in övningar, though I will use previously unseen questions. Therefore it will be an advantage to you to attend övningar held each week.
  
  With regard to grading according to the Bologna agreement, the exam paper will be divided into two halves, part I and part II. The grades D and E, can be achieved by answering part I questions only to the level of 80% and 70% of the available marks for part I respectively. The grade Fx (which allows komplettering) requires 60% of the available marks on part I. The grades A, B and C are achieved by obtaining at least 80% on part I, and respectively 60%, 40% and 20% of the marks available on part II.
  
  Part I questions will cover the basic material of the course, and will be similar to the exercises from övningar. Part II questions will cover the more advanced material of this course drawn, and will also be similar to the exercises from övningar.
  
  The omtenta will have the same format, and will run in the tenta period at the end of period 4.
  
  

  ---

  Komplettering Rules for this Course

  The following rules will be applied to the course 2D1385 as from 2008-03-11 with regard to komplettering.
  
  Under the new Bologna system to qualify for komplettering you must at least obtain the grade Fx. If you obtain this grade, you can raise it to an E grade without resitting the exam, by following the instructions below. You must resubmit your komplettering work no later than the end of the seven week period after you have taken the exam. (So if you take the exam in period 4 2007/2008 you must submit by the end of period 1 2008/2009.)
  
  Komplettering Instructions If you have failed the exam, but have been offered komplettering, then you must write out the correct answer to each full question (i.e. Q1, 2 or 3) that you have failed. You have failed a question if you have gotten less than 50% of the total points available for that question. You do not need to rewrite answers to a question which you have passed in its entirety. You can submit your new answers to me whenever you are finished.
  

  ---

  Overall Course Mark

  This year, for the first time, the lab marks must be integrated into the exam marks according to the Bologna agreement. I will integrate the lab mark with the exam mark to give a final mark in the following way.
  
  To get a grade A for the course as a whole you must achieve at least a grade A on the exam and at least a grade A on the lab.
  
  To get a grade B for the course as a whole you must achieve at least a grade B on the exam and at least a grade B on the lab.
  
  To get a grade C for the course as a whole you must achieve at least a grade C on the exam and at least a grade C on the lab.
  
  To get a grade D for the course as a whole you must achieve at least a grade D on the exam and at least a grade C on the lab.
  
  To get a grade E for the course as a whole you must achieve at least a grade E on the exam and at least a grade C on the lab. You can also achieve a grade E by obtaining at least a grade Fx on the exam, completing any komplettering work which is assigned to you, and obtaining at least a grade C on the lab.
  
  To get a grade Fx for the course as a whole you must achieve at least a grade Fx on the exam and at least a grade C on the lab.
  
  

  ---

  Code of Honour

  At CSC there is a general code of honour hederskodex for all courses. Please read this!

  Up to course home page.
  

  ---

  Responsibility for this page: <karlm(at)nada.kth.se>
  Last edited 29th August 2008
  Technical support: <webmaster(at)nada.kth.se>