2.2). In this
section you will learn how different solution variants can be modeled. You obtain
several variants if you create a model for a product family, or if you want to evaluate
several solution alternatives for one system to identify the best one.
Let ??™ s begin with the requirements from the status quo where the essential
requirements are separated from the technical ones. We put both areas into a
package by the name of core requirements . Next, we determine the requirements
that are NOT valid for all variants. If you are just looking for solution variants, you
should limit your search to the technical requirements. If you are looking at a
product family, you should be aware of the fact that essential requirements too
can belong to the variants.
A core requirement refers to the entire system and is independent of the
particularities of system variants. A variant requirement refers exclusively to a
variant and is valid only for the system design of that variant.
Put one package for each variant on the level of the core requirement package
and then, in each of them, create subpackages for essential and technical requirements.
Pages:
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281