by manuel c. salas advisor: dr. bernard p. zeigler university of arizona 2008

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

Upload: cory-carson

Post on 20-Jan-2016

224 views

Category:

Documents


0 download

TRANSCRIPT

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

By Manuel C. Salas

Advisor: Dr. Bernard P. ZeiglerUniversity of Arizona

2008

Page 2: 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

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

• 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.

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

• 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.

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

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

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

• Alternatives to the SDLC methodologies.

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

• 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.

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

• 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 .

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

• 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.

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

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

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

ID RequirementText

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.

4The Generator shall send data every 1 second.

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

SESMicroRepresentation1. 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!

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(structure)

Generate DEVS

Models (behavio

r)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al 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!

active

passive

start

Generator

output GenData

external event

internal event

output event

passive

stop

stop

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

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

Define Requireme

nts

Define Requireme

nts

Extract Structural Aspects

Extract Structural Aspects

Capture Spreadshe

et Data

Generate FD-

DEVS Models

(behavior)

Generate DEVS

Models (structur

e)

UpdatePES

Transform PES to

DEVSJAVA

Create Test

Models

Verify Created Models

Simulate

Extract Behavior

al Aspects

Extract Behavior

al Aspects

Page 23: By Manuel C. Salas Advisor: Dr. Bernard P. Zeigler University of Arizona 2008
Page 24: By Manuel C. Salas Advisor: Dr. Bernard P. Zeigler University of Arizona 2008
Page 25: By Manuel C. Salas Advisor: Dr. Bernard P. Zeigler University of Arizona 2008

• 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.

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

• 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.

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

• 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.

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