Describe the details of FTR and Walkthrough.

FTR (Formal Technical Review) and Walkthrough are both methods used in software engineering for inspecting and reviewing software artifacts, such as requirements documents, design specifications, or code. Let’s break down each one:

1. Formal Technical Review (FTR):

• Purpose: FTR aims to identify defects and issues in software artifacts early in the development process.
• Participants: Typically involves a formal group of reviewers, including developers, testers, project managers, and sometimes users or stakeholders.
• Process:
  • Preparation: Before the review meeting, the artifact to be reviewed is distributed to all participants. Reviewers examine the artifact thoroughly, noting any defects, ambiguities, or inconsistencies.
  • Meeting: In a structured meeting, the reviewers discuss their findings and document them. Discussions may involve clarifying requirements, questioning design decisions, or pointing out potential problems.
  • Follow-up: After the meeting, the author of the artifact addresses the identified issues, making corrections or modifications as necessary.
• Documentation: The results of the review, including identified issues and actions taken, are documented for future reference.

1. Walkthrough:

• Purpose: Walkthroughs are more informal compared to FTR and are primarily aimed at familiarizing team members with the content of a document or code.
• Participants: Typically involves the author of the artifact and a small group of peers or stakeholders.
• Process:
  • Presenter: The author presents the artifact, walking through its content, explaining its purpose, structure, and key points.
  • Discussion: Participants can ask questions, seek clarification, or provide feedback during the walkthrough. This interaction helps in ensuring everyone understands the artifact and can provide valuable insights.
  • Note-taking: Notes may be taken during the walkthrough to capture feedback, questions, and suggestions.
• Follow-up: After the walkthrough, the author may revise the artifact based on the feedback received.

Key Differences:

• Formality: FTR is more formal, structured, and involves a larger group of reviewers. Walkthroughs are less formal and typically involve a smaller group.
• Purpose: FTR focuses on identifying defects and improving quality, while walkthroughs are more about understanding and gathering feedback.
• Depth of Review: FTR involves a thorough examination of the artifact for defects and issues, while walkthroughs are more focused on understanding the content and gathering initial impressions.

Here is an comparision between both : https://www.doubtly.in/q/compare-ftr-walkthrough-sepm/