User loginNavigation |
Detected contradictions in large information systemsWith respect to detected contradictions in large information system, according to [Russo, Nuseibeh, and Easterbrook 2000]: "The choice of an inconsistency handling strategy depends on the context and the impact it has on other aspects of the development process. Resolving the inconsistency may be as simple as adding or deleting information from a software description. However, it often relies on resolving fundamental conflicts, or taking important design decisions. In such cases, immediate resolution is not the best option, and a number of choices are available: Ignore - it is sometimes the case that the effort of fixing an inconsistency is too great relative to the (low) risk that the inconsistency will have any adverse consequences. In such cases, developers may choose to ignore the existence of the inconsistency in their descriptions. Good practice dictates that such decisions should be revisited as a project progresses or as a system evolves. Defer - this may provide developers with more time to elicit further information to facilitate resolution or to render the inconsistency unimportant. In such cases, it is important to flag the parts of the descriptions that are affected, as development will continue while the inconsistency is tolerated. Circumvent - in some cases, what appears to be an inconsistency according to the consistency rules is not regarded as such by the software developers. This may be because the rule is wrong, or because the inconsistency represents an exception to the rule that had not been captured. In these cases, the inconsistency can be circumvented by modifying the rule, or by disabling it for a specific context. Ameliorate - it may be more cost-effective to ‘improve’ a description containing inconsistencies without necessarily resolving them all. This may include adding information to the description that alleviates some adverse effects of an inconsistency and/or resolves other inconsistencies as a side effect. In such cases, amelioration can be a useful inconsistency handling strategy in that it moves the development process in a ‘desirable’ direction in which inconsistencies and their adverse impact are reduced. By Hewitt at 2014-04-10 20:20 | LtU Forum | previous forum topic | next forum topic | other blogs | 3561 reads
|
Browse archives
Active forum topics |
Recent comments
20 weeks 1 day ago
20 weeks 1 day ago
20 weeks 1 day ago
42 weeks 2 days ago
46 weeks 4 days ago
48 weeks 1 day ago
48 weeks 1 day ago
50 weeks 6 days ago
1 year 3 weeks ago
1 year 3 weeks ago