link R-PMS System Use Cases : Model . R-PMS System - Q3 : System
Use Case - T07-04 Validate reasons for missing data elements link
| Properties |
| Name | Value | ||||||||
| Description |
This modeling step is used to verify that there is no missing data due to construction work and to convert that data into FILL values in the DB tables. |
||||||||
| Transit From |
|
||||||||
| Id | UC70 | ||||||||
| Abstract | false | ||||||||
| Leaf | false | ||||||||
| Root | false | ||||||||
| Stereotypes | Modeling | ||||||||
| Business Model | false | ||||||||
| Status | Identify | ||||||||
| Rank | Unspecified | ||||||||
| Relationships Summary |
| Name | Begin | End | |||
|
|
|
|
|||
| Scenario |
| Steps | |||
1.  Actor - KDOT PMS Modeler queries for Date fields with Dummy values |
|||
| 2. SYSTEM provides records without data | |||
|
3. Actor - KDOT PMS Modeler Manually reviews data records |
|||
| 3.1. Checks data collection for segment | |||
| 3.2. if Data was NOT collected then | |||
| 3.2.1. Determine if van should rescan | |||
| 3.2.2. if Van should NOT rescan | |||
| 3.2.2.1. Determine reason not collected and/or data values provided using non-scan process | |||
| 3.2.2.2. Set date to Default date of: | |||
| 3.2.2.2.1. Jan01-Under construction | |||
| 3.2.2.2.2. Jan02-Averaged from nearby segments | |||
| 3.2.2.2.3. Jan03-Subjective measure | |||
| end if | |||
| end if | |||
| 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 |
|
||
| Visibility | Unspecified | ||
| Stereotypes | Include | ||
| Appears In |
| Diagram | |||
|
|
|||