代做VT6000CEM、代写 c++，java 程序

项目预算：开发周期：发布时间：要求地区：

Faculty of Engineering, Environment and Computer Coventry University
VT6000CEM Individual Project Preparation &
VT6001CEM Individual Project
Study Guide for Students
2023-24
1

INTRODUCTION 3
1. INDIVIDUAL PROJECT -THE BASICS 4
1.1 What is it? 4
1.2 Project support sessions & milestones 4
1.3 Elements of a project 7
2. CHOOSING A SUITABLE PROJECT 8
2.1 Seven golden rules 7
3. PROJECT DELIVERABLES 12
3.1 Project proposal 12
3.2 Prototype 12
3.3 Progress milestones 13
3.4 Final product 13
3.5 Project report 13
4. THE SUPERVISOR'S ROLE 17
5. DOING THE PROJECT 18
6. ASSESSMENT 19
7. PLAGIARISM AND COLLUSION 20
8. CITATIONS AND REFERENCES 20
9. DEMONSTRATION 20
10. THE FINAL REPORT 21
11. SUBMIT YOUR REPORT 21
APPENDIX A: MODULE SPECIFICATIONS 22 APPENDIX B: PROPOSAL TEMPLATE AND MARKING CRITERIA 31 APPENDIX C : FINALREPORT MARKING CRITERIA & GRADING NOTES 37 APPENDIX D : UARC ETHICS APPROVAL LOW RISK PROJECTS 40 APPENDIX E : DECLARATION OF ORIGINALITY 48 APPENDIX F: RECORD OF SUPERVISOR MEETING 49
2

Introduction
The purpose of this study guide is to provide you with a set of guidelines to direct and support work from topic selection through to completion of an Information Technology or related Individual Project. This guide will cover the contents which include 10 credits module “Individual Project Preparation” in semester 1 and 20 credits module “Individual Project” in the following semesters and the consecutive workload of these two modules contributes around quarter of your study workload over the academic year. Hence, it will have a dominant influence on your final degree classification. Please take your own time to read the guide carefully.
Besides often being deterministic to the classification of your degree, the project is your opportunity to showcase your skills to potential employers. Many graduates of this programme shared their experience that at job interviews their interviewers would most probably ask them to elaborate the major achievements in their final year project. Therefore, the project is one of the best ways for you to:
i) Provide evidence of your ability to do a substantial piece of work in IT or related field.
ii) Demonstrate your self-management skills, initiative, and relevant technical skills.
Having a good project can often be a great advantage in an interview. Hence you should make every endeavour to perform well in your project as it can often make a fortune to your future job prospects.
3

1. Individual Project - The Basics 1.1 What is it?
The aim of this module is to allow students to conduct primary research (with secondary research support) in a topic area relevant to their degree title. Students are expected to design, implement and critically evaluate a functional or simulated system, object or concept and to acquire further knowledge of a specialist technical area. To this end, students will undertake a substantial project which will exercise the in-depth technical, problem-solving, creative and other skills required of a professional practitioner. Students will be required to ensure that their work conforms to appropriate codes of practice and meets the ethical requirements of the University. Successful completion of the project will require methodical planning, record keeping and self-management and effective communication, execution and delivery of an agreed artefact.
Support and guidance will be provided by a project supervisor who will be the primary point of contact for a student on this module. The topic of the individual project will be agreed between you, your supervisor and the co-marker. Suitable topics may stem from staff, you and occasionally other outside organisations. You can also refer to Appendix A for details of module descriptions.
1.2 Project Support Sessions & milestones
Project consultation sessions will be held throughout your study to support your project work. These sessions cover different aspects of the work you will beexpected to carry out, demonstrate and report on. You are strongly recommended to attend these sessions to ensure that you are aware of the details of the submission requirements stipulated in the scheduled milestones.
1.2.1 Full Time Students Project Schedule
26 Oct-9 Nov
Students and supervisors meet and work out a draft project specification (multipage)
Dates Milestones Details
4 Sep 2023
Individual Project Preparation
Semester 1 starts, and students are assigned supervisors
12 Oct
1) Project Summary (1 pageA4) - project preference/proposal - project statement
Propose project by supervisor or students – submit project summary electronically thru email or on e- platform (e.g. moodle)
4

23Nov -7 Dec
2) Project proposalPresentation
students present proposal with PowerPoints
14 Dec (by 6:00pm)
3) Submit Project Proposal and Plan (45%), Mini Literature Review (1,500 word limit) (45%), SHAPE Ethics Process (10%)
Individual Project preparation assessments (soft copy submitted electronically)
late Jan
20 Jan
15 Mar 19 Apr 3 May
4)
5)
7) 8)
9) 10)
Review and comments on specification (Marks given to each student for the proposal)
Interim project progress review
First draft of final report
Brief presentation on report draft & software/hardware deliverables Second draft of report
Brief presentation on report draft & software/hardware deliverables
Feedback and Formal Mark back by supervisor to student for project specification
Students arrange to meet supervisors to review & present the project progress
Students submit and present first draft of final report for supervisor’s comments & review
Students submit and present second draft of report for supervisor’s comments & review Students submit and present final draft of report for supervisor’s comments &review
11 Jan 2024
Implementation of Individual Project
Semester 2 starts (Tentative)
25 Jan – 8 Mar
6) Literature review, primary & secondary research results summary & analysis, design prototype and implementation
Students report the progress by drafting and presenting the first few chapters of the report for comments
11) Final draft of report
12) Brief presentation on report draft &
software/hardwaredeliverables
17 May
14) Demonstrations/oral presentations
Students give oral presentations and demonstrations of their projects
24 May
13) Project deliverablessubmission
Submit project outcome/deliverables (2 copies of associated documents)
17 June
15) Overall project marks
Overall project marks to be submitted and project reports to be returned by supervisors and second markers
1.2.2 Part Time Students Project Schedule
Dates Milestones Details
30 August 2023
Individual Project Preparation
Project brainstorming before discussion with supervisors
20 Sep
Meeting and Discussing details with Project Supervisor
Meet with different project supervisors to confirm the interest topics and confirm the project
5
supervision

20 Sept – 11 Oct
Feasibility Study
Find our the project and confirmation of project supervisors’ assignment
29 Oct
1) Project Summary (1 pageA4) - project preference/proposal - project statement
submit project summary electronically thru Moodle
1 Oct-16 Dec
Students and supervisors meet and work out a draft project specification (multipage)
Feedback and Formal Mark back by supervisor to student for project specification
Students arrange to meet supervisors to review & present the project progress
Students submit and present first draft of final report for supervisor’s comments &review
Students submit and present second draft of report for supervisor’s comments & review
Finalize the reports and system and keep communicate with project supervisor
17 Dec
2) Project proposalPresentation
students present proposals with PowerPoint
31 Dec (by mid-night)
3) Submit Project Proposal and Plan (45%), Mini Literature Review (1,500 word limit) (45%), SHAPE Ethics Process (10%)
Individual Project preparation assessments (soft copy submitted electronically)
late Jan
25 Jan
31 Mar 29 Apr
19 May - 22 Jul
4) Review and comments on specification (Marks given to each student for the proposal)
5) Interim project progress review
9) First draft of the final report
10) Brief presentation on report draft &
software/hardwaredeliverables 11) Second draft of the report
12) Brief presentation on report draft & software/hardware deliverables
2 Jan 2023
Implementation of Individual Project
Semester 2 starts
Jan – early Mar
6) Literature review, primary & secondary research results summary & analysis, design prototype and implementation
Students report the progress by drafting and presenting the first few chapters of the report for comments
18 May
13) Final draft of the report
14) Progress presentation on report draft
60-70% completed project demonstration& software/hardware deliverables
15) Progress report
Students submit and present final draft of report for supervisor’s comments & review
Progress report demonstration
22-26 July
16) Demonstrations/oral presentations
Students give oral presentations and demonstrations of their projects
17 Aug
13) Project deliverablessubmission
Submit project outcome/deliverables
6

17 Sep
15) Overall project marks
Overall project marks to be submitted and project reports to be returned by supervisors and second markers
Remarks: The schedule will be updated according to the learning pace and environment. Please refer to the updated FT & PT schedule provided by the programme coordinator.
1.3 Elements of a Project report
Students are required to write a thesis which tells people about the research you have done. This can be structured in whatever sensible way you prefer, but it needs to have the following parts:
• An introduction. What's your hypothesis? Why is your work interesting? What are your trying to achieve?
• A literature survey. What have other people done? What new knowledge will your work add? What is the current state of the art missing and how are you going to address that?
• Your methodology. How did you go about validating / disproving your hypothesis? Why is your method sound? Why should anyone trust your results?
• Your results. What did you do? How?
• Your analysis of your results. What do your results mean? Why are they interesting?
Did you validate your hypothesis or disprove it?
• A reflection on the management of your project and the social, legal or ethical issues that you needed to consider. Your first supervisor may have a very good idea of how well you tackled your project - however second supervisors may not have any idea. For this reason, you need to include an account of the conduct of the project. What problems you encountered, how you overcame them, how diligently you worked, how you sought advice.
• Conclusions. What did your work contribute and how could it be continued by others?
7

2. Choosing a Suitable Project
A critical part of the success or failure of any project is the initial choice of what to work on. This is a surprisingly difficult part of any project, in some ways the most difficult part, and it's something that we see students struggle with year on year.
2.1 Seven golden rules:
When deciding on the project topic you wish to work on the first key to success i s :
Know yourself - Do something you are interested in
A final year project is a six month, single person project and in most Universities in the UK. Students will have to study several other modules concurrently. This is a long time to be working on a single piece of coursework, so it is important to choose a project which will hold your attention for that length of time. Moreover, you will be working on other things at the same time, so ideally you need to choose a project that is compelling enough that you want to work on it, in preference to doing other things.
Secondly:
Choose a small but difficult project
A "difficult" project is likely to be looked upon favourably because it will be a bigger step away from what you have already been taught, you will need to be reading more academic literature, you will be showing more independent learning, and so on. These are some of the most important factors in getting a good grade, and far outweigh factors such as finishing every part of your practical work.
8

Thirdly:
Have a research question
A project proposal should pose a problem, not a solution to a problem. Ideally, it is best to phrase this as a research question, such as the following:
• Is algorithm X more efficient than algorithm Y?
• Is it possible to implement product Z on the cloud?
• Can feature L be added to programming language P?
• Can theorem T be proven?
• Can algorithm Z be adapted to be used in conditions D?
... and so on. There are several advantages to this. One is that this is a standard form of writing in academia, and your project will be marked against academic criteria. Secondly, if the aim of your project is to answer a question then you leave the issue of how to answer that question reasonably open ended. It may be that you have a very clear idea, at the start of the project, what you are going to do. That's fine, but as you progress through the project you may well find literature that enlightens your views on how your question can be answered. Thirdly, your answer to the question may not be what you expect. That's fine, it's OK to find out that actually, your algorithm isn't as efficient as you thought, or the theorem cannot be proved, so long as you give solid, convincing evidence for your answer.
Fourthly:
Do something practical
If you are working in the sciences, it really is important that you do something practical as part of your work. For these purposes "practical" can mean experimental work or mathematical work - it's OK to prove a theorem, for example, as the main part of the "practical" content of your work. What you should avoid though, is vague, nebulous, ‘thought-pieces’, which have no clear results and cannot be evaluated. Avoid anything with a title like "an investigation into X" or "a dissertation on Y". These sorts of writing are well accepted in the humanities (BA courses), but for a scientific (BSc Courses) piece of work
9

you need to propose a question and find some answer to it. Equally, a literature review is not really a project in itself; it needs some research question and evaluation with it to form a complete project.
Fifthly:
Focus on evaluation from the start
Evaluating your work will likely be the last practical work you complete before finishing your project writing. However, you should know from the start of your project how you plan to do this. As with unit-testing, or usability testing, it is best to have designed you evaluation in as much detail as possible before you start you practical work. That way, you know that what you are aiming for is something that can be evaluated in the manner in which you have planned. Remember, the purpose here is to determine whether your project has answered your original research question.
In general, your evaluation will fall into one of the following categories:
• Performance evaluation: either testing the speed, memory footprint, scalability, load- balancing, or other aspect of the performance of a program or system. This is often the easiest form of evaluation -- it can be performed by a program and so automated, the results can be analysed and presented using a statistics and you will not be reliant on users. Work in programming languages, networking, operating systems, databases, and hardware tend to suit this sort of evaluation well.
• User-acceptance testing and usability: if your project involves creating a product for end-users to test, especially if you have an industrial client, then it is essential that you perform some sort of user acceptance testing. Good options for this are the talk-aloud protocol or semi-structured interviews. NEVER, EVER, EVER think that a "heuristic" evaluation is sufficient. Heuristic methods only catch basic errors; they tell you nothing about how your users will actually experience your product.
• Formal or semi-formal methods: such as proving a theorem, using a model checker (such as SPIN), using a formal method such as B or Z to show that your work is free of particular types of errors.
Sixthly:
Take (academic) advantage of your supervisor
10

Every student will have at least one supervisor, who will usually be actively involved in research, consultancy or something similar. This sort of work can provide a wealth of good ideas for projects and has several advantages. Firstly, your supervisor will propose projects that have the right scope and difficulty for your degree course. Secondly, if your supervisor has an interest in what you are doing, they will have a vested interest in seeing you succeed and of course will have a lot of relevant expertise with which they can advise you. Lastly, it is likely that your work will be used by other members of a research group which will give you access to feedback on what you have done.
Seventhly:
Be flexible (within reason)
Remember that a project is a marathon, not a sprint. It may well be that you get part way along the journey and find out that what you had first set out to do is actually impossible, or impossible within the scope of the project. Or it may be that you find some other way of answering your research question, or you uncover some literature which shows that the question can actually be answered very simply. In this case, you should speak with your supervisor and find a way to reword or even completely change your original research question. This is quite a reasonable thing to do and happens often in "real" research projects, so you should not be worried about it. Your final project does not have to match the original proposal exactly, but you should be able to explain why the changes you made were necessary.
Summary
• DO choose a project that will hold your interest for the duration of the project.
• DO NOT choose a project that is the same size or scope as a coursework, or
something that is very similar to work you have been set in a module.
• DO propose a "difficult" problem -- it is easier to pass a challenging project than an
"easy" one!
• DO propose a research question, and an idea for solving it.
• DO propose a project with some sort of practical or mathematical component, DO NOT
set out to write a commentary on a topic.
• DO have a very clear plan for how you will evaluate your project. This should clearly
state how you will determine whether or not you have answered your research
question.
• DO NOT evaluate an end-user product with only heuristic methods. 11

• DO test end-user products with real users.
• DO take advantage of the expertise of your project supervisor and their research
interests.
• DO be flexible if you find that your original research question cannot be answered, or if
you find that a more "interesting" research question emerges during your project.
3. Project Deliverables
3.1 Project Proposal
The detailed project proposal aims to help you refine your general research question to a well- focused and achievable piece of practical research work.
The first section: “Defining your research project” focuses on your research question and the plan for conducting your primary method. The second section: “Abstract and Literature Review” is to help you identify current academic sources of literature that are highly relevant to your project and to help you get a head-start in producing your literature review.
Your detailed project proposal will be graded in the second semester. However, it is highly recommended that you submit it as soon as possible to obtain detailed supervisor feedback on your project.
The detailed proposal (Submitted by 31 December 2023) has no suggested word length – although 2000 words would be in order.
3.2 Prototype
The Prototype is intended to be a rough outline of your proposed final product. It is not expected to be complete or perfect.
However, it should demonstrate that you are making satisfactory progress towards your final project aim and final product.
Prototypes will typically be software, but for some projects may take other forms.
You will be required to demonstrate your prototype to your supervisor and second marker as part of the assessment for the module. During the demonstration, you will also be expected to discuss the motivation for the main features of the prototype and answer questions relating to the proposed design of your final product.
12

3.3 Progress Milestones
Progress milestones should be set and presented along with your Project Proposal.
As with any project, you may need to review your progress and adapt your plans to meet your final deadline.
Your progress concerning the milestones you have set will be assessed during meetings with your supervisor and form a continual assessment of your project management skills.
You must demonstrate to your supervisor that you are making satisfactory progress and can complete the project in the remaining time.
3.4 Final Product
Your Final Product will be demonstrated during the final meeting with your supervisor and second marker.
Ideally, you will be able to provide a fully completed product, however, the nature of a project such as the one you are undertaking is unpredictable. If your product is incomplete, it should be clear which parts are finished, which are still at a prototype stage and which are yet to be undertaken. Again, during the demonstration, you will be expected to discuss the development and testing of the product and answer questions relating to the project.
3.5 Individual Project Report (Not less than 10,000 words)
The appropriate structure of the Report varies according to the scientific, engineering, or business research method you have used, the features you have chosen to emphasise, and the degree title you are pursuing. It is your responsibility to ensure that you are clear about where your project's contribution (‘novel contribution to knowledge’) lies and that all work is explained clearly and in the correct format.
The following Report structure should therefore be seen as a guide only. It is probably the case that few Reports will stick to it rigidly. It is your responsibility to consult with your supervisor and adapt to suit your project. Types of problem-solving project other than software development projects are likely to need a different structure.
13

1. Title page (Mandatory), including title, author, student ID, degree title, name of Supervisor, name of institution ('Coventry University, Faulty of Engineering, Environment and Computing, Department of Computing, Mathematics and Data Science’) and Date of Submission.
2. Statement of Originality. (Mandatory) – This is a one-page, signed statement. Pro- forma will be provided. It is your signed statement that you have not plagiarised the work in part or full. JPG
3. Preamble, including (a) Table of Contents; (b) Abstract (suggested length: half a page); (c) Acknowledgements.
4. Abstract should be a succinct and self-standing summary of the project's basis, context and achievements. Minimally an abstract does three things: (1) It states the problem that you set out to solve, (2) It describes your solution and method, and (3) It states a conclusion about the success of the solution. Be straightforward and factual and avoid vague statements, confusing details and "hype". Do not be tempted to use acronyms or jargon to keep within the half-page limit. Consider that search engines, librarians and non-computer scientists wishing to classify your Report rely on the abstract. You may, if you wish, provide a short list of keywords (2-6 is reasonable) at the end of the abstract.
5. Introduction. In this section, you should describe the problem you set out to solve with the project. An introduction might, for example, begin by stating, "The work described in this report aimed to provide a software tool with which people can arrange meetings." Avoid starting a Report with an irrelevant history of information technology. For example, the following would not be a good introductory sentence, "Since Bill Gates launched Outlook, people have been using technology to arrange meetings."
Explain whatever background the reader will need to understand the problem. The background might refer to previous work in the academic literature that provides evidence that the problem is a real and significant problem worth solving. The background may identify a community, organisation or set of users that will benefit from your research. Include a clear and detailed statement of the project aims and provide an overview of the structure of the solution.
CRITICAL! Use the introduction to define any terms or jargon you will use throughout the rest of the report. Why? Because people define and understand terms differently
14

from one another. Your definition of ‘cloud computing’ may differ from your supervisor’s definition of ‘cloud computing’. By stating your definition clearly, you can avoid misunderstandings about your work.
Conventionally, the last part of the introduction outlines the remainder of the Report, explaining what comes in each section – keep this brief.
6. Literature Review (Mandatory). Please read Chapter 4 of ‘Awesome Projects’. A lecture will be given on literature reviews.
7. Method: This chapter should describe what you did to answer your research question (or to support your thesis, if you think of it that way) and how you went about it (essentially your research design). You should describe your research design sufficiently so that another researcher can recreate your work to check your results.
8. Evaluation / Results: In this chapter, you should evaluate what you have done and say what answer (to your research question) you have arrived at. It may be that you describe some experiments in your method, and this section records your results and analysis of those results. This is an important section -- most students gain or lose marks in their literature review or evaluation. The key to producing a convincing evaluation is to plan what information or results you will need to write this section very early in the project.
9. Discussion. Here you will summarise your achievements and also the deficiencies of your project. You can also say what you would or could have done, if you had had more time or if things had worked out differently. It is important to be completely honest about the deficiencies and inadequacies of your work, such as they are. Part of your aim is to demonstrate your ability to recognise problems that remain.
10. A reflection on the management of your project and the social, legal or ethical issues that you needed to consider, including your response to feedback from your presentation (Mandatory). Your first supervisor may have a very good idea of how well you tackled your project - however second supervisors may not have any idea. For this reason, you need to include an account of the conduct of the project. What problems you encountered, how you overcame them, how diligently you worked, how you sought advice, how you responded to feedback. This chapter will be evidence
15

driven – which is why you need to keep a log or diary of your project, maybe a project management timeline with milestones, keep evidence of each supervision meeting (signed off by your supervisor), Keep notes of supervisor feedback to your presentation and reflect on them in this chapter.
11. Conclusion. Give a brief statement of how the solution that you have provided addresses the problem stated in the introduction. Provide an evaluative statement based on the results. You should not introduce new material.
12. References For your Final Year project, you must cite and reference work to which you owe an intellectual debt. It is required that you cite and reference work that provides supporting evidence. You must cite and reference work so that the reader can find the sources that have been quoted. (Remember that we use the APA referencing system of ‘in-text citations’ and a list of references at the back of the report. There will be a lecture on this)
13. Appendices. (More on these later)
A List of elements suggest to be included with your report
• Statement of Originality
• Certificate of Ethical Approval
• Meeting records (appendix)
Feedback notes from your presentation (appendix)
Reference:
https://www.coventry.ac.uk/globalassets/media/global/writing-a-report.pdf
16

4. The Supervisor's Role
You will be assigned a supervisor who will meet regularly with you and other students as a group to help plan and manage the work. It is your responsibility to research material and techniques appropriate to the subject of the project. The responsibilities of the supervisor are primarily to provide guidance on the management of the project, the standard of work required, what can realistically be achieved in the available time and to give feedback on work done (including the writing of the report).
Wherever possible you will be assigned a supervisor with an interest in the project topic but this cannot be guaranteed.
In the initial stages of the project, you and your supervisor will discuss objectives that must be achieved and appropriate scope for the project. The relative importance of the various aspects of the project will be defined by negotiation between the two of you. Projects develop unpredictably, the initial objectives are only intended as a guide to the level expected and details may change. One learning objective is concerned with you coming to terms with creatively and proactively managing the scope of the project.
You and your supervisor will meet regularly throughout the duration of the project. Your progress will be reviewed and assessed in these sessions and will include milestone assessment, where simple milestone tasks must have been completed, i.e. prioritised requirements or research questions. You should stay in contact with and make use of your peers for support, guidance, and review.
As well as providing guidance, your supervisor will mark your work with the support of a second marker. You will be expected to attend demonstration sessions as timetabled or make alternative arrangements to show and explain your work to your assessors.
The Project Report should be submitted for marking by your supervisor and co-marker, accompanied by supporting material in the form of software and documentation; hardware design and build; and any other relevant documentation and materials.
17

5. Doing the Project
I. Plan and get start as early as possible.
II. Attend the project consultation Sessions regularly and record the progress and
discussion with supervisor (Appendix F)
III. Think of a project topic and discuss it with your supervisor.
IV. Prepare a proposal and discuss the ethical issues with your supervisor (refer to Appendix B & D).
V. Conduct a literature survey and study similar systems related to your project/research focus. Submit your proposal and literature review and complete the SHAPE Ethical approval checklist before the end of semester 1(refer to Appendix B & D).
VI. Follow your project plan to gather user specifications, design and implement your systems and evaluate the outcomes.
VII. Start drafting your report early; that way, you will be more relaxed about how much you write.
VIII. Let your supervisor see drafts early on. If you need help with your writing style and appropriateness of technical content, you need to know about it when you have written the first few chapters, not when you have written the whole report.
IX.