Degree requirements for projects

12 Chapter 1 n Introduction the project. Sometimes the client and the user are one and the same but often, if you are developing a system for a company, for example, they are not. For instance, you might be asked to develop a web site for a company to sell its products. The client is your contact within the company, but your users is anyone who will access that site. Conflicts usually arise when the client and the user are different: for example, should you provide something the client requests that you know the user won’t like? How do you persuade the client that the user needs a particular piece of functionality when the client feels it is unnecessary? In other cases your supervisor may be your client andor user as they may have proposed the project you are undertaking. In this case, your supervisor will be acting in all three roles. This can cause conflicts as their advice as a supervisor may not tally with their needs as a user for example, as a user they may request certain features from your software system, but as a supervisor may recommend that you do not include that feature as it may take too much effort for little reward.

1.4.4 Examiners

The number and type of examiners you will encounter on your course will largely depend on the level of project you are undertaking undergraduate or postgraduate and the regulations your institution has in place these vary by institution and country. At the undergraduate level, for example, your supervisor may be the only person to mark your project. However, it is more likely that another academic in your department or perhaps another department within your university will be involved. Moving to postgraduate projects, external examiners those from other departments and usually other universities will be involved. Any number of examiners can be involved in project assessment – from individual examiners to panels of examiners that act as a committee to evaluate the contribution of your work. The examiners will look for a number of things in your project, from the contribution a PhD project makes, for example, to the use of appropriate processes, methods, and techniques for an undergraduate software development-type project. Chapter 10 discusses the criteria examiners look for when evaluating projects. Depending on the nature of your course, examiners can also be involved at different stages as your project progresses. For example, an examining committee may be involved early on to evaluate your project’s requirements or proposal. Or, an examiner may need to see an annual report or other information. You should be aware of the regulations regarding the evaluation and examination of your project and follow any procedures closely. Institutions are quite strict when it comes to examinations and insist that procedures are followed to the letter. Make sure that your supervisor is aware of the current procedures at your institution and obtain the institution’s advice on the requirements for the examination of your project.

1.4.5 Evaluators and testers

If you are developing a software system as part of your project, you will need to test and evaluate this system at some point. It would be wrong to complete all the testing and evaluation on your own, and so others will be involved. These people can range from your client, who has requested the software, the users who will actually use the software, to people either expert or not – for example, colleagues 1.5 How this book is arranged 13 from your course who are not involved with the project but can nevertheless provide useful feedback. Chapter 6 discusses the issues surrounding software evaluation and testing in more detail. It also describes those involved with the evaluation and raises some issues you will need to consider when using others in this capacity. •

1.5 How this book is arranged

1.5.1 Overview

This book is split into five main sections that approximate chronologically to your pro- ject’s progress. Section 1 includes this chapter and covers some preliminary background material on the types of projects you might pursue and the nature of research. Section 2 covers the skills necessary to set your project’s foundation. It covers topics such as choosing a project, planning how to undertake the project, and literature searching and reviewing. Section 3 looks at how to manage your project as it is progressing. This section also includes ways of developing software systems if this is relevant to your own project. Section 4 covers completing and submitting your project – writing reports, giving presentations, viva voce examinations, etc. Section 5 looks into the future – for example, taking your project further after it is completed. Figure 1.5 depicts how this book is arranged. While sections are designed to be read in or- der as your project progresses, the chapters within each section can be read in the order that suits your needs. Note that Chapter 3 Choosing a project and writing a proposal should be read before Chapter 4 Project planning and risk management while Chapter 5 Literature searching and literature reviews can be read before, after, or even between both of these. Note It is advisable to read Section 10.2 in Chapter 10 before you proceed any further with your project. It describes what examiners will ultimately be looking for and evaluating within your project. Knowing what you need to aim for now is useful as it will guide you in the way you undertake your project and provide a focus for your effort. In addition, for those in need of instant help, Section 10.7 provides the top ten tips for successful projects based on other sections within the book. Figure 1.5 How this book is arranged