ICT321 Architecture and System Integration Assessment Answer
Architecture and System Integration
Assessment and Submission Details
This task consists of a demo code package and a technical report for the integration plan. Submit your work as (1) a .zip file which contains the code files and (2) your report (a .docx file) to Blackboard Task 3. Please follow the submission instructions described in this document.
The task is an individual assignment and will be marked out of a total of 100 marks and forms 40% of the total assessment for the course. ALL assignments will be checked for plagiarism by SafeAssign system provided by Blackboard automatically.
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.
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. Assignment submission extensions will only be made using the official University guidelines.
Case Study: Victoria Health – Technology Strategy
As with all heath systems around the world, the Victorian State Government are confronting increasing cost pressures in delivering health services. As part of healthcare reform, the Victorian Department of Health and Human Services are developing a more person-centred system that focuses on keeping people healthy throughout their lives. Technology is at the centre of this new strategy to efficiently and cost effectively improve the health and wellbeing outcomes for its Victorian population.
The technology based strategic roadmap named Digitising health will enable clinical information to be shared safely, and in such a way as to meet individual needs and produce better and more cost-effective outcomes.
The 6 building blocks of Digitising Health are (Victoria Department of Health & Human Services 2016):
- Implementing digital clinical systems: reducing the reliance on paper-based systems when delivering clinical care.
- Shared clinical information: sharing relevant health and wellbeing information with those actively supporting the person.
- System integration and interoperability: providing a robust, secure and interoperable health network and systems infrastructure that provides equity of access for all individuals.
- Person-centred and place-based health and wellbeing: transitioning from provider-centred healthcare towards preventive health and personalised pathways centred on the individual and responsive to their needs, location and preferences.
- Preventive health and early intervention: focusing on prevention and early intervention to reduce the occurrence of chronic disease and start the journey to health and wellbeing early in life.
- Applied health research, education and analytics: using analytics and research to facilitate the proactive identification of consumer healthcare needs to better position the sector to meet future challenges.
After evaluating various platforms, Victoria Health finally decided to adopt a Service Oriented Architecture (SOA) for its future IT infrastructure. However, the managers from clinical services would like to gain a deeper understanding of:
- Computing and storage infrastructure design,
- Information integration,
- Application and Service Integration, and
- Technologies behind Application and Service Integration including a small specific demonstration of these technologies along with a brief explanation of the concepts and principles of how it works.
There are 2 parts to this Assignment:
Part 1 - Integration Demo (40%)
For this integration demo, 3 data sources with fictitious records are provided, including:
- “ clinics.csv ” contains the details about the clinical offices,
- “clinic_locations.xml” contains the location coordinates for each clinic,
- “clinic_services.csv” contains a list of clinic offices and the services they offer.
Please follow the instructions carefully. There are two major components in the demo system:
Data integration demo. In this demo, you are required to implement a Python script file with the name ‘data_integration.py’ to correctly merge records from different given data sources into one CSV output file named “clinic_service_locations.csv”.
The Python petl framework is recommended for this implementation. The output file “clinic_service_locations.csv” consists of the following fields (attributes):
- ClinicServiceID – a unique field identifying each record from clinic_services.csv
- Service – the service name from clinic_services.csv
- ClinicID – the ID for each clinic
- Suburb – the “Suburb” from clinics.csv
- Postcode – the “Postcode” from >clinics.csv
- Latitude – the “Lat” value from clinic_locations.xml
- Longitude – the “Lon” value from clinic_locations.xml
RESTful Web service demo. In this demo, you are required to implement a Python scrip with the name ‘web_service.py’ to provide two RESTful Web services:
- Get services by postcode. The server should accept a ‘getServices’ query from the client browser similar to “/getServices?postcode=xxxx”. After processing this request, the service should return a HTML document containing the list of available services for a given postcode, including the following fields (attributes): Service, Suburb.
- Get clinics by service name. The server should accept a ‘getClinics’ query from the client browser similar to “/getClinics?service=xxxx”. After processing this request, the service should return a HTML document containing the list of available clinics for a given service, including the following fields (attributes): ClinicID, Suburb, Latitude, Longitude.
The Python Bottle and petl frameworks are required for this implementation. Data for the service is from the output file “clinic_service_locations.csv” of the integration demo.
Very Important Note:
For ease of demonstration, your code must be self-contained. In addition to using Standards based HTML and Python, petl and Bottle are the only additional frameworks you should need. ALL required files must be provided with your submission and should not require any extra installation.
HINT: Most of the code for this assignment is demonstrated in the workshops.
Code Package Format
You are required to compress all your Python code, data files and all supporting packages/modules into one .zip file and upload it to Blackboard.
Part 2 – Integration Report (60%)
In addition to the above Demo code (40%) you are required to include a Report (60%) based on the above case study explaining the key concepts for:
- Application and Data Storage Infrastructure design,
- Information Management and Integration,
- Application and Service Integration, and
- The demo design and execution instructions.
Please use the following outline in your report:
|2||Application and Data |
Storage Infrastructure Design
|Discuss various cloud options and their suitability. Design a cloud infrastructure strategy.|
|3||Information Management and Integration||Discuss and design strategies to integrate the multiple data sources developed and used by different teams for various business units and stakeholders.|
|4||Application and Service Integration||There are many different types of applications and services coexisting in Victoria Health, including legacy applications, internal Web services, and external Web services. Some external services are provided by business partners and others are from public service providers such as Google Map and Google Search. Discuss and design service and application integration strategies.|
|5||Demo Design and Execution||Provide clear instructions on how to run your demo. Explain the key technologies used in your demo.|
Consult Rubric in Appendix A for more details on how this question will be marked.
Your report should be around 1000 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.