Task 2
Consists of a demo code package and a technical report for the integration plan. Submit your work as a .zip file, which contains the code files (another .zip file) and your report (a .docx file), to Blackboard Task 2. Please follow the submission instructions described in this document.
The assignment will be marked out of a total of 100 marks and forms 30% of the total assessment for the course. ALLassignments will be checked for plagiarism by SafeAssign system provided by Blackboard automatically.
Refer to your Course Outline or the Course Web Site for a copy of the “Student Misconduct, Plagiarism and Collusion” guidelines.
Assignment submission extensions will only be made using the official Faculty of Arts, Business and Law Guidelines.
Requests for an extension to an assignment MUST be made to the course coordinator prior to the date of submission and requests made on the day of submission or after the submission date will only be considered in exceptional circumstances.
Case Study: Industrial Internet for GE
After evaluating various platforms, GE finally decided to adopt a Service Oriented Architecture (SOA) for its future IT infrastructure. GE was impressed with your Template based, Reference Architecture approach set out in your Task 1 ‘Industrial Internet’ Report and has accepted your recommendations regarding:
- Computing and storage infrastructure design,
- Application / service integration, and
- Information integration.
However GE Executives would like to gain a deeper understanding of the Technologies behind your recommendation and have asked for a small specific demonstration of these technologies along with a brief explanation of the concepts and principles of how it works.
Because GE have medical clinic related applications in many clinics around Australia, GE Executives would like a demonstration of keeping track of demographic information for each medical clinic location. The demo enables GE employees to browser search the locations of medical clinics in Google Maps using a postcode and retrieve an example of current demographic information along with the map. There are three major components in the demo system:
- Data integration demo. In this demo, there are two data source files: “clinics.csv” contains the information about fictional clinics, and “locations.xml” contains the information about the location coordinates for each clinic. A Python scrip file with the name “py” should be implemented to read these two data files. Using the Python petl framework you are required to:
- clean the data in the “clinics.csv”. This involves using python and Regex to standardise email addresses so they are usable as a html link, and
- output the merged and cleaned data into a CSV file with the nam
- RESTful Web service server demo. In this demo, you are required to build a RESTful Web service which supports a ‘getlocation’ query from the client browser similar to
- Mashup demo. In this demo, you are required to build a mashup application which accepts a postcode as the input. If a medical clinic in that suburb can be found, then its location is displayed in Google Map. Otherwise, the default clinic (with postcode 2000) is displayed. A HTML file “html” should be implemented. In this file, a text field is provided at the page top to accept user’s input of postcode. In addition, a Submit button will trigger the “getlocation” Web Service to retrieve its corresponding latitude and longitude, and highlight and centre the location in Google map
In addition to highlighting the positon on the map, a user is able to click on the marker bubble and see an information window containing:
- suburb specific demographic information or a link to that information, and
- a link to the email address for that clinic. After clicking on the email link, the user’s email application must pop up and automatically insert the subject line
“Clinic Enquiry”.
Important Note: For ease of demonstration to GE executives, your code must be self-contained. In addition to using Standards based HTML and Python, petl, Bottle and parser are the only additional frameworks you should need. If you use others they must be provided and not require installation.
In addition to the above Demo code (70%) you are required to include a Report (30%) explaining the key concepts around the demo design and implementation. Moreover, you need to explain how to run your demo/code.
Please use the following outline in your report:
- Introduction
- Data merging and cleaning
- RESTful Web services
- Mashups
- Demo running instructions
- Conclusion
The detailed distribution of marks can be found at the end of this file.
The following guidelines will be used in marking each part of the assignment:
100% | 90% | 75% | 65% | 50% | 25% | 0 | |
Outstanding: | High | Distinction: | Credit: | Pass: | Fail: | Not | |
Distinction: | Submitted: | ||||||
An outstanding | An excellent | More than | Competently | Satisfactorily | Did not | No attempt | |
attempt – well | piece of work | competently | meets the | meets the | sufficiently | made or | |
formatted and | that meets all | meets the | criteria as | criteria. | meet the | different from | |
professionally | the specified | criteria | specified with | criteria to | what is | ||
presented | criteria with | specified with | few minor | pass. | acceptable | ||
piece of work. | very minor | only minor | mistakes or | ||||
omissions or | mistakes or | omissions. | |||||
mistakes | omissions. |
Code Package Format
The code implementation should be with Python 3 and PyCharm.
Your .zip code package should include Python source files, data files, and all supporting packages/modules. Make sure your demo codes are runnable in PyCharm after being unzipped.
Report Format
Your report should be no less than 800 words and it would be best to be no longer than 1500 words.
The report MUST be formatted using the following guidelines:
- Paragraph text – 12 point Calibri single line spacing
- Headings – Arial in an appropriate type size
- Margins – 2.5cm on all margins
- Header – Report title
- Footer – page number (including the word “Page”)
- Page numbering – roman numerals (i, ii, iii, iv) up to and including the Table of Contents, restart numbering using conventional numerals (1, 2, 3, 4) from the first page after the Table of Contents.
- Title Page – Must not contain headers or footers. Include your name as the report’s author.
- The report is to be created as a single Microsoft Word document (version 2007, 2010, 2013 or Office 365). No other format is acceptable and doing so will result in the deduction of marks.
- No reference is required.
Submission
Submit your work as a zip file to Blackboard Task 2 by the due date of 11:59pm Friday, Week 12. Inside the zip file, a zip package of code and a Word file of report should be included.
The assignment will be assessed according to the marking sheet. Late submission will be penalised according to the policy in the course outline. Please note Saturday and Sunday are included in the count of days late.
Assignment Return and Release of Grades
Assignment grades will be available on the course website in two weeks after the submission.
An electronic assignment marking sheet will be available at this time.
Where an assignment is undergoing investigation for alleged plagiarism or collusion the grade for the assignment and the assignment will be withheld until the investigation has concluded.
Assignment Guidelines
This assignment will take a number of weeks to complete and will require a good understanding of application and information integration technologies for successful completion. It is imperative that students take heed of the following points in relation to doing this assignment:
- Ensure that you clearly understand the requirements for the assignment – what has to be done and what are the deliverables.
- If you do not understand any of the assignment requirements – Please ASK the course coordinator or your tutor.
- Each time you work on any aspect of the assignment reread the assignment requirements to ensure that what is required is clearly understood
Appendix A
Marking Sheet for ATMC ICT705 2017.S3 Assignment 2
Student name:
Student ID:
Report (30%):
Items | Maximum | Marks | |||||
Marks | Obtained | ||||||
Report formatting (font, header and footer, table of content, | 3 | ||||||
numbering, correct spelling, grammar) | |||||||
Introduction | 2 | ||||||
Data merging and cleaning | 7 | ||||||
RESTful Web services | 7 | ||||||
Mashups | 6 | ||||||
Demo running instructions | 3 | ||||||
Conclusion | 2 | ||||||
Total = | 30 | 0.0 | |||||
Code implementation (70%):
Items | Maximum | Marks | ||||||
Marks | Obtained | |||||||
1.a | - data_merger.py – cleaning | 10 | ||||||
1.b | - data_merger.py – merging | 10 | ||||||
2.a | - clinic_locator.py – Web service | 10 | ||||||
2.b | - clinic_locator.py – input error handling | 10 | ||||||
3.a | - clinic_map.html – form layout | 10 | ||||||
3.b | - clinic_map.html – locator | |||||||
10 | ||||||||
3.c - clinic_map.html – information window – email link | 5 | |||||||
3.d | - clinic_map.html – information window – demographics | 5 | ||||||
Total = | 70 | 0.0 | ||||||
No comments:
Post a Comment