[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebBP] 6/14/2004: Need for Feedback for ebXML IIC on Use Cases
Monica, I looked at their examples, and the iterating ones they had (aka looping) - and since the goal is to provide a complete set of BP related use cases - these seemed the ones that completed the story for them. Not sure what else there could be for typical BP examples. Thanks, DW ----- Original Message ----- From: "Monica J. Martin" <Monica.Martin@Sun.COM> To: "David RR Webber" <david@drrw.info> Cc: "ebXML BP" <ebxml-bp@lists.oasis-open.org> Sent: Monday, June 14, 2004 10:59 PM Subject: Re: [ebBP] 6/14/2004: Need for Feedback for ebXML IIC on Use Cases > David, > Are these cases related to looping constructs or additional use cases > you would provide as input? See original request. Thanks. > > >Webber: Use Case bp#1 - Invalid payload. > > > >Responder receives a payload that fails to > >validate against XSD. > >Return "Invalid document" response. > > > >Use Case bp#1a - Invalid payload > > > >Responder recieves a payload that is syntactically > >OK - but is not the correct payload type - eg BP > >tells you you are going to get a certain type of > >BOD - and you get one that is its close cousin > >instead. Return "Invalid document" response. > > > >Use Case bp#2 - Business problem. > > > >Responder receives a payload that is syntactically > >OK - but information is wrong - e.g. PurchaseOrder > >but the Order quantity = zero, or the Item ID is missing, > >etc. Return "Business problem" response. > > > >Use Case bp#3 - Access failure > > > >Requester system simply cannot reach the responders > >system - simulates network failure - or infrastructure > >re-configuration - eg - move to new server - change > >of port address, etc. Return - protocolFailure response. > > > >These with the timeout and retry counts examples I > >think do cover off a whole chunk of problems. > > > >I guess another area is things like "Addressee not > >recognized - etc" - but I suspect they have those > >use cases already as part of envelope testing. > >.......... > >mm1: They are using three use cases (attached). In thinking about these use > >cases and the process related functions, what other cases would we see > >the use of looping. I have identified: > > > > * retryCount Reiteration of sending a message again if the > > appropriate response or signal was not received > > * Indirectly for checks on statuses for time to perform > > * BSI checks on signal receipts to trigger backend system > > * Business document processing may allow the condition for a > > response to be sent or the successful handoff from the BSI to the > > backend systems could also apply for looping usage. > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]