Aimee Pail Brown Subrata Acharya

Slides:

Advertisements

Similar presentations

Depicting EHRs Immunization capability HL7 WGM – September 11, 2006 Immunization Storyboard project update.

Advertisements

Sequential Logic Circuits. Set-Reset Latch The Set-Reset latch or bistable is a simple sequential logic circuit that remembers what has happened to the.

Modeling Main issues: What do we want to build How do we write this down ©2008 John Wiley & Sons Ltd. vliet.

Systems Documentation Techniques

Information System Design IT60105

1 SWE Introduction to Software Engineering Lecture 16 – System Modeling An Example.

COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk Modeling methodology for real estate transactions Radoš Šumrada Faculty.

Slide 7B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.

IBM Rhapsody Simulation of Distributed PACS and DIR systems Krupa Kuriakose, MASc Candidate.

Topic 5 – Sensors and Monitoring Systems 1)TechMed scenario covers Sensors and their uses in hospitals In the scenario: “A patient-monitoring system is.

OBJECT ORIENTED METHODOLOGIES Week04. Agenda… © Jerry Kotuba SYST39409-Object Oriented Methodologies 2  This week  Quiz 1  Take up ICE-01  Check “Grade.

1 SAD2 - UML 2 nd Lecture Sequence Diagram and other dynamic views Lecturer: Dr Dimitrios Makris

Homework 3 – Sample Solution Targeted Application –Electronic medical records (EMR) system in the “Designing Human-Centered Distributed Information Systems”

Object-Oriented Analysis and Design An Introduction.

Chapter 4 – Requirements Engineering Lecture 3 1Chapter 4 Requirements engineering.

Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.

1 Interaction diagrams and activity diagrams Speaker: 陳奕全 Real-time and Embedded System Lab 15 August 2002.

Paper written by Flavio Oquendo Presented by Ernesto Medina.

Context Diagrams. What are dataflow diagrams used for? Dataflow diagram  A graphical representation that depicts information flow and the transforms.

Systems Analysis and Design in a Changing World, 3rd Edition

1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.

An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.

Lecture 18: Object-Oriented Design – Interaction and State Diagrams Anita S. Malik Adapted from Schach (2004) Chapter 12.

Object Oriented Methodologies

What to remember from Chap 13 (Logical architecture)

1 On To Object Design Chapter 14 Applying UML and Patterns -Craig Larman.

The Play Team Registered Charity Number: The Play Team is made up of people who specialise in helping children and young people Registered Charity.

Activity 4 Data flow diagram of a school attendance system

BPEL Business Process Engineering Language A technology used to build programs in SOA architecture.

UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.

CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.

A Student Guide to Object-Oriented Development

Dynamic Models Sequence Diagrams Collaboration Diagrams Activity Diagrams.

Data Flow Diagrams Ramzy Kaoukdji. What is a Data Flow Diagram? - A graphical Representation of the flow of data through an information system, modeling.

CONTENTS: 1.Abstract. 2.Objective. 3.Block diagram. 4.Methodology. 5.Advantages and Disadvantages. 6.Applications. 7.Conclusion.

Summary from previous lectures

Activity Diagramming by Andrzej Rosolski Stanisław Gliniewicz.

Data Flow Diagrams A data flow diagram is a tool that depicts the flow of data through a system and the work or processing performed by the system.

JIT Medical Application Project IC System Design Matching Between IC Cards & IC System Zhoulan Zhang

VIEWS b.ppt-1 Managing Intelligent Decision Support Networks in Biosurveillance PHIN 2008, Session G1, August 27, 2008 Mohammad Hashemian, MS, Zaruhi.

Program Design & Development EE 201 C7-1 Spring

Modeling of Service Oriented Architecture: From Business Process to Service Realization Petr Weiss and Marek Rychlý Brno University of Technology, Faculty.

Nursing – Engineering Collaboration Ideas Jill Steiner Sanko, PhD, MS. ARNP, CHSE-A Susana Barroso-Fernandez, PhD(c), RN, BSN Research reported in this.

Lab 3 Data Flow Diagram CPIT 250 System Analysis and Design.

Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.

Elaboration: Iteration 3. Elaboration: Iteration 3 Basics Inception and iteration-1 explored many basic OOA/D modeling basics. Iteration-2 narrowly emphasized.

GCSE COMPUTER SCIENCE Computers

Jim Fawcett CSE681 – Software Modeling and Analysis Fall 2017

Chapter 5 System modeling

Main issues: • What do we want to build • How do we write this down

BTS430 Systems Analysis and Design using UML

SOFTWARE DESIGN AND ARCHITECTURE

Chapter 11: Collaboration Diagram - PART1

Unified Modeling Language

ISE 428 ETM 591 IDM 404 VISIO Symbols for Quality Engineering and Quality Management Dr. Joan Burtner, CQE Associate Professor of Industrial Engineering.

UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.

Specifying collaborative decision-making systems

Use Case Modeling - techniques for detailing use cases

Requirements To Design In This Iteration

How do we convince people that in programming simplicity and clarity —in short: what mathematicians call "elegance"— are not a dispensable luxury, but.

Function Notation “f of x” Input = x Output = f(x) = y.

Paper written by Flavio Oquendo Presented by Ernesto Medina

Engineering Quality Software

Introduction to Logic diagrams and truth tables

Ch. 28 Larman UML & Patterns

Introduction to Logic diagrams and truth tables

On to Object Design c. 14.

Chapter 4 Sequence Diagrams

Presentation transcript:

Aimee Pail Brown Subrata Acharya Just in Time E-Learning for Medical Application Milestone 2: Scenarios Formalized for Able and Unable Patient Aimee Pail Brown Subrata Acharya

Introduction Milestone 1 Milestone 2 Create two scenarios for JiT Medical Application Unable Patient Scenario Able Patient Scenario Create UML sequence diagram for scenarios Milestone 2 Formalize the scenarios Timing constraints Orchestration and Choreography Software Tool MagicDraw (12.5 EAP beta 1) Provides tools to draw UML, orchestration, choreography diagrams Representation of scenarios via pi-Calculus

Scenario – Unable Patient Sensor Equipment takes video/picture of Patient Data sent to Condition and Record Agent for storage Sensor detects alarm and alerts Hospital Hospital receives alarm and alerts Physician and Nurse Physician queries Patient’s Current Condition for Diagnosis Physician Requests Nurse/Dispatch to perform action After action is performed, Doctor again queries Patient’s condition for outcome of action

Sequence Diagram - UML

Orchestration – Execution Flow

Choreography – Agent Collaboration

Scenario – Able Patient Patient takes reading (temperature) by sensor equipment Data sent to Condition and Record Agent for storage Sensor detects alarm and alerts Hospital Hospital receives alarm and alerts Physician and Nurse Physician queries Patient’s Current Condition for Diagnosis Physician sends an Action to be performed by Patient After action, Physician again queries for updated Condition of Patient

Sequence Diagram - UML

Orchestration – Execution Flow

Choreography – Agent Collaboration

Formalization using Pi-Calculus State Transition of Data & Alert Propagation

Formalization using Pi-Calculus Sensor Data Propagation Notation: (Patient(data!); Sensor(data?,data!); Condition(data?,data!); Records(data?))* Alarm Propagation Notation: Patient(data!); Sensor(data?,alarm!); (Condition(alarm?,alarm!); Records(alarm?))|(Hospital(alarm?, alarm!);(Expert(alarm?)|Nurse(alarm?))) Notation Symbols: ; - sequential composition ? – input data ! – output data * - iteration | - parallel composition

IC Card team takes on from here…. Thank You!!!