Architecture of Distributed Systems Homework Assignment 1

Slides:



Advertisements
Similar presentations
MgmtSecurity QOS Transport Packaging Extensions Wire Inspection Discovery Publication Registry Description Business Level Agreements Service Level Agreements.
Advertisements

Executional Architecture
Database Design Process. The Steps 1.What does the database/application need to do? 2.Develop the tables 3.Establish relationships 4.Set up the forms.
Mark CerritelliMatthew Fister Charles Cole Mine Yalcinalp.
Week1 Architecture - Lecture outline & Assignments Dr. John Abraham UTPA.
2-Oct-15 Bojan Orlic, TU/e Informatica, System Architecture and Networking 12-Oct-151 Homework assignment 1 feedback Bojan Orlic Architecture.
HOMEWORK 08D Block diagrams Problem 1: Problem 2:
Project X Group Y Presenters: (indicate roles). Part I: Project Overview System provides functionality X Motivation for project –Address problem with…
Arch-1 9.Architecture. Arch-2 What’s Architecture? Description of sub-system –Components/sub-systems –Their interaction Framework for communication.
Elimination Method Day 2 Today’s Objective: I can solve a system using elimination.
PLUS.
NTC 362 Week 4 Individual INDP, Part 3 Review the assignment Integrative Network Design Project. Write a 3- to 5-page paper that includes the following.
BUS 352 Week 2 Assignment Social Business Networking and E- Commerce Select one of the social networking sites for business professionals listed in Insights.
Nursing homework help BEST ASSIGNMENT.
FPGA IMPLEMENTATION OF TCAM Under the guidance of Dr. Hraziia Presented By Malvika ( ) Department of Electronics and Communication Engineering.
5 steps to responding to your talent supply and demand
Viewing Data-Driven Success Through a Capability Lens
Event Handling Patterns Asynchronous Completion Token
Commerce Diagram Template
The Development Process of Web Applications
Local Area Networks Chapter 4.
IS301 – Software Engineering Dept of Computer Information Systems
ECE 671 – Lecture 1 Introduction.
CS 3700 Networks and Distributed Systems
CSC 480 Software Engineering
Systems Analysis and Design in a Changing World, 6th Edition
Virtual LANs.
CS & CS Capstone Project & Software Development Project
MPA TM543Competitive Success/snaptutorial.com
MPA TM543 Education for Service- -snaptutorial.com
POS 355 knowledge is divine-- snaptutorial.com. POS 355 Entire Course For more classes visit Please check All Included Assignments.
Protocol Architectures
Krste Asanovic Electrical Engineering and Computer Sciences
Mach Kernel Kris Ambrose Kris Ambrose 2003.
ECE 671 – Lecture 1 Introduction.
Architecture of Distributed Systems
A Scalable content-addressable network
CS 3700 Networks and Distributed Systems
Academic Communication Lesson 3
Chapter 2: The Linux System Part 1
CS322D Tutorials.
0.4 Solving Linear Inequalities
CIS 83 week 1 Class website Syllabus review Course outline
Distributed computing using the internet
Verification Concepts for SysmL v2
Rudolf Mak January 21, Jan-19 Rudolf Mak
Session 9 Back Home Application.
Communicating Professionally with Your American Professors
EEL 4598/5718: Computer Communications
COMP4442 Cloud Computing: Assignment 1
Project Management Concepts May 5th, 2016
Guidelines Use a Large Bold Font (20PT or Larger)
What is Project Human Resource Management (PHRM)?
API Management Diagram Icons
One-slide Research Overview
Ancient Architecture & Worldview
P.O.D. # 32 2/4/19.
CIS 83 week 1 Class website Syllabus review Course outline
АВЛИГАТАЙ ТЭМЦЭХ ҮНДЭСНИЙ ХӨТӨЛБӨР /танилцуулга/
SPL P65 – Test preparation
Course Wrap-up and Integration
Week1 software - Lecture outline & Assignments
SPL – Telematic session P55 – Test preparation
Verification Concepts for SysmL v2
Cognitive Insurance Architecture Template
Cognitive Car Information Template
Digital Computer & Digital Systems
DBA Workflow Diagram Template
Week1 Architecture - Lecture outline & Assignments
Exam #2 covering Sections 11 to 15 - NEXT CLASS!
Presentation transcript:

Architecture of Distributed Systems Homework Assignment 1 R. H. Mak

Exercise Consider the models on the following slides and answer the following questions. Each model is provided with a hyperlink to acknowledge its source and for additional information. What building blocks do you see? What do they represent? Are they conceptual (C) or physical (P)? Same questions as 1, but now for connectors? Do not forget (C) or (P)! To which views (1..*) does the model belong? Motivate why, and identify corresponding stakeholders and their concerns. Which of the following EFRs are addressed (Y + motivation | N)? Performance/scalability, availability/reliability, security, maintainability, other? Is there a concept of distribution (Y + motivation | N)? Comment on the clarity/semantics of the diagram  |  |  , plus motivation Keep you answers crisp! Rudolf Mak 9-May-19

Taken from: VICSDA: using virtual communities to secure service discovery and access Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19

Taken from: https://engineering. linkedin Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19

Taken from: https://https://www.oreilly.com/learning/docker-networking-service-discovery Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19

Taken from: http://ithare.com/mmog-rtt-input-lag-and-how-to-mitigate-them/ Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19

Taken from: http://www.eetimes.com/document.asp?doc_id=1278566 Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19

Taken from: http://www.informit.com/articles/article.aspx?p=1927741&seqNum=2 Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19

https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6298895 Taken from: https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6298895 Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19

Taken from: http://http://www.mikepluta.com/category/architecture/ Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19

Taken from: https://www.programiz.com/python-programming/package Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19

Taken from: https://www.w3.org/TR/2004/NOTE-ws-arch-20040211/#service_oriented_architecture Building blocks Which, what + (C |P): Connectors Which, what + (C |P): View – concern – stakeholder (1..*): Extra-functional requirements (Y + motivation) | N : Security: Availability & reliability: Maintainability: Performance and scalability: Distribution (Y + motivation) | N : Clarity/Semantics (  |  | ) + motivation: Rudolf Mak 9-May-19