1 - How do you classify this thesis (1 - Weak, 2 - Average, 3 - Above average, 4 - Excellent)? 
	3
2 - What is your overall expertise concerning the subject areas of this thesis? 
	I think no 2 fits best. 
	1 - I am an expert
	2 - I am knowledgeable in the area, though not an expert
	3 - I am not an expert. My evaluation is that of an informed outsider
3 - Technical strength (1 - Weak, 2 - Average, 3 - Above average, 4 - Excellent) 		
	2
4 - Presentation. Is the thesis well written? (1 - Weak, 2 - Average, 3 - Above average, 4 - Excellent) 	
	3
5 - Summary of the thesis (Short summary of the thesis)
	(From the thesis)
	Embedded real-time systems are becoming increasingly complex.
	Troughout software history, increasing complexity has been handled by
	abstractions and automation. A recent step in this direction is the use of the
	state machine notation in UML as a basis for implementation.
	This report provides a study of the state machine based approach compared	
	with conventional programming from a number of viewpoints. The study
	covers usability, quality, management and platformissues. Special emphasis
	is put on the constraints of hard real-time systems. The report also includes
	a simplified example of the state machine approach, applied to a real-time
	application appearing in radar systems.
6 - Points in favour and against (also sent to the authors)
	Favour: A very interesting subject. I think many designer are dealing with this question if UML is useful or when it is useful in hard real-time system.
		A very systematic cover over pros and cons using UML.
	Against: In my opinion the authors have try to cover over to many aspect. Anyway all of them relevant when choosing between different design methods. 
--------------------------------------------------------
1 - How do you classify this thesis (1 - Weak, 2 - Avarage, 3 - Above avarage, 4 - Exellent)?

3 - Above average

2 - What is your overall expertise concerning the subject areas of this thesis? 

1 - I am an expert,2 - I am knowledgeable in the area, though not an expert,3 - I am not an expert. My evaluation is that of an informed outsider

2 - Knowledgeable

3 - Technical strength (1 - Weak, 2 - Avarage, 3 - Above avarage, 4 - Exellent)

3 - Above average

4 - Presentation. Is the thesis well written? (1 - Weak, 2 - Avarage, 3 - Above avarage, 4 - Exellent)

4 - Excellent

5 - Summary of the thesis (Short summary of the thesis)

Summary:

-         Study of code generation from UML state machines

-         Focus on hard real time systems

-         Example system similar to real systems within hosting organisation at Ericsson Microwave Systems

-         Study based upon experience from the product Rational Rose Realtime


6 - Points in favour and against (also sent to the authors)

+

o        Good background

o        Well described implementation case

o        Good cover of UML statecharts with pros and cons

o        Very good text and disposition of the material

-

§         No clear recommendation for the next step (Likes that as a decision maker)

§         Missing discussion regarding current and coming possibilities of exchanging models between tools

§         Missing discussion regarding expected future tool improvement. For example effects of new standards incorporated in the product, upgrades and other tool makers products. 
--------------------------------------------------------------------------
1 - How do you classify this thesis (1 – Weak, 2 – Avarage, 3 – Above avarage, 4 - Exellent)?

 3

2 - What is your overall expertise concerning the subject areas of this thesis? 

1 – I am an expert,2 – I am knowledgeable in the area, though not an expert,3 – I am not an expert. My evaluation is that of an informed outsider

2

3 – Technical strength (1 – Weak, 2 – Avarage, 3 – Above avarage, 4 - Exellent)

 3

4 – Presentation. Is the thesis well written? (1 – Weak, 2 – Avarage, 3 – Above avarage, 4 - Exellent)

3

5 - Summary of the thesis (Short summary of the thesis)

 Undersöker hur utveckling av RT-system kan baseras på UML tillståndsmaskiner i jämförelse med vanlig programmering. Speciellt används ROSE-RT som implementerar en variant av ROOM.  Som exempel används ett radarsystem vilket modelleras med två olika "design patterns". En prestandaanalysis genomförs för jämförelse mellan de två modellerna och det bättre "design pattern" väljs för vidare utveckling.
Vidare diskuteras hur den genererade koden från ROSE-RT kan mappas till en en given hårdvara och  ROSE-RT utvärderas som verktyg.

6 - Points in favour and against (also sent to the authors)

Mycket grundligt genomfört arbete i ett aktuellt och viktigt område. Intressant att se en utvärdering av hur ROOM/ROSE-RT fungerar för utveckling av hårda realtidssystem. Rapporten i huvudsak välskriven (bra språk) men med en hel del slarvfel (t.ex. stämmer inte sidnumren i TOC!). 

Betyg i "technical strength" nära 4.