Software Testing
Software Testing
1 2
Project planning
Involves defining objectives, creating a work breakdown
structure, identifying task dependencies, allocating resources,
and assessing risks.
Software metrics
Software metrics are quantitative measures used to assess various aspects
of software development, including size, complexity, quality, and efficiency
2 Risk Management
Risk management involves identifying, assessing, and mitigating potential risks to ensure
project success. This includes evaluating impact, creating mitigation plans, monitoring risks,
implementing responses, and documenting information.
COCOMO and risk management are essential for successful project planning, control, and
delivery.
Cocomo model
Cocomo (Constructive Cost Model) is a regression model based on LOC, used to predict project
parameters such as size, effort, cost, time, and quality.
Organic : Organic software projects require small team size, well-understood problem, and
experience.
Embedded : A software project requiring the highest level of complexity, creativity, and
experience requirement fall under this category.
E= a(KLOC)^b
time= c(Effort)^d
Risk Management
Risk management in software testing involves identifying, analyzing, and mitigating potential risks to
minimize their negative impact. It allows for proactive decision-making, resource allocation, and
contingency planning, ultimately improving the overall effectiveness and success of software testing
projects.
Key points:
Risk Identification: The first step in risk management is to identify potential risks that may arise
during the testing process.
Risk Monitoring and Control: Throughout the testing process, risks should be continuously
monitored to track their status and effectiveness of mitigation strategies.
Regular communication and sharing of risk-related information help ensure everyone is aware of the
identified risks and mitigation actions.
Software Reliability and
Quality Assurance