Books for you

We bring this issue up regularly in our team meetings, trying to focus on our
goals, our time, and the costs. The more we analyze the lesser the risk that the
finished system might not meet the requirements. But the more we analyze the
higher the costs. Little analysis at low cost increases the risk. We have to find a
good trade-off between risk and time or cost.
46 CHAPTER 2 The Pragmatic SYSMOD Approach
for example. The underlying aspects that have to be taken into consideration in
the system development are the same.
I ??™ ve used the word ??? system ??? several times in the last short paragraph above.
You may not have noticed it. But I still haven ??™ t even mentioned what I mean by a
system. This is one of these trivial terms that are used all the time but hardly ever
defi ned or examined. The term ??? system ??? is relative and varies with the onlooker ??™ s
standpoint. For a software developer it means a software application that may
have a few hardware artifacts. For a hardware developer it means the exact opposite.


Pages:
110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134