Example of BDD/scenario based vertical slicing (for PM/PO community)
0 likes591 views
The document discusses high availability for establishing atomic communication paths. It states that if a request to establish a flow path is accomplished, all flows composing the connection will be programmed, but if the request fails, no flows will be programmed and an error will be reported via rollback. Typical failures include timeouts or operations failing, such as attempting to program a full flow table on a switch. Acceptance criteria include committing successfully programmed flows and rolling back failed requests to maintain integrity and atomicity.
Example of BDD/scenario based vertical slicing (for PM/PO community)
- 1. High Availability Epic HA.01 - HA: Atomiccommunicationestablishment.<Priority:H> The NetworkAdmin,orthe application,requiringapath establishmentserviceviaAPIcanassume that, incase the requestisaccomplished,all the flowscomposinga connectionare programmed.Incase a requestisfailed,noflowisprogrammed(roll back),andanerror isreported.The roll backhappens because the procedure time out,orbecause one of the operationsfails.Typical case issettingupanew flowona switchthathas a full flowtable. Acceptance Criteria: HA.01 related vertical slices: ID Name Slice (story) HA.01.1 Commit functionality As a sysadmin, I want commit on successful request, so that all the flows composing a path are programmed on relevant switches. Example scenario: Network path “installation” Given a request to install a path, When that request succeeds, Then the commit happens and no errors are reported. HA.01-2 Rollback functionality As a sysadmin, I want rollback on failed requests in order to maintain integrity, so that the state is restored accurately and atomicity is preserved. Example scenario: “timeout” type exception Given a request to install a path, When that request fails, Then the rollback happens and errors are reported.
- 2. …