Graceful Evolution Monitors
Software development teams are required to produce applications that are enmeshed with contributory systems over which the team have no control. This highlights the need for an approach that allows the developed application to evolve gracefully to changes in the contributory systems. This work proposes an approach to graceful evolution which is appropriate for rapid application development environments. The approach combines elements of Risk Analysis Method (Anton, 1997), with the perspective given by considering Dynamic Inconsistency (Lamsweerde, Letier and Ponsard, 1997). The approach investigates assumptions made about requirements; the obstacles to those assumptions are then identified. The obstacles are assessed with respect to their impact on the running system and the decision is made to resolve, monitor or ignore the obstacle. The assessment provides both directly and through the monitoring logs guidance to the software development teams of the type of corrective action needed. This work considers a theoretical example drawn from experience in the action needed. This work considers a theoretical example drawn from experience in the telecommunications industry for which one of the
IROA Heuristic B: The failure of an external entity or actor to behave as assumed could cause an obstacle to that assumption. 5. Enhancement of the DSDM framework for the use with the IROA approach. (5 marks) Systems development in the type of environment outlined above can cause dynamic inconsistencies. Dynamic inconsistencies refer to differences between requirement specifications and the actual runtime behaviour of the system implementing those requirements (Lamsweerde, Letier and Ponsard, 1997). Such dynamics inconsistencies can arise from changes to assumptions about the environment (Feather and Fickas, 1995) and can be tackled using obstacle analysis (Anton, 1997), (Laamsweerde and Letier, 1998) and requirements monitoring (Feather and Fickas, 1995). With enmeshed systems changes to assumptions about the environment would occur because the application development team is unlikely to know all the relevant details of changes to be implemented in the enmeshed systems due to maintenance.
Some topics in this essay:
Anaysis BSA,
Heuristics Anton’s,
Letier Ponsard,
Baskerville Stage,
Page Sivagurunathan,
DSDM Consortium,
According Anton,
Feather Fickas,
Jay Arthur,
Lamsweerde Letier,
line test,
iroa approach,
test unit,
line test unit,
bsa system,
obstacle analysis,
legacy system,
assumptions requirements,
line test units,
test units,
legacy systems,
existing line,
existing line test,
data line test,
baskerville stage 1996,
Join now to see the rest of the essay!
Approximate Word count = 2606
Approximate Pages = 10 (250 words per page double spaced)
|
Example Essays Home
