This second edition guides the reader through successful planning and implementation of a thesis project and provides students in computer science and information systems with all the advice they need. The reader friendly text offers a simple step by step guide to the key processes involved using an approach that has been tried and tested by the authors over a number of years. A new chapter on information seeking and use and a subsection entitled improve your learning and grade have been added to strengthen the material on how to search for relevant literature and also how to validate it. In addition, this comprehensive and easy to follow text has been fine tuned and updated wherever appropriate. …mandatory reading for all students embarking on their final year project. Easy to read, loaded with good advice and filled with to the point examples, it covers in a step by step fashion each and every aspect that readers might be looking for. Whether you have a bachelor, master or ph.d thesis ahead of you, i strongly recommend you first study this excellent text.

Klaus dittrich, department of information technology, university of zurich, switzerland this book… presents a very clear exposition of basic research concepts that are often taken for granted and assumed to be part of common knowledge. Brian fitzgerald, university of limerick, ireland from the reviews: the authors have written a short book for students doing final year projects in computer science and information systems. Because the authors are from sweden, the details of the procedures and expectations will vary in other countries. However, in the hands of a discerning reader, this book could be useful at several levels, at many colleges and universities, and in many countries. The first section of the book introduces general concepts related to final year projects. Chapter 2 describes research and research methods in computer science and information systems. Chapter 4 provides a very brief overview of the process of conducting final year projects.

The second and most extensive section of the book describes chronologically the major steps in the project. Chapter 5 describes the process of choosing a subject and developing a formal proposal. Chapter 11 discusses drawing your conclusions, evaluating your work, and identifying future work.

Chapter 13 discusses the report itself, including both general writing style and specific citation styles. The book also includes a bibliography, a list of things not to do, and a list of relevant bibliographies available on the internet. According to the authors, the amount of time spent reading a particular source is not relevant to whether it should be discussed in your analysis. The authors provide many such useful suggestions, which, although obvious, might be forgotten in the rush to write. They suggest studying a journal article in the subject area to examine the typical structure of a research report. In addition, they suggest identifying both good and poor decisions made during the research process. They also point out this useful piece of advice: you can usually get away with being boring, if what you say is well organized and clear but you cannot get away with talking nonsense just by being entertaining.

About the conclusions of the project report, the authors say, this is not the time or place to surprise the enthusiastic reader this is a technical report, and not a novel where the least suspected person is found to be the murderer at the end. Similarly, this book has no surprises, just well organized, clear, and useful advice. Acm computing reviews, december 2002 the authors have written a short book for students doing final year projects in computer science and information systems. � according to the authors, ‘the amount of time spent reading a particular source is not relevant to whether it should be discussed in your analysis.’ the authors provide many such useful suggestions …. Ann fleury, acm computing reviews, december, 2002 students in the master of cs and master of science in cs programs are not required to do a master's thesis or master's project but may opt to do one. Note: students in the master of cs program can do a master's project but not a master's thesis. To opt for a master's thesis or master's project, a student must have at least three a's and one b in four core courses.

Int 2 English Critical Essay Marking

Students who have not yet completed their core course requirements must be aware that if these grade criteria are not met, they will be required either to take additional courses in order to satisfy these requirements, or complete the program under the coursework only option. The student must find a faculty member who is willing to work with the student and supervise the thesis or project. Faculty members will customarily agree to serve as a thesis or project advisor only when they have an interest in the topic and a high degree of confidence in the ability of the student to complete the thesis or project.