link R-PMS System Use Cases : Model . R-PMS System - Q4 : System
Use Case - T10-03 Prepare for Pavement type changes based on projects link
| Properties |
| Name | Value | ||||||||
| Description |
Determine if there are any pavement type changes due to ongoing project work in each District |
||||||||
| Transit From |
|
||||||||
| Id | UC87 | ||||||||
| Abstract | false | ||||||||
| Leaf | false | ||||||||
| Root | false | ||||||||
| Stereotypes | PMS Activity | ||||||||
| Business Model | false | ||||||||
| Status | Identify | ||||||||
| Rank | Unspecified | ||||||||
| Relationships Summary |
| Name | Begin | End | |||
|
|
|
|
|||
| Use Case Note |
| ■ Workflow | |||
| • // Write down briefly how user perform the work | |||
| ■ Business Logic | |||
| • // Write down what user expect the system to react upon certain condition (e.g. low inventory alert level) | |||
| • Look at pavement type prior to project | |||
| • Examine what pavement type is going to become | |||
| • Let PMS Operator know that the pavement type must be changed | |||
| ■ Decisions | |||
| • // Write down the decisions made during the meeting (e.g. Must allow accessing from mobile devices) | |||
| • | |||
| ■ Follow-up | |||
| • // Write down the items that should follow-up in the coming meeting | |||
| • | |||
| PMS Current |
| Steps | |||
1.  Actor - KDOT PMS Operator Look at pavement type prior to project |
|||
|
2. Actor - KDOT PMS Operator Examine what pavement type is going to become |
|||
|
3. Actor - KDOT PMS Operator Changes pavement type in PMS Network |
|||
| 3.1. Submit Pavement Type to System for change on PMID | |||
| 3.2. SYSTEM Makes changes to PMS Network data | |||
| R-PMS Desired |
| Steps | |||
|
1. Actor - KDOT District Personnel submits CRF for project completion |
|||
| 2. SYSTEM Examines the pavement data in the CRF form | |||
| 2.1. Pavement type prior to project | |||
| 2.2. Pavement type post project | |||
| 3. SYSTEM Determine if pavement type has changed | |||
| 3.1. Make appropriate changes to PMS Network if pavement type has changed | |||
| Tagged Values |
| Name | Type | Value | |||
| Level | Ad Hoc Enumeration | User | |||
| Complexity | Ad Hoc Enumeration | Medium | |||
| Use Case Status | Ad Hoc Enumeration | Initial | |||
| Preconditions | Multi-line Text | ||||
| Post-conditions | Multi-line Text | ||||
| Author | Text | Kristy Rizek and Jerry W. Manweiler, Ph.D. | |||
| Assumptions | Multi-line Text | ||||
| References |
| File Name | Description | ||
|
|
|||
|
|
|||
| Relationships Detail |
| Name | Value | ||
| Name | |||
| From |
|
||
| To |
|
||
| Visibility | Unspecified | ||
| Stereotypes | Include | ||
| Appears In |
| Diagram | |||
|
|
|||