Group 4 Anders Linseth Magdalena Lipska Nicolai Friis Tobias Melcher

Slides:



Advertisements
Similar presentations
Computer Systems & Architecture Lesson 2 4. Achieving Qualities.
Advertisements

MapReduce Online Created by: Rajesh Gadipuuri Modified by: Ying Lu.
CS 443 Advanced OS Fabián E. Bustamante, Spring 2005 Resource Containers: A new Facility for Resource Management in Server Systems G. Banga, P. Druschel,
Intraship Integration Control Instructor: TV Prabakar.
Visual Traffic Simulation Thomas Fotherby. Objective To visualise traffic flow. –Using 2D animated graphics –Using simple models of microscopic traffic.
Design Creative Process of transferring the problem into a solution
Rhapsody in C++ Tool Training "Essential" © I-Logix v3.0 1/29/2001 Adv-1 Section 4 Advanced Level Concurrency.
1 Exercise a short summary of you so your professor can get to know you better: Name, company, job/role/title, most interesting SE area, any architecting.
Software Architecture in Practice Part Two: Creating an Architecture 2nd Ed. Len Bass, Paul Clements, Rick Kazman.
Concurrency, Threads, and Events Robbert van Renesse.
Computer Organization and Architecture
ESA UNCLASSIFIED – For Official Use Deterministic Communication with SpaceWire Martin Suess CCSDS Spring Meeting /03/2015.
Adaptive Stream Processing using Dynamic Batch Sizing Tathagata Das, Yuan Zhong, Ion Stoica, Scott Shenker.
IV&V Facility Model-based Design Verification IVV Annual Workshop September, 2009 Tom Hempler.
1 Software Testing Techniques CIS 375 Bruce R. Maxim UM-Dearborn.
New Challenges in Cloud Datacenter Monitoring and Management
What is it? A mobile robotics system controls a manned or partially manned vehicle-car, submarine, space vehicle | Website for Students.
Achieving Qualities. Architectural Tactics  A tactic is a design decision that influences the control of a quality attribute response.  A collection.
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
Achieving Qualities 1 Võ Đình Hiếu. Contents Architecture tactics Availability tactics Security tactics Modifiability tactics 2.
Real-Time Software Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Teaching Deliberative Navigation Using the LEGO RCX and Standard LEGO Components Gary R. Mayer, Dr. Jerry Weinberg, Dr. Xudong Yu
Advanced Operating Systems CIS 720 Lecture 1. Instructor Dr. Gurdip Singh – 234 Nichols Hall –
Based on D. Galin, and R. Patton.  According to D. Galin  Software quality assurance is:  A systematic, planned set of actions necessary to provide.
Verification and Validation Overview References: Shach, Object Oriented and Classical Software Engineering Pressman, Software Engineering: a Practitioner’s.
Group 9 “The software architecture of a program or computing system is the structure or structures of the system, which comprise software elements, the.
Mobile robot controller Group 2. Group 2 - Robot controller project - TDT4240 Software Architecture Group 2 Leif Hamang Bru Lisa W. Eriksen Kay Are Ulvestad.
May PEM status report. O.Bärring 1 PEM status report Large-Scale Cluster Computing Workshop FNAL, May Olof Bärring, CERN.
Reference: Ian Sommerville, Chap 15  Systems which monitor and control their environment.  Sometimes associated with hardware devices ◦ Sensors: Collect.
30 October Agenda for Today Introduction and purpose of the course Introduction and purpose of the course Organization of a computer system Organization.
Maeda, Sill Torres: CLEVER CLEVER: Cross-Layer Error Verification Evaluation and Reporting Rafael Kioji Vivas Maeda, Frank Sill Torres Federal University.
 Apache Airavata Architecture Overview Shameera Rathnayaka Graduate Assistant Science Gateways Group Indiana University 07/27/2015.
Real-time Software Design King Saud University College of Computer and Information Sciences Department of Computer Science Dr. S. HAMMAMI.
Performance Performance is about time and the software system’s ability to meet timing requirements.
Computer Architecture CIS 222 Computer Architecture CIS 222.
A N I N - MEMORY F RAMEWORK FOR E XTENDED M AP R EDUCE 2011 Third IEEE International Conference on Coud Computing Technology and Science.
Group 3 Ballfinder a highly modifiable system. Introduction Quality attribute: Modifiability Environment: Random maze Known number of balls One light.
CS 2310 Final Project - Driving Behavior Monitor Haifeng Xu Dec. 5, 2013.
1 Why Threads are a Bad Idea (for most purposes) based on a presentation by John Ousterhout Sun Microsystems Laboratories Threads!
1 Software Architecture in Practice Architectural Design (Again, the amputated version)
Evaluating the Fault Tolerance Capabilities of Embedded Systems via BDM M. Rebaudengo, M. Sonza Reorda Politecnico di Torino Dipartimento di Automatica.
Dr. Awais Majeed Achieving Quality CSE 861- Software System Design & Architecture.
Project Overview Project Name Company Name Presenter Name.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Chapter 1 Characterization of Distributed Systems
Deterministic Communication with SpaceWire
Real-time Software Design
Information Systems Development
A Scalable Approach to Architectural-Level Reliability Prediction
Advanced Operating Systems CIS 720
SEDA: An Architecture for Scalable, Well-Conditioned Internet Services
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
CS703 – Advanced Operating Systems
Applying Control Theory to Stream Processing Systems
Advanced OS Concepts (For OCR)
Achieving Qualities.
COEN346 Tutorial Monitor Objects.
Verification and Validation Overview
Real-time Software Design
Rigorous Development Of a Safety-Critical System Based on Coordinated Atomic Actions By Subash M S.
Introduction to Software Testing
Fault Tolerance Distributed Web-based Systems
Fundamental Test Process
Operating Systems Lecture 1.
Major Topics in Operating Systems
Scheduling.
CSE 153 Design of Operating Systems Winter 2019
SEDA: An Architecture for Well-Conditioned, Scalable Internet Services
Modeling Event-Based Systems in Ptolemy II EE249 Project Status Report
Focus (using Colours) Focus (using forms)
Presentation transcript:

Group 4 Anders Linseth Magdalena Lipska Nicolai Friis Tobias Melcher Robot Project Group 4 Anders Linseth Magdalena Lipska Nicolai Friis Tobias Melcher

Project problems Development of a robot controller: Creating a requirement specification. Designing an architecture. Evaluation (ATAM). Implementing and testing. Quality attributes in focus: Performance Availability

Availability Fault detection Fault recovery Fault prevention Exception handling will ensure that the system keeps running. Fault recovery Passive redundancy. Checkpoint/rollback. Fault prevention Process monitor. When a fault is detected the monitoring process shall delete the nonperforming process and create a new instance of it.

Performance Resource demand Resource management Resource Arbitration Increase computational efficiency. By implementing efficient algorithms in critical areas latency can be reduced. Bound sensor information queue sizes depending on speed. Resource management Introduce concurrency. Threads should be implemented to enable concurrency whereever this is possible. Resource Arbitration Priority scheduling of accessing sensor information.

Architectural pattern Control loop

Logical view Controller User Feedback and Fault reporting Movement Control Sensor Input

Process view Robot Control Fault Prevention Sensor Interpreter

Demonstration And now some action…

Experiences Importance of doing exhaustive work in early phases. Learnt to design an architecture with focus on certain quality attributes. ATAM, how not to do it… How hard and time consuming it is to implement a robot controller.

Findings / achievements The ATAM process can be a useful evaluation method if implemented correctly. Managed to partly implement the architecture.

Conclusion In a small project like this it is difficult to see the effect of a well designed architecture. ATAM – too big for a small project. Architecture is ”easy”, implementation is ”difficult”.