Case Study Report
which is of interest to you. While some topics are suggested in this document, you are encouraged to choose any other suitable topic (in which case, you need to seek your lecturer’s approval before starting the work). In your report, after giving a brief general overview, you need to narrow down to some specific issues (e.g., architecture, layers, protocols, devices, applications, etc.). Assessment for this task is based on the report content, organization and completeness, clarity, and creativity. A detailed marking criteria and guidelines are provided in the table on pages 2-3.
The Avoiding Plagiarism Course is a fundamental part of this assessment item. You are not able to submit your report until you review this course as well as attempt the associated Quiz with a satisfactory result (8/15). This course can be accessed by selecting “Avoiding Plagiarism Course” on the left hand menu of the vUWS site for this unit.
This work is to be carried out individually or as a group of two students. The written report is due in the week 11, make your submission through Turnitin link on vUWS by midnight Tuesday, the 2nd of May. This assessment item is worth 20% of the total marks in this unit. A penalty of 10% per day will apply for a late submission. Please note that submitted report will be analysed thorough Turnitin plagiarism detection software. In addition to submitting the assignment through a Turnitin link, you should submit a filled and signed assignment cover sheet (provided on the unit vUWS site under the ‘Assessment’ -> ‘Case Study Report’ folder) to the lecturer during the lecture time.
Please strictly follow these instructions when writing your case study report:
· Four to maximum five pages long (2000 to 2500 words – word count includes references)
- Submit the assignment only in Microsoft Word
You should also adhere to the following writing and formatting requirements:
- all page margins 1cm (top, bottom, left and right);
- font Times, size 11 points;
- single line spacing (double or single column);
- 6 points after paragraph spacing and 0 point before paragraph spacing;
- title (14 point, in the middle, bold );
- bellow the title include your name and SID;
- abstract (italic font, 100-200 words in length);
- introduction (approximately 1 page in length);
- body of the report (sections numbered sequentially with appropriate heading and sequentially numbered subsections, if needed);
- all tables and figures have appropriate captions, and references if not original work;
- conclusions (1-3 paragraphs in length);
- students are strongly encouraged to use figures when explaining more complex concepts;
- references that are used in the report and clearly referred to in the material of the report If you do not have experience with referencing please examine the example reports, referencing guides provided on vUWS and the library website at the link provided below.
- For this unit use only APA or Harvard UWS referencing The guides for these referencing styles are provided on vUWS and at: http://library.uws.edu.au/uws_library/guides/referencing- citation
- Optionally you can use the Endnote referencing software and Harvard UWS style that are available as a free download at: http://library.uws.edu.au/uws_library/guides/referencing-citation/endnote
- Two example reports are provided on vUWS, files: “Study Report Example PDF” under the ‘Assessments->Case Study Report -> Case Study Report Resources’ folder. Please download these examples and examine them carefully.
Plagiarism, poor or no referencing is the main reason for low marks or failure in this assessment item.
In order to facilitate selection of project topics, each student or group must provide the information asked for in the table at the page 4 of this document as soon as possible, but no later than the 8th of March. You will then be informed of the topic assigned to you through vUWS. Following that, you are encouraged to prepare your first progress report, which outlines your topic and how you
intend to carry out the work. It should be in the form of short (less than one page) synopsis of your case study report. You can also make an appointment, for a brief meeting with the lecturer or the course coordinator during the weeks six or seven, to discuss the progress report that you hand in before the meeting. The meeting can be scheduled during the consultation time. Your second progress report, which should be a written outline of your final report, is due at the start of another meeting with the lecturer or the unit coordinator during the weeks nine or ten. Please make another appointment for that meeting. This progress report should be a draft of your final report, 3-4 pages long. The progress reports are not compulsory, however the students are strongly encouraged to submit them and receive feedback from lecturer or unit coordinator. Students that do not provide progress reports often achieve very poor results in this assessment.
Marking criteria
The table below provides practical guidelines for each of the aspects of the report accompanied with list of common problems. The table also shows the exact distribution of the marks awarded for each of the marked aspects.
Task | Guidelines | Common Problems/ Issues | Marks |
Format | Precisely follow the writing and formatting
requirements provided on the page 1. |
If you did not follow the specified formatting
requirements you will lose one to two points for each requirement that you did not follow. Commons issues include: large page margins, too short introduction, inaccurate line spacing or/and font size and unnecessary empty space/s. |
15 |
Abstract | An abstract is a very short summary of the main
findings in your report. |
Abstract is unclear, too long or two short.
Abstract is presented as a short introduction instead of a very short summary of the main findings of your report. |
5 |
Introduction | Succinctly introduce your topic and specify the
structure and the content for the rest of your study report. Length – close to 1 page. |
Introduction is too short or confusing. You did
not specify the content for the rest of the report. Contains inaccurate information. |
10 |
Main body | Think carefully how you are going to organise
your main body – discuss this with your lecturer. Whenever copying text from the reference use double inverted commas (“ ” ) to clearly delineate between such reference and other content of your report. Only small part of the content should be referenced exactly “ as- is” instead references are critically compared, summarised, paraphrased and rephrased. In other words, the main body of your study report should demonstrate understanding of the topic covered by summarising and paraphrasing your references. Level of technical details and complexity does not have to be high but try to relate to material covered during lectures such |
The content is unclear – grammatical and
spelling mistakes makes the content hard or impossible to understand. Most or all of references are copied without an attempt of comparing, summarising and/or paraphrasing. The student copied reference text but did not reference it or/and enclosed it in “ ” . The subtopics appear disconnected. Does not relate to topics covered in this unit such as layers, protocols and devices. |
40 |
|
as: layers, architectures, devices and protocols.
If you do not understand some technical concepts that is OK, simply do not cover it. Copying technically complex definitions from a source without showing that you understand them is not desired, instead interpret materials that you read! |
|||
Conclusions | Explain why is your topic important?
Did you identify some major trends for the future? Describe any personal reflections on the learning experience/process that you went through to create this study report – for example you have found it very difficult or interesting or very complex? Length 1-3 paragraphs. |
Very brief or/and unspecific and/or does not
outline future trends, and/or does not reflect on research experience. |
10 |
References | Quality and quantity of references. Reference
sources in order of importance are: scientific journals, conference proceedings, books, magazines, internet sources. Follow precisely the referencing style requirements! |
Did not use any of the required scientific sources
such as journals and conference proceedings. No, or infrequent in-text references and/or an inaccurate referencing style. The student copied reference text but did not reference it or/and enclosed it in “ ” . The list of references does not adhere to the specified style or is not included at all. |
20 |
TOTAL
MARK |
100 |
Suggested Topics
- The Internet: Historical Viewpoint and Social Aspects
- Network Intrusion Detection Systems
- Networking: Pricing and Billing Mechanisms and Issues
- Security in Peer-to-peer networking
- Point-to-Point Protocol
- IPv6: Structure, Advantages, and Implementation Issues
- VPN: Implementation and QoS Issues
- High Speed Networks
- . Optical Fibre Networking: Technology and QoS Issues
- . Personal Communications
- . IP Networks and Multimedia Services (e.g. VoIP, IPTV, video streaming architecture and standards)
- . GRID, Distributed Computing Technologies and Services
- . 11 based wireless network
- . WiMAX based wireless networks
- . Long Term Evolution (4G) mobile phone systems and networks
- . Convergence in computer network technologies
- . Sensor networks and their implementation
- . Security in wireless networks
- . Wireless spectrum (frequency) allocation issues
- . Mobile phone – a device that integrates multiple wireless technologies
- . Digital Subscriber Line (DSL) technologies
- . The Internet and democracy
- . Network requirements in E-health
- . Facebook – a distributed application
- . Australian National Broadband Network
- . Radio-frequency identification (RFID) technology
- . Near field communication (NFC) technology
- . Torrent protocol
- . Future of the Internet
- . 11ac based Wi-Fi
- . Automatic diagnostic of network performance problems
- . Routing algorithms
- . Network simulation
- . Video conferencing (communication) over IP networks
- . Voice communication over IP networks (VoIP)
- . DNS protocol (development, security and future)
- . HTTP protocol (development, security and future)
- . Australian National Broadband Network
- . Radio-frequency identification (RFID) technology
- . Near field communication (NFC) technology
- . Automatic diagnostic of network performance problems
- . Network requirements for on-line gaming
- . Cloud computing