R-PMS System Use Cases : Model . R-PMS System - Q3 : System
Use Case - T07-02 Generate and load frame-based HPMS data (State + HPMS) link
Properties |
Name | Value | ||||||||
Description |
To prepare data for Planning and for NCViewer application
This Use Case is also used to generate the planning view for the nonState data.into the PMS.LCMSFrameHPMSnon data table |
||||||||
Transit From |
|
||||||||
Id | UC27 | ||||||||
Abstract | false | ||||||||
Leaf | false | ||||||||
Root | false | ||||||||
Stereotypes | Modeling | ||||||||
Business Model | false | ||||||||
Status | Identify | ||||||||
Rank | Unspecified |
Relationships Summary |
Name | Begin | End | |||
|
|
|
Use Case Note |
■ Inputs and Previous Actions | |||
• Summary reports from Mandli RVW as CSV files | |||
■ Actions | |||
• run summary reports | |||
• Load data into tables | |||
• create view for current year | |||
• email planning | |||
■ Output | |||
• SQL Views of State and nonState table for each year | |||
• email Planning to let them know that the data is available |
PMS Current |
Steps | |||
1. ![]() |
|||
2. SYSTEM imports the data into the KSR.LCMSFrameHPMSST table | |||
3. ![]() |
|||
4. ![]() |
R-PMS Desired |
Steps | |||
1. ![]() |
|||
2. SYSTEM imports the data into the KSR.LCMSFrameHPMSST table | |||
3. SYSTEM uses SQL Developer to create current year view into the data | |||
4. SYSTEM emails Planning that the data available |
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 | |||
|