Instructions, Rules and Expectations for Breakout Groups presented by Vassili Alexiadis Cambridge Systematics, Inc.

Slides:



Advertisements
Similar presentations
Classroom Assessment Techniques for Early Alert of Students At Risk Carleen Vande Zande, Ph.D. Academic Leaders Workshop.
Advertisements

DOCUMENT TYPES. Digital Documents Converting documents to an electronic format will preserve those documents, but how would such a process be organized?
MAPPING DATA FLOW DIAGRAMS INTO STRUCTURE CHARTS
Beyond “The System Shall...” A Journey from Good to Great Requirements.
Next Generation Simulation Core Algorithms and Data Sets presented by Vassili Alexiadis Cambridge Systematics, Inc. January 2003 DTFH61-02-R
©GoldSim Technology Group LLC., 2015 Designing Well-Structured and Scalable Models April 2015 Webinar.
1 Introduction to modeling Process modelling. 2 Where are we? #TitleDate 1Introduction ORM modeling Relational modeling
Next Generation Simulation Core Algorithms and Data Sets presented by Vassili Alexiadis Cambridge Systematics, Inc. DTFH61-02-R
CLAReT PERSONAS AND SCENARIOS. When? Personas were used in the CLAReT workshops as a role play activity. Participants were required to assume a persona.
16/13/2015 3:30 AM6/13/2015 3:30 AM6/13/2015 3:30 AMIntroduction to Software Development What is a computer? A computer system contains: Central Processing.
Relations Diagram (or Interrelationship Digraph).
Case-based Reasoning System (CBR)
Cognitive Processes PSY 334 Chapter 8 – Problem Solving May 21, 2003.
Testing an individual module
NGSIM Framework. Objectives  Define simulation framework Simulation package componentsSimulation package components Core model components – NGSIM focusCore.
System Management Network Environment Vehicle Characteristics Traveler Characteristics System Traveler Influencing Factors Traveler: traveler characteristics,
Chapter 1 Program Design
Task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7.
Principles of Procedural Programming
Accounting Information Systems: An Overview
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
QUESTIONNAIRE DESIGN: AN INTRODUCTION By Lizzette Rojas, PhD and Flordeliz Serpa, PhD Non-Profit Evaluation & Resource Center, Inc. (NPERCI)
SpecFlow & Gherkin Behavior Driven Development. Definitions Behavior Driven Development SpecFlow Structure Gerkin Demo Agenda.
- Travel Well Criteria.
Chapter 4 Principles of Quantitative Research. Answering Questions  Quantitative Research attempts to answer questions by ascribing importance (significance)
Instructional Design Brian Newberry. Instructional Design Instructional Design is a systematic process for the creation of educational resources.
Background The Encyclopedio of Life (EOL) is an ROR open source project to create a free, online reference source and database for every one of the 1.8.
Chapter 2 The process Process, Methods, and Tools
Modelling information systems
Business Analysis and Essential Competencies
1M.Sc.(I.T.), VNSGU, Surat. Structured Analysis Focuses on what system or application is required to do. It does not state how the system should be implement.
CVUHSD Linked Learning Summer Institute 2015 Direct Interactive Instruction (DII) and Behaviors of learning and Teaching (BLT)
CHAPTER ONE Problem Solving and the Object- Oriented Paradigm.
Outcome Based Evaluation for Digital Library Projects and Services
CSCI 3140 Module 2 – Conceptual Database Design Theodore Chiasson Dalhousie University.
Creating a Shared Vision Model. What is a Shared Vision Model? A “Shared Vision” model is a collective view of a water resources system developed by managers.
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Chapter 12 Evaluating Products, Processes, and Resources.
Chapter 1 Accounting Information Systems: An Overview Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 1-1.
Measuring the Quality of Decisionmaking and Planning Framed in the Context of IBC Experimentation February 9, 2007 Evidence Based Research, Inc.
Modeling and simulation of systems Model building Slovak University of Technology Faculty of Material Science and Technology in Trnava.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
Chapter 7 Software Engineering Introduction to CS 1 st Semester, 2015 Sanghyun Park.
Chapter 1 Program design Objectives To describe the steps in the program development process To introduce the current program design methodology To introduce.
Methodological Problems in Cognitive Psychology David Danks Institute for Human & Machine Cognition January 10, 2003.
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
Copyright © 2009 First Steps Training & Development, Inc. All rights reserved. 11 Adult Learning Systematic Learning.
Requirements Analysis
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Introduction to Codes, Standards, and Regulations Chattanooga State CC.
Planning Instruction A Review of the Cognitive Domain and Performance Objectives.
Program Design. Simple Program Design, Fourth Edition Chapter 1 2 Objectives In this chapter you will be able to: Describe the steps in the program development.
Quality Improvement Tools for Intervention Determination Presenters: Kris Hartmann, MS Healthcare Analyst, Performance Improvement Projects Don Grostic,
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
 Problem Analysis  Coding  Debugging  Testing.
UNIT – II BUSINESS PROCESS MANAGEMENT
Principles of Quantitative Research
The Systems Engineering Context
Software Engineering Development of procedures and systematic applications that are used on electronic machines. Software engineering incorporates various.
Complexity Time: 2 Hours.
پروتكل آموزش سلامت به مددجو
CSc4730/6730 Scientific Visualization
The Evolution of the Algorithms for Collective Behavior
For University Use Only
CATHCA National Conference 2018
Software Engineering Practice: A Generic View
Chapter 11 Describing Process Specifications and Structured Decisions
Presentation transcript:

Instructions, Rules and Expectations for Breakout Groups presented by Vassili Alexiadis Cambridge Systematics, Inc.

Breakout Groups  Goals Define and rank NGSIM requirementsDefine and rank NGSIM requirements -Focus on practical user needs Map user requirements into algorithm requirementsMap user requirements into algorithm requirements  Methodology Use simple, common language for discussing requirementsUse simple, common language for discussing requirements -Framework: Influencing factors and behavioral algorithms -Scenarios/situations Understood by users, modelers, developersUnderstood by users, modelers, developers

Scenarios and Situations  Scenario A set of influencing factors, which a user wants to model, independent of the state of the systemA set of influencing factors, which a user wants to model, independent of the state of the system Defined using diagrams and frameworkDefined using diagrams and framework Focus on scenarios which are difficult to model correctly with existing toolsFocus on scenarios which are difficult to model correctly with existing tools Identify available data sets and algorithmsIdentify available data sets and algorithms  Situation A set of influencing factors, which a user wants to model, including the state of the systemA set of influencing factors, which a user wants to model, including the state of the system Clarify behavioral algorithm needs, within a scenarioClarify behavioral algorithm needs, within a scenario

Scenario Example Physical Network Environment System Management Elements Vehicle Characteristics Short Merge Area Ice on Surface Aggressiveness “Short Merge with Localized Ice” Traveler Characteristics Influencing factors chosen to define a scenario must be salient. Salient means that these particular influencing factors are the features of the scenario that matter or somehow differ from typical conditions

Desired Outcomes  Users and Modelers Ranked scenariosRanked scenarios  Developers Understanding of fit with commercial productsUnderstanding of fit with commercial products -Input on format and documentation of NGSIM algorithms and data sets -Input on validation procedures  Users, Modelers and Developers Potential sources of algorithms and data setsPotential sources of algorithms and data sets Structural critique: Discuss NGSIM frameworkStructural critique: Discuss NGSIM framework Process critique: Issues with processProcess critique: Issues with process