D.3.3 ALGORITHMS FOR INCREMENTAL ... - SecureChange

Fig. 4. SI* conceptual model
quirements, he can run the requirement analysis to determine the level of achievement
also for top-level requirements.
Identify the problem. If some of the requirements are not fulfilled, the requirement
engineer must identify the problem.
1. If there is a problem with the ReM, the requirement engineer must backtrack
and search for an alternative way of updating the ReM when considering the
change request that was initially passed from the user.
b If there is a problem with testing, the test engineer must determine whether
there is the need to generate new test cases or not.
4 Change management for evolving requirements
For the change management process in the requirement domain we consider here the
SI* requirement model [11] based on the Tropos methodology. As illustrated in Fig. 4,
we consider the concept of goal and a subset of SI* relations, namely AND/OR decomposition,
means-end, require, request, and dependency relations.
The requirement analysis process consists of five steps:
1. Identify relevant stakeholders, modeled as actor (circle) and its structure.
2. Capture and refine actors’requirements as goal (rounded rectangle).
3. Define means to achieve their goals- i.e., process (hexagon) or resource (rectangle).
4. Model strategic dependencies between actors in fulfilling/executing/providing some
goals/processes/resources.
5. Model specific security and risk related aspects such as introducing security goals,
which are goals protecting assets and that can be identified as result of risk analysis
[24] or analyzing trust relations and delegation of permissions among actors
[11].
6