You could run a
model request to determine whether all requirements have at least one model
element that realizes them, and vice-versa, whether each model element is based
directly or indirectly on a requirement.
Modeling these relations is costly. While it ??™ s easy to model the relationships, it
is costly to maintain them. The benefi t is higher than the cost if many changes are
made to the model during the course of the project, or if the model is used for
subsequent projects. A good traceability of the relations is then very important. It is
also possible that your principal or standards you have to comply with dictate the
traceability of the requirements all the way to the design or the fi nished system.
PROJECT DIARY
Project Time 8152
The good preparation and coordination with the customer in the analysis now
pays. The domain issues and insecurities have been clarified largely, so that we
can fully deal with the technical challenges in the design.
There are still white spots in the analysis model, which we will now examine in
the further course of the project.
Pages:
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274