Design Of An Intelligent Framework For Managing Vuca In Software Requirement Risks

Abstract

Now-a-days, Information technology has covered almost every aspect of human life. newlineThe software industry is a main component of IT industry. Software projects have a newlinevery high probability of failure and a major reason behind is poor requirement newlineengineering process. It is a widely accepted fact that requirements are the backbone of newlineany software product. These are the conditions or capabilities to be met by a system to newlinesatisfy a contract, specification or any other formally imposed documents. A good newlinequality software requirement specification document is the key of successful product newlinedevelopment and delivery. Requirement elicitation and documentation is the primary newlineand vital step in software development life cycle. It is also a very critical phase where newlinerequirements must be analysed for any potential risk. Potential requirement related newlinethreats or risks must be identified in the earlier stages of development so that negative newlineimpact of their effect can be minimized. Study of various surveys and literature reveals newlinethat requirement risk especially volatility, uncertainty, complexity and ambiguity in the newlinerequirements have a significant role in success of a software project. These four risks newlineare also abbreviated as VUCA risks that are also accepted in other industries. newlineRequirement volatility is defined as a threat to any software under development. It is not newlinealways possible to ignore it. Sometimes the requirements are essential to be changed or newlinethe client may reject the software without his desired change. Volatility factors like newlinechangeability, detectability and dependability have been used to prioritize the volatile newlinerequirements. Requirement ambiguity is a very common threat that is present in almost newlineevery requirement specification document. Existence ambiguous words or sentences in newlinethe requirement document may completely change the direction of product being newlinedeveloped. Ambiguity in requirements leads to uncertainty of requirements. The newlinerelationship between uncertainty and ambiguity is analysed. Requirement complexity newlinehas