Books for you

It has
no end in itself. This perspective can get lost in the large number of (technical)
details an engineer has to deal with, especially in later project phases. However, all
use cases have to have been realized when the system is shipped. You can think
of use cases as the ??? lighthouses ??? of your project, which you always have to have in
sight to ensure that you reach your goal straight on in the secure groove.
This is the approach that ??™ s also behind the catchword ??? use case-driven, ???
used in many process models or software development architectures (including,
e.g., the oose Engineering Process ( OEP ) [35], the Rational Unifi ed Process
( RUP ) [31], and the 41-Architecture [30]). It means that the use cases are always
kept in focus in the individual system development phases.
2.4 Modeling Use Cases
66 CHAPTER 2 The Pragmatic SYSMOD Approach
To identify services, we fi rst of all look at the system context model and ask ourselves
what the actor wants of our system, especially with regard to incoming information
fl ows.


Pages:
145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169