QAfOSS Model Instruction
	QAfOSS	-	Quality Assurance Framework for Open Source Software Development
	Introduction
		The research focuses on Quality Assurance activities under the Open Source Software Development Model. The result of the study contributes to the development of the QAfOSS framework.
		The QAfOSS framework aims the determination of the process capability in OSS projects and measures a project success factor. In the following, the measurement method is briefly explained.
		Use this link to the QAfOSS framework
	Process Capability Determination
		The process capability determination method measures the capability level of applied processes in your OSS project. The project you contribute most too is in scope of this assessment. The result shows the degree the model fits to your processes. These findings are used for further statistical analysis to show correlations between process capability and project success.
		Please consider that terms are kept general. Process outcomes, purposes and practices are defined in generally accepted QA terms. Sometimes, the ability to abstract is required when comparing stated practices to your project. For instance, process outcomes are achieved similarly but the process is used more informally as defined in the framework. In this case mark the process as 'applied' and perform the evaluation as described below.
		Please enter values only in the yellow fields
		How to approach the Process Capability Determination Method?
		Evaluate every process in terms of applicability and its characteristics
		1.	Determine the applicability of the process:
			If the process is applied (even informal) - select 8
			If the process is not applied at all select 0 - skip step 2 and proceed with step 3
		2.	If a process exists - evaluate its characteristic:
			Evaluate for each process the four criteria:
			Functionality measures the process compliance, its completeness and suitability in the project environment. The assessment focuses on the compliance to standards, the completeness and correctness of transformation from input to output.	Functionality is rated:
				+4 Over fulfilled
			Example: Requirements Review Process - if e.g. in your opinion new features are continuously reviewed in a scheduled core team meeting, results are tracked and changes are incorporated into project planning would this express the functionality is 'over fulfilled'.	+2 Strongly fulfilled
				0 Mainly fulfilled
				-2 Partially fulfilled
				-4 Not fulfilled
			Usability focuses on the understandability, learnability and operability aspects of a process. It describes the efforts to understand and to learn the process as well as the capability of the process executor to use it.	Usability is rated:
				+1 Strongly fulfilled
			Example: Requirements Review Process - if e.g. in your opinion this process is easy to understand and operable then the usability is 'strongly fulfilled'.	0 Mainly fulfilled
				-1 Partially fulfilled
			Reliability regards the process fault tolerance and its maturity. It measures how reliable the process itself is and determines the failures during the process as its recoverability. The maturity is determined by the capability of the process to avoid failures because of faults in the process.	Reliability is rated:
				+1 Strongly fulfilled
			Example: Requirements Review Process - if e.g. to your opinion the process is well established and reliable then the reliability is 'strongly fulfilled'.	0 Mainly fulfilled
				-1 Partially fulfilled
			Efficiency rates the process performance in terms of e.g. time behaviour or the resource utilisation as degree of output to input. For instance the required processing time, the resource usage or the degree of complexity compared to the process results.	Efficiency is rated:
				+2 Over fulfilled
			Example: Requirements Review Process - if e.g. in your opinion the process is highly efficient as it leverages resources efficiently and delivers good results then the process efficiency is 'over fulfilled'	+1 Strongly fulfilled
				0 Mainly fulfilled
				-1 Partially fulfilled
				-2 Not fulfilled
		3.	Assign degree of importance of the process	Anticipated Importance:
			In your opinion please evaluate the importance of the process.	5 Major importance
			Select a value in the range from 5-0 according to the scale.	4 Strongly important
				3 Important
				2 Minor important
				1 Less important
				0 Not relevant at all
		4.	Please enter your comments
			Please describe any deviations, missing activities and give us suggestions for further improvements.