R-PMS System Use Cases : Model . R-PMS System - EPMS/KANPAV : System
Use Case - KANPAV-00 1R PMS Prediction System
link
| Properties |
| Name | Value | ||
| Description |
Overall Use Case that is used to generate the 1R priority list for each district |
||
| Transit From | |||
| Id | UC31 | ||
| Abstract | false | ||
| Leaf | false | ||
| Root | false | ||
| Stereotypes | UseCase, Modeling | ||
| Justification | Modeling of the pavement system is a necessary step in the 1R process | ||
| Business Model | false | ||
| Primary Actors | Actor - KDOT PMS Modeler | ||
| Status | Identify | ||
| Rank | Unspecified | ||
| Relationships Summary |
| Use Case Note |
| ■ Inputs or Prior Activities | |||
| • KHS Network Segments Data | |||
| • Traffic Data | |||
| • Road Category Specifications | |||
| • Distress State Specifications | |||
| • Past Action Data | |||
| • Scheduled Work Data | |||
| • Auxiliary PMS Data elements | |||
| ■ Actions | |||
| • Include the following Use Cases | |||
| ♦ Lock Data per Actor supplied Date | |||
| ♦ Calculate Discrete Condition State per segment | |||
| ♦ ... | |||
| ■ Outputs | |||
| • Recommendation list per district | |||
| • Segment State Vector for Priority Formula Calculation | |||
| • Segment State Vector for ... | |||
| • Segment State Vector for ... | |||
| • Segment State Vector for ... | |||
| ■ Follow-up | |||
| • // Write down the items that should follow-up in the coming meeting | |||
| • | |||
| Actions |
| Steps | |||
|
1. |
|||
| 2. SYSTEM Include the following Use Cases | |||
| 2.1. Lock Data per Actor supplied Date | |||
| 2.2. Calculate Category Type per segment | |||
| 2.3. Calculate Distress State per segment | |||
| 2.4. Calculate Remaining Life per segment | |||
| 2.5. ... | |||
| 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 | Include | ||||||||||
| Name | Value | ||||||||||
| Name | |||||||||||
| From |
|
||||||||||
| To |
|
||||||||||
| Transit From |
|
||||||||||
| Visibility | Unspecified | ||||||||||
| Stereotypes | Include | ||||||||||
| Name | Value | ||||||||||
| Name | |||||||||||
| From |
|
||||||||||
| To |
|
||||||||||
| Transit From |
|
||||||||||
| Visibility | Unspecified | ||||||||||
| Stereotypes | Include | ||||||||||
| Name | Value | ||||||||||
| Name | |||||||||||
| From |
|
||||||||||
| To |
|
||||||||||
| Transit From |
|
||||||||||
| Visibility | Unspecified | ||||||||||
| Stereotypes | Include | ||||||||||
| Appears In |
| Diagram | |||
|
|
|||