software quality

Question 1

load testing

Answer 1

checks application ability to perform under anticipated user loads. identify performance bottle necks

Question 2

stress testing

Answer 2

testing application under extreme workloads to see how it handles high traffic. identify breaking point

Question 3

endurance testing

Answer 3

make sure that the software can handle the load over a long period of time

Question 4

spike testing

Answer 4

tests reaction to sudden large spikes in user load

Question 5

scalability testing

Answer 5

determine the application’s effectiveness in scaling up to support an increase in the user load

Question 6

smoke testing

Answer 6

software testing process that determine whether the deployed software build is stable or not. confirmation for the QA team to proceed with further software testing. consists of minimal set of tests run on each build to test software functionalities

Question 7

vulnerability scanning

Answer 7

done through automated software to scna a system against known vulnerability signatutes

Question 8

security scanning

Answer 8

identifying network and system weaknesses and later provides solutions for reducing these risks

Question 9

penetration testting

Answer 9

simulates an attack frm a malicious hacker

Question 10

risk assessment

Answer 10

involves analysis of security risks observed in the organization and recommends control measures

Question 11

security auditing

Answer 11

internal inspection of applications and OS for security flaws

Question 12

ethical hacking

Answer 12

hacking organization software systems - expose security flaws in the system

Question 13

posture assessment

Answer 13

combines security scanning, ethical hacking and risk assessments to show an overall security posture of an organization

Question 14

software quality attributes - runtime

Answer 14

performance
security
availability
functionality
usability

Question 15

software quality attributes - runtime AVAILABILITY

Answer 15

probability that the sysyem is operating properly when it is requested for use. probability that a system is not failed or undergoing a repair action when it needs to be used

Question 16

MTBF

Answer 16

mean time between failures - average time between failures of a tech product. higher the time between failure, the more reliable the system.

Question 17

MTTR

Answer 17

mean time to repair a system either manually or technically. includes repair and testing time. clock only stops when system is fully functional again

Question 18

MTTR (the other one)

Answer 18

mean time to recovery/restore - time to recover from failure

Question 19

MTTF

Answer 19

Mean time to failure - average time between non-repairable failures of a tech product

Question 20

why do usability tests

Answer 20

uncover problems in the design
discover opportunities to improve
learn about users behavior and preferences

Question 21

software quality attributes - non-runtime

Answer 21

modifiability/maintainability 
portability
reusability
integrability
testability

Question 22

modifiability

Answer 22

relates to the cost of change and refers to the ease with which a software system can accommodate changes

Question 23

portability

Answer 23

the possibility to use the same software in different environments
software that is available for two or more different platforms or can be recompiled for that system

Question 24

reusability

Answer 24

modularity - dividing code into reusable sections
high cohesion - modules should be functionally related to perform a task
low coupling - low level of interdependence between modules

Question 25

integrability vs interoperability

Answer 25

interoperability - real time data exhange between different system that speak directly to one another in the same language
integration - process of combining mulitple applications to function together as one uninterrupted system often using middleware

Question 26

testability

Answer 26

should be easy enough to run any test

Question 27

Benefits of code reviews

Answer 27

consistent design and implementation
minimizing your mistakes and their impact
ensureing project requirements and meeting requirements
improving code performance
sharing new techniques

Question 28

some software quality metrics

Answer 28

number of lines, files
field bugs
code churn 
static analysis findings
bug arrival rate
test failures