R-PMS System Use Cases : Model . R-PMS System - EPMS/KANPAV : System
Use Case - KANPAV-06 Normalize Highway Segment Data link
Properties |
Name | Value | ||||||||||||
Description |
This Use Case represents the need for the Scan Data to be normalized such that data from one segment of the KHS can be directly compared to data from another KHS segment. The normalization process can be built upon other external normalization procedures or can be a singular process. |
||||||||||||
Transit From |
|
||||||||||||
Transit To |
|
||||||||||||
Id | UC46 | ||||||||||||
Abstract | false | ||||||||||||
Leaf | false | ||||||||||||
Root | false | ||||||||||||
Stereotypes | Modeling, UseCase | ||||||||||||
Justification | In order to compare segments across the various data elements it is necessary to normalize the data elements using such techniques as the Equivalent Thickness (ET) of the pavement and identified possible corrective actions | ||||||||||||
Business Model | false | ||||||||||||
Primary Actors | Actor - KDOT PMS Modeler | ||||||||||||
Status | Identify | ||||||||||||
Rank | High |
Relationships Summary |
Extension Points |
Name | Value | ||
Name | Calculate Road Families | ||
Sequence Number | -1 |
Scenario |
Steps | |||
1. ![]() |
|||
2. SYSTEM Utilizing Current Year and Historical Scan data | |||
2.1. Identify Normalization Scheme regarding each data element as well as across the data vector | |||
2.1.1. Individual Data Elements Required: | |||
2.1.1.1. Roughness | |||
2.1.1.2. Rutting | |||
2.1.1.3. Faulting | |||
2.1.1.4. Cracking | |||
2.1.1.5. Joint Distress | |||
2.1.2. Individual Data Elements As Needed: | |||
2.1.2.1. Last Major Action Data | |||
2.1.2.2. Cross Slope Data | |||
2.1.2.3. Structure Data | |||
2.1.2.4. Traffic Data | |||
2.1.2.5. etc. | |||
2.2. Cross segment normalize the data based upon the Normalization Scheme |
Details |
Name | Value | ||
Level | Summary | ||
Complexity | High | ||
Use Case Status | Initial | ||
Implementation Status | Scheduled | ||
Preconditions | |||
Post-conditions | |||
Author | Rick Miller and Jerry W. Manweiler, Ph.D. | ||
Assumptions |
Tagged Values |
Name | Type | Value | |||
Level | Ad Hoc Enumeration | ||||
Complexity | Ad Hoc Enumeration | ||||
Use Case Status | Ad Hoc Enumeration | ||||
Implementation Status | Ad Hoc Enumeration | ||||
Preconditions | Multi-line Text | ||||
Post-conditions | Multi-line Text | ||||
Author | Text | ||||
Assumptions | Multi-line Text |
References |
File Name | Description | ||
|
Relationships Detail |
Name | Value | ||||||||||||||||||||||||||||||
Name | |||||||||||||||||||||||||||||||
From |
|
||||||||||||||||||||||||||||||
To |
|
||||||||||||||||||||||||||||||
Transit From |
|
||||||||||||||||||||||||||||||
Abstract | false | ||||||||||||||||||||||||||||||
Final Specialization | false | ||||||||||||||||||||||||||||||
Leaf | false | ||||||||||||||||||||||||||||||
Visibility | Unspecified | ||||||||||||||||||||||||||||||
Derived | false |
Name | Value | ||||||||||
Name | |||||||||||
From |
|
||||||||||
To |
|
||||||||||
Transit From |
|
||||||||||
Visibility | Unspecified | ||||||||||
Stereotypes | Extend |
Name | Value | ||||||||||
Name | |||||||||||
From |
|
||||||||||
To |
|
||||||||||
Transit From |
|
||||||||||
Visibility | Unspecified | ||||||||||
Stereotypes | Include |
Appears In |
Diagram | |||
|