| ID |
Status |
Summary |
|
150
|
New |
implementer's guide 1.0.2 examples - a couple of errors
|
|
149
|
Accepted |
elementRef type
|
|
148
|
Applied |
Remove reference to ENUM from the Implementers Guide
|
|
147
|
Applied |
Implementers Guide: Car Repair - except for 1st pass, no evaluator task for the 1st loop-back?
|
|
146
|
Applied |
Implementers Guide: Car Repair - 3 decisions, only 2 probability sets...
|
|
145
|
Applied |
Implementers Guide: Flaw in Car Repair flow?
|
|
144
|
Applied |
Implementers Guide/Visio: Car Repair, missing 'e' in DataState for Itemized Issues...
|
|
143
|
Applied |
Suggested text to claify scope of example scenarios
|
|
142
|
Applied |
Parameter for Triangle distribution
|
|
141
|
Applied |
Sandboxing - Duration parameter
|
|
140
|
Accepted |
Create a tabular form of the sim data used in the implementer's guide
|
|
139
|
Differed |
v1.1 - Explicitly exclude use of ResultRequest within ScenarioParameters
|
|
138
|
Applied |
BPSim: Spec: Section 7 omits applicability of result requests to scenario parameters
|
|
137
|
Applied |
Table of Car Repair parameters per BPSim extension to XPDL
|
|
136
|
Applied |
Implementer's Guide: Example bpmn and xpdl need updating for the 1.0 published XSD
|
|
135
|
Differed |
Typos and minor changes to the Specification Document
|
|
134
|
Applied |
Implementer's Guide: Simplification of example 1
|
|
133
|
Done |
Speading the word(2): Business Analysis events/conferences - PW&WCBA 2013 (Orlando, September)...
|
|
132
|
Done |
Speading the word: adding BPSim.org to BPM reference sites...
|
|
131
|
Applied |
Implementer's guide: section 6 Test Cases
|
|
130
|
Applied |
Implementer's guide: section 5 Glossary
|
|
129
|
Applied |
Implementer's guide: 4.3.5, "As we can see..." - where?
|
|
128
|
Applied |
Same (i.e. ; or . instead of ,) with "...provide a solution to the Front Office, otherwise they request further assistance..."
|
|
127
|
Applied |
Implementer's guide: typo in 4.1.1 ; (or .) instead of , (see Description)
|
|
126
|
Applied |
Implementer's guide: Loan example - Start Event: Triangular Distribution?
|
|
125
|
Differed |
BPSIM: If too late, please ignore... transferTime: redundant and potentially indeterminable? or a gap?
|
|
124
|
Applied |
BPSim v1.0: Section numbering - 6 used twice!
|
|
123
|
Applied |
Implementers Guide Property Parameter Expression
|
|
122
|
Applied |
Implementers Guide document and BPMN files still refer to process analysis data & paf rather than BPSim
|
|
121
|
Done |
Implementer's guide: Use case = Process? (see also #120)
|
|
120
|
Done |
Implementer's guide: Use Case Scope terms...
|
|
119
|
Applied |
Implementer's guide: simulation...synthetically?
|
|
118
|
Applied |
Implementer's guide: comparison with 'real-life'...
|
|
117
|
Applied |
Implementer's Guide: export and import simulation extensions?
|
|
116
|
Applied |
The Distribution Parameter should contain the timeUnit attribute
|
|
115
|
Duplicate |
Control Parameters for Events and Activites - triggerCount for Intermediate Catching Events or Receive Message Task After Event-Based Gateway
Type-Defect
Priority-High
Usability
|
|
114
|
WontFix |
Clarification Control Parameters for Event-Based Gateway - Applies to Gateway Itsef or Downstream Events
Type-Enhancement
Priority-Medium
Usability
|
|
113
|
WontFix |
Control Parameters for Activities - Receive Message Task and Any Activity With Inbound Message Flow
Type-Defect
Priority-High
Usability
|
|
112
|
Applied |
UserDistribution schema warning
|
|
111
|
Applied |
Distribution attributes should be mandator in the xsd?
|
|
110
|
Applied |
Difference between XSD and text descriptions of Calendar in RC1
|
|
109
|
Differed |
Apply Calendar to Result Request
|
|
108
|
Applied |
Results - Resources
|
|
107
|
Applied |
Results - Process Level
|
|
106
|
WontFix |
Results - End Event
|
|
105
|
Applied |
remove "edited with" comment from 0.4 xsd
|
|
104
|
Applied |
and local timeunit element to TimeParameters and local currencyUnit to CostParameters
|
|
103
|
Done |
Clarification on the results structure
|
|
102
|
WontFix |
Provide DecimalParameter element for Constant Parameters
|
|
101
|
WontFix |
Add anyAttribute to attributes of Parameter and ParameterValue complex types
|
|
100
|
Applied |
Scenario does not have vendor attribute
|
|
99
|
WontFix |
TimeParameters should have duration as independent property
|
|
98
|
Done |
Not an issue: When are we supposed to resume the online meetings?
|
|
97
|
WontFix |
Clarification on resource selection as defined in BPMN vs PAF Applicability v0.1.xlsx
|
|
96
|
Applied |
Clarification on how defaults behave for Start Events & Intermediate Events with / without PAF data
|
|
95
|
Applied |
When should Property Parameters be applied to Intermediate Events, Task, Sub-Process, Call Activity, Event Sub-Process, Gateways
|
|
94
|
Applied |
PAF Expression Serialization
|
|
93
|
WontFix |
Parameter value change via Calendar
|
|
92
|
Applied |
Introduce a <Condition> element to the Control Parameters perspective
|
|
91
|
Applied |
Document the order that element parameters are applied when setting multiple parameters for an element
|
|
90
|
Applied |
The name attribute of the <Property> element contained by the <InstanceParameters> element should be use=required
|
|
89
|
WontFix |
TruncatedNormalDistribution can only be truncated on the min side
|
|
88
|
WontFix |
Add some way to return errors from the simulation if an error occured in the simulation
|
|
87
|
WontFix |
We need to add a variableCost parameter
|
|
86
|
Applied |
The VendorExtension differs from the AnalysisExtendedOption used by the 0.2a schema
|
|
85
|
Done |
Resource Parameters
|
|
84
|
Done |
Do we need simulation parameter(s) for incoming and outgoing message flows attached on tasks
|
|
83
|
Applied |
How to deal with incorrect and/or underspecified(incomplete) simulation scenario data
|
|
82
|
Done |
How to deal with incorrect and/or underspecified(incomplete) process models
|
|
81
|
Done |
FYI: verified that certain Task Types (e.g. Manual) cannot have any incoming or outgoing Message Flows
|
|
80
|
Applied |
Need to specify which portions of ISO 8601 Date/Time are applicable in the context of our Spec
|
|
79
|
WontFix |
VendorExtension metaclass not needed, not helpful
|
|
78
|
Applied |
The metamodel spec document needs separate sections for object properties
|
|
77
|
Applied |
Metamodel spec document needs numbered clauses
|
|
76
|
WontFix |
elementParameters association should not be composition
|
|
75
|
Applied |
Continuous and discrete should be subtypes of DistributionParameter, not a boolean on it
|
|
74
|
WontFix |
ElementParameters and "collection-type" classes generally
|
|
73
|
WontFix |
Implementors guide: Suggestions
|
|
72
|
Applied |
Error in Specification document v0.23 Priority parameters
|
|
71
|
WontFix |
Overriding parameters that are specified in the BPMN interchange format
|
|
70
|
Done |
Sandboxing - lag time from different incoming flows
|
|
69
|
Done |
Sandboxing - processing Time
|
|
68
|
Applied |
UserDistributionDataPoint text description changes
|
|
67
|
Applied |
Should the quantity attribute of the ResourceParameters be an integer or a fraction with units
|
|
66
|
WontFix |
[Implementer's Guide] Clarify implementation for the resource quantity
|
|
65
|
WontFix |
If not mistaken, if ElementParameter is an Abstract class, then children should inherit from it...
|
|
64
|
Duplicate |
What's the meaning of Priority of an Element?
|
|
63
|
Applied |
Interruptile: if to parametize the whole process execution, it shouldn't be under PrioritizeParameter
|
|
62
|
WontFix |
Same: XYZParemeters (where XYZ=Time,Priority, etc.) should be XYZParameter...
|
|
61
|
Applied |
baseTimeUnit+baseCurrencyUnit: if to reflect whole schema, it should be a param of ProcessAnalysisData, not of a Scenario
|
|
60
|
WontFix |
Separate ScenarioResult (as child class of Scenario), instead of overloading Scenario
|
|
59
|
WontFix |
ScenarioParameter, instead of ScenarioParameters
|
|
58
|
WontFix |
ElementParameter, instead of ElementParameters
|
|
57
|
Applied |
General comment on the data model: defining 1-to-many relationships
|
|
56
|
Applied |
ScenarioParameters-Run length determined by Token volume
|
|
55
|
Applied |
Applicability of the various Parameters for Process Elements in the context of an ouput scenario
|
|
54
|
Applied |
Applicability of the various Parameters for Process Elements in the context of an input scenario
|
|
53
|
Differed |
Initial State
|
|
52
|
Differed |
Arrivals and initial state
|
|
51
|
Applied |
Add a Priority control parameter for tasks
|
Code