Package - R-PMS Requirements link
Properties |
Name | Value | ||
Description |
Replacement PMS System Requirements package hierarchy |
||
Abstract | false | ||
Leaf | false | ||
Root | false | ||
Visibility | public |
Children |
Name | Description | ||
|
System much be configurable to allow for best meeting requirements and to allow for future modifications |
||
|
|||
|
|||
|
Support development and integration of forms for gathering input from users |
||
|
General System Requirements defined by State of Kansas and Kansas Department of Transportation |
||
|
|||
|
Integrate with KDOT GIS tools (or provide comparable imbedded tools) |
||
|
integrate with KDOT highway inventory systems |
||
|
Integrate with KDOT historic pavement condition data |
||
|
Generate, distribute, retain, reports as needed |
||
|
Integrate with KDOT (and other typical) pavement condition systems |
||
|
Maintain interfaces with systems to obtain and provide relevant interchange of data |
||
|
|||
|
|||
|
Support KDOT Asset Management processes (TAMP) |
||
|
Integrate with KDOT project management systems |
||
|
Specification of the KDOT PMS security requirements for the R-PMS system. |
||
|
|||
|
Support workflow to help streamline processes and keep users informed of progress and relevant tasks |
||
|
Replacement PMS (R-PMS) Requirements Master Requirement Model Element R-PMS System Must, Should, is Desired to all requirements contained by this Master Requirement Requirement Priority M=Mandatory, E=Expected, D=Desirable |
||
|
Provide and meet KDOT and PMS Technical Architectural Requirements |
||
|
Note:An ordered list of these requirements can be found selecting the link in the upper left: Model Lists: Glossary, Requirements, and Use Cases and then selecting the R-PMS Requirements List in the lower left pane. |