IMAT 5314 MSc Project Roadmap

Text Box: RESEARCH AND DEVELOPMENT

IMAT 5314 MSc Project Roadmap

  1. Choose Project and Find Supervisor

When: Before end of taught modules

You need to choose or devise your own project, and get agreement from your Supervisor that it’s suitable. You will be allocated a supervisor by the MSc Project Module Coordinator but it’s better if you find your own. If possible, do this before the end of your taught modules.

See Project Guide Section 1 and Section 4.2.

  • Elaborate Project Idea

When: As soon as topic chosen

You need to work out what requirements your system will meet and/or what your research work will involve doing. Work on this as soon as your taught modules are complete.

  • Identify Research Questions

When: As soon as topic chosen, revise and elaborate up to deadline

Your project needs to be scholarly work that addresses research questions. You need to come up with a set of questions you can use your project work to answer. See the document Formulating Research Questions for Development Projects for guidance on how to do this.

  • Write Terms of Reference

When: As soon as topic agreed, as quickly as possible

You need to produce a Terms of Reference document, including a time plan. You MUST complete an Ethical Review Form. Work on this as soon as you’re done with your taught modules. The aim of the ToR is to achieve a clear vision of a viable project, including research questions and product objectives. See Project Guide Section 5 on how to write a ToR and complete the Ethical Review Form.

  • Literature Survey

When: After topic agreed, until deadline

All projects need to be grounded in the context of what’s needed and why, and the technological state of the art. An element of research and fact finding is essential.

  • Research and Development

When: After first draft of ToR

Start doing substantial work on your project as soon as you have a first draft of the ToR.

  • Write Dissertation

When: Start assembling pieces early

Try to write pieces early, especially describing papers you’ve read so you don’t need to read them again, and detailing technical issues while they’re fresh in your mind. Remember that taking your research questions seriously and writing a good critical review is crucial. See Project Guide Section 7 for guidance on writing your dissertation, avoiding plagiarism, coming up with a sensible structure,and doing referencing properly.

  • Submit

When: Deadline Day (normally Friday 6 September 2019)

You need to submit an electronic copy of your dissertation to Turnitin on or before your deadline. See Project Guide Section 2 (deadlines) and Section 3 (what to submit). Your supervisors may appreciate a paper copy.

  • Viva

When: After deadline, as agreed with Supervisor and Second Reader

A viva voce examination comprising a presentation and/or demo and questions is mandatory (see Project Guide Section 8). It normally takes about 50 minutes. You arrange a convenient time with your Supervisor and Second Reader.

Critical Analysis of a Chief Information Officer’s (CIO’s) Strategy

Faculty of Computing, Engineering and Media – Resit Coursework Specification 2018/19

Module name: Management of Information Systems
Module code: IMAT5206
Title of the Assignment: Critical Analysis of a Chief Information Officer’s (CIO’s) Strategy
This coursework item is: (delete as appropriate) Summative  
This summative coursework will be marked anonymously Yes  
The learning outcomes that are assessed by this coursework are: Have a comprehensive understanding of the purpose of information systems within organisations and IS/IT departments in order to analyse given scenarios and propose evaluated solutions to given problems. Critically analyse concepts within information systems selection, evaluation and deployment. Review and assess information sources within IT management literature, both trade and academic.
This coursework is:   Individual
If other or mixed … explain here:  
This coursework constitutes 40% of the overall module mark.
Date Set: 05 Oct 2018 (week 1)
Date & Time Due: 06 Sep 2019 (week 49)
The ‘normal’ coursework return date for this work is:   Note that you should normally receive feedback on your coursework by no later than 20 University working days after the formal hand-in date, provided that you have met the submission deadline.   04 Oct 2019 (week 01)
When completed you are required to submit your coursework via: Blackboard and Turnitin
Late submission of coursework policy: Late submissions will be processed in accordance with current University regulations which state: the time period during which a student may submit a piece of work late without authorisation and have the work capped at 40% [50% at PG level] if passed is 14 calendar days. Work submitted unauthorised more than 14 calendar days after the original submission date will receive a mark of 0%. These regulations apply to a student’s first attempt at coursework. Work submitted late without authorisation which constitutes reassessment of a previously failed piece of coursework will always receive a mark of 0%.”
Academic Offences and Bad Academic Practices: These include plagiarism, cheating, collusion, copying work and reuse of your own work, poor referencing or the passing off of somebody else’s ideas as your own. If you are in any doubt about what constitutes an academic offence or bad academic practice you must check with your tutor. Further information and details of how DSU can support you, if needed, is available at: http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/academic-offences.aspx and http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/bad-academic-practice.aspx                
Tasks to be undertaken: Select a Chief Information Officer (CIO) interview from Computer Weekly (see examples at:Top 10 CIO interviews of 2017Top 10 CIO interviews of 2016Top 10 CIO interviews of 2015Top 10 CIO interviews of 2014   Read carefully and reflectively and identify themes and viewsInvestigate and briefly overview company’s recent IT history prior to the interview.For each theme: Explain the theme, clarify and define any terms; Expand with reference to stories and tasks; Set in the context of recent IT history of company;Critically appraise the CIO’s view, strategy and approach to the stated theme. What do you think about what is said? What are the positive and negative points about the theme? From investigating the background of the management of information systems in the company identify any issues and problems, which you think the CIO should be addressing, i.e., What is not said? The CIO will wish to be seen in a positive light and there may be issues that are not mentioned.Give suggestions for future strategy and direction that you think the CIO should pursue.   Notes: Use the most recent CIO interviews e.g. 2016, 2017. If using an older interview, reflect briefly in the future strategy section on progress made since the interview.You must demonstrate critical appraisal of the CIO’s ideas and beliefs. You must address themes with reference to stories and sets presented in the module.
Deliverables to be submitted for assessment: The essay should be between 1500 and 2500 words. It should be sectioned: Introduction to IT at the company. Theme sections. Missing Issues. Future direction.
How the work will be marked: See marking grid below.  
Module leader/tutor name: Prof. Laurence Brooks
Contact details: laurence.brooks@dmu.ac.uk


Marking Criteria

Criteria 0 to 39% 40 to 49% 50 to 59% 60 to 69% > 70%
Analysis of CIO interview and identification of themes. Cursory, no careful reading of interview Basic understanding Overall good. Good set of themes. Very good. Wide range of themes. Excellent. Comprehensive and complete set of themes.
Explanation of concepts and definition of terms. None. Terms clearly not understood. Some basic definitions which do not demonstrate clear understanding. Good. Most terms defined. Very good. All terms defined. Clear understanding expressed. Excellent. Give alternative definitions. Shows deep understanding and reflection.
Critical appraisal and analysis. Absent Mostly a descriptive report. Good. Critical statements provided, but some are not backed up and feel like anecdotal opinion. Very good. Well argued, insightful. Excellent. Set in context, insightful. Giving range of arguments, referring to material outside case study,.
Reference to stories and sets None Mentions some titles and ideas, but not clear if relevant stories and sets have been read. Good, Correct references to stories and sets which add to understanding of themes, Very good. Comprehensively integrating stories and sets into the themes. Excellent. Reflection on stories and sets used to enhance critical analysis of themes and provide creative insights.
Recommendations Limited One or two obvious recommendations, a little irrelevant. Good, solid, common sense recommendations, but not really inspiring. Recommendations show understanding of the themes and should be addressed by the CIO. Recommendations are insightful, creative and get to the heart of the critical themes and issues. They bring novel vision.
Quality of writing Badly expressed, at points incoherent, leaving the reader in the dark. Superficial, a pedestrian. Sometimes difficult to understand what is meant. Good. Clear, practitioner relevant language, readable, analysis of themes reads well. Clear layout. Very good. Writing is clear and engagement. Well presented, easy and attractive to read. Excellent Demonstrates not only mastery of the themes but an ability to communicate enthusiasm and leaves the reader both inspired and guided.