Prev | Current Page 97 | Next

Tim Weilkiens

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

3 .
We barely know the functions that are desirable for the system and its goals.
This amount of knowledge is not suffi cient to develop the system. We have to deal
with the issue of where all the information on system requirements will come
from or, more exactly, from whom.
Table 2.3 Summary: Identifying stakeholders.
Reference card: Identify stakeholders.
Incoming and outgoing data
Project context:
Basic ideas and goals for the system; background
situation; framework conditions and other information
from the project environment.
Stakeholder:
An individual or organization that has an interest in the
system and may have requirements.
Motivation/description
Why? It is decisive for the success of the project that the needs of all stakeholders
are suffi ciently fulfi lled.
What? Identify all individuals and organizations that may have requirements to or an
interest in the system.
How? The list of stakeholders is initially elaborated in a workshop and continually
reviewed during the project.
Where? Stakeholders are the sources of requirements.


Pages:
85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109
Lokaty jednodniowe domy wczasowe naprawa komputerów Warszawa transport odpadów ochrona mienia