Programming in computing projects

10 Chapter 1 n Introduction

1.3.2 Degree requirements for projects

As this book is aimed at students on both taught degrees and research de- grees, it is worth spending a little time looking at the differences between the projects undertaken at these different levels. These are general guide- lines – your own department and university and country can offer specific guidance on what is and what is not appropriate for your own level of study. A project undertaken as part of a taught course bachelor’s or master’s degree does not need to make great breakthroughs in science. It might involve the development of some software, it could be an extended case study, or it might be research-based. However, generally speaking, you would not be expected to produce work at a level that could be published in an academic journal or presented at an international conference. This is not the case for research degrees, however. An MPhil should produce work that could be published perhaps with some reworking, whereas students pursuing a PhD will probably be expected to have published some of their work before completing the fi- nal thesis and, in some European countries, this is compulsory. At the research degree level, Chinneck 1999 contrasts master’s in this case, research-based postgraduate study with PhD-level work in the following way: ‘The contribution of knowledge of a Master’s thesis can be in the nature of an incremental improvement in an area of knowl- edge, or the application of known techniques in a new area. The PhD must be a sub- stantial and innovative contribution to knowledge’. The University of Derby 1999 notes the following abilities a student is expected to demonstrate at research degree level: n an ability to work independently with minimum supervision; n an ability to draw on existing knowledge and identify additional knowledge needed for your study; n an ability to critically evaluate advanced literature journal papers; n ‘an ability to conceive original ideas’; n an ability to plan your work effectively; n an ability to select and use appropriate hardware, software, tools, methods and techniques; n an ability to present your work effectively in written and oral forms; n an ability to critically evaluate your own work and justify all aspects of it; n an ability to identify areas of further research in your chosen area. Abilities marked with an asterisk are those that should be evident in taught degree projects as well. What sets research degree work apart is, mainly, an ability to Figure 1.4 Higher education 1.4 Stakeholders 11 ‘conceive original ideas’. This emphasises that for a research degree you are expected to make some kind of contribution to knowledge, not just repeat the work of others. This is discussed in more detail in Chapter 5. •

1.4 Stakeholders

1.4.1 Overview

Stakeholders are any individuals who are involved with your project. The most important person in your project is you. You are responsible for the overall completion of your pro- ject, meeting milestones, achieving objectives, satisfying users, satisfying the examiners, and so forth. Your project has many other stakeholders, and they all have significant roles to play. They include your supervisors, your users, your clients, your examiners and any software testersevaluators you might employ as part of your system evaluation if you have one in your project.

1.4.2 Your supervisor

Imagine your project as a large boulder. At the start of your project, this boulder is quite difficult to push stationary objects like to remain stationary. Getting a project started is always difficult. However, once the project is underway the boulder is rolling, it becomes much easier to push and gathers momentum as the project un- folds. Now, picture your supervisor alongside you. It is that person’s role to encourage you as you push this boulder your project along. Your supervisor will encourage you at the start as you try to get the boulder moving. They are also there to ensure you are pushing in the right direction. The supervisor will have an eye on the route you are taking and provide the occasional prod to keep you and the boulder on course. Your supervisor is also there to provide encouragement. If you feel yourself flagging at any stage, your supervisor should be there to support you and give you the help you need. In Chapter 3, we look at ways in which you might be able to choose your supervisor and, in Chapter 7, how to use your supervisor effectively as your project progresses. Sometimes particularly for research degrees, you may have more than one supervi- sor. This is especially common where the area of study straddles two fields of expertise. In addition, research degrees often have a supervisor someone who is responsible for the student overall and a director of studies or director of research. The director of research is sometimes a more senior member of academic staff who is interested in the strategic rather than week-to-week direction of the project. You may see your supervisor once every one or two weeks, but you would see your director of research only every six months or perhaps once a year.

1.4.3 Clients and users

If your project involves the development of a software system or involves action research or case studies, you will probably be working with a client andor a user. It is important to realise the distinction between these two stakeholders. A client is usually the project’s sponsor – the one who has requested the system be developed or study undertaken. The user, on the other hand, will be the one who eventually uses the system or the results of