A Software Project Risk Analysis Tool Using Software Development Goal Modeling Approach

Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 340)

Abstract

There are fewer practices for identification of risk factors in software development though everyone is aware of the impact of risks over project’s success parameters. To avoid risks or to identify risks, each team member needs to practice goal modeling at each phase of software development life cycle. It is not only project manager’s task to focus over risk occurrences but also it must be the duty of each team member to keep an eye on an assigned task and relative risk factors. As per an industrial need, “Sketch the Risk” tool is designed and developed in the most user-friendly way and hence, any team member from the project group can analyze given task from many views. The focus of development of “Sketch the Risk” tool is to identify risk events and avoid risk factors like project development delays, increase in the estimated cost, unnecessary rework, human resources utilization, etc. Unlike of existing approaches that are focusing over early stage to identify risk events, we proposed and developed new technique that takes care at each stage of software development life cycle. In essence, this paper presents identification goals and sub-goals in recurring manner just parallel to the spiral model of the software process.

Keywords

Requirement engineering Requirement oriented goal analysis Requirement-driven risk analysis Software risk 

References

  1. 1.
    Aversano, L., Grasso, C., Tortorella, M.: Goal-driven approach for business/IT alignment evaluation. Procedia Technol. 9, 388–398 (2013)CrossRefGoogle Scholar
  2. 2.
    Zhang, H., Li, J., Zhu, L., Jeffery, R., Liu, Y., Wang, Q., Li, M.: Investigating dependencies in software requirements for change propagation analysis. Inf. Softw. Technol. 56(1), 40–53 (2014)CrossRefGoogle Scholar
  3. 3.
    França, A.C.C., Da Silva, F.Q., Felix, A.D.L., Carneiro, D.E.: Motivation in software engineering industrial practice: a cross-case analysis of two software organisations. Inf. Softw. Technol. 56(1), 79–101 (2014)CrossRefGoogle Scholar
  4. 4.
    Schnabel, I., Pizka, M.: Goal-driven software development. In: IEEE 30th Annual IEEE/NASA Software Engineering Workshop, SEW’06 (2006)Google Scholar
  5. 5.
    Verner, J.M., et al.: Risks and risk mitigation in global software development: A tertiary study. Inf. Softw. Technol. 56(1), 54–78 (2014)Google Scholar
  6. 6.
    Dalpiaz, F., Souza, V.E.S., Mylopoulos, J.: The many faces of operationalization in goal-oriented requirements engineering. In: Proceedings of the Tenth Asia-Pacific Conference on Conceptual Modelling, vol.154. Australian Computer Society, Inc. (2014)Google Scholar
  7. 7.
    Zvonko, K., Kafol, C.: Types of risk in a system engineering environment and software tools for risk analysis. Procedia Eng. 69, 177–183 (2014)CrossRefGoogle Scholar
  8. 8.
    Mogk, N.W.: A requirements management system based on an optimization model of the design process. Procedia Comput. Sci. 28, 221–227 (2014)Google Scholar
  9. 9.
    Wang, T., Li, B., Zhao, L., Zhang, X.: A goal-driven self-adaptive software system design framework based on agent. Phys. Procedia 24, 2010–2016 (2012)CrossRefGoogle Scholar
  10. 10.
    Patil, S., Ade, R.: Software requirement engineering risk prediction model. Int. J. Comput. Appl. 102(2), 1–6 (2014) Google Scholar

Copyright information

© Springer India 2015

Authors and Affiliations

  1. 1.D.Y. Patil School of Engineering and TechnologyPune UniversityPuneIndia

Personalised recommendations