Risk is a concept that denotes the precise probability of specific eventualities.
Listed below are Risk in software quality assurance:

1. Risk of new technology: Generally software is developed in the presence of new technology. Typically, such changes mean that those who program to this interface or platform must “come up to speed” on it. Whenever new technology is involved there is an always a risk that it will take longer than anticipated to create the desired software. There is always a risk for creating a highly-prone code or architecture.
2. Risk of no testability: This risk is easiest to solve, yet it is hardest to implement in on-going organization. Testability is also affected by such things as complexity, nested loops versus module calls, nested IF THEN ELSE structures versus CASE structures and module calls, dependencies, programmer assumptions, inconsistent patterns, poor modularity and environmental dependencies.
3. Risk of poor training: Some companies refuse to send their employees to conference or take commercial courses. Employees have a difficult time keeping up with technology. This results in software which is with lot of mistakes or bad designs.
4. Risk of missing deadlines : One major risk is not getting a product to market in time to exploit the marketing window is fixed; how much of a product a company sells depends on how early their product reaches the marketplace within that marketing window.
5. Risk of poorly defined users: When there is a potential of millions of users, it is often very difficult to describe the user environment. If a software product is felt as being too difficult to use, going down too extended a period of time, or not doing exactly what users want or what their business needs, users tend to look the competition .If users do not “trust” a company’s product , they will look elsewhere.

Related posts:

1. Pros and Cons of Automatic Software for Website Submission
2. Type of Software Testing Positions
3. Costs Associated With Risk Management