Closed InKyungChoi closed 1 year ago
Regarding Process Design: could adding Activity as a new class with subtypes Process, Sub-process, Process step, Task help?
This question may come up for most classes in Business Group that refer to some aspect of a Process (e.g. Process Method, Process Input, Process output, Process Metric, etc.) -- they may be relevant at other levels as well (sub-process, process step, etc.), not only for processes.
I am putting together GSIM clickable. Business Group was already complicated in version 1.2, and we added even more relationships in version 2.0, so it is pretty threatening :D Of course we should not remove relationship based on it, but it got me wonder if some of relationships are actually redundant.
What relationship between Process Design and Business Process do we need? If it is something similar to what we have between Process Design and Process Step - is this really needed? Process Design is implemented by at least one Process Step, and Business Process has at least one Process Step. Then any Business Process implements Process Design.
Change Definition is already informed by Concept which is a super-class of many other classes (e.g., Variable, Population, Category), do we need to have a relationship with Population additionally? If I read the definition of Change Definition, it doesn't give the impression that Population is particularly important
Process Pattern has at least one Process Design, and if Process Design already specifies delivery of Business Function, do we need a relationship "Process Pattern "supports" Business Function"?
Decision made (see #43):
Here is the updated version of Business Group (only around design-level GSIM classes)
Regarding associations around Business Service
The association (in orange color) between Business Service and Business Process is redundant (because it is covered by Process Step), the same for the association between Business Service and Statistical Program Design (because it is covered by Process Design). Delete?
Regarding Process Design
It seems the target of design (Process Design) is at the level of Business Process, not Process Step. The decision to add an association between Business Process and Process Design as well as new definition ("specification of each Process Step and description of their arrangement in a Business Process needed to perform a Business Function") in this task team also supported this view.
But in practice, I think there are cases where we want to "design" Process Step. Let's say our Business Function is "integrate data" (GSBPM sub-process 5.1), and we want to design a Business Process for that. Then, the Process Design would have multiple Process Steps (e.g., "read in data", "find identifier", "merge via identifier", "check matching rate") and corresponding Process Input Specifications and Process Output Specifications and a Process Control Design (note that Process Design has only one Process Control Design) that controls the flow between above Process Steps. In this case, would it be useful to be able to say certain inputs are for certain Process Step? I guess this might be partially addressed by (new) direct associations between Process Step and Process Input/Output Specification (as in https://github.com/UNECE/GSIMRevision/issues/7), but it seems duplicating to have thess specifications attached for both Process Step and Business Process (unless @FlavioRizzolo meant to remove the associations between specifications and Business Process). Any thoughts?