1. MSc projects intro1 MSc project allocation Unit PJ60P Dr Jim Briggs jim.briggs@port.ac.uk http://www.pums.cam.port.ac.uk/projects/

2. MSc projects intro2 Master’s Projects What is a Master’s Project? Why are they important? What is the process? What is the timescale? What are the main problems? Questions?

3. MSc projects intro3 What is a Master’s Project? The investigation and solution of a significant practical or theoretical problem within your area of study. –i.e. Software Engineering students must undertake a SE topic, e-Commerce student must undertake an e-Commerce topic, etc. The end result will be a Project report (and probably a software artefact). –It will be the report that is marked

4. MSc projects intro4 Devise a solution to a problem define objectives acquire information establish criteria plan determine process adopt methodologies analyse requirements use tools construct artefacts evaluate solutions report work

5. MSc projects intro5 The project is important largest single piece of work you do (60 credits) do something you are good at or enjoy employers will ask you about it at interview show off your skills and knowledge integrates material in other units essential for BCS membership you can’t get an MSc without one!

6. MSc projects intro6 Project schedule (PT) Allocation –Over summer –Last minute ones in October Doing –Start October Reporting – two deadlines –May –September

7. MSc projects intro7 Project schedule (FT) Allocation –April/May Doing –Agree specification by Friday 20 th May 2005 Reporting –September

8. MSc projects intro8 What is the process? Choose a topic (3 possibilities): –Select one from our Project Database –Find an external client with a problem –Devise your own * You will then be allocated a supervisor (* and a client if it is your own project)

9. MSc projects intro9 Project allocation process All projects need a client Proforma for ideas to be "approved" Ideas go into a database Students pick from the list Matchmaking “Own” ideas limited to student who owns it

10. MSc projects intro10 What is the process? You complete a Project Specification which must then be agreed by your client and supervisor Project is undertaken, supported by your supervisor and in conjunction with your client Project report submitted in September and an oral presentation given

11. MSc projects intro11 Project supervision Supervisor allocated by projects co-ordinator It is your project –Supervisor advises and guides –Supervisor does not tell you what to do Meet once per fortnight (FT) / month-ish (PT) –Set an agenda (report, review, set objectives, discuss alternatives) Don’t refuse to be supervised

12. MSc projects intro12 What is the process? The key source of information and the key tool for administering projects is the PUMS website –http://www.pums.cam.port.ac.uk/projects/ cohorts/msc2005/index.htmhttp://www.pums.cam.port.ac.uk/projects/ cohorts/msc2005/index.htm This will be updated in the next few weeks as the project allocation process begins

13. MSc projects intro13 What is the timescale? February – March: –Think about the kinds of things you might wish to do as a project March – May: –Identify/choose suitable project –Do some background research –Work on project skills, e.g. Information retrieval ‘Critical’ Literature reviews

14. MSc projects intro14 What is the timescale? End May – early September: –Work full-time on project September: –Project presentation –Project report hand-in

15. MSc projects intro15 What are the main problems? Time Time-management The summer vacation (students & supervisors!) Report writing (esp. for international students) Dealing with academic literature at Masters level

16. MSc projects intro16 Reporting on the project Presentation –Peer assessment Report –Marking scheme is public (projmark.htm) –Good artefact does not necessarily imply good report (and vice versa) –Marked by supervisor and moderator –Third marking if they cannot agree

17. MSc projects intro17 Good things and bad things +publishable standard +clear aims & objectives +perceptive analysis +interesting conclusions +evidence of understanding +good artefacts +challenging work +good presentation –errors of fact –vague aims –little or no analysis –trite conclusions –misinterpretations –poor artefacts –facile work –poor presentation