Conquering Complex and Changing Systems Object-Oriented Software Engineering System Design:Hardware/ software mapping, example Päivi Ovaska.

Slides:



Advertisements
Similar presentations
Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 16, Methodologies: Putting It All Together.
Advertisements

Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 6, System Design: Decomposing the System.
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 1 Example of a Problem Statement: Introduction into.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
8.
System Design Chapters 6-7 Object-Oriented Software Engineering:
Conquering Complex and Changing Systems Object-Oriented Software Engineering TJSS: Defining access control, example Päivi Ovaska.
Conquering Complex and Changing Systems Object-Oriented Software Engineering TJSS System Design Lecture 12 Päivi Ovaska.
Conquering Complex and Changing Systems Object-Oriented Software Engineering TJSS: Defining persistent data stores, example Päivi Ovaska.
Conquering Complex and Changing Systems Object-Oriented Software Engineering TJSS Design goals and System Decomposition, example Päivi Ovaska.
Conquering Complex and Changing Systems Object-Oriented Software Engineering TJSS: Identifying boundary conditions, example Päivi Ovaska.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 UML Sequence Diagrams  Used during system.
Chapter 29 Structure of Computer Names Domain Names Within an Organization The DNS Client-Server Model The DNS Server Hierarchy Resolving a Name Optimization.
Addressing Design Goals
Conquering Complex and Changing Systems Object-Oriented Software Engineering Art for Chapter 9, Testing.
Ch 7: Sys. Architecture: Design Decisions to Address Goals
Understanding Networks. Objectives Compare client and network operating systems Learn about local area network technologies, including Ethernet, Token.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System architectures Updated: November 2014.
1 System Design: Addressing Design Goals We are starting from an initial design, along with a set of design goals. What is the next step?
TJSS luennot System Design Lecture 1
Introduction to Management Information Systems Chapter 5 Data Communications and Internet Technology HTM 304 Fall 07.
CS 432 Object-Oriented Analysis and Design
Distributed Systems Architecture Presentation II Presenters Rose Kit & Turgut Tezir.
Using UML, Patterns, and Java Object-Oriented Software Engineering Example of a Problem Statement: Introduction into ARENA.
The Design of System Architecture
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 3, Project Organization and Communication.
Chapter 9 Elements of Systems Design
The Design Discipline.
Conquering Complex and Changing Systems Object-Oriented Software Engineering Art for Chapter 11, Project Management.
Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 3, Project Communication.
Addressing design Goals  We decompose the system to address complexity  Assigning each subsystem to team to work on  But we also need to address system.
UML Development - Overview PROGRAM ACTORS ANALYSIS Domain Objects DESIGN IMPLEMENTATION D A T A D I C T I O N A R Y Time USE CASES ANALYSIS CLASS DIAGRAM(S)
HOW WEB SERVER WORKS? By- PUSHPENDU MONDAL RAJAT CHAUHAN RAHUL YADAV RANJIT MEENA RAHUL TYAGI.
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 6, System Design Lecture 2.
Introduction to Technology Infrastructure Chapter 1.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Design “There are two ways of constructing.
How computer’s are linked together.
Software Architecture in Practice Architectural description (The reduced version)
MACIASZEK, L.A. (2001): Requirements Analysis and System Design. Developing Information Systems with UML, Addison Wesley Chapter 6 - Tutorial Guided Tutorial.
Conquering Complex and Changing Systems Object-Oriented Software Engineering Art for Chapter 8, Rationale Management.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 6 System Design: Decomposing the System.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Overview System Design II (slides Part B)
Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 7 System Design: Addressing Design Goals.
Application Block Diagram III. SOFTWARE PLATFORM Figure above shows a network protocol stack for a computer that connects to an Ethernet network and.
NETWORK HARDWARE AND SOFTWARE MR ROSS UNIT 3 IT APPLICATIONS.
Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 13, Configuration Management.
10/8: Software What is software? –Types of software System software: Operating systems Applications Creating software –Evolution of software development.
NETWORKING COMPONENTS Buddy Steele Assignment 3, Part 1 CECS-5460: Summer 2014.
Lecture 18: Object-Oriented Design
Windows Azure. Azure Application platform for the public cloud. Windows Azure is an operating system You can: – build a web application that runs.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
DESIGN OF SOFTWARE ARCHITECTURE
Higher Computing Networking. Networking – Local Area Networks.
Computer Science 340 Software Design & Testing Software Architecture.
Data Communications and Networks Chapter 9 – Distributed Systems ICT-BVF8.1- Data Communications and Network Trainer: Dr. Abbes Sebihi.
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 6, System Design Lecture 1.
INTERNET AND PROTOCOLS For more notes and topics visit: eITnotes.com.
Vignesh Ravindran Sankarbala Manoharan. Infrastructure As A Service (IAAS) is a model that is used to deliver a platform virtualization environment with.
Web Services Blake Schernekau March 27 th, Learning Objectives Understand Web Services Understand Web Services Figure out SOAP and what it is used.
Assignment # 3 Networking Components By: Jeff Long.
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 6, System Design Lecture 1.
COMPUTER NETWORKS Hwajung Lee. Image Source:
COMP1321 Digital Infrastructure Richard Henson March 2016.
Two New UML Diagram Types Component Diagram Deployment Diagram.
9 Systems Analysis and Design in a Changing World, Fifth Edition.
Analyzing UML Descriptions of Architectures Using Information Theory
OO Methodology OO Architecture.
NUTV – Basic and Expanded Service
Information Technology Ms. Abeer Helwa
Addressing Design Goals
Presentation transcript:

Conquering Complex and Changing Systems Object-Oriented Software Engineering System Design:Hardware/ software mapping, example Päivi Ovaska

Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 2 Selecting a hardware configuration and platform  Many systems run on more than one computer and depend on access to an intranet or to Internet  The use of multiple computer can address high-performance needs or to interconnect multiple distributed users  Carefully examine the allocation of subsystems to computers and the design of the infrastructure for supporting communication betwee subsystems.  Computers are modeled as nodes in UML deployment diagrams  includes also selecting a virtual machine (operating system, database management system, communication package, web browsers) onto which the system should be built

Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 3 Selecting a hardware configuration and platform for MyTrip  PlanningSubsystem and RoutingSubsystem run on two different nodes  PlanningSubsystem runs in WebServer and RoutingSubsytem runs in onboard computer  Unix machine as a virtual machine for the WebServer  Web browsers Netscape and Internet Explorer for onboard computer  UML Deployment Diagram for MyTrip (Rose version)

Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 4 Allocating objects and subsystems to nodes in MyTrip  Objects and subsystems are assigned to nodes  RoutingSubsystem and PlanningSubsystem share the objects Trip, Destination, Crossing, Segment, Direction  Create a new subsystem to support communication between instances of these classes via a wireless modem: Communication Subsystem  Only segments not part of the trip are stored in RoutingSubsystem. Adjacent segments not part of the trip are stored only in the PlanningSubsystem. We need objects in the RoutingSubsystem that can act as a surrogates to Segments and Trips in the PlanningSubsystem. We create two new classes SegmentProxy and TripProxy, that act on the behalf of Segment and Proxy classes.(Proxy design pattern next lecture)[Gamma et al., 1994]  In the case of replanning by the driver, these classes will transparently request the CommunicationSubsystem to retrieve the information associated with its corresponding Segments on the PlanningSubsystem.  The CommunicationSubsystem is used for trasferring a complete trip from PlanningSubsystem to RouteAssistant.

Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 5 MyTrip revised design model CommunicationSubsystem  The CommunicationSubsystem is responsible for transporting objects from the PlanningSubsysem to the RoutingSubsystem Connection  A Connection represents an active link between the PlanningSubsystem and the RoutingSubsystem. A Connection Object handles exceptional cases associated with loss of network services Message  A Message represents a Trip and its related Destinations, Segments, Crossings and Directions, encoded for transport