By Manuel C. Salas Advisor: Dr. Bernard P. Zeigler University of Arizona 2008.

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

ECOE 560 Design Methodologies and Tools for Software/Hardware Systems Spring 2004 Serdar Taşıran.
Object-Oriented Software Development CS 3331 Fall 2009.
CS487 Software Engineering Omar Aldawud
Ch 3 System Development Environment
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
DEVS-Based Simulation Web Services for Net-Centric T&E Saurabh Mittal, Ph.D. Jose L. Risco-Martin*, Ph.D. Bernard P. Zeigler, Ph.D. Arizona Center for.
ECE Synthesis & Verification1 ECE 667 Spring 2011 Synthesis and Verification of Digital Systems Verification Introduction.
Model-based Analysis of Distributed Real-time Embedded System Composition Gabor Madl Sherif Abdelwahed
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
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
Principle of Functional Verification Chapter 1~3 Presenter : Fu-Ching Yang.
5/24/011 Advanced Tool Integration for Embedded Systems Assurance Insup Lee Department of Computer and Information Science University of Pennsylvania.
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Introduction to Software Testing
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
1 Introduction Chapter 1. 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.
Xactium xDSLs Run Models Not Code Tony Clark
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
© Siemens AG, CT SE 1, Dr. A. Ulrich C O R P O R A T E T E C H N O L O G Y Research at Siemens CT SE Software & Engineering Development Techniques.
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
Chapter 1 The Systems Development Environment
CLEANROOM SOFTWARE ENGINEERING.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers Unit 11 Slide 1 Chapter 1 The Systems Development Environment.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
1 SYS366 Lecture 1: Introduction to Systems. 2 What is Software Development? Software Development implies developing some software – but it does not involve.
DEVS Namespace for Interoperable DEVS/SOA
Reliable Design of Safety Critical Systems Dr. Abhik Roychoudhury School of Computing
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Framework for the Development and Testing of Dependable and Safety-Critical Systems IKTA 065/ Supported by the Information and Communication.
June 05 David A. Gaitros Jean Muhammad Introduction to OOD and UML Dr. Jean Muhammad.
Team Think For You. Outline  Introduction  Process  Requirements Engineering  Architecture  Detailed Design  Testing  Demo  Extensibility  Conclusions.
Formalized Model Development & Test Generation: Key Role of Abstraction Bernard P. Zeigler Arizona Center for Integrative Modeling and Simulation (ACIMS)
Haptic Interfaces and Force-Control Robotic Application in Medical and Industrial Contexts Applicants Prof. Doo Yong Lee, KAIST Prof. Rolf Johansson,
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Software Debugging, Testing, and Verification Presented by Chris Hundersmarck November 10, 2004 Dr. Bi’s SE516.
Unifying Discrete and Continuous Simulation with Discrete Events: DEVS as the Next Modeling Standard Bernard P. Zeigler Arizona Center for Integrative.
DUNIP: DEVS Unified Process Integrated Development and Testing in Service Oriented Architecture Dissertation Defense Saurabh Mittal April 20, 2007 ECE.
An Overview of the Arizona Center for Integrative Modeling and Simulation (ACIMS) University of Arizona Arizona State University Bernard P. Zeigler
© 2005 by Prentice Hall Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
OBJECT-ORIENTED SOFTWARE DEVELOPMENT PROCESS BTS430 Systems Analysis and Design using UML.
PRJ566 Project Planning & Management Software Architecture.
Chapter 27 The Engineering Design Process. Learning Objectives Describe the various factors that are changing the design process Discuss the steps in.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.
DEVS and SES as a Framework for Modeling and Simulation Tool Development Bernard P. Zeigler Arizona Center for Integrative Modeling and Simulation University.
The Systems Development Environment Systems Analysis and Design II.
International Telecommunication Union © ITU-T Study Group 17 Integrated Application of SDL Amardeo Sarma NEC Europe Ltd.
Transforming DEVS to Non-Modular Form For Faster Cellular Space Simulation Arizona Center for Integrative Modeling and Simulation Electrical and Computer.
Approach and Techniques for Building Component-based Simulation Models Bernard P. Zeigler, Ph.D. Hessam S. Sarjoughian, Ph.D. Arizona Center for Integrative.
Hardware/Software Co-Design of Complex Embedded System NIKOLAOS S. VOROS, LUIS SANCHES, ALEJANDRO ALONSO, ALEXIOS N. BIRBAS, MICHAEL BIRBAS, AHMED JERRAYA.
Www. senseglobal.com 1 MS4 Modeling Environment (MS4 Me) System Entity Structure based DEVS Modeling and Simulation environment July, 2015 MS4 Systems,
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
Object-Oriented Analysis & Design
Chapter 1 The Systems Development Environment
Object-Oriented Software Engineering Using UML, Patterns, and Java,
V-Shaped SDLC Model Lecture-6.
Chapter 1 The Systems Development Environment
Designing Software for Ease of Extension and Contraction
Baisc Of Software Testing
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
A GUI Based Aid for Generation of Code-Frameworks of TMOs
A Development-Testing-Maintenance model for software evolution
Presentation transcript:

By Manuel C. Salas Advisor: Dr. Bernard P. Zeigler University of Arizona 2008

Motivation Objectives Background Contributions AutoDEVS AutoDEVS to Autonomous Road Survey (DEMO) Conclusions Future Work

Improve systems development to reduce human effort, time constraints, and production costs. Unify every step of development and integration from business modeling to application deployment. Overcome the "incoherence problem" between different stages of the development process. Introduce automation in the development of systems to increase productivity and hide complexity.

To provide a methodology to increase productivity by automating the life cycle process of a system. To exploit model continuity to reduce incoherence between development phases. To help developers identify and focus on the most critical parts of the system. To provide a methodology that allows developers to create high performance distributed real-time systems that are extensible flexible, interoperable, reusable, and reliable.

Many Organizations make use of the Systems Development Life Cycle (SDLC) methodologies.

Alternatives to the SDLC methodologies.

M & S Development Tools: Rational Rose Real-Time Pros: - Unifies the project team by providing a set of integrated tools. - Automatic code generation to reduce development risk. - UML model debugger Cons: - Focuses on design not on requirements. - Doesn’t support concurrency in Statechart Diagrams. - Doesn’t support Activity Diagrams, i.e. simulation, verification, test case gen.

Introduce AutoDEVS as a methodology to automate the development of complex, distributed, real-systems. Demonstrate that this methodology overcomes the “incoherence problem” between different stages of design thru “model continuity”. Develop a distributed simulation-based system for an autonomous robotic survey to show the powers of AutoDEVS. Provide a solution to automate the constant road supervision needed to improve productivity and reduce human efforts in a mine.

AutoDEVS is based on the Discrete Event Specification System (DEVS) and SES formalism. Provides a Methodology to: Automate the development of DEVSJAVA models to increase productivity and focus on the real aspects of the system. Exploit model continuity to reduce “incoherence” between development phases by following the “Modeling-Simulation- Execution approach. Go from a “spreadsheet” containing requirements specifications to a real-time executing system. Allow alternative models to be selected, generated and evaluated.

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects IDRequirementText 1 Generators shall be GpsDataGenerator, SurfaceDataGenerator, and WirelessDataGenerator. 2 All the Generators components shall be started by the Generators. 3 All the Generators components shall be stopped by the Generators. 4 The Generator shall send data every 1 second.

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects SESMicroRepresentation 1. From the GenComponent perspective, Generators are made of more than one Generator! 2. A Generator can be GpsData, SurfaceData, or WirelessData in class! 3. From the Component perspective, Generator sends GenData to Generators!

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (structure) Generate DEVS Models (behavior) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects FDDEVSRepresentation 1. Generator: to start passivate in passive! 2. Generator: when in phase passive and receive Start then go to active! 3. Generator: when in active and receive Stop then go to passive! 4. Generator: hold in active for time 1 then output GenData and go to active!

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects

Define Requirements Extract Structural Aspects Capture Spreadsheet Data Generate FD-DEVS Models (behavior) Generate DEVS Models (structure) Update PES Transform PES to DEVSJAVA Create Test Models Verify Created Models Simulate Extract Behavioral Aspects

AutoDEVS provides a methodology to automate systems development. AutoDEVS methodology provides a natural and effective way to model distributed real-time systems’ structure, behavior and timeliness. AutoDEVS methodology raises the importance of simulation to analyze and predict results before deployment. AutoDEVS allows developers to focus more on the core of the system.

AutoDEVS combines DEVS and SES formalisms to allow the creation of structured information hierarchically and efficiently. AutonomousRoadSurvey has been developed to show how AutoDEVS overcomes “incoherence problem”. AutoDEVS and ARS motivate the industry to exploit automated systems to improve productivity and reduce human efforts. ARS provides a solution to automate the supervision of roads within a mine.

AutoDEVS: - Integrate with FD-DEVS, SESBuilder and DEVS/SOA. - Provide more automation for the model’s behavioral aspects. - Allow updates without compromising current models. ARS: - Improve algorithms to find roads. - Extend Runner survey information, i.e. “blind areas”, quality of surface, materials found. - Minimize downtime of operation by introducing more Runners to the system. - Automate the execution of Runners to periodically update the Central System and Supervisors.