This repository has been archived on 2025-12-15. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
2024-09-20 14:17:13 +03:00

12 lines
3.6 KiB
HTML

<!doctype html>
<html>
<head>
<title>Description Assignment 1</title>
<meta charset="utf-8">
</head>
<body>
<p dir="ltr" style="text-align: left;">This assignment has two tasks and has 10 points in total. The deadline for the assignment (both tasks) is <strong>Thursday 23.2 until 1600.</strong> It is enough if one member of the group submits the file. Allowed file types include doc and pdf. <br></p><p dir="ltr" style="text-align: left;"><strong><u>Task-1</u> (8 points)<br></strong></p><p dir="ltr" style="text-align: left;">You have to select a distributed system case study as conveyed previously. Search and learn about how the system works, and what are different elements and operations. Submit a report which <u><strong>must</strong></u> address the following aspects:</p><ol><li>Why did you select this particular case study? (0,5 points)<br></li><li>What was the situation before this distributed system was implemented? How were the tasks executed? (0,5 points)<br></li><li>How different components in your case study are interlinked? Include an architectural diagram. If downloaded from the Internet mention the source and explain the working. (1 point)<br></li><li>What architectural style has been used in your case study? In your
opinion, why is it a preferred option over other architectural styles? (1 point)<br></li><li>Are there any videos explaining your case study? If so, please mention the source. (0,5 points)<br></li><li>Revisit the properties of distributed systems discussed in the class, how are the properties considered in your case study? For instance, how it handles failures, transparency, etc. (1,5 points)<br></li><li><span id="page3R_mcid16"><span role="presentation" dir="ltr">The key requirements for any distributed system are scalability, reliability,</span></span><span id="page3R_mcid17"> <span role="presentation" dir="ltr">performance, and openness. Provide three</span><span role="presentation" dir="ltr"> </span><span role="presentation" dir="ltr">examples</span><span role="presentation" dir="ltr"> </span><span role="presentation" dir="ltr">of where these requirements</span> <span role="presentation" dir="ltr">might</span><span role="presentation" dir="ltr"> </span><span role="presentation" dir="ltr">be in conflict with each other, how does your case study deal with these potential conflicts? (2 points)<br></span></span></li><li><span id="page3R_mcid19"><span role="presentation" dir="ltr"></span><span role="presentation" dir="ltr">Does your case study include multiple data storage facilities? If so,</span></span><span id="page3R_mcid20"><span role="presentation" dir="ltr"> why?&nbsp; (1point)<br></span></span></li></ol><div><br></div><div>If you refer to the content that is coming from other sources, please mention the source. Also, mention the contribution of each group member in the assignments' tasks. If you have queries in this regard, feel free to reach and if there are difficulties in finding the topic, the TA will help you in finding one. <br></div><div><br></div><div><br></div><div><strong><u>Task-2 </u>(2 points)<u><br></u></strong></div><div>Create a post on the course discussion forum in Moodle about your case study. The post should briefly explain the elements of the case study from your report for your course fellows to read and learn about your case study. It is mandatory for each group to:</div><div><br></div><div><ol><li>&nbsp;Post about the case study on Moodle.&nbsp;(1 point)</li><li>Comment on at least 2 posts by other groups. You can ask questions about working, give comments, etc. (1 point)</li></ol></div>
</body>
</html>