1

Emergency Vehicle Awareness System

(EVAS)

And

Model Based Systems Engineering

DOCUMENT NUMBER: RELEASE/REVISION: RELEASE/REVISION DATE:

SE401-RMB-001 Initial 10 May 2010

CONTENT OWNER:

Robert Brown

Student ID: rmbyh5

Missouri University of Science & Technology (MS&T)

Spring Semester 2010

2

ISSUE RECORD

Revisions to this document will be affected either by re-issue of the document in its entirety, or by

amendment list action.

ISSUE INCORPORATED

BY

DATE REMARKS

Initial Robert Brown 10 May 2010

3

TABLE OF CONTENTS

Page

1.0 Scope ....................................................................................................................................... 4

2.0 Reference Documents ............................................................................................................. 4

3.0 General Description of the EVAS .......................................................................................... 5

3.1 Background ................................................................................................................. 5

3.2 Customer Need ........................................................................................................... 6

3.3 EVAS Model Folder Structure ................................................................................... 7

3.4 Customer Requirements .............................................................................................. 8

3.5 Emergency Vehicle Awareness System (EVAS) ....................................................... 8

3.5.1 EVAS Requirements ..................................................................................... 8

3.5.2 EVAS Block Definition Diagram ................................................................. 9

3.5.3 EVAS Internal Block Diagram ..................................................................... 9

3.5.4 EVAS Use Case .......................................................................................... 10

3.6 Emergency Vehicle Awareness Subsystems (EVASubsystems) ............................. 11

3.6.1 Requirements ............................................................................................... 11

3.6.2 Emergency Vehicle (EV) ............................................................................ 11

3.6.2.1 Block Definition Diagram ...................................................................... 11

3.6.2.2 EV Use Case ........................................................................................... 12

3.6.2.3 EV Sequence Diagram ............................................................................ 13

3.6.2.4 EV Activity Diagrams ............................................................................ 14

3.6.3 Cell Phone (CP) ........................................................................................... 15

3.6.3.1 CP Use Case ........................................................................................... 15

3.6.3.2 CP Activity Diagram .............................................................................. 15

3.6.4 Intersection Subsystem (IS) ........................................................................ 16

3.6.4.1 IS Use Case ............................................................................................. 16

3.6.4.2 IS Activity Diagram ................................................................................ 16

4

1.0 Scope

This paper describes the use of SysML graphical modeling language to support the analysis and design

of the Emergency Vehicle Awareness System (EVAS). Artisan Studio screen shots were captured to

illustrate the development of the EVAS using SysML diagrams that include the following:

- Requirements Diagrams

- Activity Diagrams

- Sequence Diagrams

- Use Cases

- Block Definition Diagrams

- Internal Block Diagrams

- Package Diagrams

2.0 Reference Documents

The documents listed below where used during the development of the EVAS using MBSE:

Document Number Description

ISBN:

978-0-12-3478607-4

A Practical Guide to SysML, by Sanford Friedenthal, Alan

Moore, and Rick Steiner

ISBN:

978-0-12-374274-2

Systems Engineering with SysML/UML, Modeling,

Analysis, Design; by Tim Weilkiens

Artisan Studio ®, SysML Tutorial, Version 7.1-a; Dated

15 December 2009

5

3.0 General Description of the EVAS

3.1 Background

Many emergency response vehicles (especially those of police, fire and ambulance services) are likely

to be fitted with audible and visual warning devices, which are designed to facilitate their movement

through traffic to reach their destination, and to provide some protection on the scene.

In the United States alone, more than 156,000 accidents involving emergency vehicles occurred at

intersections from early 1980s to 1995, resulting in 6,550 deaths. National Safety Board statistics

show that 40% of firefighters killed in the line of duty died in accidents on the way to an incident. The

majority of these accidents are at intersections.

This may be due to increased traffic in our cities, better sound proofing in cars, or even confusion on

the part of the public.

“Confusion, inattention, mobile phones, car radios, hearing impairment, distracting children and failure

to hear sirens and see flashing lights are just a few of the many causes of serious accidents that result in

multi-million-dollar lawsuits against cities and states.”

6

3.2 Customer Need

The public is in need of a system that provides an early warning of approaching emergency vehicles

(EV) at major intersections to decrease the number of accidents that involve EV and to increase the

availability and safe arrival of emergency personnel to the consumer in need.

Figure 3.2-1 – Intersection Diagram, is an illustration of an EV approaching an intersection.

Figure 3.2-1 Intersection Diagram

EV 1

2 3

1 – EV

2 – Intersection Sensors

3 – Cell Phone Users

7

3.3 EVAS Model Folder Structure

The EVAS Model was organized into a

“Tiered” Structure as shown to the left:

- Tier 0 – Customer

- Tier 1 – System

- Tier 2 – Subsystem

- Tier 3 – Components

Using the Tier Structure in the model would

support the same type of organization I

would use in DOORS for all requirements

and requirements traceability.

Within each folder (or package) there

includes block definition diagrams and

folders for Interfaces, Requirements, and

Use Cases.

8

3.4 Customer Requirements

3.5 Emergency Vehicle Awareness System (EVAS)

3.5.1 EVAS Requirements

9

3.5.2 EVAS Block Definition Diagram

The EVAS is decomposed into three independent subsystems:

(1) Emergency Vehicles (Police, Fire, and Ambulance)

(2) Department of Transportation (Intersection Subsystems)

(3) Telecommunication Industry (Cell Phone Subsystems)

3.5.3 EVAS Internal Block Diagram

10

3.5.4 EVAS Use Case

The emergency vehicles (police, fire, ambulance) would provide the origin to the EVAS. EVs are

fitted with audible and visual warning devices (sirens and flashing lines), which are designed to

facilitate their movement through traffic and to provide some protection on the scene.

However, to increase the protection to the EV, additional capabilities need to be integrated into the EV.

The concept would involve transmitting a signal (Artisan Variable: evaSignal) that will be received by

the intersection subsystems (IS) and the cell phone subsystems (CP) to warn drivers and pedestrians

that the EV is approaching an intersection.

11

3.6 Emergency Vehicle Awareness Subsystems (EVASubsystems)

3.6.1 Requirements

3.6.2 Emergency Vehicle (EV)

3.6.2.1 Block Definition Diagram

12

3.6.2.2 EV Use Case

13

3.6.2.3 EV Sequence Diagram

14

3.6.2.4 EV Activity Diagrams

15

3.6.3 Cell Phone (CP)

3.6.3.1 CP Use Case

3.6.3.2 CP Activity Diagram

16

3.6.4 Intersection Subsystem (IS)

3.6.4.1 IS Use Case

3.6.4.2 IS Activity Diagram