Practice Test Geeks(Echocardiogram) Certified Echocardiogram Technician Practice Test
← All ECHOCARDIOGRAM Flashcard Decks

Software Development Lifecycle Flashcards

7 cards from real ECHOCARDIOGRAM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Software Development Lifecycle flashcards as text

  1. What is the purpose of a 'software validation plan' required for FDA-regulated echo analysis software?

    Answer: To document how the software will be tested to confirm it performs as intended for clinical use

    FDA 21 CFR Part 11 and related guidance require a validation plan that documents test strategies to confirm software meets its intended clinical use.

  2. Which SDLC concept describes breaking a large echocardiography platform into smaller, independently deployable services (e.g., separate report generator and measurement engine)?

    Answer: Microservices architecture

    Microservices architecture splits an application into loosely coupled services that can be developed, deployed, and scaled independently.

  3. During SDLC planning for a new echo AI feature, a team creates a list of tasks, estimates effort, and assigns priorities. This is known as:

    Answer: Backlog grooming

    Backlog grooming (or refinement) is the process of reviewing, estimating, and prioritizing items in the product backlog before a sprint.

  4. What does 'continuous integration' (CI) mean in the development of echo software?

    Answer: Automatically merging and testing code changes frequently to detect defects early

    CI automatically builds and tests the codebase whenever a developer commits changes, catching integration errors as early as possible.

  5. A hospital's echo software project is delayed because requirements kept changing mid-development. Which SDLC model is best suited to accommodate frequent requirement changes?

    Answer: Agile/Scrum

    Agile/Scrum embraces changing requirements through short iterative sprints and regular stakeholder collaboration.

  6. What is the significance of 'traceability matrices' in healthcare SDLC documentation?

    Answer: They link each requirement to its corresponding design, code, and test cases to ensure complete coverage

    A requirements traceability matrix ensures every requirement is designed, implemented, and tested, which is essential for FDA and Joint Commission compliance.

  7. In SDLC, what is 'technical debt' in the context of an aging echocardiography reporting system?

    Answer: Accumulated shortcuts or outdated code that makes future changes harder and more costly

    Technical debt refers to the implied cost of rework caused by choosing expedient short-term solutions over better long-term approaches.