Podcast
Questions and Answers
What is the primary purpose of functional testing after code development?
What is the primary purpose of functional testing after code development?
Which of the following is NOT a type of testing performed during the V&V process?
Which of the following is NOT a type of testing performed during the V&V process?
What key documentation describes how validation will be performed?
What key documentation describes how validation will be performed?
Which technique is commonly used to identify defects during the development process?
Which technique is commonly used to identify defects during the development process?
Signup and view all the answers
What is the role of a Test Plan in the validation process?
What is the role of a Test Plan in the validation process?
Signup and view all the answers
In Risk Management, which of the following statements is most accurate?
In Risk Management, which of the following statements is most accurate?
Signup and view all the answers
What is the purpose of maintaining Review Logs?
What is the purpose of maintaining Review Logs?
Signup and view all the answers
Which of the following is a common method for ensuring processes were followed correctly?
Which of the following is a common method for ensuring processes were followed correctly?
Signup and view all the answers
Which phase occurs immediately after testing in the software development lifecycle?
Which phase occurs immediately after testing in the software development lifecycle?
Signup and view all the answers
What characterizes a risk in a project context?
What characterizes a risk in a project context?
Signup and view all the answers
Study Notes
Software Risks
- Schedule Risk: Wrong time estimation, untracked resources, unidentified complex functionalities, and unexpected project scope expansions.
- Budget Risk: Wrong budget estimation, cost overruns, and project scope expansion.
Programmatic Risks
- Running out of funds, market development, changing customer product strategy and priorities, and government rule changes.
Operational Risks
- Risk of loss due to improper process implementation, failed system, or external event risks.
- Failure to address priority conflicts, resolve responsibilities, and insufficient resources.
- No proper subject training, resource planning, or communication within the team.
Technical Risks
- Causes: Continuously changing requirements, unavailable or initial-stage technology, complex product implementation, and difficult project module integration.
- Consequences: Failure of functionality and performance.
Software Development Risks
- Improper use of technology, inability to translate user needs into technical requirements, uncontrolled system access, and ineffective security and privacy practices.
- Program errors.
Testing Risks
- Not Enough Training/Lack of Test Competency, Lack of Test Tools, Lack of Management Understanding and Support of Testing.
- Lack of Customer and User Involvement, Not Enough Schedule or Budget for Testing.
Risk Mitigation
- Form a risk analysis team, identify risks, estimate the magnitude of risk, and examine work documents for review comments.
Dynamic Testing
- Main objective: Confirm that the software product works in conformance with business requirements.
- Executing code to check functional behavior, memory/cpu usage, and overall system performance.
- Performed at all levels of testing, can be black or white box testing.
V&V Involvement in SDLC
Requirements Phase Activities
- Determine test strategy, adequacy of requirements, and generate functional test conditions.
Design Phase Activities
- Determine consistency of design with requirements, adequacy of design, and adequacy of test plans.
- Generate structural and functional test conditions.
Program (Build) Phase Activities
- Determine consistency with design, adequacy of implementation, and generate structural and functional test conditions for modules and units.
Test Phase Activities
- Test application system.
Installation Phase Activities
- Place tested system into production.
Maintenance Phase Activities
- Modify and retest.
Requirement Validation & Review
- Walkthroughs, reviews, and inspections are techniques to identify defects at each stage of development and maintenance.
- Key documentation: Verification Review logs, Check sheets.
Validation
- Ensures the system operates according to plan by executing system functions through a series of tests.
- Key documentation: Validation Test Strategy and Test Plan, Test cases and test scripts, Test results log, Check sheets, Defect logs.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
Related Documents
Description
This quiz covers various risks associated with software development, including schedule risks, resource risks, and budget risks. It helps in understanding the common pitfalls and challenges that can affect the success of a software project.
