20th Anniversary Brochure - Stan Ackermans Institute

3TU.School for Technological Design,
Stan Ackermans Institute offers eleven
two-year postgraduate technological designer
programmes. This institute is a joint initiative
of the three technological universities of the
Netherlands: Delft University of Technology,
Eindhoven University of Technology and
University of Twente. For more information
please visit: www.3tu.nl/sai.
3TU.School for Technological Design
STAN ACKERMANS INSTITUTE
Software Technology
20 years of practical solutions for industry

Content
Foreword
History
Former OOTI’s
The industry
Projects
The future
2 Johan Lukkien; 20 years of OOTI
4 20 Years of Software Technology / Stan Ackermans Institute
6 Bernard Venemans
8 William van der Sterren
10 Ad Peeters
12 Yanja Dajsuren
14 Marten Jansen; Océ Technologies
16 Ton Kostelijk; Philips Applied Systems
18 Hans Duisters; Sioux Embedded Systems
20 Frans Reckers; TU/e Embedded Systems Institute
22 Athanasios Chliopanos; Video HW prototyping using COTS programmable hardware
24 Charalampos Xanthopoulakis; Integration into the national healthcare infrastructure
26 Eugen Schindler; A model-based engineering framework for developing production printers
28 Bo Wang; Using virtualisation technology for high-performance medical image processing
30 Ready for the future!

2
Johan Lukkien
Foreword 3
20 years of OOTI
In your hands you have a booklet written for the occasion of
20 years of OOTI. As scientific director of OOTI I am proud of
what has been achieved. At the same time I know that it is
others who have brought OOTI this far.
OOTI is a Dutch acronym and stands for ‘Ontwerpers Opleiding
Technische Informatica’. This was the original name that is
still used today. In most English texts it is referred to as the
‘Software Technology’ programme. In the current perspective of
celebrating the 20th anniversary I will use the term OOTI.
Seventeen years ago I joined Eindhoven University as a postdoc
in the group of prof. dr. Martin Rem. At that time, Martin was
very enthusiastic about the new OOTI programme he had set up
together with prof.dr. dipl.ing. Dieter Hammer, and which was
then starting its fourth year. I quickly became involved as it
was a pleasure to work with these students who were fascinated
by technical challenges and opportunities. I remember that
Jan Mulder and I shocked the department by bringing an
oscilloscope over from the department of electrical engineering.
Since those early days I have always remained enthusiastic about
OOTI, as a teacher in a variety of courses and as a project coach.
Intimately linked to OOTI and its success are the names of the
founding fathers, Martin Rem and Dieter Hammer. Both served
OOTI for a long time in some form of directorship. Martin Rem
was scientific director for the last five years. Had it not been
for his passing away in the spring of this year, he would still be
director now. We regret that he is no longer with us and we miss
his inspiration and enthusiasm.
Five years ago on the occasion of the 15-year celebration,
Martin Rem wrote that OOTI brings ‘broadening, deepening and
skills’. He also expressed his expectation that the emphasis on
deepening at that time would change into one of broadening.
I think this is indeed what has happened with the recent change
of the curriculum. The original OOTI goal of preparing students
better for industrial practice is at the heart of this new
programme. I am sure OOTI will continue to deliver highly
trained young people who are of great value to the industry
around us.
The topic of the symposium on the occasion of this 20th
anniversary is once again software and systems. During these
20 years the role of software in systems has increased
tremendously, and the role of a typical ‘OOTI’ has become more
and more focused on the software structure and its extra-
functional properties. The interaction of this software with its
environment, as in embedded systems, is a very important
element. The software architecture cannot be seen independently
of the system architecture of which it is a part. In this
symposium we want to draw attention to this combination,
which is found in systems of all sizes – from the very largest
right down to small embedded devices.
I am looking forward to another 20 years of success for the
OOTI programme.
prof.dr. Johan Lukkien
Scientific Director, OOTI

4
History
20 years of Software Technology
To find out more about the establishment and history of
Software Technology, we have to go back quite a while.
Because the start of the technological designer’s
programmes was a direct result of the introduction of
the two-phase university education structure in 1982.
This meant that a scientific study programme had to be
completed within four years, instead of the five years which
were allowed before then. This first phase of four years led
to a master’s or ingenieur’s diploma. The second phase was
the doctorate or PhD programme.
The first designer’s programmes
The introduction of the first phase proved to be a problem,
particularly for the universities of technology, because
technical education formerly lasted five-and-a-half years. This
then had to be reduced to four years, which meant less depth of
the programmes. Indications were soon received from industry
that the incoming graduates were not of a sufficient level; they
were no longer up to the standard of the engineers formerly
supplied by the universities of technology. Five multinationals
raised this problem and started a campaign for the second
phase to be changed into a designer’s programme for industry,
which would allow the level of the engineers to be restored to
the old standard. The universities of technology responded to
this call and set up designer’s programmes in a range of subjects.
And once those programmes had received legal approval, the
first official designer’s courses were up and running.
Initially there was no designer’s programme in computer science.
And that was a big omission, according to prof.dr. Martin Rem,
because computer science was the discipline of the future. He
raised this with the Executive Board of Eindhoven University
of Technology, and that led in 1988 to the start of the OOTI
programme (Professional Doctorate in Engineering degree
programme on Software Technology), with Martin Rem as
director.
Strong links with industry
A ‘programme group’ was set up to define the structure and
content of the course, and this included not only computer
science specialists but also electrical engineers and management
experts. That resulted in a broadly based programme which was
very complementary to the relatively specialised ingenieur’s
course. The programme was focused on industry, and the aim was
to train the OOTI students for higher-level positions. Industry
was involved in the programme right from the start, for example
by providing guest lecturers and equipment, and the programme
was also advertised in national newspapers. Today’s Software
Technology programme continues to maintain strong links with
industry – there is a steady stream of requests for projects, and
guest lecturers are still being provided.
The first intake of OOTI students mainly came from TU/e itself,
but later there were also increasing numbers from all over the
The Stan Ackermans Institute
The TU/e coordinated the designers’
programmes right from the start, and
set up a special office for this purpose.
This was later merged with the Instituut
Vervolgopleidingen (IVO, institute for
further education), which provided
engineers with the knowledge and skills
that they needed to work in industry.
After the merger, both bureaus continued
under the name Stan Ackermans Institute,
Netherlands. The last ten years have seen a very rapid increase
in the numbers of international students, due partly to Software
Technology’s strong links with industry.
Tailor-made programme
The new OOTI designer’s programme was divided into an in-house
period of a little over a year, followed by a nine-month on-site
project. This structure is still followed at present. The projects
are initiated by requests from industry. Students work on the
design projects in the companies concerned, and these then
form their graduation projects. The formal study part of the
programme consists of a number of modules, which initially
were computer science, electrical engineering and management,
although management was later replaced by physics.
Intake interviews are first held with students applying for the
Software Technology designer’s course. This allows assessment
of their level of knowledge and of which modules they can best
follow. That means this is a tailor-made programme! However
most applicants fail to make the required grade, because
Software Technology only accepts the best students.
Knowledge and skills
At first the programme was very broadly based, and was intended
to complement the often one sided first-degree courses which
the students had done. That’s why there was a detailed list of
all the knowledge and skills which they had to possess by the
named after Stan Ackermans who made
a major contribution to the development
of the designer’s programmes and had
recently died. The Stan Ackermans
Institute facilitated the designer’s
programmes at the TU/e but also had
its own staff, for example to carry out
research into the fundamentals of
‘designing’. The Stan Ackermans Institute
went through a far-reaching reorganisation
five years ago, and the designer’s
programmes now fall directly under the
TU/e departments. The Stan Ackermans
Institute no longer has its own office,
although it has a director. It has become
a collective name for all the technological
designer’s programmes in the Netherlands,
most of which are based in Eindhoven.
All these activities now fall under the
3TU.Federation of the three leading
universities of technology in the
Netherlands.
end of the programme. But because of the constantly increasing
numbers of applicants with different backgrounds, a lot of
time had to be spent on qualification programmes. Once the
programme had been running for ten years that list of
requirements was shortened, which led to a reduction in the
number of qualification programmes.
Software architect or system architect
Today there is once again a development towards a broadening
of the programme. While graduate designers formerly specialised
in a specific software aspect, that has now been broadened to
a knowledge of software architecture. The Software Technology
programme has also been modified in line with this trend.
As well as that, one of the key directions for the future of
Software Technology is the growth of integrated systems, which
increasingly contain ICT, mechanical and electrical elements. For
this reason a mechanical engineering module has been added
and the electronics content has increased greatly, which allows
students to gain the necessary skills as system architects.
It’s essential to respond to developments like these, because
this is the only way that the Software Technology designer’s
programme can continue to provide industrial designers with the
right skills for their work. Those designers are familiar with the
latest developments in industry, and they are able to apply their
technological knowledge effortlessly to those developments.
5

6
Former OOTI’s Bernard Venemans
7
“Knowledge
of project
methodology
gave me a head
start over other
developers”
When Bernard Venemans started his studies in Applied
Physics, he soon realised that he had a very strong interest
in computer science. So he made sure that he already
included some work in that direction during his studies.
After graduating, he found that OOTI was the perfect way
to broaden his knowledge in the software engineering field.
After an extensive qualification programme he started at
OOTI in 1999, and he’s never regretted that. “Especially the
knowledge that I gained about project methodology gave me
a head start over other developers”, says Bernard.
Bernard did his graduation project at LogicaCMG, an international
ICT company. There he helped to develop a test framework:
TestFrame. For this product he developed a module to test
embedded systems. “Take an embedded network processor,
for example. To be able to test this kind of system properly, you
first have to set up test routines based on the specifications.
After that it’s often effective to automate them, and in many
cases this is a completely different discipline”, Bernard explains.
USA: Silicon Valley
During this project an inquiry was received through a partner of
LogicaCMG from a US company that was interested in TestFrame.
It was Bernard who visited them to make the necessary arrangements.
“They were so pleased with the partnership that they
asked me if I wanted to stay”, he says. “So I first of all completed
my OOTI programme and then went back to Silicon Valley in
the USA. I worked there for two years at that company, SDT, and
travelled around a lot in the USA.”
There were also other benefits of his stay in the USA, because
that’s where he met his wife, a Japanese diplomat. After two
years in the US, she was transferred to Tokyo. “That’s when I
had to think very carefully about what I was going to do. I was
happy in the US, although there was an economic dip at that
time. So finally I decided to go with her. After all, how can you
maintain your relationship if you’re so far away from each other?”
Japan: Tokyo
In Japan he started with freelance work for his former employer
and with learning the Japanese language. “If you’re going to
work for a Japanese company you have to speak Japanese”,
he says, “and apart from that I wanted to be able to talk to my
wife’s family. So I mastered the language and got a job at
Nippo Electronics (a subsidiary of NEC), where I worked as an
embedded software developer for TV studios with HDTV facilities.
But after three years of hard work we decided to come back
to the Netherlands. It was difficult for us to keep up with the
working ethos in Japan.”
Thinking at a higher level
Back in the Netherlands he found a job at Ordina Technical
Automation, from where he is currently on detachment to Vialis.
This is a company that specialises in equipment like traffic
management systems. Bernard is one of the project leaders for
development projects: “It’s all about developing the products of
the future, and that’s great fun to do. On the one hand you’re
working with technology, and on the other hand you’re thinking
at a higher level about the strategy, progress and the budget.
I’d had the role of project leader earlier in an annual workshop
during the OOTI programme, so I already knew what that felt
like. Now I can see the value of that in practice. And I’ve also
found the strong international focus of OOTI to be valuable. We
learned there how to get things done in different cultures, and
I’m still benefiting from that now.”

8
Former OOTI’s William van der Sterren
9
“OOTI has been
positive for my
career right
from day one”
William van der Sterren has no doubt at all: without OOTI he
would never have been able to do design work in a research
environment. And the programme also taught him some
things about his own skills, which didn’t only prove to be in
the field of technology.
Together with a fellow OOTI student, William did his graduation
project in 1995 at TNO-FEL. The organisation was carrying out
research into the best anti-mine warfare methods for the Dutch
Navy.
“That was shortly after the first Gulf War”, William explains.
“There was extra attention for anti-mine warfare after two costly
American battleships had been damaged by a few cheap sea
mines. The project we were working on was aimed at creating a
software environment in which TNO could combine all kinds of
simulations and models of mines and ships. An environment of
this kind would allow anti-mine warfare studies to be carried out
more easily and quickly. We were able to work on this project
thanks to a former OOTI student who was working at TNO and
was familiar with the organisation’s wishes and with the skills
of OOTI graduates. After that my colleague stayed at TNO where
he continued developing our project.”
More and more software in medical systems
After OOTI William worked for eight years as a member of the
scientific staff at Philips Research, starting on interactive television
and internet by satellite. Instead of the standard research
work William mainly built prototypes, which he found much more
interesting: “The great thing about a prototype is that you can
show that something really works and how it differs from what
we already know. You can let people see that for themselves.”
Later the emphasis in his work shifted to software architecture
and medical systems. In 2003 William switched to the development
of MRI scanners for Philips Healthcare.
“These scanners contain an increasing amount of software, and
there are two reasons for that. First of all because controlling
the scanning process requires more and more flexibility and
intelligence, and the best way to achieve that is through software.
And secondly because enhancing, displaying and storing
the images of the human body are also software functions. The
biggest challenge now is to make the software so that it’s easy
to extend. We’re constantly thinking up new functions and
improved equipment, but we’re struggling with how to add these
quickly and in a way that doesn’t cause problems with future extensions.
How can you do that with a team of people within the
processes of your organisation? That’s the constant challenge.”
“I found I can do a lot more than technical work alone”
“OOTI has been positive for my career right from day one”, says
William. “It helped me to get into Philips Research, and to be
able to do design work in a research environment. As well as
that, it has led to me being promoted a number of times. That’s
due on the one hand to the good reputation of the programme,
but it’s also a result of having done some work that stands out.”
OOTI has also taught William something about himself:
“During the programme I found I can do a lot more than
technical work alone. That has helped me on a number of
occasions. For example last year when I switched to a new and
completely different position. Now I’m a ‘black belt’, with the
task of solving quality problems by means of both a technical
and an organisational approach.”
“But in any case I don’t need to promote OOTI any more”, he
concludes. “Because in my position I meet a lot of people who
have also completed the programme. And of course that speaks
for itself.”

10
Former OOTI’s Ad Peeters
11
“Without OOTI
I’d never have
been able to do
what I do now”
Ad Peeters was one of the first wave of OOTI students in
1988. He had completed his Computer Science studies in
four years, and was able to continue working at OOTI on the
subject of his graduation project, trace theory. He’s currently
still working on this technology, but now as CTO of
Handshake Solutions, a part of Philips that will soon become
independent. At OOTI he gained a broad understanding of
his field, and the chance to try things out for himself. That’s
been a big benefit in his career. Now he travels the world to
promote ‘his’ technology.
“Trace theory is a line that was started by Martin Rem”, Ad
explains. “It’s all about the way in which circuits on ICs work.
Trace theory is a formalism which allows you to reason about
correctness properties.”
At that time OOTI students didn’t yet do their graduation projects
in industry. But Ad already had contacts with the Philips
department that was working on this technology. After gaining
his industrial designer’s diploma, Ad also took his doctorate in
this subject. He followed an internship in the same department
at Philips, which since then he has never really left. “All that
time I’ve continued working on the same technology, although
in a series of different positions. I started as a researcher and
was given more and more management tasks. Now I’m CTO, and
together with two other colleagues we’re running a company of
22 people. A few years ago we recruited a CEO who is taking us
through the transformation process from a research department
into an independent commercial company.”
Energy-efficient ICs
Ad Peeters travels all over the world to promote his technology
to IC companies. Interest is increasing steadily. Among other
benefits, ICs made with this technology are very energy efficient.
Around 500 million of them are already in use, in applications
that include electronic passports, cars and mobile phones. “For
example there’s an IC using our technology in a specific Nokia
range. This allows the telephone to be equipped with NFC, Near
Field Communication”, says Ad, not without pride. “I’ve launched
my concept on the market and now I have to make sure that it
really takes off and can continue to grow. It’s great to do that,
but it takes a lot of patience and hard work.”
Plenty of freedom
“I learned a lot in my two years at OOTI”, says Ad. “It was a
broadly based programme, which gave me a sound base in this
specialised field. We also had the chance to try all kinds of
things for ourselves. In fact that was the main theme in those
two years: give people plenty of freedom, then they’ll find out
how to do it by themselves. We were glad to take advantage of
that, also because we knew we were backed by people with a lot
of know-how, and we could ask them anything we wanted.”
There’s one more thing that Ad benefits from every day, and
that’s the Technical Writing & Editing course. “Having ideas is
easy”, he says, “but if you’re going to do anything with them
you have to be able to convince other people. I can immediately
spot the people who haven’t done this course.”
“In fact I could never have done what I do now without OOTI”,
he concludes, “which is why I regard it as a plus-point if job
applicants have also done this programme. Because then you
know that they possess a number of the required skills.”

12
Former OOTI’s Yanja Dajsuren
13
“Thanks to OOTI
I’ve achieved
one of my
dreams: working
for one of
the world’s top
companies”
In Mongolia she was a computer science lecturer at a large
university and was involved in software development. But
an international career was a big attraction. She chose the
Netherlands because of its reputation as a liberal country,
and gained her MBA in Maastricht. But finally she decided to
continue her career in software, and looked for a technical
programme. OOTI turned out to be exactly what she wanted.
Yanja started at OOTI in 2003, and has never regretted that for
a minute. Her graduation project was at Philips Research, where
she contributed to the development of a component model for
HVE (High Volume Electronic) devices. “That’s the technology
for re-using software components in different products, which
reduces the costs of software development and shortens the
time to market. Software re-use has already been introduced, so
various component models were developed for different product
families”, Yanja explains. “The aim of my graduation project was
to define fundamental concepts and mechanisms of proprietary
and commercial component models towards a single and
evolutionary component model.”
Immediate job offer
Even while she was still working on her graduation project, it
was already clear that Philips wanted to offer her a job after
gaining her PDEng diploma. “I was very pleased with that,
because I was working with a great group of people. There was
always a lot of discussion, especially with people who invented
different component technologies for Philips. I learned a lot
from them.”
In 2005 Yanja started as a research scientist at Philips Research,
after which she joined a project by Philips Semiconductors.
A year later that company became independent under the name
NXP Semiconductors. Yanja continued working on the same
project with the same colleagues after the spin-off, so not much
changed. “Now I’m working with other research scientists at NXP
on how to improve the ease and predictability of the integration
of NXP’s own software, as well as the integration of third-party
software into NXP’s platforms. We’re investigating how Model
Driven Architecture can enable a conceptual design which is
independent of the platform and realisation technologies, and
which can be used to configure third-party implementations.”
Just like a family
Yanja is very happy that she did the OOTI programme. “Thanks
to OOTI I’ve been able to achieve one of my dreams, because I
wanted to work for one of the world’s top companies. Thanks to
OOTI it was very easy to get a job”, she says. “That’s certainly
due to the industry related projects. These are very intensive,
but they teach you how things are done in industry. It’s hard
work, but the benefits are clear. As Thomas Jefferson once said:
‘The harder I work, the more luck I seem to have’. That’s exactly
how it works at OOTI.
Another thing that’s been very valuable is that you learn all
kinds of other skills at OOTI, such as teamworking, communication
skills and multicultural awareness. There’s much less
attention for things like that in ordinary programmes. I really
have very positive memories of OOTI, and also of the people I
studied and worked with. We were just like a family, and I’m still
in touch with most of them.”
“I think that most OOTI graduates are ambassadors for the
programme, because their professional successes seem to have
made OOTI a well known ‘brand’ in (Dutch) industry”, she
concludes. “I’m still involved myself as a committee member
of the former students’ association XOOTIC. That enables me to
give something back to OOTI.”

14
“OOTI graduates
have an
inherently
high level”
Marten Jansen
The industry 15
Océ Technologies
“We have good experience with OOTI graduates and we like to
work with them”, says Software Development Manager Marten
Jansen. He has been involved with OOTI people in different
ways during his career. “In my early years I supervised a number
of OOTI students in their final projects. That gives you a good
impression of the programme. And we currently have a number
of former OOTI students here who are making good contributions
to achieving our Research & Development goals. Two of them are
even developing into excellent architects.”
Immediately productive
Marten Jansen is very positive about the level of the OOTI
graduates: “That level is inherent in the people themselves.
It’s due partly to the stringent selection procedure, which
ensures that only the top people in their field are admitted
to the programme. We can see that directly. They are good
designers who are usually productive immediately. They also
possess the necessary communication skills, which are absolutely
essential as far as we’re concerned because of the complexity of
our processes.”
More attention for processes
Talking about the future direction of the Software Technology
programme, Marten Jansen says: “Keep selecting stringently
and don’t make any concessions in that. Also continue to pay
attention to the balance between the theoretical basis (which is
excellent) and the practical aspects. During their final projects in
our company, OOTI students don’t work on the strategic aspects
of our product development programme. So they don’t really find
out about the decision-making and management in projects until
they’re working in the company. That’s why more attention could
be given in the programme to practical aspects, for example by
including guest lectures in the curriculum about processes in
different companies. Those processes are often rather intangible,
but of course they are very important. It would be a benefit
for OOTI graduates if they knew more about different types of
processes, and their relative strengths and weaknesses, as well
as about the decision-making in those processes.”

16
“OOTI graduates
make better
career progress”
Ton Kostelijk
The industry 17
Philips Applied Systems
“At Philips Applied Systems we develop ‘first of a kind’ products,
and OOTI graduates can be very useful in that process”, says
system architect Ton Kostelijk, “but they can also learn a lot
here.” He’s very happy about the collaboration with Software
Technology: “I even give lectures there, about the performance
bottlenecks that you can encounter in various kinds of
systems. And they also really do listen to people from industry.
For example I once recommended that they add the subject of
‘testing’ to the programme. That’s now been done.”
Real high-flyers
He regards the Software Technology programme as very focused,
although each OOTI graduate is different. “The people who
come to us are usually the real high-flyers, both in terms of
programming skills and in project experience. We noted for a
while that there were some big cultural differences, but the
curriculum has now been greatly improved in that respect.”
Earlier responsibilities
“The ability of OOTI graduates to think in abstract terms ensures
that they are given responsibility earlier in our lab, and as a
result they make better progress in their careers. They sometimes
lack in-depth programming skills, but usually gain those very
quickly. And they also have very good social skills. I sometimes
see that even though individuals may really be introvert, they’ve
gained those social skills during the OOTI programme. That’s
quite an achievement.”
Keep putting quality first
Ton Kostelijk also has some suggestions to make for Software
Technology in the future. “Keep on putting quality first, by
which I mean the right combination of in-depth technical
knowledge and communication. And check innovations for
quality.”

18
“Our region can
only grow if
there are
enough firstclass
software
architects”
Hans Duisters
The industry 19
Sioux Embedded Systems
On the back of the business card of Hans Duisters, director of
Sioux Embedded Systems, you can read the message: ‘Source of
your development’. And that’s exactly what Sioux does: investing
in the development and application of innovations in software
development. “The Netherlands is a knowledge economy. For a
company – and the region as a whole – to be able to grow, and
to increase productivity, you have to invest in know-how. As
well as that, in today’s market the distinguishing features of a
product or system are in the software”, Hans Duisters explains.
“It’s the software that defines the functionality, which is why
software innovations are vitally important for companies. That’s
what Sioux specialises in, by bringing together knowledge and
applications. We spot innovations all over the world, and we make
sure that our customers and software professionals can benefit
from them. That means our position as service provider has
changed. We’re increasingly thinking together with the customer
about how we can transform technology into good business.”
Vital link
The Eindhoven region is developing rapidly, according to Hans
Duisters. “Formerly there were just a few large companies here.
But we’re now seeing the development into an ‘ecosystem’ of
collaborating companies, in which all the individual partners do
what they’re best at. For example the software architects used
to work mainly for the big companies. But now you can also find
them at the suppliers to those companies. They’re a vital link
in the development process of a product, which is why it’s so
important for more OOTI people to be trained.”
More practical experience
Hans Duisters himself has a lot of experience in working with
OOTI graduates: “We hire them and then immediately give them
a follow-up stage to their training. But we don’t just do that
with OOTI graduates, because we’re also working constantly to
improve ourselves. We invest a lot of money in the development
of our people. That’s absolutely essential, because otherwise we
couldn’t be innovative.”
“There are two areas in which the OOTI graduates distinguish
themselves”, he adds. “They do that in both their technical and
personal qualities. Technically, they have a lot more practical
experience than other graduates. That’s undoubtedly due to the
project work they’ve done. Add to that the fact that building
software requires real teamwork. And that in turn demands
personal skills which the OOTI graduates possess in good
measure. We can see that the selection for the programme is
very stringent, and that helps us to recruit the right people.”
As a region we have to let our voice be heard, Hans Duisters
believes. “Our region can’t grow unless we have sufficient first-
class software architects. That’s why my recommendation is
simple: double the size of the programme, to allow OOTI
graduates to make a real contribution to the development of
the region.”

20
The industry Frans Reckers
21
“There’s a huge
demand for
people with the
skills of the
OOTI graduates”
TU/e Embedded Systems Institute
Project manager Frans Reckers has worked with a lot of OOTI
graduates at Philips during the past fifteen years. In fact he has
supervised around twenty of them in their final projects, and has
worked for years with others. “A lot of OOTI graduates were so
good that we could use them immediately as beginning
designers on interesting research and product development
projects in different Philips units”, he explains. “That’s why
everyone was so enthusiastic, including the OOTI graduates
themselves. And it’s not just Philips – the Embedded Systems
Institute (ESI) on the TU/e campus is also glad to give assignments
to OOTI students during their graduation projects.”
Good selection method
Frans Reckers: “We started at that time with a few graduation
projects, and that was a big success. The good selection method
for the programme is an important factor. They select students
with a good mix of knowledge, personal skills and practical
ambitions. Then they add in-depth knowledge and broader
experience during the two-year programme. The OOTI students
already possess the required competences right from the start”,
he notes. “And if things go well during their graduation projects,
then you can be sure you have the right candidates.”
Breakthrough projects
“The graduation projects are defined in a separate process, with
a creative contribution by the candidates themselves. I’ve now
been through that process fifteen times. We usually select the
subjects together on the basis of ideas about new products
or applications. These have always been ‘genuine’ projects, in
which they went through the entire project cycle one time.
That meant that after graduating they could be put to work
immediately on breakthrough projects. I’ve always found it
interesting to work with talented young people who want to
develop new applications in the fields of design and architecture.
That’s a great thing to do, and as far as I’m concerned it’s an
important part of my professional life. Many of the people from
OOTI provide a significant quality increase for the unit in which
they’re working.”
Frans Reckers, also speaking as a member of the External
Advisory Committee (EAC) of OOTI, has just one important
recommendation for the future: “Try to double your size.
Because there’s a huge demand for people with the specific
OOTI skills.”

22
Projects Challenges
23
Provide insight into the requirements and feasibility aspects
of video hardware prototyping within a software-oriented
group. Design a re-usable prototyping framework on FPGA
that will enable an earlier start of video software
development, and therefore earlier time to market.
Achieve maximum re-usability of existing components
and architectures.
Results
An analysis of the requirements, risks and points of attention
that a software group must be aware of to carry out a hardware
prototyping project. To gain hands-on experience and to
support our claims, we went through all the steps of designing
on FPGAs coming up with a proof-of-concept prototype, a
hardware emulation infrastructure implemented on an FPGA
platform. The framework enables fast integration of new video
processing hardware IPs, providing all the adaptation layers
required for abstracting from the NXP-specific protocols to the
FPGA interfaces and IOs.
Benefits
The developed prototype, although in an immature state,
is the first attempt of developing a re-usable and scalable
hardware emulation framework within and for the needs of a
software group. The group can use it as a base for a powerful
FPGA prototyping framework to expand the capabilities of
the hardware simulation environment or in similar projects.
The documentation produced during this project can also help
in decision-making and risk management in future projects.
Finally this project enabled the group to gain valuable knowledge
of FPGA prototyping, as well as of tools and methods for
IC design and integration.
Athanasios Chliopanos
Video HW prototyping using COTS
programmable hardware
“His enthusiasm and drive
increased with every new
problem encountered.
Many problems were
encountered, tackled and
resolved, taking large
development efforts.
It paid off, after nine
months of hard work we
now know better what it
takes to realise an FPGA
prototype using off-the-
shelf hardware.”
K. Brink,
NXP Semiconductors
The Nexperia Home Software organisation is responsible for supporting NXP Semiconductors’ sales in
the TV application domain by providing cost-effective platform software solutions. The customer base
is large and consists of various major TV setmakers. The Video Software group develops software
components that implement functions related to video processing and video streaming.
Dependency between hardware and software development
The video processing software executes on target hardware. This creates a dependency between software
and hardware development. The target hardware is not available to the Video Software group in the
early stages of development, because it is developed in parallel with the software. To minimise timeto-market,
there is a strong preference to complete a major part of the software development before the
actual hardware becomes available. Due to the limited resources available on the system, the PC-based
simulation framework emphasises the logical and synchronisation aspects of video processing, offering
limited debugging capabilities. The solution proposed in this project is a video hardware prototyping
framework which enables fast integration of video hardware blocks on an off-the-shelf programmable
hardware platform. Due to its high accuracy and resemblance to the final hardware IC, it provides the
simulator with the functional video processing aspects which were formerly lacking, thereby enhancing
its capabilities.
The Video Hardware Prototype project also evaluated the feasibility of a hardware prototyping project
within a software-oriented group without previous experience in hardware development. The project
answered crucial questions about the extent to which an off-the-shelf approach compensates for the
lack of hardware competence within a group, as well as about the portability of an ASIC design to an
off-the-shelf prototyping platform. In addition, the process followed in this prototyping project provided
valuable insight into selecting, setting up and developing on an off-the-shelf FPGA development board,
revealing potential pitfalls and ways to avoid them.
Flexible prototyping framework
The resulting product, a flexible prototyping framework that enables the rapid prototyping of NXPcompatible
video processing modules, is being evaluated both within a hardware simulation environment
as well as by on-chip testing. The aim is for the video hardware prototype to become the base for a
re-usable FPGA prototyping platform used by the Video Software group in future video software
development projects.

24
Projects Challenges
25
The major challenge we had to deal with stemmed from
the considerable fluidity and vast diversity pervading the
establishment of interoperability in healthcare. Official
specifications for connection to the healthcare IT infrastructure
are either incomplete or still undergoing a long
process of maturing. The two countries we examined
– Germany and the Netherlands – although neighbouring,
have applied different standards and technologies in
their national healthcare infrastructures. Furthermore,
standardisation committees issue their guidelines, while
groups of experts are keen to promote their own solutions.
In the light of these developments, the underlying challenge
proved to be the derivation of an architecture that would
enable connectivity with the national healthcare infrastructures,
while maintaining a loose coupling with their intrinsic
features.
Results
The results of the project include an extensive documented
analysis of interoperability in the healthcare domain, highlighting
the various alternatives, along with a proposed
architecture and design.
Furthermore, we developed a prototype to show the creation
and transmission of a referral note to the Catharina Hospital,
Eindhoven, and the reception of the corresponding discharge
note, in accordance with the requirements of the Dutch
healthcare infrastructure.
Benefits
Philips Applied Technologies – Digital Systems & Technologies
has enriched its information inventory with knowledge about
the status, trends, and alternatives in the domain of interoperability
in healthcare. It also has a tangible demonstrator
in cooperation with a prestigious healthcare institute, the
Catharina Hospital, which it can use for promotional purposes
to potential customers.
Charalampos Xanthopoulakis
Integration into the national
healthcare infrastructure
“The work of Charalampos
resulted in ..., and better
understanding of the
domain, not only for him
but also for me and
probably others as well.”
D. La Hei,
Philips Applied
Technologies
Integrating Philips Motiva into the Dutch and German national healthcare infrastructures
In recent studies, home telemonitoring has been proven to reduce mortality and hospitalisation rates
for chronic heart failure patients. Philips’ remote patient management technology enables care teams
to monitor patients’ progress outside the hospital, promoting patient self-management, as well as
facilitating two-way communication between patients and their care providers.
Engaging patients with personalised healthcare content
Philips has developed Motiva, a new TV-based telemedicine platform, designed to engage patients with
daily, personalised healthcare content, and to help care managers reach more patients, influence longterm
behaviour change and reduce healthcare costs. Philips Motiva took the Medical Device & Diagnostic
Industry by storm, winning prestigious awards and being praised by healthcare consortiums in this field.
Meanwhile, demands for the formulation of a set of standards to enable information exchange between
healthcare providers in different countries were increasing. Most notably in Germany and the Netherlands,
specific governmental institutes took up the challenge of developing a suitable framework for
establishing interoperability in the healthcare domain. The objective was to define a set of protocols
that could standardise the format of the exchanged information, along with an architecture that could
support the interconnection of the various healthcare providers.
Integration into national healthcare infrastructures
Philips Applied Technologies foresaw an interesting business opportunity that was worth exploring. It
envisaged integrating the Philips Motiva system into the national healthcare infrastructures. One of the
first steps was therefore to stipulate a number of scenarios for further investigation and prototyping,
such as the referral of a Motiva patient to a doctor and the subsequent discharge from the hospital.
The developed demonstrator combines multiple technologies such as Web Services, SOAP, XML, Java
and the Health Level 7 Version 3 protocol, a widely accepted protocol for modelling workflows, entities
and concepts to enable interoperability in healthcare. To enhance the persuasive power of the
demonstrator, we launched a joint venture with the Catharina Hospital Eindhoven to visualise the
exchange of information in a real healthcare IT environment.

26
Projects Challenges
27
In a multidisciplinary design environment of continually
increasing complexity, it is important for a high-tech company
to develop products faster while maintaining quality.
Although engineers and architects at Océ-Technologies BV are
very good at doing complex projects (many concepts, design
iterations and disciplines), there is a core of design information
they want to use as a compass on the often foggy road of
taking engineering decisions.
Results
A flexible foundation for capturing essential multidisciplinary
design parameters has been developed: MoBasE. Several
applications of MoBasE have been investigated, including
simulation, design visualisation, testing, domain-specific
modelling and software synthesis. In the case study of paper
path development, all of these applications have been
successful, taking the overall engineering process to a higher
level.
Benefits
Using information models built on MoBasE in the engineering
process allows the prevention of duplication and enables the
availability of every piece of information to all tooling. Architects
and managers can quickly get early feedback on design
decisions they make without building a prototype and writing
software. Software engineers can automatically transfer design
decisions as parameters or templates in their code.
Eugen Schindler
A model-based engineering framework
for developing production printers
“Eugen Schindler has gone
into lengths to guarantee
the success of MoBasE
… most importantly, he
has organized a pilot in
a product development
group with excellent
results.”
Ronald Fabel
Océ Technologies
Making production printers involves many technical disciplines such as mechanics, electronics, computer
science, chemistry and physics. Developing printers consists of numerous development activities such
as design, simulation, implementation, test, integration and validation. The MoBasE (model-based
engineering) framework provides the basis for interfacing multidisciplinary models and organising
development activities.
Multidisciplinary reasoning and design
Performing printer development activities effectively in a highly complex environment requires a high
level of multidisciplinary reasoning and design. To speed up development lead time without
compromising quality, the design process should be facilitated in such a way that early design space
exploration can be done, consistency in design information can be maintained, and more insight can be
gained from each step in an incremental design phase. The essence of addressing these concerns boils
down to handling the design information carefully and keeping it meticulously. A basis for fostering
design information is an information model that describes the multidisciplinary design. The MoBasE
framework provides this basis.
Paper path development
MoBasE promotes consistency - every piece of design information must have a single, unambiguous,
authoritative representation within the design information space. Moreover, MoBasE facilitates digital
availability and accessibility of multidisciplinary design information for all disciplines and tools
concerned. The MoBasE framework is also a starting point for automation of implementation, test,
simulation and other product development activities. By practical application of paper path development,
MoBasE has proven to be a successful concept. Other areas of printer development will benefit from
MoBasE as well.

28
Projects Challenges
29
The biggest challenge is to guarantee the real-time
performance of the image-processing pipeline. In a medical
imaging device, real-time image processing and background
tasks are executed in parallel at the same time. These tasks
have different priorities and use computer resources such
as memory, processor load and internal system bandwidth.
These resources must be properly distributed depending on
the priority of the task.
Results
The result of this project showed us that virtualisation
technology is still too immature to share and manage
resources for combined real-time image processing and
background tasks. The main reasons are the impossibility
of sharing advanced graphics card features among multiple
virtual machines, high IO overheads, lack of IO resource
partitioning, and virtual CPU and virtual network performance
limitations.
Benefits
The results of the feasibility analysis uncovered a number
of shortcomings and challenges of using virtualisation
technology for the combination of image processing and
background tasks on the same PC. It provides enormous
insight into how virtualisation technology needs to be
improved to make it suitable to solve the problem.
Bo Wang
Using virtualisation technology
for high-performance medical
image processing
“Bo carefully uncovered a
number of shortcomings,
and some plain
‘showstoppers’ in the
application of
virtualization technology
for our problem.”
Eric Suijs,
Principal Architect
Digital Image Handling
Philips Healthcare – X-Ray
Within interventional X-ray, there is a growing need for sophisticated real-time imaging which give the
medical specialist direct feedback. However, image processing is a demanding process that requires a
large amount of computing resources. The main drive for cost reduction does not allow for an increase in
equipment expenses. This led to a feasibility study of the combination of image processing and background
tasks on a single multi-core processor.
Mobile surgery system
Nowadays in the X-ray division of Philips Healthcare, a multitude of high-performance imaging chains
is required with advanced image analysis functions such as object recognition, monition detection and
feature extraction which are realised in software on standard multi-core PCs. This leads to a continuous
need for power consumption reduction, cost reduction and miniaturisation of X-ray systems, especially
for the mobile surgery system. To satisfy this need, Philips Healthcare is considering combining low
latency image processing with background processing on a single multi-core processor. One of the
scheduling approaches to combine real-time image processing and background tasks on the same
processor that is often suggested is virtualisation, an emerging technology that makes a single physical
resource appear to function as multiple logical resources. Resource management is handled at a high
level in the systems where different virtual systems receive a part of the system resources.
Virtualisation architectures
The goal of this project is to investigate the combination of real-time image processing and background
tasks on the same processor using virtualisation technology. During this project, a comprehensive
feasibility analysis was carried out, appropriate virtualisation architectures were defined, and
demonstrators were built for running an image-processing pipeline. The demonstrators serve as
research platforms for analysing feasibility relevant aspects such as performance, device sharing and
resource partitioning.

30
The future
Ready for the future!
The SAI designer programmes were conceived some 25 years
ago as an answer to the increasing challenges posed by
industry developments to the engineering community.
Several developments have combined and are continuing to
combine to make the engineering practice more complex.
Technological advances follow each other ever more quickly
under the pressure of global competition, providing more
opportunities for innovation. Products are becoming more
complex to meet customer demands, while at the same time
increasing in size, both intrinsically and by integration of
heterogeneous components. Companies are focusing on
differentiating their products to create more business value.
Laying the foundation for solving multidisciplinary problems
Master’s (then Ir ) programmes typically focus on educating
people who are capable of thinking at a high level of abstraction,
who have a critical attitude, and are capable of doing research.
However, solving the complex problems described in the
introduction demands a more mature kind of professional such
as a technological designer or architect, who can function in a
dynamic, multidisciplinary and resource constrained environment.
In the area of software technology, the OOTI programme was set
up to bridge (at least a part of) this gap by offering training
along several lines. First of all, a number of advanced courses
were offered that were not part of the Master’s programme, such
as advanced Software Engineering, Systems Architecting, and
Software Design courses and workshops. Secondly, a number of
workshops were introduced to expose trainees to topics at the
interface of software engineering on the one hand and physics,
electronics and mechanics on the other, thereby laying the foundation
for the ability to solve multidisciplinary problems. Thirdly,
a number of training courses were introduced to complement
trainees’ academic qualities with both professional and personal
development, to prepare them for careers as software professionals
who are able to function in and lead multidisciplinary teams.
From course oriented to project-oriented
In 2007 an important innovation was introduced. The Software
Technology programme, as the OOTI programme was called by
now, was restructured from a course oriented to a project-
oriented programme. The first 15 months of the programme
were divided into 5 blocks comprising a 3- or 4-week period of
lectures and training, and a project. The projects allow a good
portion of the insights gained in the lectures and workshops
to be applied under the guidance of coaches from industry.
Each project allows the trainees to solve an industrial problem,
practice their team and personal skills and learn to balance
requirements from a new problem and technology domain.
Each block builds on the preceding one to allow the trainees
to learn from their mistakes, practice new skills, reinforce
what has already been learned, and deal with more complex
problems.
Tasting practical problems
In the next few years the new programme structure will be
further implemented, improved and refined. Through its structure
the programme allows the trainees to get a taste of 6 different
application and technology domains, which will give them broad
and valuable experience. In addition, it provides the opportunity
to introduce current, concrete problems put forward by our
industry partners. Industry involvement also allows the trainees
to appreciate business issues such as time and resource
constraints, and the added value of the solution to the
customer. The new set-up allows for regular and coordinated
renewal of courses and projects, to keep the education of our
graduates at a high level of quality and relevance. The
combination of academic and industry involvement allows
trainees, in their courses and projects, to anticipate and explore
the adoption in industry of new research developments such as
component- and model-based engineering, as well as practical
approaches for verification and validation.
Staying innovative and inspiring
The Software Technology programme continues to be a unique
programme that aims at educating new generations of
professional software designers and architects. It has served
as an example for the regular Computer Science curriculum in
Eindhoven, which has adopted some of its innovations. This
development constitutes a continuous challenge for the
Software Technology programme to stay innovative and inspiring,
and also as an educational programme to retain its added
value over the Master’s programmes. Software Technology is
committed to achieving this, maintaining the goals of
reinforcing the academic qualities which its graduates gained
during their Master’s programmes, while broadening and
deepening their multidisciplinary and professional qualities.
The Software Technology programme is ready for the future.
31

32
Credits
Edited by:
Coordinator Software Technology
Eindhoven University of Technology
Harold Weffers
Ad Aerts
Text:
Lian van Hout communicatie, Eindhoven
PDEng candidates of the Software Technology programme
Production:
Lian van Hout communicatie, Eindhoven
Photography:
Rien Meulman, Eindhoven
Design:
vanRixtelvanderPut ontwerpers, Eindhoven
Printing:
Drukkerij Lecturis, Eindhoven

3TU.School for Technological Design,
Stan Ackermans Institute offers eleven
two-year postgraduate technological designer
programmes. This institute is a joint initiative
of the three technological universities of the
Netherlands: Delft University of Technology,
Eindhoven University of Technology and
University of Twente. For more information
please visit: www.3tu.nl/sai.
PDEng Students: 1988 H. Bisseling, H. Eemers, L. Gorrissen, M. Kamps, H. van Maren, A. Peeters, E. van
der Sluis, F. van der Stappen. 1989 M. Diepstraten, M. Kuunders, J. Mulder, S. van der Smagt, S. Stoffels,
E. van de Velden, E. Vriezekol. 1990 B. Atzema, A. Jansen, M. van der Korst, L. Lakeman, P. Leijten,
E-J. Marinissen, F. Zwiggelaar. 1991 H. Aarnink, C. Bakker, F. van den Berk, Ms. E. van den Broek,
J. Brouwer, M. Ceelen, R. Deckers, B. van Gompel, J. Koster, M. Lindwer, S. Pauws, M. Peek, R. Schiefer,
H. Schot, E. Suijs, P. Timmermans, Y. van de Vijver, F. Zoontjes. 1992 E. Argante, R. Derwig, R. Engbers,
A. Glim, E. Hautus, K. Hayes, E. Hermans, D. Hoogvorst, J. Langenberg, R. Lukassen, B. Meijer, M. van
Nieuwenhoven, R. Reinds, P. van Riel, F. Ruijs, P. Schats, C. Toma, M. Verhoeven, R. de Waal. 1993
W. Alberts, T. van den Berg, A. Bink, M. Brassé, P. de Crom, G. Dierx, T. van Drimmelen, R. Gelderblom,
L. Geurts, E. van Gruijthuijsen, A. Hanse, J. van der Heijden, P. Kemp, E. de Kock, E. Knapen, N. Kuijpers,
M. Martin, M. Meesters, E. Micklei, J. Moonen, G. Naumoski, M. Penners, O. Pigmans, J. Sleuters,
C. Smakman, B. Stappers, W. van de Sterren, P. Vink, H. Weffers, M. van Wijngaarden 1994 E. Algra, M. van
Balen, B. Barenburg, J. van Beek, F. Benders, M. Bijsterveld, Ms. J. Blijenberg, M. Boosten, Ms. G. Fábián,
R. Geraets, R. Gijsbers, R. Jansen, P. Janson, R. Knubben, P. de Krom, F. Lamerikx, G. Schouten, J. Sliva,
P. Vestjens, H. Visser, J. de Vocht, F. Vonk. 1995 M. Bachri, B. Bon, P. Cardone, M. Danilushkin, G. van
Doren, E. Engelsman, P. Foliant, J. Heijmans, A. Hofkamp, Ms. H. Hollenberg, K. Holtman, H. Jacobs,
Ms. C. van Leeuwen, E. Rietjens, J. Soede, M. Soede, H. Thuijls, E. van Veldhoven, R. Vermeulen, A. Vrijsen,
E. Wijgerink, H. van Woerkom, R. Wouters. 1996 B. Bergevoet, B. van den Broek, R. Caelers, N. Chen,
K.-J. Dijkzeul, L.P. van Drimmelen, Ms. S. Dumont, M. van Erp, R. van Gassel, A.Glas, A. Gouder de
Beauregard, R. Koster, Mrs. C. LePair-Taphorn, F. van Lingen, D. Lowet, R. Marcelis, M. van den
Muyzenberg, R. Penners, R. van de Roer, V. Bos. 1997 P. Benschop, W. Dees, R. Golsteijn, M. Grodek,
E. Knezo, R. van Nieuwburg, T. Novosad, D. Peeters, M. Peters van Ton, Ms. X. Pu, E. Raijmakers,
Ms. A. Verstraten. 1998 Ms. N. Belousova, S. Cristescu, S. Estok, F. Frasiñcar, Ms. P. Garcia, D. Manolache,
I. Nitescu, L. Papalau, P. Šamalik, G. van Stipdonk, M. Tomáš, R. Vdovják, B. Venemans, B. Xu, F. Zavoianu,
M. Zelina. 1999 T.F. Albu, P. Barna, Ms. L. Bougrina, M. van Hartskamp, M. Hudak, M.A.F. Jansen,
S. Kooijmans, M. Kychma, Mrs. H. Ma, G. Muitjens, A. Nesterenko, A. Novikov, Mrs. A. Oborzynska,
K. Oborzynski, P. Rusnak, S. Shumski, T.M. Tran. 2000 Ms. M.A. Albu, X. Jin, M. Pastrnak,
V. Shcherbatyuk, M. Tas, I. Vojsovic. 2001 Y. Bondarau, F. Chelminski, C. Delnooz, D. Jarnikov,
Ms. J. Kapustova, Ms. A. Kryvinchanka, X. Liu, Y. Mazuryk, Ms. G. Michael, A. Mikheyev, M. van Osch,
C. Pau, Ms. Y. Qi, Mrs. E. Shumskaya, L. Voinea, L. Vrijnsen. 2002 C. Acuna, C. van Best, R. Cuppen,
Mrs. C. Peter, V. Ilchenko, J. van Leeuwen, X. Liu, S. Lukin, Mrs. N. Mulyar, Mrs. E. Mumford, A. Nicolaas,
J. Pastrnak, R.G.O. Peters, L. Posta, D.O. Siahaan, S. Srinivasan, Ms. M.Tjiong, A. Yakimovich. 2003
H. Byelas, A. Bykov, M. Cerveny, Ms. Y. Dajsuren, R. Dinu, T. Geelen, J. Gommans, A. Gopalakrishnan,
Gopakumar G., F. Maswar, Ms. S. Mu, V. Niculescu, T. Özkeles, B. Rem, D. Shah, A. Smahlei, W. Wang.
2004 J. Bakker, Ms. Y. Dang, D.T.D. Do, L. Florean, Ms. R. Frunza, P. Georgiadis, Ms. T. Gurzhiy, S. van der
Hoest, Mrs. E. Korshunova, S. Naimat, J. van de Pol, N.S. Popa, A.M. Rosheuvel, M.C.B. Verdonk,
J. Vrijnsen, Ms. F. Wu, Ms. B. Xi. 2005 Chliopanos, Ms. I. Dobai, B.J.T. Golsteijn, Ms. I.M. Iota-Vatafu,
X. Li, Ms. Z. Li, P. Łopatka, J. Meijles, C. Nair, Ms. L. Rahman, P. Sae-Ui, C. Xanthopoulakis, J. Zhang,
Y. Zhang. 2006 Ms. M.A. Contiu, O. Cota, S. Damen, Ms. E. Khmelinskaya, M. Kovacioglu, Ms. H. Moneva,
Ms. C. Petrutiu, Mrs. S. Pillai, Ms. M.C. Popa, I. Sabir, E. Schindler, Ms. D. Schipper, Ms. B. Wang,
M. Xu. 2007 M. Afzal, Ms. Z. Akkus, T. Batsuuri, Ms. X. Chen, J. Crespo Cedeño, Ms. O. Dragomir,
E. Elsackers, Ms. L. Hakobyan, A. Kalloe, J. Kavuma, O. Mendez, , Mrs. C. Padmanabha Pillai, E. Sluiters,
Ms. T. Song, A. Virginia, A. Zlatanos.