Prev | Current Page 109 | Next

Tim Weilkiens

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

For example, a statement
says where you ??™ ll most likely be getting to if you turn right. Be glad about
the information and ask what if you chose to turn left.
2.2 Determining Requirments
40 CHAPTER 2 The Pragmatic SYSMOD Approach
The result from interviews, workshops, and studies are stakeholder requests.
In the fi rst go, you have no predefi ned granularity or structure. If you ??™ re informed
by a stakeholder that he requires this or that system, then you have a stakeholder
request. If you look at it more closely you may fi nd that it is a functional requirement
which is further refi ned by several use cases. Or it is a performance plus a
physical requirement and something of a functional requirement.
We add the requirements identifi ed to our model. SysML offers a suitable
model element for this purpose ( Figure 2.7 ). It describes in a very general way a
requirement to the system, i.e., a contract between the customer or stakeholder
and the systems engineer.
Each requirement gets a unique ID. SysML does not dictate a given format.


Pages:
97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121
wzmacniacze gsm rehabilitacja w warszawie tonery konica konkurs mapa notebook toshiba