"Don''t wait for someone to write a book you want to read, write it yourselfl" This was the message we received when we asked around for a book that described final year projects for computer science and information systems. In this book, we have gathered our experiences of conducting and supervising final year projects in computer science and information systems. In this book, we present a process for conducting final year projects. This process was developed at the University of Skovde, Sweden. It has been applied successfully to a wide spectrum of projects, with many different subject areas and styles of project. Typical subject areas have included, for example, artificial intelligence, theoretical computer science, databases, data communication, distributed systems, human-computer interaction, operating systems, real-time systems, software engineering, systems analysis and technology transfer. The styles of projects have been both theoretical and more empirically oriented, and have included both science and technology oriented projects. It is our hope that this book will be a valuable companion to the three actors involved in a final year project: student, supervisor and examiner. In addition to the general descriptions and advice provided in this book, we want to emphasise that it is important for students to find out the exact requirements at the department where the project is undertaken. May 2002 Mikael Berndtsson Jorgen Hansson Bjorn Olsson Bjorn Lundell Acknowledgements This book would not have been possible without the support ofa number of people.

"Don''t wait for someone to write a book you want to read, write it yourselfl" This was the message we received when we asked around for a book that described final year projects for computer science and information systems. In this book, we have gathered our experiences of conducting and supervising final year projects in computer science and information systems. In this book, we present a process for conducting final year projects. This process was developed at the University of Skovde, Sweden. It has been applied successfully to a wide spectrum of projects, with many different subject areas and styles of project. Typical subject areas have included, for example, artificial intelligence, theoretical computer science, databases, data communication, distributed systems, human-computer interaction, operating systems, real-time systems, software engineering, systems analysis and technology transfer. The styles of projects have been both theoretical and more empirically oriented, and have included both science and technology oriented projects. It is our hope that this book will be a valuable companion to the three actors involved in a final year project: student, supervisor and examiner. In addition to the general descriptions and advice provided in this book, we want to emphasise that it is important for students to find out the exact requirements at the department where the project is undertaken. May 2002 Mikael Berndtsson Jorgen Hansson Bjorn Olsson Bjorn Lundell Acknowledgements This book would not have been possible without the support ofa number of people.

"Don''t wait for someone to write a book you want to read, write it yourselfl" This was the message we received when we asked around for a book that described final year projects for computer science and information systems. In this book, we have gathered our experiences of conducting and supervising final year projects in computer science and information systems. In this book, we present a process for conducting final year projects. This process was developed at the University of Skovde, Sweden. It has been applied successfully to a wide spectrum of projects, with many different subject areas and styles of project. Typical subject areas have included, for example, artificial intelligence, theoretical computer science, databases, data communication, distributed systems, human-computer interaction, operating systems, real-time systems, software engineering, systems analysis and technology transfer. The styles of projects have been both theoretical and more empirically oriented, and have included both science and technology oriented projects. It is our hope that this book will be a valuable companion to the three actors involved in a final year project: student, supervisor and examiner. In addition to the general descriptions and advice provided in this book, we want to emphasise that it is important for students to find out the exact requirements at the department where the project is undertaken. May 2002 Mikael Berndtsson Jorgen Hansson Bjorn Olsson Bjorn Lundell Acknowledgements This book would not have been possible without the support ofa number of people.