USN-1.1 Development of USN Embedded Software based on Model-Driven Approach Lim, Dong-Jin Hanyang University Feb. 14, 2008.

Slides:



Advertisements
Similar presentations
Operating Systems Manage system resources –CPU scheduling –Process management –Memory management –Input/Output device management –Storage device management.
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
UML Diagrams Jung Woo. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, business.
Overview: Chapter 7  Sensor node platforms must contend with many issues  Energy consumption  Sensing environment  Networking  Real-time constraints.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
TOSSIM A simulator for TinyOS Presented at SenSys 2003 Presented by : Bhavana Presented by : Bhavana 16 th March, 2005.
Where Do the 7 layers “fit”? Or, where is the dividing line between hdw & s/w? ? ?
The Rhapsody in C++ Tool Training "Essential" © I-Logix v2.3 25/9/2000 EI-1 “Essential” Rhapsody in C++ Introduction.
Contiki A Lightweight and Flexible Operating System for Tiny Networked Sensors Presented by: Jeremy Schiff.
NIOS II Ethernet Communication Final Presentation
Chapter 1 and 2 Computer System and Operating System Overview
HAS. Patterns The use of patterns is essentially the reuse of well established good ideas. A pattern is a named well understood good solution to a common.
© Copyright Eliyahu Brutman Programming Techniques Course.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
© 2008 IBM Corporation Behavioral Models for Software Development Andrei Kirshin, Dolev Dotan, Alan Hartman January 2008.
UML. Overview of UML Diagrams Structural : element of spec. irrespective of time Class Component Deployment Object Composite structure Package Behavioral.
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
Intro to dot Net Dr. John Abraham UTPA – Fall 09 CSCI 3327.
MoteWorks Installation
Chapter 5 – System Modeling
Smith’s Aerospace © P. Bailey & K. Vander Linden, 2005 Architecture: Component and Deployment Diagrams Patrick Bailey Keith Vander Linden Calvin College.
1 I-Logix Professional Services Specialist Rhapsody IDF (Interrupt Driven Framework) CPU External Code RTOS OXF Framework Rhapsody Generated.
Slides created by: Professor Ian G. Harris Test and Debugging  Controllability and observability are required Controllability Ability to control sources.
PowerDesigner 与对象建模. 2 Why Using UML? Visually define and communicate the structure and behavior of an application Represent systems using Object-Oriented.
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.
CSE 403, Spring 2007, Alverson Software Architecture “Good software architecture makes the rest of the project easy.” McConnell, Survival Guide.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
NIOS II Ethernet Communication Final Presentation
Rhapsody V4.2 "Specialist" Tool Training © I-Logix /08/20031 Specialist Rhapsody Getting Rhapsody In C generated code to run.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Documenting Software Architectures 1.Uses and Audiences for Architecture Documentation Architecture documentation serves as a means of education Architecture.
TAL7011 – Lecture 4 UML for Architecture Modeling.
ARTIFACT UML Actor A Use Case 1 Use Case 2 Actor B Document FileManager GraphicFile File Repository DocumentList FileList Customer name addr withdraw()
I-Logix Proprietary and Confidential CPU External Code RTOS OXF Framework Rhapsody Generated Code CPU External Code IDF Framework Rhapsody Generated Code.
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
Slide 1 CSC450 Review & Summary Slides adapted from various sources.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Introduction to UML and Rational Rose UML - Unified Modeling Language Rational Rose 98 - a GUI tool to systematically develop software through the following.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
Unified Modeling Language. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems,
Low Power Management for CC2430 Jinho Son Real-Time System Lab.
Low Power Sensor Node Design with MSP430 + CC2520 YoonMo Yeon
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
Software Architecture of Sensors. Hardware - Sensor Nodes Sensing: sensor --a transducer that converts a physical, chemical, or biological parameter into.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Rhapsody 2003년 3월 12일 배대호.
CC2430 module Jinho Son Real-Time System Lab.
UML Diagrams By Daniel Damaris Novarianto S..
UML Diagrams Jung Woo.
Online Shopping APP.
CMPE419 Mobile Application Development
UML dynamic Modeling (Behavior Diagram)
Behavioral Models for Software Development
Unified Modeling Language
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Analysis models and design models
Chapter 7 –Implementation Issues
Appendix A Object-Oriented Analysis and Design
CMPE419 Mobile Application Development
Presentation transcript:

USN-1.1 Development of USN Embedded Software based on Model-Driven Approach Lim, Dong-Jin Hanyang University Feb. 14, 2008

USN-1.2 V-Development Process

USN-1.3 Model-Based / Model-Driven Design  Model?

USN-1.4

USN-1.5 UML 2.0 Diagrams Communication Diagrams Sequence Diagrams Interaction Diagrams Class Diagrams Deployment Diagrams Component Diagrams Object Diagrams Structural Diagrams State Machine Diagrams Timing Diagrams Activity Diagrams Behavioral Diagrams Use Case Diagrams Package Diagrams Structure Diagrams Interaction Diagrams

USN-1.6 Use Case Diagram This diagram shows what the system does and who uses it.

USN-1.7 Sequence Diagram Sequence Diagrams show how instances communicate over time.

USN-1.8 Class Diagram Class diagrams show classes and relations between them.

USN-1.9 Object Diagram Object Diagrams show instances of classes and show which ones are linked to others at run time.

USN-1.10 State Machine Diagram State machines are used when we need to wait until something happens before going to a different state.

USN-1.11 Activity Diagram Activity diagrams are used to describe behavior for operations, classes or use cases. As soon as one activity finishes the next one starts.

USN-1.12 Timing Diagram A Timing Diagram shows the timing between objects.

USN-1.13  The Rhapsody framework is a collection of base classes that are used by the code generated from a user’s model.  There are two main parts to this framework:  The Object eXecution Framework which is the part of the framework that will always be linked into the final generated code  The Animation and Tracing Framework, which is only used when animating or tracing and as such is less important to understand than the OXF. The Framework CPU External Code RTOS OXF Framework Rhapsody Generated Code

USN-1.14 The Object eXecution Framework  There are three main parts to the Object eXecution framework: 1. Event Driven Framework 2. Container Classes 3. Operating System Adapter Layer Event Driven Framework Operating System Adapter Layer Container Classes CPU External Code RTOS OXF Framework Rhapsody Generated Code

USN-1.15 Interrupt Driven Framework  By using the Interrupt Driven Framework (IDF), it is possible to run Rhapsody in C without the need for an Operating System  The IDF can replace the OXF and RTOS  It generates smaller code. For example a simple stopwatch example takes 20K on an ARM7 (framework + libraries + generated code)  Requires just a periodic interrupt to be setup (so that timeouts can be used in Statecharts) CPU External Code IDF Framework Rhapsody Generated Code

USN-1.16 IDF model  Everything in this model is independent of the actual compiler and cpu used.  Everything that depends on the cpu and compiler is included in a separate “adapter” model

USN-1.17 IDF model

USN-1.18 USN Platforms  Crossbow Micaz  Atmega128L(128K Flash, 4K Ram)+Chipcon2420  S/W: UC Berkeley TinyOS 2.0  MoteView, MoteWorks

USN-1.19 USN Platforms  TI Chipcon CC2420DB  ATmega128L+Chipcon2420  S/W: WinAVR, RF lib (source)  ZigBee Stack: Z-Stack(IAR), TI MAC

USN-1.20 USN Platforms  TI Chipcon CC2420DB  MSP430(16bit)+Chipcon2420  ZigBee Stack: Z-Stack(IAR), TI MAC

USN-1.21 USN Platforms  TI Chipcon CC2430DK  SoC: 8051 core + CC K Ram+32K/64K/128K Flash  ZigBee Stack: Z-Stack(IAR), TI MAC

USN-1.22 USN Platforms  Radiopulse MG2400  MG2400(8051+Zigbee Tranceiver+4K Ram)+64K Flash  S/W: Keil uVison2, ZigBee Full Stack  HW(128K flash) & SW upgrade

USN-1.23 USN Platforms  Atmel AT86RF230  ATmega1281V(128K Flash, 8K RAM, 3.3V)+AT86RF230  ZigBee Stack: MeshNetics(AVR-GCC), MAC(IAR, AVR- GCC)

USN-1.24 USN Platforms  Silicon Labs  8051(128K flash)+CC2420  ZigBee Stack: Keil 8051

USN-1.25 USN Platforms  RENESAS  M16C(16bit)+CC2420  ZigBee Stack: HEW  3 rd Party Compiler: IAR

USN-1.26 USN Platforms  K-mote(MSP430F1611+CC2420) : Crossbow TelosB compatible  ATmega128L+CC2420

USN-1.27 Development of Framework  ATmega128L+CC2420, Z-Stack/MAC lib, IAR compiler  ATmega1281V+AT86RF230, MAC source, IAR compiler  MSP430+CC2420, Z-Stack/MAC lib, IAR compiler

USN-1.28 ATmega128+CC2420+TI Z-Stack

USN-1.29 ATmega128+CC2420+TI Z-Stack

USN-1.30 ATmega128+CC2420+TI RF lib (source)