Self-Cleaning Particulate Filter Project Filter II Team Presenters: Roger Ostrander Steve Van Neste Demo given by: Roger Ostrander.

Slides:



Advertisements
Similar presentations
CS 267: Automated Verification Lecture 8: Automata Theoretic Model Checking Instructor: Tevfik Bultan.
Advertisements

In this presentation you will:
Wireless Phone Tic-Tac-Toe Josh Morelli. Project Description The purpose is to illustrate the interfacing of hardware and wireless phones using standard.
UML: Use Cases Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
Introduction to BizAgi. Slide 2 User Interface (Summary) The user interface for BizAgi resembles Office It uses a similar ribbon The Palette contains.
RA Doc In General Be brief. >50 pages probably means you did something wrong Don’t include everything (shotgun approach) “Crispness” and conciseness are.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Model Checking. Used in studying behaviors of reactive systems Typically involves three steps: Create a finite state model (FSM) of the system design.
Software Testing and Quality Assurance
Adaptive Cruise Control Group 2 Presenters:Lydia Eatmon Ben Deneweth Toby Tripp Craig Vasel.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Automotive Door Controls DOORS 1 Presenter: Hyun-soo Kim, Ketan Patel, David Tkaczyk Demo Given by: David Linsey.
Project Doors Group Doors 3 Presenters: Becky Smith, Tim Hollosy Demo Given by: Tim Hollosy.
Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.
1 SWE Introduction to Software Engineering Lecture 15 – System Modeling Using UML.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
CS 425/625 Software Engineering Software Testing
Project Name Group Name: Customer: Name of Customer Project Manager: Student Name1 Project Facilitator: Student Name1 Customer Liaison/Domain Expert:Student.
16/27/2015 3:38 AM6/27/2015 3:38 AM6/27/2015 3:38 AMTesting and Debugging Testing The process of verifying the software performs to the specifications.
Anti-Lock Braking System ABS1 Presenter: Josh Walworth Demo Given by: Ryan Stephenson.
From Scenarios to Paper Prototypes Chapter 6 of About Face Defining requirements Defining the interaction framework.
Self-Contained Particulate Filter Filter 3 Presenters: Ian Gray, Kyhia Bostic Demo Given by: Nathan Sullivan.
ABS 4 Presenters: Hong Jung, Binh Lai, Matthew Martin, Joe Mongiat, and Travis Ratcliff.
ACSE th Conference The Iconic Programmer Stephen Chen.
New Mexico Computer Science For All More Looping in NetLogo Maureen Psaila-Dombrowski.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Cheng/Dillon-Software Engineering: Formal Methods Model Checking.
Microsoft Access 2000 Creating Tables and Relationships.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
Prepared by Afra`a Sayah. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2.
Automating Database Processing Chapter 6. Chapter Introduction Design and implement user-friendly menu – Called navigation form Macros – Automate repetitive.
 CS 5380 Software Engineering Chapter 8 Testing.
USF college of engineering EEL Engineering Design1 Term & Meeting Info: Spring M 6:30pm – 9:15pm. Angelina Colannino, John Hook, Kjersti.
Computer Science 12 Mr. Jean May 2 nd, The plan: Video clip of the day Review of common errors in programs 2D Arrays.
Dr. Tom WayCSC Testing and Test-Driven Development CSC 4700 Software Engineering Based on Sommerville slides.
Oracle Data Integrator Procedures, Advanced Workflows.
CPS120 Introduction to Computer Programming The Programming Process.
Software Testing Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Visual Basic Programming
Software Testing and Quality Assurance Software Quality Assurance 1.
CSC 480 Software Engineering Lecture 15 Oct 21, 2002.
“The perfect project plan is possible if one first documents a list of all the unknowns.” Bill Langley.
1 SQL - II Data Constraints –Applying data constraints Types of data constraints –I/O constraints The PRIMARY KEY constraints The FOREIGN KEY constraints.
Software Engineering Principles Dr. José M. Reyes Álamo.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Anti-lock Brake System Group 2 Presenters: Christan Balnius, Zain Kazim, Mark Pulver Demo Given by: Brian Lawnichak.
1 Specification A broad term that means definition Used at different stages of software development for different purposes Generally, a statement of agreement.
Software Systems Verification and Validation Laboratory Assignment 4 Model checking Assignment date: Lab 4 Delivery date: Lab 4, 5.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
Application Management Editor. Defining Node and Node Capabilities and Functions. MICA2 Monitor Interface Temperature Light Mic pressure Message Node.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2.
Onboard Diagnostics Diagnostics III Project Manager: Dennis Kelly Documentation Manager: Paul Robinson Facilitator: Richard Ford Research Manager: Arif.
Loops causes program to execute the certain block of code repeatedly until some conditions are satisfied. Suppose you want to execute some code/s 10 times.
Ultrasonic Rangefinder
Group Y Presenters: (indicate roles)
JavaScript: Control Statements.
Group Y Presenters: (indicate roles)
And the text with form..
Arrays, For loop While loop Do while loop
IMPORTANT NOTICE TO STUDENTS:
Testing and Test-Driven Development CSC 4700 Software Engineering
Software testing.
KU College of Engineering Elec 204: Digital Systems Design
FLUENCY WITH INFORMATION TECNOLOGY
Presentation transcript:

Self-Cleaning Particulate Filter Project Filter II Team Presenters: Roger Ostrander Steve Van Neste Demo given by: Roger Ostrander

Unique Feature of System: The Voltage Regulator A controller subsystem that controls current the heating elements during the Cleaning Sequence. Components of unique feature: Timer. Regulator of pulsed current. Element incrementer.

What does feature support? Functionality of Voltage Regulator: controls the ramp-up and ramp down of current to currently selected functional elements. Sample scenario description: (see normal sequence diagram in D.D.)

Key Model The System Monitor Checks the values of the system and says when and when not to clean the filters It is key because Illustrates the primary control logic Demonstrates RPM change functionality Shows the concurrency needs and peer-to- peer relationship requirements

[PressStart = true RevStart = true RPMStart = true GetCS() == false] /BeginCleaningSequence [RPMStart = true GetCS() == true] /BeginCleaningSequence Element Checking RPM Checking Revolutions Checking Pressure Checking

Critical Properties Required Element Failures Required Response to the Failed Element Required Response to Pressure Abnormalities Required Cleaning Sequence Start, Execution and Continuation

Promela and XSpin Results of analysis Both the starting and cleaning functionality of the system was modeled Assertion statements were used to verify that the system started properly, a failed element would be skipped during cleaning, and that the ramp down of current began properly Discussion of results All three critical properties were verified without errors The model ran in Xspin until it ran out of memory

Demo of Prototype High-level features of User Interface: Start/Stop Engine Everything changeable (RPM, etc) “Defaults” button

Scenarios Cleaning Sequence is initiated. Executor check, then send message to Voltage Regulator to start the Cleaning Cycle. Voltage Regulator receives the message to start, it will repeatedly pulse and increment the current until the System Monitor senses the current is between amps. System Monitor sends warning message to Executor.

Scenarios Voltage Regulator begin the ramping down process. Voltage Regulator calls ‘increment current element’ function. The Executor checks if it is >=8, then set Cleaning Sequence to ‘false’. Error encountered(no temperature change ). System Monitor stores failed elements and Voltage Regulator stops Cycle. Voltage Regulator calls Executor to increment the current, when =8, Cleaning Sequence is ended until it is next initiated.