EGATSU-SP flashcards
EGATSU-SP · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- System boundary
- The conceptual line separating a system from its environment, defining which elements are inside the system and which external entities interact with it across interfaces.
- Verification
- Confirmation through objective evidence that specified requirements have been fulfilled; it answers whether the product was built according to its specification.
- Validation
- Confirmation that the requirements for a specific intended use have been fulfilled; it answers whether the correct product was built for its users.
- Traceability
- The ability to follow the life of a requirement in forward and backward directions, linking it to sources, design elements, implementation, and tests.
- Configuration item
- An entity within a configuration that satisfies an end-use function and can be uniquely identified at a given reference point for configuration management purposes.
- SMART requirements
- A mnemonic for Specific, Measurable, Achievable, Relevant, and Time-bound; requirements failing any criterion are ambiguous or untestable and need revision.
- MoSCoW prioritization
- A prioritization scheme classifying requirements as Must have, Should have, Could have, or Won't have; Must-have items are mandatory for the current delivery.
- Requirements traceability matrix
- A table mapping each requirement to its source, design element, implementation artifact, and test case, revealing coverage gaps and change impact.
- Non-functional requirement
- A requirement describing a quality attribute or constraint of a system, such as performance, security, usability, or reliability, rather than a specific behavior.
- Use case
- A sequence of actions a system performs that yields an observable result of value to an actor, typically documented with preconditions, postconditions, and flows.
- Earned Value Management
- A project performance technique comparing planned value, earned value, and actual cost; SPI = EV/PV and CPI = EV/AC indicate schedule and cost health.
- Coupling and cohesion
- Design metrics where low coupling means modules depend on each other minimally and high cohesion means a module's elements belong together functionally.
- Interface Control Document
- A document defining the physical, electrical, and logical characteristics of an interface between two system elements, including data formats and protocols.
- Layered architecture
- A design structure in which each layer provides services to the layer above and consumes services from the layer below, with strict layering forbidding skip-layer calls.
- Design pattern
- A reusable solution to a recurring design problem, categorized as creational, structural, or behavioral, and described independently of any specific implementation.
- Preliminary design review
- A formal review confirming that the allocated baseline and preliminary design satisfy requirements and that the design is ready to proceed to detailed design.
- Configuration management
- A discipline comprising identification, control, status accounting, and audit of configuration items to maintain integrity throughout the product lifecycle.
- Change control board
- The authority responsible for reviewing, approving, or rejecting proposed changes to a configuration baseline and ensuring impact assessment is performed.
- Infrastructure as Code
- Provisioning and managing infrastructure through machine-readable definition files rather than manual processes, enabling repeatable and version-controlled environments.
- Functional configuration audit
- A review verifying that a configuration item's actual performance meets the requirements specified in its functional and allocated baselines.
- Boundary value analysis
- A black-box test technique selecting values at and just inside or outside the boundaries of input domains, where defects are most likely to occur.
- Equivalence partitioning
- A black-box technique dividing input data into classes where all members are expected to be processed similarly, reducing the number of test cases needed.
- Regression testing
- Re-execution of selected tests after changes to confirm that no new defects were introduced, with test selection guided by change impact analysis.
- Quality assurance versus quality control
- Quality assurance is process-oriented and preventive, while quality control is product-oriented and detective; testing is an example of quality control.
- Defect severity and priority
- Severity measures the impact of a defect on system operation, while priority measures the urgency of its fix; the two attributes are independent.
- MTBF and MTTR
- Mean time between failures is total operating time divided by failure count; mean time to repair is total downtime divided by incident count; availability = MTBF/(MTBF+MTTR).
- Root cause analysis
- A structured method such as 5 Whys, fishbone diagram, or fault tree analysis used to identify the fundamental reason a problem occurred, not just its symptoms.
- Runbook
- A version-controlled document of procedures for routine operations and incident response, tested in advance and maintained as the system evolves.
- Predictive maintenance
- Maintenance triggered by condition data and trend analysis rather than fixed schedules or failures, aiming to intervene before a functional failure occurs.
- CIA triad
- The core security model of confidentiality, integrity, and availability, where each attribute must be considered when designing and evaluating controls.
- Risk response options
- The four standard strategies for handling risk: avoid, mitigate, transfer, and accept; residual risk remains after controls are applied.
- Defense in depth
- A security strategy using multiple layered controls across physical, network, host, application, and data domains so that one failure does not compromise the system.