John D. McGregor C15.1 – Process/AUTOSAR

Slides:



Advertisements
Similar presentations
BY MAULIK PATEL CED, GPERI Computing Architecture.
Advertisements

Objectives In this session, you will learn to:
8.
Building Applications using ASP.NET and C# / Session 1 / 1 of 21 Session 1.
Technical Architectures
Database Application Application logic: presentation (input /output)
SWE Introduction to Software Engineering
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System architectures Updated: November 2014.
Establishing the overall structure of a software system
Client/Server Computing. Information processing is distributed among several workstations and servers on a network, with each function being assigned.
Web Application Architecture: multi-tier (2-tier, 3-tier) & mvc
Introduction to Databases Transparencies 1. ©Pearson Education 2009 Objectives Common uses of database systems. Meaning of the term database. Meaning.
The Design Discipline.
Copyright © cs-tutorial.com. Introduction to Web Development In 1990 and 1991,Tim Berners-Lee created the World Wide Web at the European Laboratory for.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
E-Learning Material Web Application Design 3. Web Application Design Architecture Which objects go where? The final model notation Summary.
Architectural Design To explain the advantages and disadvantages of different distributed systems architectures To discuss client-server and distributed.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Slide 1 Physical Architecture Layer Design Chapter 13.
CPSC 875 John D. McGregor C16 - DSMs. Partitioning _jetta_horn_recall/index.htm?hpt=T2
Client – Server Architecture. Client Server Architecture A network architecture in which each computer or process on the network is either a client or.
CpSc 875 John D. McGregor AADL. Point of sale system.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Architecture.
The Client/Server Database Environment Ployphan Sornsuwit KPRU Ref.
Personal Computer - Stand- Alone Database  Database (or files) reside on a PC - on the hard disk.  Applications run on the same PC and directly access.
Architectural Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Database Architectures Database System Architectures Considerations – Data storage: Where do the data and DBMS reside? – Processing: Where.
John D. McGregor Class 4 – Initial decomposition
Introduction Database integral part of our day to day life Collection of related database Database Management System : software managing and controlling.
Infotainment architecture John D. McGregor. Business logic server Database server client model views controllers.
Chapter 7: Architectural Design Chapter 11 in textbook 1.
CPSC 875 John D. McGregor Design Concept. Functional decomposition.
Arch-1 9.Architecture. Arch-2 What’s Architecture? Description of sub-system –Components/sub-systems –Their interaction Framework for communication.
CSC 480 Software Engineering High Level Design. Topics Architectural Design Overview of Distributed Architectures User Interface Design Guidelines.
Chapter 1 Revealed Distributed Objects Design Concepts CSLA.
Chapter 9  Definition of terms  List advantages of client/server architecture  Explain three application components:
TM 8-1 Copyright © 1999 Addison Wesley Longman, Inc. Client/Server and Middleware.
CPSC 871 John D. McGregor Module 8 Session 3 Assignment.
Client – Server Architecture A Basic Introduction 1.
CS223: Software Engineering Lecture 14: Architectural Patterns.
CPSC 372 John D. McGregor Module 6 Session 4 Sonar.
Statistics Monitor of SPMSII -High level and detailed design Warrior Team Pu Su Heng Tan Kening Zhang.
Navigation Framework using CF Architecture for a Client-Server Application using the open standards of the Web presented by Kedar Desai Differential Technologies,
1 LM 6 Database Applications Dr. Lei Li. Learning Objectives Explain three components of a client-server system Describe differences between a 2-tiered.
2 Copyright © Oracle Corporation, All rights reserved. Basic Oracle Net Architecture.
A Presentation Presentation On JSP On JSP & Online Shopping Cart Online Shopping Cart.
CPSC 875 John D. McGregor C18. Partitions Requirements Need is for an e-commerce system which presents catalog item descriptions and takes orders. The.
Distributed Systems Architectures Chapter 12. Objectives  To explain the advantages and disadvantages of different distributed systems architectures.
Distributed Systems Architectures. Topics covered l Client-server architectures l Distributed object architectures l Inter-organisational computing.
CPSC 875 John D. McGregor C16.
WEB TESTING
Chapter 12: Architecture
6/25/2018.
CPSC 875 John D. McGregor C16.
Software Engineering Architectural Design Chapter 6 Dr.Doaa Sami
Software Design and Architecture
The Client/Server Database Environment
CSC 480 Software Engineering
Deployment Diagram.
John D. McGregor Session 9 Testing Vocabulary
John D. McGregor Quality attributes
John D. McGregor C8 - Tactics
John D. McGregor Session 9 Testing Vocabulary
Introduction to Databases Transparencies
Systems Analysis and Design in a Changing World, 6th Edition
Tiers vs. Layers.
Chapter 12: Physical Architecture Layer Design
Software Design Lecture : 8
Serpil TOK, Zeki BAYRAM. Eastern MediterraneanUniversity Famagusta
Presentation transcript:

John D. McGregor C15.1 – Process/AUTOSAR CPSC 875 John D. McGregor C15.1 – Process/AUTOSAR

Requirements Need is for an e-commerce system which presents catalog item descriptions and takes orders. The system must be able to take advantage of mobile devices. The system must be available internet wide.

Client server basic style system

Architectural style – N-Tiered e-commerce architecture Client/server client presentation business logic database

Factors Separate machines Separate purposes Scalability Database latency becomes critical Thin client presentation business logic database

Decomposition of client side model controller view Thin client presentation business logic database

Use a Database Framework model controller view Thin client presentation business logic database

Autosar

Rules for Interfaces

Layer Interactions

Error handling

Errors

Automation/Communication Statements about values in the product Assert invariants assumption: input < 20 Guarantees guarantee: output < 100 Statements about the structure of the system connected(a : component, conn : connection, b : component) : bool = parent(source(conn)) = a and parent(destination(conn)) = b memory_bound(logical : component, physical : component) : bool = has_property(logical, Deployment_Properties::Actual_Memory_Binding) and member(physical, property(logical, Deployment_Properties::Actual_Memory_Binding)) AGREE Resolute

Here’s what you are going to do Use AGREE and Resolute to illustrate the validity of your model. Add statements to your model and evaluate them. Submit the instrumented code and a couple of screen shots by 11:59PM on March 25th.