21.10.02ES Seminar1 Communicating Transaction Processes P.S. Thiagarajan National University of Singapore Joint Work with: Abhik Roychoudhury; ……

Slides:



Advertisements
Similar presentations
Embedded System, A Brief Introduction
Advertisements

ECOE 560 Design Methodologies and Tools for Software/Hardware Systems Spring 2004 Serdar Taşıran.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
PRESENTED BY USHA GHIMIRE. Introduction-The need for MBSE MBSE now and present shortcomings A view of MBSE in the future Key advantages and disadvantages.
Documenting a Software Architecture By Eng. Mohanned M. Dawoud.
Hydra (A General Framework for Formalizing UML with Formal Languages for Embedded Systems*) *from the Ph.D. thesis of William E. McUmber Software Engineering.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
2 Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how statecharts can be used to describe system behaviors  Use statecharts.
Software Testing and Quality Assurance
1 SWE Introduction to Software Engineering Lecture 23 – Architectural Design (Chapter 13)
Review of “Embedded Software” by E.A. Lee Katherine Barrow Vladimir Jakobac.
Models of Computation for Embedded System Design Alvise Bonivento.
Applying Ulysses to Bluetooth Alvise Bonivento Mentor: Marco Sgroi.
Systems Engineering Project: System Validation and Verification Using SDL Ron Henry ENSE 623 November 30, 2004.
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
Modeling State-Dependent Objects Using Colored Petri Nets
1 Model-based Software Engineering 師大資工鄭永斌. 2 History While dealing with complex entity, other engineering has learned not to learn it by building it.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
End-to-End Design of Embedded Real-Time Systems Kang G. Shin Real-Time Computing Laboratory EECS Department The University of Michigan Ann Arbor, MI
Mahapatra-Texas A&M-Fall'001 Codesign Framework Parts of this lecture are borrowed from lectures of Johan Lilius of TUCS and ASV/LL of UC Berkeley available.
Chapter 10: Architectural Design
Chapter 7: The Object-Oriented Approach to Requirements
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
Chapter 10 Architectural Design
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Reliable Design of Safety Critical Systems Dr. Abhik Roychoudhury School of Computing
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Software Engineering Research paper presentation Ali Ahmad Formal Approaches to Software Testing Hierarchal GUI Test Case Generation Using Automated Planning.
Ch.2 Part C: Message Sequence Charts, UML EECE **** Embedded System Design.
1 Interacting Process Classes P.S. Thiagarajan National University of Singapore Joint with: Ankit Goel, Abhik Roychoudhury, Sun Meng To be presented at.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Ch. 2. Specification and Modeling 2.1 Requirements Describe requirements and approaches for specifying and modeling embedded systems. Specification for.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Lecture 18: Object-Oriented Design – Interaction and State Diagrams Anita S. Malik Adapted from Schach (2004) Chapter 12.
C. André, J. Boucaron, A. Coadou, J. DeAntoni,
Internal Talk, Oct Executable Specifications using Message Sequence Charts Abhik Roychoudhury School of Computing National University of Singapore.
The Unified Modeling Language Part II Omar Meqdadi SE 2730 Lecture 9 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
1/26 On-demand Learning Series Software Engineering of Web Application - Object-Oriented Development & UML Hunan University, Software School.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Formal Methods.
OBJECT ORIENTED AND FUNCTION ORIENTED DESIGN 1 Chapter 6.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
1 Copyright  2001 Pao-Ann Hsiung SW HW Module Outline l Introduction l Unified HW/SW Representations l HW/SW Partitioning Techniques l Integrated HW/SW.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
CSCI1600: Embedded and Real Time Software Lecture 11: Modeling IV: Concurrency Steven Reiss, Fall 2015.
Course: COMS-E6125 Professor: Gail E. Kaiser Student: Shanghao Li (sl2967)
Prof. Hany H. Ammar, CSEE, WVU, and
Duminda WijesekeraSWSE 623: Introduction1 Introduction to Formal and Semi- formal Methods Based on A Specifier's Introduction to Formal Methods (J. Wing)
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
1 CEN 4020 Software Engineering PPT4: Requirement analysis.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Toward product architecture oriented requirements analysis for product line development in systems engineering Kei Kurakawa Nara Institute of Science and.
Chapter 0: Introduction
EE 249 Embedded Systems Design
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
The Process of Object Modeling
Object-Oriented Analysis
Appendix A Object-Oriented Analysis and Design
An Introduction to Embedded Software Architecture and Design
Design Yaodong Bi.
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Design.
Presentation transcript:

ES Seminar1 Communicating Transaction Processes P.S. Thiagarajan National University of Singapore Joint Work with: Abhik Roychoudhury; ……

ES Seminar2 The Main Features To support System Level Design –One Level of Abstraction higher than C, C++, VHDL.. UML-compatible –MSCS + Asynchronous control flow –Based on MSCs (Message Sequence Charts) –Sequence Diagrams

ES Seminar3 Why System Level Design? Closer to end-use(r). Less detailed and more architecture-neutral. Easier reuse/adaptaton. Easier to verify. –Safety-critical applications need to be correct. –Catch design errors early. –Coupling with a correct-by-construction synthesis method is an attractive option.

ES Seminar4 What is Available? Data flow graphs. Automata of various kinds. Petri nets. State charts. Esterel, Lustre. SDL, UML.

ES Seminar5 Why UML-compatible? UML is getting rapidly established as a standard. –Mainly in software engineering projects –Increasingly so in embedded systems domain. Offers a suite of graphical notations: –Multiple views –Behavioral and structural diagrams. –Object orientation.  Reuse, adaptation

ES Seminar6 An Idealized Design Flow Requirements Exec. Specifications. Intermediate representation SW/HW Implementation. High Level Description

ES Seminar7 Requirements and Exec. Specifications Requirements : Message Sequence Charts (MSCs) Exec. Specifications : –State charts. UML supports both but no clear distinction made. Other Exec. Spec. : –Petri nets, –MPAs (Message Passing Automata), ….

ES Seminar8 MSCs Message Sequence Charts: –Describe scenarios. –A finite pattern of interaction between agents (object instances,..). –A story

ES Seminar9 Message Sequence Charts rq U1R rq y n U2

ES Seminar10 Message Sequence Charts rq U1R rq y n U2

ES Seminar11 Message Sequence Charts rq U1R rq y n U2 internal action

ES Seminar12 Message Sequence Charts rq U1R rq y n U2 internal actions

ES Seminar13 Message Sequence Charts rq U1R rq y n U2

ES Seminar14 Message Sequence Charts rq U1R rq y n U2

ES Seminar15 Message Sequence Charts rq U1R rq y n U2

ES Seminar16 Message Sequence Charts rq U1R rq y n U2

ES Seminar17 Message Sequence Charts rq U1R rq y n U2

ES Seminar18 Message Sequence Charts rq U1R rq yn U2

ES Seminar19 Message Sequence Charts rq U1R rq y n U2

ES Seminar20 Message Sequence Charts rq U1R rq y n U2

ES Seminar21 Message Sequence Charts rq U1R rq y n U2

ES Seminar22 CTPs Communicating Transaction Processes. An executable spec. mechanism. –Based on MSCs. A network of interacting agents. –Agent’s interaction pattern behavior:  Standard distributed system model –Interaction:  Guarded choice of MSCs.  Transaction schemes.

ES Seminar23 Distributed System Models Petri nets Data flow graphs Statecharts Distributed transition systems (many kinds!) Process algebras (CCS, CSP, …)

ES Seminar24 PI1 IB1IB2 PI2 I1 B I2 P2

ES Seminar25 PI1 IB1IB2 PI2 I1 B I2 P2

ES Seminar26 PI1 IB1IB2 PI2 I1 B I2 P2

ES Seminar27 PI1 IB1IB2 PI2 I1 B I2 P2

ES Seminar28 PI1 IB1IB2 PI2 I1 B I2 P2

ES Seminar29 PI1 IB1IB2 PI2 I1 B I2 P2 But the boxes will have internal structure. A complex Transaction Scheme.

ES Seminar30 Transaction Scheme waitcount2:= waitcount2 + 1  2data.present & B.free  2data.present &  B.free  I2B req y add data I2B req n I2B   2data.present 

ES Seminar31 PI1 IB1IB2 PI2 I1 B I2 req y add data  2data.present & B.free 

ES Seminar32 PI1 IB1IB2 PI2 I1 B I2 req y add data  2data.present & B.free  

ES Seminar33 PI1 IB1IB2 PI2 I1 B I2 req y add data  2data.present & B.free  

ES Seminar34 PI1 IB1IB2 PI2 I1 B I2 req y add data  2data.present & B.free  

ES Seminar35 PI1 IB1IB2 PI2 I1 B I2 req y add data  2data.present & B.free  

ES Seminar36 PI1 IB1IB2 PI2 I1 B I2 req y add data  2data.present & B.free  

ES Seminar37 PI1 IB1IB2 PI2 I1 B I2 req y add data  2data.present & B.free  

ES Seminar38 P11 I1  1data.present  no-op  1data.present   1data.present  no-data  1data.present  data  1data.present  P11 Transaction Scheme I1

ES Seminar39 Analysis Issues Determine whether a CTP is bounded. Determine if a CTP can deadlock. Determine if a CTP is well-formed.

Current Status The CTP Model SMV ES Representation Verilog Analysis Verification Simulation; Synthesis Case Studies Modeling

Current Status The CTP Model SMV ES Representation Verilog Analysis Verification Simulation; Synthesis Case Studies Modeling Pankaj Jain Nikhil Jain Kamrul Hasan Talukdar Tran Tuan Anh Ge Zhiguo

ES Seminar42 Future Work Add multiple instances of a process. –Object features Add timing constraints. Develop the computational model. –Interactions with environment (sense, actuate) –Computational steps (control law) –Schedulability is a key issue. HW/SW Partitioning; Architectural mapping; Synthesis?