wiki:PRO_CHANGE_TRANSACTION_SAFETY_R0

Version 1 (modified by peko, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=PRO_CHANGE_TRANSACTION_SAFETY_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

This task represents the transaction safety of changes. Transaction safety is a term that has occurred from databases where one make transactions to the database. Generally it means to keep the integrity and the state consistent. Transactions should be made at once and should be undone if something is messed up in the middle of the transaction. Same applies to changes. Changes should either happed and be constructed or not. Imagine one has a composite change (see PRO_CHANGE_COMPOSING_R0) which is made of a number of small changes. Either all changes should be undone when undo is required or none should be undone.

Task requirements

  • Define how to make transaction safety possible.

Task result

  • source code

Implementation idea

PRO_CHANGE_PRIMITIVES_R0
PRO_CHANGE_TRANSACTION_SAFETY_R0
PRO_CHANGE_COMPOSING_R0
PRO_CHANGE_MANAGER_R0

How to demo

Design

Implementation

Testing

Comments