MIS603 Microservices Architecture Assessment 2

Subject Code and Title 	MIS603 Microservices Architecture 
Assessment 	Assessment 2 Written Assessment   
Individual/Group 	Individual 
Length 2500 words with 10% leeway on either side 
Laureate International Universities

Learning Outcomes

a) Synthesise research to determine understanding of micro-services and how they contribute to new business processes

b) Collaboratively recommend strategies for transitioning to contemporary computer architectures that maintain efficiencies and address changing business requirements c) Negotiate change management and highlight benefits to address complex business needs.

d) Reflect on moral and ethical issues in transitioning to new technologies.

Context:

Now that you have reviewed the history of computing and demonstrated an understanding of the concept of software architecture and the various types of software architecture in Assessment 1, you are now tasked to examine a case and advise a company in the transition to microservice architecture.

Instructions:

Having read your report on the history of computing and a survey of software architecture, the Chief Technology Officer of Whiteboard (the ‘Company’) decided to overhaul its technology strategy and the management of its IT delivery teams to ensure they provide reliable student and learning management systems to over 600 universities and institutions across the world. Whiteboard is a leading student and learning management system provider, supporting over 10 million students worldwide.

Flexibility and agility are critical to the Company so that they can incorporate new code and new technologies that facilitate teaching and learning as frequently as they can and measure the effort of that. Continuous and frequent delivery lies at the core of the Company’s IT strategy and offers a great competitive edge to the Company over its competitors.

The System they provide comprehensively manage the entire lifecycle of a student, from student recruitment, student enrolment, tuition fee payment, learning content management, to student academic record management, graduation and the issuance of qualification and certificate.

The Company is considering a restructure. “We are nowhere close to a continuous and frequent delivery module, as it requires a shift to a more microservice-based approach to the monolithic system”, said the Chief Technology Officer. “What we are looking to do is to break the System up architecturally into microservices so that we can release code that does not have any dependencies across the other components of the System.”

The Company is satisfied with the credentials you established in the previous report and have engaged you to write a report to further advise them on the transition to microservice architecture. Your report should address the following tasks:

  • A definition and introduction to microservice architecture;
  • Examples of successful implementation of microservice architecture for at least three companies in different industries. You should include the benefit microservice architecture brought to them. There is no architecture free lunch, therefore you should also discuss the challenges they faced in the implementation of microservice architecture;
  • Discuss the principles of service modelling and technologies available for integration, e.g. SOAP, XML-RPC, REST.
  • Discuss the challenges in splitting the backend monolithic system that represent substantial amount of the behaviour of the Company’s system.
  • Discuss any ethical, legal and security issues in the transitioning to microservice architecture.

Your report should include the following

  1. Title page: Subject code and name, assessment number, report title, assessment due date, word count (actual), student names, student IDs, Torrens email address, campus learning facilitator, and Subject coordinator. Not included in the word count.
  2. Executive summary: should include the purpose of the report, the problem including key issues considered and how they were investigated, your findings and recommendations. This part should be approximately three quarters of an A4 page but must not be longer than one (1) A4 page. Not included in the word count.
  3. Table of Contents (ToC): should list the report topics using decimal notation. Need to include the main headings and subheadings with corresponding page numbers, using a format that makes the hierarchy of topics clear. Because you are including a ToC the report pages should be numbered in the footer as follows: title page has no page number; and main text to have Arabic numerals commencing at 1. Create the ToC using MS Word’s ToC auto-generator rather than manually typing out the ToC. Instructions can be found here https://support.office.com/en-gb/article/Create- a-table-of-contentsor-update-a-table-of-contents-eb275189-b93e-4559-8dd9-c279457bfd72#__create_a_table. Not included in the word count.
  4. Introduction: provide a brief description of the company as given in the case scenario including any assumptions, a concise overview of the problem you have been asked to research, the main aims/purpose of the report, the objectives to be achieved by writing the report (include the tasks outlined in the case study) and how you investigated the problem. Provide an outline of the sections of the report. Should be approximately 250 words.
  5. Body of the report (use appropriate headings in the body of the report.): Ensure that you address the tasks listed in the case study scenario. Do NOT use generic words such as ‘Body, Body of the Report, Tasks’ as section headings. Create meaningful headings and subheadings that reflect the topic and content of your report. Should be approximately 1800 words.
  6. Conclusion: restate the purpose of the report and key issues investigated and the related findings based on your research and analysis. Explain the significance of your findings for addressing the problem stated in the case scenario and any limitations. State how your report has achieved its objectives and any future work to be considered. Should be approximately 250 words.
  7. Recommendation: make specific and actionable recommendations to Whiteboard to help their transitioning into microservices architecture. Should be approximately 200 words.
  8. Reference list. Not included in the word count.
  9. Appendices if necessary. Not included in the word count.

General Assessment Requirement

Incomprehensible submissions. Assessments provide the opportunity for students to demonstrate their knowledge and skills to achieve the required standard. To do this, assessment responses need to be both clear and easy to understand. If not, the University cannot determine that students have demonstrated their knowledge and skills. Assessments will, therefore, be marked accordingly including the potential for 0 (zero) marks where relevant.

Case study. Assessment response must focus on the case study scenario given in the Task Instructions. Any assessment items that do not address the case study scenario may be awarded 0 (zero) marks.

Track changes. If you use Track Changes when writing your assessment, you must ensure that the submitted document is the final and correct version of the document. That is, if your submitted report contains Track Changes or Comments or any other editing marks it may be awarded 0 (zero) marks. It is your responsibility to submit the final and correct version of your report.

Check with marking criteria. Before submitting your assessment, you should check it against the assessment criteria and the marking rubric included in this specification to ensure that you have satisfactorily addressed all the criteria that will be used to mark your submission.

Academic language. All submissions should be thoroughly proof-read for spelling, typographical or grammatical errors before being submitted. Do not reply on the ‘spell-check’ function in your word processing program. If, for example, ‘affect’ is substituted for ‘effect’, your program may not detect the error.

Referencing

It is essential that you use appropriate APA style for citing and referencing research. Please see more information on referencing here http://library.laureate.net.au/research_skills/referencing

Assessment Attributes

Fail (Unacceptable) 0-49%

Pass

(Functional)

50-64%

Credit

(Proficient) 65-74%

Distinction

(Advanced)

75 -84%

High Distinction

(Exceptional)

85-100%

Definition and introduction to microservice

architecture

15%

Failed to provide a definition for

microservices architecture or the definition for microservices architecture is fundamentally incorrect. The answer demonstrated little understanding of the concept of microservices architecture.

There are significant errors in the definition of microservices architecture. The answer demonstrated a limited understanding of the concept of microservices architecture.

There are some minor errors in the definition of microservices architecture.

Correct definition of and

comprehensive introduction to microservice architecture. The answer has some room for improvement.

Correct definition of and

comprehensive introduction to microservice architecture. The answer demonstrated

a very in-depth understanding of microservice architecture.

Three examples of successful implementation of microservice

architecture

25%

Provided examples of successful implementation of microservice architecture for at least one company in different industries.

Did not include the benefit microservice architecture brought to each of the companies, or the benefit is too general to be considered relevant.

Did not discuss the challenges each of the companies faced in the implementation of microservice architecture.

Provided examples of successful implementation of microservice architecture for at least two companies in different industries.

Did not include the benefit microservice architecture brought to each of the companies, or the benefit is too general to be considered relevant.

Did not discuss the challenges each of the companies faced in the implementation of microservice architecture.

Provided examples of successful implementation of microservice architecture for at least two companies in different industries.

Include the benefit microservice architecture brought to each of the companies, but the benefit is somewhat general.

Discussed the challenges each of the companies faced in the implementation of microservice architecture, but the discussion is not thorough.

Provided examples of successful implementation of microservice architecture for at least three companies in different industries.

Included the benefit microservice architecture brought to each of the companies, but there is

some room for improvement.

Discussed the challenges each of the companies

faced in the implementation of microservice architecture, but the discussion is not thorough.

Provided examples of successful implementation of microservice architecture for at least three companies in different industries.

Included the benefit microservice architecture brought to each of the companies.

Thoroughly discussed the challenges each of the companies faced in the implementation of microservice architecture

Principles of service modelling and integration

technologies

15%

The understanding of the principles of service modelling is incorrect.

Discussed either at least one synchronised OR asynchronised technology

for service communication, the discussion demonstrated little understanding of the technology.

Included a discussion on the

principles of service modelling.

Discussed either at least one synchronised OR asynchronised technology for service communication, the discussion demonstrated limited understanding of the technology.

Included a discussion on the

principles of service modelling.

Discussed either at least one synchronised OR asynchronised technology for service communication.

Included a discussion on integration technologies.

A clear discussion on the principles of service modelling.

Discussed both at least one synchronised and asynchronised technology for service communication.

A clear discussion on integration technologies.

A thorough discussion on the principles of service modelling.

Discussed in great depth about both at least one synchronised and asynchronised technology for service communication.

A comprehensive discussion on integration technologies.

Challenges in splitting the backend monolithic systems

15%

Included a discussion on the challenges in splitting the backend monolithic system that represent substantial amount of the behaviour of the Company’s system, but the discussion demonstrated little understanding of transitioning from monolithic architecture to microservice architecture.

Did not include a discussion on splitting a centralised database

Included a discussion on the challenges in splitting the backend monolithic system that represent substantial amount of the behaviour of the Company’s system, but the discussion is too general to be considered relevant to the case.

May not include a discussion on splitting a centralised database

Included a discussion on the challenges in splitting the backend monolithic system that represent substantial amount of the behaviour of the Company’s system, but the discussion is somewhat general.

Mentioned the need to split a centralise database.

A clear discussion on the challenges in splitting the backend monolithic system that represent substantial amount of the behaviour of the Company’s system.

A clear discussion on splitting a centralised database.

A thorough discussion on the challenges in splitting the backend monolithic system that represent substantial amount of the behaviour of the Company’s system.

A thorough discussion on splitting a centralised database.

Ethical, legal and security issues in the transiting to microservice

architecture

15%

Failed to identify any ethical, legal and security issues in the transitioning

to microservice architecture.

Included a discussion on the ethical, legal and security issues in the transitioning to microservice architecture, but the understanding of one of the aspects is significantly lacking.

Included a discussion on the ethical, legal and security issues in the transitioning to microservice architecture, but there is room for improvement.

A clear discussion on the ethical, legal and security issues in the transitioning to microservice architecture.

A thorough discussion on the ethical, legal and security issues in the transitioning to microservice architecture.

Report structure, professional writing and references

15%

Well synthesised and extensive research;

More than 14 current references.

Approximately 60% or more of the references were academic references.

Thorough referencing. Citations and reference list accurate and consistent with Torrens APA referencing style. All citations/references listed.

Written expression was clear and correct; Grammar excellent; correct use of punctuation; minimal or no spelling errors; and evidence of thorough proof-reading.

Report structure is complete, included: An Executive Summary, ToC,

Table of Content,

Introduction, Body,

Conclusion, References.

Basic research;

At least ten current references but less than six academic references.

Some errors with Torrens APA referencing style.

Incomplete reference list. References not cited properly in text.

Some major grammatical or proofreading errors. Language frequently weakened by inexact word choices. Spelling errors.

A few structural elements are missing.

Well synthesised and extensive research;

More than 14 current references.

Approximately 60% or more of the references were academic references.

Thorough referencing. Citations and reference list accurate and consistent with Torrens APA referencing style.

All citations/references listed.

Written expression was clear and correct; Grammar excellent; correct use of punctuation; minimal or no spelling errors; and evidence of thorough proof-reading.

Report structure is complete, included: An Executive Summary, ToC, Table of

Content, Introduction, Body, Conclusion, References.

Well synthesised and extensive research;

More than 14 current references.

Approximately 60% or more of the references were academic references.

Thorough referencing. Citations and reference list accurate and consistent with Torrens APA referencing style. All citations/references listed.

Written expression was clear and correct; Grammar excellent; correct use of punctuation; minimal or no spelling errors; and evidence of thorough proofreading.

Report structure is complete, included: An Executive Summary, ToC,

Table of Content,

Introduction, Body,

Conclusion, References.

Well synthesised and extensive research;

More than 14 current references.

Approximately 60% or more of the references were academic references.

Thorough referencing. Citations and reference list accurate and consistent with Torrens APA referencing style. All citations/references listed.

Written expression was clear and correct; Grammar excellent; correct use of punctuation; minimal or no

spelling errors; and evidence of thorough proof-reading.

Report structure is complete, included: An Executive Summary, ToC,

Table of Content,

Introduction, Body,

Conclusion, References.