-Let's now put together all that we have discussed - -2
-and see how a requirements engineering process actually works. - -3
-So, first of all, we saw that requirements engineering - -4
-consists of three main steps. Elicitation of the requirements, - -5
-in which we extract requirements from various sources. Modeling - -6
-in which we represent the requirements using one or - -7
-more notations or formal reasons and analysis, in which - -8
-we identify possible issues with our requirements and there is - -9
-actually a 4th step that we kind of mention - -10
-but not explicitly. And this is the negotiation that can - -11
-happen between the stakeholders and the developers, during which - -12
-requirements are discussed and modified until an agreement is reached. - -13
-So if you want to think of this as a - -14
-process, so as a sequence of steps, we can see - -15
-that we start from elicitation. So we start by eliciting - -16
-an initial setup requirements. We negotiate and refine this set, - -17
-then we model the resulting requirements. And finally, we - -18
-analyze such requirements. However, the process doesn't really stop here. - -19
-Why? Well, because as a result of the analysis, - -20
-we might have to perform further elicitation. And so this - -21
-process is not really a sequential one, but rather - -22
-an iterative process. So, in practice, we continue to iterate - -23
-over these four steps gathering a better and better understanding - -24
-of the requirements at every iteration until we are happy - -25
-with the settle requirement that we gather and stop the process. -- cgit 1.4.1