During this activity, we review the design decisions we
made so far, and identify additional use cases.
1. Configuration use cases:
The handling of most persistent objects is already
described in the use cases developed during analysis. Additional use cases are
identified when reviewing persistent objects.
2. Exceptional
use cases:
In general, an exception is an unexpected event or error
that occurs during the execution of the system exceptions are caused by
A user error: The user mistakenly or deliberately inputs
data that are out of bounds for example; a negative value or a fractional value
in a genetic parameter could lead to wrong and inconsistent data
A Hardware failure:
Hardware ages and fails.
A Software bug:
An error can occur either because the system or on its components contain a
design error. Although writing bug free software is difficult.
No comments:
Post a Comment