The Thermo SIG met from 10:30 am till 12:20 pm (Central European Time).
Agenda
Chemical Reactions interface specification.
Participants
BASF (represented by Sergej BLAGOV), AmsterCHEM (represented by Jasper van BATEN), Shell Global Solutions (represented by Mark STIJNMAN), Michel PONS (Consultant as CTO)
Agenda
Textual Chemical Reactions interface specification.
Highlights
Thermo SIG focussed on the chapter of the Chemical Reactions interface specification dedicated to Compound Slates. The list of Actors and the definition of priorities defined for the Use Cases were added to the section on Use Cases. It was also made plain that the chapter deals only with Compound Clients that support multiple Compound Slates. This complements usefully the scope of the chapter that is already targeted only to Compound Servers who deal with multiple Compound Slates. Having this scope made clearer helps in simplifying the preconditions that apply to each Use Case.
Thermo SIG discussed the possibility to define a Use Case that would simply explain how the active Compound Slate is set on a Compound Server since this action is present in several Use Cases. Such a definition was found unnecessary since comprising only one simple step.
Thermo SIG revisited Use Case UC-CS-002 “Obtain list of compounds for a compound slate” and made some modifications to the text with the objective to make it easier to understand.
Then the pre-conditions of Use Case UC-CS-003 “Configure subset of compounds for use with Material Template” were revised and simplified. In the flow of events of this Use Case, the wording was adapted to make it clearer who the Actor is for this Use Case.
Next the pre-conditions of Use Case UC-CS-004 “Configure Material Template for use with multiple Compound Slates” were revised and simplified. The wording in the flow of events section of this Use Case was also revised to avoid ambiguities. To ensure consistency between overall requirements expressed and this use case, text was added to the rationale of requirement REQ-51-CS that imposes that physically feasible values for property “fraction” corresponding to the default Compound Slate, must be strictly within the range from 0 to 1 inclusive. An additional requirement was found necessary and added to the list of requirements: REQ-69. It states that in all communications with the Compound Server, the Compound Client must use Compound Slate names (identifiers) defined by the Compound Server.
Revision of Use Case UC-CS-006 “Property Package converts single phase composition between compound slates” was next: it was made consistent with the definition of interface ICapeThermoCompoundSlates.
Comment made to flow of events of Use Case UC-CS-007 “Material Object converts overall composition between Compound Slates” was adressed next.
The next conference call is scheduled for August 11, 2020.
