Prev | Current Page 105 | Next

Tim Weilkiens

"Systems Engineering with SysML/UML: Modeling, Analysis, Design"

So, how do we get hold of the
requirements? Well, we simply ask them.
This sounds more trivial than it is in practice. I remember a company where
a department had developed a piece of software to support their staff in creating
a help text system. The software turned out to be a failure. The future users
of the help text software had never been asked about their requirements. In fact,
they didn ??™ t even know about their ??? luck. ??? And all this while they sat only a couple
rooms away from the development department.
Turn to your stakeholders and ask them about their requirements. Run interviews
and workshops. Collect documents, manuals of legacy systems, and the like.
Also ask your stakeholders for further stakeholders.
Table 2.5 Summary: Collect requirements .
Reference card: Collect requirements.
Incoming and outdoing data
Stakeholders:
Individuals or organizations that have a
direct interest in the system and may have
requirements.
Requirements:
Requirements to the system.
Motivation/description
Why? Requirements form the elementary basis in system development.


Pages:
93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117