Identifying Risks for Collaborative Systems during Requirements Engineering: An Ontology-Based Approach
Kirthy Kolluri, Robert Ahn, Tom Hill, Julie Rauer, Lawrence Chung · Proceedings/Proceedings of the ... International Conference on Software Engineering and Knowledge Engineering · 2022
A risk is an undesirable event that can result in mishaps if not identified early on during requirements engineering adequately.However, identifying risks can be challenging, and requirements engineers may not always be aware if risks are ignored.In this paper, we present Murphy -a framework for performing risk analysis.Murphy adopts the Reference Model, in which requirements are supposed to be met not by the projected software system behavior alone but through collaboration between the system and events occurring in its environment, hence the term Collaborative System.Murphy provides risk analysis facilities that include an activity-oriented ontology for carrying out risk analysis by systematically identifying risky activities in the system and in the environment, thereby obtaining a Risk Analysis Graph (RAG) and towards devising risk mitigation strategies later.In order to see both the strengths and weaknesses of Murphy, we experimented on developing a smartphone app involving a group of Ph.D. and senior-level graduate students -one group using Murphy and the other not using Murphy.Our observation, we feel, shows that the risks identified by the group using Murphy were able to identify more critical risks and those risks were comprehensive and relevant as.well.The results also showed that incorporating risk mitigation strategies for the risks identified can indeed help avoid them to some extent.