1. learn-ability 2.speed of operation, 3. robustness 4. recoverability, 5. adaptability


user familiarity
consistency
recoverability
user guidance
user diversity


SRS:

A Software Requirements Specification (SRS) - a requirements specification for a software system - is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).

* --> requirements -> measurable, verifiable, testable, quantifiable, clear, understandable


RISK:
probablity / impact matrix


Risk register

Risk Category 	Risk Name 	Risk Number 	Probability (1-3) 	Impact (1-3) 	Risk Score 	Mitigation 	Contingency 	Action By 	Action When
Guests 	The guests find the party boring 	1.1. 	2 	2 	4 	Invite crazy friends, provide sufficient liquor 	Bring out the karaoke 	Mack 	within 2hrs
Guests 	Drunken brawl 	1.2. 	1 	3 	3 	Don’t invite crazy friends, don't provide too much liquor 	Bring in the guards 	Jerry 	Now
Nature 	Rain 	2.1. 	2 	2 	4 	Have the party indoors 	Move the party indoors 	Milind 	10mins
Nature 	Earthquake or fire 	2.2. 	1 	3 	3 	Start the party with instructions on what to do in the event of fire or earthquake 	Implement the appropriate natural disaster response plan 	Everyone 	As per plan
Food 	Not enough food 	3.1. 	1 	2 	2 	Have a buffer 	Order pizza 	Magua 	30mins
Food 	Food is spoiled 	3.2. 	1 	3 	3 	Store the food in deep freezer 	Order pizza 	Zubair Malik 	30mins

----
quality conformance to requirements (product and  project processes)
	- fitness for use.(product does what was intended).

        *** How to manage quality?
                testing, customer testing, quality of code -> NF's, measuring
                how was it managed / monitored.

	quality planning -> how to meet the specs.
	quality assurance -> overall checks -> meet specs / processes  (PERIODIC)
	quality control -> monitoring specific results -> meet specs /processes (PERIODIC)  --> every developer is doing as they should