Topic: Risk Analysis

Message


    A second technique for allocating testing resources is based on the concept
															of risk. A risk is anything that threatens the successful achievement
															of the projects goals. The principle here is test most heavily those
															portions of the system that pose the highest risk to the project to ensure that
															the most harmful faults are identified. 


														Risks are divided into three types: business, technical and project risks.
														Project risks are largely managerial and environmental risks, such as an
														insufficient supply of qualified personnel, that do not directly affect the
														testing process. I will show how both business and technical risks are
														applicable to testing software systems.

														Business risks correspond to domain related concepts. For example, changes
														in IRS reporting regulations would be a risk for an accounting system because
														the systems functionality must be altered to conform to the new regulations.
														This type of risk is related to the functionality of the program and therefore
														to the system level testing.

														Technical risks include some implementation concepts. For example, the
														quality of code generated by the compiler is a technical risk. This type of
														risk is related to the implementation of the program and hence to the component
														level testing process.


Edited by Sangita - 19Jun2007 at 9:58pm

Author	Message
Sangita Groupie Joined: 27Apr2007 Online Status: Offline Posts: 53	Topic: Risk Analysis Posted: 19Jun2007 at 9:57pm
	A second technique for allocating testing resources is based on the concept of risk. A risk is anything that threatens the successful achievement of the projects goals. The principle here is test most heavily those portions of the system that pose the highest risk to the project to ensure that the most harmful faults are identified. Risks are divided into three types: business, technical and project risks. Project risks are largely managerial and environmental risks, such as an insufficient supply of qualified personnel, that do not directly affect the testing process. I will show how both business and technical risks are applicable to testing software systems. Business risks correspond to domain related concepts. For example, changes in IRS reporting regulations would be a risk for an accounting system because the systems functionality must be altered to conform to the new regulations. This type of risk is related to the functionality of the program and therefore to the system level testing. Technical risks include some implementation concepts. For example, the quality of code generated by the compiler is a technical risk. This type of risk is related to the implementation of the program and hence to the component level testing process. Edited by Sangita - 19Jun2007 at 9:58pm Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Beginners @ OneStopTesting