Books for you

3).
6DIN  Deutsches Institut f??r Normung e.V. (German Institute for Standardization).
2.2 Determining Requirements
42 CHAPTER 2 The Pragmatic SYSMOD Approach
We have added the customer ??™ s requirements more or less directly. These
requirements often include solution approaches, e.g., the requirement to the
enclosure size for the central unit. Technical solution approaches also have an
infl uence on the list of stakeholders we identifi ed (Section 2.2.1). For example, it
includes the cell phone manufacturer stakeholder. However, this is not desirable,
because solution approaches don ??™ t really belong to the requirements analysis. You
probably have a hunch telling you that we can ??™ t simply omit them. Unless there is
a solution idea, it is very diffi cult to fi nd good and correct requirements. So allow
for solutions and derive solution-free requirements from them, provided you need
the higher abstraction level at all.
We give our requirements model some structure to separate technical system
requirements from pure domain requirements.


Pages:
102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126