Page History

...

Table of contents
1 Introduction
1.1 General information
1.2 Goal and rationale of the course
1.3 Required Knowledge
2 Motivation on Project Work and Group Dynamics
2.1 About the Course
2.2 Project work in a didactic perspective
2.3 Training in group dynamics
3 Administrative information
3.1 Work load
3.2 Timeline
3.3 Group assignments
3.4 Rating of project work
3.5 Supervision and meetings
3.6 Pre-delivery for examiner and writing course 5 Project deliverables to examiners and jury on November 16 
3.7 6 Final presentation and demonstration on November 21 23
3.8 7 Anti-plagiarism
3.9 8 Copyright or Intellectual Property Rights (IPR)
3.10 9 Course reflection, evaluation and feedback
Appendix A – The project plan
A1. Overall project plan
A2. Concrete project work plan
A3. Project organization
A4. Templates and standards
A5. Version control procedures
A6. Documentation of project work
A7. Quality Assurance (QA)
A8. Test plan
Appendix B – Suggestion for appendices in your project plan
B1. Partners
B2. Concrete project plan
B3. Detailed phase plans
B4. Table for handling of risks
B5. Table for effort registration
Appendix C – Content of the phase/sprint documents/chapters
C1. Introduction
C2. Planning
C3. Pre-study of the problem space vs. solution space
C4. Lifecycle model: waterfall vs. agile?
C5. Requirements Specifications
C6. Estimation of realization effort of a use-case model
C8. Programming
C9. Testing
C10. Internal and external documentation
C11. Evaluation
C12. Project presentation and demonstration
C13. Appendices
4 APPENDIX D – Administrative and Technical Resources
D4.1 Office Resources
D4.2 Technical Resources
D4.2.1. Workstations
D4.2.2. Source Control Management
D4.2.4. Use of collaboration technology in the project
5 Appendix E – SCRUM – a popular agile method
E5.1. Product backlog
E5.2. Sprint planning meeting
E5.2.1. Daily Scrum status meeting
E5.2.2. Irregularities
E5.2.3. Sprint review meeting
E5.2.4. How do I prepare a project for Scrum (short tutorial)
6 Appendix F – Use-case based effort estimation
F6.1. Introduction to use-case estimation
F6.2. More on the estimation method
F6.3. A mini-discussion
F6.4. References
F6.5. Appendix: A small use-case diagram, with extra comments
F6.6. Add-on to use-case example
7 Appendix G – Guest Lectures

...

All material included in the final delivery (project documentation, prototype of the system, reflection report, final presentation) should be delivered to the group's advisor by midnight of the final delivery date. The group agrees with the advisor the delivery protocol (email, dropbox, google docs, other). 

...

Project deliverables to examiners and jury on November

...

16

By November 16 (23:59) every group needs to email the following to the course responsibles (Letizia Jaccheri and Jon Atle Gulla) and the course coordinator (Kristin Karlsen):

• URL of final project report (pdf)
• URL of 1 minute video presenting their project and product

Note that there is no printed deliverables in the course.  Since it is only the report that is handed in on November 16, you may still modify your code until the final presentation on November 23 (as long as it does not affect the report itself). 

Final presentation and demonstration on November 23

Follow up on https://www.ntnu.no/wiki/display/tdt4290/ for details about the arrangement for the day.

Room: Rooms are reserved for the final presentation. If the project demonstration requires special facilities (such as virtual reality or cave equipment), the groups can also book and have the presentation in other rooms. If your group needs to have the presentation in a specific room, please notify the course coordinator (Kristin Karlsen). Remember that the room must have space for 10-15 persons. The time and place for each presentation, will be published on the course webpage.
Laptop: Most groups use one of their personal laptops for the demonstration. If your group do not have a suitable laptop for the presentation, please notice drift@idi.ntnu.no two weeks before the presentation. A beamer will be made available in all presentation rooms.

Deliverables on November 23:

• USB key with final report, video, code and presentation slides to customer
• Presentation slides URL and code (e.g. Github) to course coordinator

The presentation schedule of November 23 is as follows:

Please note the following:

• The present day starts with an obligatory introduction at 9.30 in Drivhuset.  All students should attend.
• All members of the groups are to be present during their own presentations.
• The presentations are in English and open to the public.  The groups must invite their customers, but may also invite other people that have been involved in the project or may find the project results interesting.  The supervisors will be present.
• Normally a presentation includes both a description of the project as well as a video and demo of the implemented system.
• Each presentation is up to 30 minutes long, including the video and demo.  The examiner and the general audience have up to 15 minutes for questions.
• The group hands over the USB key to the customer at the end of their presentation.
• The presentation rooms are equipped with projectors, but other necessary equipment must be brought and installed by the student groups themselves

• Customer
• Examiner
• IDI archive
• Advisor

...

• .

Anti-plagiarism

The rules for this are very strict, see §36 in "Forskrift om studier ved NTNU" (page 23 in "Studiehåndbok for Sivilingeniørstudiet 2011-12") regarding cheating and http://www.lovdata.no/all/hl-20050401-015.html#4-7
See also http://www.idi.ntnu.no/grupper/su/publ/ese/plagiarism.html.

...