R-PMS System Use Cases : Model . R-PMS System - Q1 : System
Use Case - T02-06 Create SKID Book and Maps link
Properties |
Name | Value | ||||||||
Description |
KDOT recognizes the importance of good pavement surface friction for safety. Using a locked-wheel skid testing system, KDOT conducts many tests each year. To know where to test and how that data will be stretched over the appropriate coverage area, a process is used to generate a book of locations needing testing and corresponding maps to help locate and track the collection sites. |
||||||||
Transit From |
|
||||||||
Id | UC22 | ||||||||
Abstract | false | ||||||||
Leaf | false | ||||||||
Root | false | ||||||||
Stereotypes | UseCase, PMS Activity | ||||||||
Business Model | false | ||||||||
Primary Actors | Actor - KDOT Van Operator | ||||||||
Status | Identify | ||||||||
Rank | Unspecified |
Relationships Summary |
Use Case Note |
■ Inputs or Prior Activities | |||
• Table GEOM | |||
• GIS Mapping data | |||
■ Actions | |||
• Group PMS IDs in GEOM based on surface mix and year and continuity (even across county lines)... | |||
• Utilize an existing Web App and code base to complete the work | |||
■ Outputs | |||
• Skid book with SKID IDs (i.e. locations) identified |
R-PMS Desired |
Steps | |||
1. ![]() |
|||
2. SYSTEM queries PMS | |||
2.1. Master ID | |||
2.2. LRSKey | |||
2.3. SKID table | |||
3. SYSTEM Returns GIS Map for SKID Collection Routes | |||
4. SYSTEM Generates the SKID Book per ![]() |
Details |
Name | Value | ||
Level | |||
Complexity | |||
Use Case Status | Initial | ||
Implementation Status | Started | ||
Preconditions | GEOM Table (model element not found) GIS System (model element not found) (model element not found)(model element not found)(model element not found)(model element not found)(model element not found)(model element not found) | ||
Post-conditions | SKID Book including SKID IDs identifying the segments that should be tested (model element not found) | ||
Author | Rick Miller | ||
Assumptions |
Tagged Values |
Name | Type | Value | |||
Level | Ad Hoc Enumeration | Summary | |||
Complexity | Ad Hoc Enumeration | ||||
Use Case 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 |
|
||||||||||||||||||||||||||||||
Abstract | false | ||||||||||||||||||||||||||||||
Final Specialization | false | ||||||||||||||||||||||||||||||
Leaf | false | ||||||||||||||||||||||||||||||
Visibility | Unspecified | ||||||||||||||||||||||||||||||
Derived | false |
Name | Value | ||
Name | Dependency | ||
From |
|
||
To |
|
||
Visibility | Unspecified |
Name | Value | ||
Name | |||
From |
|
||
To |
|
||
Visibility | Unspecified | ||
Stereotypes | Include |
Appears In |
Diagram | |||
|