1. outline 3 major problems with software measurement in the software industry.

i. changing requirements in the software evolution process makes measurement tricky against
shifting or new requirements.

ii. limited time, budget and skilled personnel might hinder the implementation of
measurement process leading to inconsistencies in results.

iii. different people might interpret measurement differently leading to confusions.

2. list 3 low-cost technique for software reliability improvement.

i. code review: team members check each other’s code for potential mistakes.

ii. automated testing: using special tools like JUnit, TestNG, Postman, Jenkins, cucumber, to
test the software automatically.

JUnit: Test java program applications

TestNG: Test java software

Postman: Test if online servers respond correctly.

Jenkins: Automates tasks.

Cucumber: to test if software behaves correctly based on plain text descriptions.

iii. updates: listening to users’ feedback for problems they find and fixing it.

3. why is testing a separate area of expertise?

Because testing requires specialized skills and focus for quality assurance. Testing examines the software
from the user perspective. Testing pays close attention to details ensuring the software works well &
provide great experience for users.

4. identify 3 important types of testing that developers don’t do.

Devs don’t do security testing because, security testing requires specialized skills. E.g., web applications
specialist, network security specialist etc.

Devs don’t do performance testing because, performance testing checks how software handles users or
speed.

Devs don’t do usability testing because, usability testing checks if software is easy for regular people to
use.

NB: Generally, Devs write the efficient codes for a software system.
 5. why defect & bugs in a software product may not lead to software failure?

i. Because minor defects do not affect the overall software functionality.

ii. Because users can find ways to use the software system effectively despite the presence of
minor defects or bugs.

6. what is software metrics and their usefulness in software development.

Metrics are quantitative measures such as measurement of lines of code, measurement of complexity,
bug count, & testing coverage.

USEFULLNESS:

Guides devs to track progress & identify issues to improve the overall software quality. Also assists the
devs to make data driven decisions.

7. what is the role of the team leader for software quality review team?

i. Oversees the review process, ensuring each team member collaborates.

ii. Monitors quality assurance processes, ensuring standards are meet.

iii. Promptly solve problems ensuring smooth progress.

iv. Leaders make critical judgements to ensure that issues of high priority are addressed.

8. what are the phases in the software quality review process?

Planning; defining objectives, scopes, and method.

Execution; reviewing, finding, and documenting issues.

Reporting; summarizing findings and suggesting improvements.

9. what are software standards and its importance in the software industry?

Software standards are the guidelines to follow if you want to achieve software quality in software
development.

Importance:

Software standards ensures safety, consistency, & compatibility in a software industry fostering
software reliability.
 10. what’s the difference between software testing and software inspection?

Testing is executing the software to find defects.

Inspection is manually examining the software without executing the software.

11. what do the following software testing types FOCUSED on?

i. unit testing focuses on testing individual components for correctness.

ii. component testing focuses on testing larger parts of software.

iii. system testing focuses on testing the whole complete system.

iv. integrated testing focuses on checking interactions between integrated components.

v. white-box testing focuses on internal structures and algorithms.

vi. black-box testing focuses on assessing functionality.

11. what’s the difference between software validation and software verification?

Validation ensures that software meet user requirements & verification confirms that the software
meets specifications and standards.

12. outline the good practices that will serve as guidelines dependable programming.

i. proper documentation to understand every line code function.

ii. regular testing to catch and fix issues early.

iii. evolution control to keep track of changes.

13. what’s software maintenance?

Modifying software post-release to correct defects & enhance features.

14. types of software maintenance.

i. corrective maintenance, fixing errors and defects.

ii. adaptive maintenance, introducing software to new environments.

iii. perfective maintenance, improving software features & performances.

15. system reliability is measured by counting the number of operational failures and relating to the
demands made on the system and the time that the system has been operational. a long-term
measurement program is required to access the reliability of critical systems, define:
i. probability of failure on demand, likelihood of failure when system is demanded.

ii. rate of occurrence of failure, frequency of failure over a specified period

iii. meantime to failure, average time until failure occurs.

iv. availability, proportion of the time the system is operational.