c/
Date: Wednesday November 19, 2003 Time: 09.00-16.00 Location: Room 142
On Wednesday November 19, the software engineering group organizes a one day seminar for all of its Ph.D. students. The main goal of the seminar for the students to present the current status of their work, and to provide an opportunity to discuss issues related to the study of software engineering. The seminar is organized as a plenary session where each Ph.D. student presents the status of his/her work.
Time | Presentation | Downloads | |
09.000 | Glenn: Knowledge sharing and learning in medical work | ReportPresentation | |
09.20 | Finn Olav: A study of knowledge management and SPI in Norwegian industry | ReportPresentation | |
09.40 | Ekaterina: Supporting social awareness with collaborative virtual environments in an educational context | ReportPresentation | |
10.00 | Mingyang: Creativity and constraints in software development | ReportPresentation | |
10.20 | Break | ||
10.30 | Siv: Quantifying security risks using "all" available data: A risk-based integrated system development and risk management process | ReportPresentation | |
10.50 | Torgrim: A method for developing safer business-critical software | ReportPresentation | 11.10 | Jingyue: Empirical Study on Component-based Development in IT industries | ReportPresentation |
11.30 | Parastoo: Quality attributes and metrics in component-based development | ReportPresentation | |
11.50 | Thomas: 'Understanding the role of organizations in software development processes' | ReportPresentation | |
12.10 | Lunch | ||
13.00 | Per Trygve: Business-critical Software | ReportPresentation | |
13.20 | Jon Arvid: Methods for development of business-critical software | ReportPresentation | |
13.40 | Eivind: "Mobile and ubiquitous technology in children's collaborative learning" | ReportPresentation | |
14.00 | Break | ||
14.10 | Magne: Software Product Families: Issues on Architecture and Integration | ReportPresentation | |
14.30 | Jianyun: Shorter time-to-market for reliable and robust Web-based systems | ReportPresentation | |
14.50 | Sven: On the development of reliable Web Applications at Internet-Speed | ReportPresentation | |
15.10 | Final discussion |
Date | Remember |
November 12, 2003 | Send the title of your talk to Thomas |
Before 14:00, November 18, 2003 | Send status report and presentation to Thomas |
November 19, 2003 | The seminar |
The students have two assignments:
The Ph.D. status report is the basis for your presentation (see assignment 2). We have provided a template for the report. The status report should be 5-12 pages.
The status report provides a base line, a snapshot of our current status. This base line may later be used in tracking our progress. By repeating such seminars once every 6 to 12 months, writing a status report every time, the intention is to provide a tool for us to better monitor and track our own progress.
Each Ph.D. student has 20 minutes for presenting their work with basis in the 'Description of Ph.D. work' section of the status report (ref the status report template). It is up to each and everyone to decide the focus of their presentation. The seminary provides an opportunity to discuss our work. It might therefore be wise to angle your presentation towards issues with your work that you would like to discuss.