-
Key: SPTP-34
-
Legacy Issue Number: 4994
-
Status: closed
-
Source: U.S. Army Cecom-CSE ( Tom Wheeler)
-
Summary:
Modeling Resources, 2nd paragraph, page 14. This RFP response uses the phrase “required QoS” for identifying the QoS a client demands from a resource. To me, the word “required” implies an “all or nothing” response which I do not think is the right connotation if these QoS values are to be used at run time as well as during analysis. I believe that eventually we will want auto-generated software embedded with these QoS values where the values are exposed and acted upon by the run time infrastructure. In this case, clients may get less than optimal resource service. Recommend the phase “required QoS” be replaced with “desired QoS”. This phrase is used throughout the RFP response.
-
Reported: SPTP 1.0b1 — Tue, 19 Mar 2002 05:00 GMT
-
Disposition: Resolved — SPTP 1.0
-
Disposition Summary:
Closed, no change
-
Updated: Fri, 6 Mar 2015 20:58 GMT
SPTP — Modeling Resources, 2nd paragraph, page 14
- Key: SPTP-34
- OMG Task Force: UML Profile for Scheduling FTF