Want to create interactive content? It’s easy in Genially!

STATIC TESTING

Zoya Jetham

Created on July 12, 2023

Start designing with a free template

Discover more than 1500 professional designs like these:

Corporate Christmas Presentation

Customer Service Manual

Business Results Presentation

Meeting Plan Presentation

Business vision deck

Economic Presentation

Tech Presentation Mobile

Explore all templates

Static Testing tECHNIQUES - REVIEWS

WalkTHROUGH TECHNICAL REVIEW INSPECTION

Start

Static Testing Techniques

Static Testing

Review

Static Analysis

Informal

Technical Review

Inspection

Walkthrough

STATIC Testing

Level of Formality

Low

Informal

Walkthrough

Level of Formality

Technical Review

Inspection

High

Walkthrough

INTRODUCTION

Collaborative sessions led by document authors.
Authors guide participants through the content, aiming for common understanding and feedback.
Purpose: Ensure clarity and gather valuable input.
Particularly useful when involving stakeholders outside the software discipline.

Goals of walkthrough

Presenting the document to stakeholders both within and outside the software discipline to gather information and feedback.

Explaining and evaluating the document's contents, ensuring clarity and identifying any potential issues.

Establishing a common understanding among all participants, ensuring everyone is aligned.

Examining and discussing proposed solutions, alternatives, and reaching a consensus.

Addressing and resolving any conflicts or disagreements that arise during the discussion and feedback process.

Fivegoals

WALKTHROUGH

Benefits of Walkthroughs

01

Improved Communication and Collaboration

01. Communication

02

Early Issue Detection and Resolution

02. Early Detection

03

Knowledge Transfer and Learning

03. Knowledge Transfer

04

Stakeholder Satisfaction

04. Stakeholder Satisfaction

Technical Review

Khushi PatelD105

Technical Review

What is Technical Review?

It is a form of static testing. The technical review approach, involves the examination of various technical documented artifacts, used in the development of a software application, as per the standards and specified requirements.

Design

Development

Operation

Maintenance

+ info

What is Technical Review?

Purpose: To verify and validate the requirements and specifications, implemented in the software application, against, what is specified in the software requirement specification (SRS). It is used to locate defects, prevailed in the design, requirements, specifications, use cases, test cases and other types of documentation work.

Characteristics

Identify errors, inconsistencies, or omissions and to verify that the document is accurate, complete, and compliant with relevant standards and regulations.

Led by a trained moderator, but possibly also by a technical expert.

Technical Reviews are documented and uses a defect detection process that has peers and technical specialist as part of the review process.

Focuses on technical content of the document. It is a less formal review.

Benefits

Can help you to avoid: Incorrect/incomplete information, outdated information, inconsistent/ conflicting information, Compliance issues and formatting or editorial issues.

Ensure, at an early stage, that technical concepts are used correctly

Assess the value of technical concepts and alternatives in the product and project environment

Inform participants of the technical content of the document.

What to Look for in a Technical Document Review:

Structure

Content

Format

Language

Consistency

Compliance

References

Usability

What to Look for in a Technical Document Review:

Review the document’s content to verify that it is accurate, complete, and relevant to its intended purpose. Look for errors, inconsistencies, or omissions in the information presented.

Content

Review the document’s formatting to make sure that it is consistent and easy to read. Look for issues such as font size, spacing, margins, and page numbering.

Format

Review the document’s structure to ensure that it is well-organized and easy to follow. Look for issues such as headings, subheadings, and the logical flow of information.

Structure

Review the document’s language to secure that it is clear, concise, and appropriate for the intended audience. Look for issues such as spelling errors, grammar errors, and overly technical language.

Language

What to Look for in a Technical Document Review:

Review the document to confirm that it complies with applicable regulations, standards, and guidelines. Look for issues such as non-compliance with safety standards, environmental regulations, or data protection laws.

Compliance

References

Review the document’s references to check that they are accurate and up-to-date. Look for issues such as outdated sources or incorrect citations.

Review the document for consistency in terminology, formatting, and style. Look for issues such as inconsistent use of abbreviations, inconsistent capitalization, or inconsistent use of headings.

Consistency

Make sure that the technical document is user-friendly and easy to navigate. Look for issues such as unclear instructions, difficult-to-read fonts, or poorly labeled tables and figures.

Usability

Summary

Walkthrough

Technical Review

Purpose

Ensure clarity and gather valuable input.

Verify and validate the requirements and specifications and detect bugs and defects

Type

Informal

Formal / Informal

Trained moderator or technical expert

Led by

Author

Technical Doc. - Information about the design, development, operation, or maintenance of a technical product or system

Document part

Complete SRS

Inspection

Tanvi Halankar

Technical Review

INTRODUCTION

Most formal review type.

Roles are well-defined.

In the inspection meeting the defects found are logged and any discussion is postponed until the discussion phase.

ROLES INVOLVED

PRODUCER

MODERATOR

REVIEWER

RECORDER/SCRIBE

Reviever:"In Section 5.1, I noticed the presence of a duplicate requirement."

Recorder: "Duplicate requirement of Section 4.3 in Section 5.1""

SRS

STEPS

Planning

Preparation

Inspection Meeting

Logging & Documentation

Discussion Phase

Follow Up

GOALS

Improve document quality

Remove defects early

Common understanding among participants.

Train new employees

Learn from defects and improve

Measure document quality through sampling

CHARACTERISTICS

Involves peers to examine the product

Rules and checklists are used during the preparation phase

The defects found are documented in a logging list or issue log.

Formal follow-up is carried out by the moderator applying exit criteria.

COMPARISON

Technical Review

Walkthrough

Inspection

Author,Moderator,Reviever,Recorder

Moderator / Team Members

Participants

Development Team

Moderator (Inspection Meeting)

Moderator /Technical Expert

Author

Leader

Participants

Formal

Generally Informal

Type

Formal/Informal

What Do You Think?

The recorder is responsible for documenting the defects found during the process.

The recorder is responsible for fixing identified defects.

Info

Spin the wheel!

reviews

ANSWER THE QUESTIONS

0 POINTS

FOR 25 POINTS

What is the primary goal of a walkthrough?

Achieving a common understanding

Identifying defects in the code

Conducting performance testing

25 POINTS

RIGHT!

Keep spinning the wheel!

25 POINTS

FOR 50 POINTS

What are the characteristics of a Technical Review?

Led by a trained moderator, formal, and focuses on technical content.

Led by the development team, less formal, and focuses on usability testing.

Led by a technical expert, formal, and focuses on non-technical content.

75 POINTS

RIGHT!

Keep spinning the wheel!

75 POINTS

FOR 75 POINTS

Which statement best describes the role of inspection in the software development process?

Inspection is an optional activity that can be skipped if the project is running behind schedule.

Inspection is a mandatory activity that must be conducted after software deployment.

Inspection is an important part of quality assurance and helps improve software artifacts.

150 POINTS

RIGHT!

Keep spinning the wheel!

150 POINTS

FOR 100 POINTS

What is one of the benefits of walkthroughs?

Automated code analysis

Real-time debugging

Early issue detection

250 POINTS

RIGHT!

Keep spinning the wheel!

250 POINTS

FOR 250 POINTS

What is the purpose of using checklists during a review or inspection process?

To assign tasks to team members

To ensure that all required elements are included in the document

To document identified defects and their solutions

500 POINTS

RIGHT!

Keep spinning the wheel!

500 POINTS

FOR 500 POINTS

Which aspect should be reviewed to ensure that technical concepts are used correctly?

Compliance

Content

Usability

1000 POINTS

CONGRATULATIONS!

LOG

CHECKLIST

TRY AGAIN!

write your title here

Phasellus at viverra risus. Vivamus vulputate consequat.

Lorem ipsum dolor sit amet

Phasellus at viverra risus. Vivamus vulputate consequat.

Write a subtitle here

Lorem ipsum dolor sit amet

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer odio turpis, varius vitae tempor vel, venenatis vel lectus. Donec molestie, nisi in rhoncus faucibus, nibh dui elementum purus, at efficitur elit magna convallis mauris. Sed ac justo ac felis bibendum tempor ac ac leo. Ut vehicula maximus nisl, vitae luctus neque volutpat et. Phasellus at viverra risus. Vivamus vulputate consequat magna, hendrerit consectetur erat suscipit vitae.

Phasellus at viverra risus. Vivamus vulputate consequat.

Lorem ipsum dolor sit amet

Phasellus at viverra risus. Vivamus vulputate consequat.

+ INFO

Lorem ipsum dolor sit amet

write your title here

Lorem ipsum dolor

43%

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Lorem ipsum dolor

30%

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Lorem ipsum dolor

27%

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Technical Document Review Stages

Compliance Review

Technical Review

Peer/ Editorial Review

Self Review

SUMMARY

Author Leads: The walkthrough is guided by the document's author

Common Understanding: Walkthroughs foster shared comprehension among participants.

By Leveraging team expertise, walkthroughs contribute to project success by identifying risks and exploring diverse perspectives.

write your title here

Phasellus at viverra risus. Vivamus vulputate consequat.

Lorem ipsum dolor sit amet

Phasellus at viverra risus. Vivamus vulputate consequat.

Write a subtitle here

Lorem ipsum dolor sit amet

Phasellus at viverra risus. Vivamus vulputate consequat.

Lorem ipsum dolor sit amet

Phasellus at viverra risus. Vivamus vulputate consequat.

+ INFO

Lorem ipsum dolor sit amet

Walk Through

Reviews

Inspection

Knowledge sharing

Effective and find many faults

Inexpensive, yet finds some faults

Strengths

Output is dependent on the ability of the reviewer

Expensive and requires very skilled participants

Weakness

Find few faults

write your title here

Lorem ipsum dolor

43%

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Lorem ipsum dolor

30%

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Lorem ipsum dolor

27%

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

1000 POINTS

CONGRATULATIONS!

Choose your prize:

Pet

Box

Travel

1000 POINTS

CONGRATULATIONS!

Choose your prize:

Pet

Box

Travel

THE BOX IS EMPTY

1000 POINTS

CONGRATULATIONS!

Choose your prize:

Pet

Box

Travel

Walkthrough

Collaborative sessions led by document authors.
Authors guide participants through the content, aiming for common understanding and feedback.
Purpose: Ensure clarity and gather valuable input.
Particularly useful when involving stakeholders outside the software discipline.

list

subtitle here

Title here

Duis autem vel eum iriure dolor in hendrerit in

Title here

Duis autem vel eum iriure dolor in hendrerit in

Title here

Duis autem vel eum iriure dolor in hendrerit in

6. Methodology

Field work

Lorem ipsum dolor sit amet consectetur adipiscing elit mattis cras habitasse primis, hendrerit condimentum dictum cursus est magna tortor nec sociosqu molestie aenean, quisque porta elementum diam bibendum volutpat leo platea litora dui. Tellus vulputate taciti sodales netus litora dapibus, urna consequat parturient habitasse.

Population and sample

6. Methodology

Procedures and variables

Tools

9. Conclusions

Lorem Ipsum dolor sit amet consecteuter

Discussion

Walkthroughs

Achieving a Common Understanding

MOBILE Mockup

Horizontal infographics

Design

Subtitle

Social beings. We need to interact with one another. We learn in a collaborative way.

Plan

Subtitle

We are visual beings. We can understand images from millions of years ago, even from other cultures.

CReATIVITY

Contextualize your topic

+ INFO

Do you need more reasons to create dynamic content? No problem! 90% of the information we assimilate is received through sight and, what’s more, we retain 42% more information when the content moves.

MOBILE Mockup

Horizontal infographics

+ INFO

DESIGN

Your content is good, but it‘ll engage much more if it’s interactive. Capture your audience's attention with an interactive photo or illustration.

Contextualize your topic

MOBILE Mockup

Horizontal infographics

WOW EFFECT

Contextualize your topic

Yep, you read that right. Interactivity and animation can turn even the most boring content into something super fun. In Genially, we use AI (Awesome interactivity) in all our designs so that you can level up with interactivity and turn your content into something that engages and provides value.

+ INFO

Timeline Title

19XX-19XX

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

19XX

Subtitle here

+info

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent scelerisque euismod arcu, venenatis porttitor quam condimentum ac. Nam ultricies ipsum vel gravida ultrices.

Walkthroughs

Achieving a Common Understanding

Gallery

View +

Gallery II

View

Video

Mauris vulputate sem in tristique interdum.Praesent convallis volutpat cursus. Mauris rutrum dignissim lorem ac euismod.

+ info

Video

Play video

Process

Step 1

Step 2

Step 3

Mauris vulputate sem in tristique interdum pellentes orci enim.

+ info

Comparison

Praesent sagittis dictum ante id elementum. Praesent convallis volutpat cursus. Mauris rutrum dignissim lorem ac euismod. Proin dictum ut orci a venenatis. Etiam efficitur fermentum risus, ut molestie nisl mattis et dolor.

Thanks!

ROLES INVOLVED

PRODUCER

MODERATOR

REVIEWER

RECORDER/SCRIBE

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

REVIEWER

Reviewers are individuals with expertise in the subject matter related to the document under inspection.
They carefully examine the document, compare it with relevant standards, and identify defects, inconsistencies, or areas for improvement.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

19XX

Lorem ipsum dolor sit

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit.

RECORDER/SCRIBE

Responsible for documenting the defects identified during the inspection meeting.
Record each defect with a clear description, its location in the document, and any relevant references.

In this phase of the review, a technical document is checked for clarity, organization, and consistency. The purpose of technical editing is to ensure that the document is easy to read and understand and that the information is presented logically and consistently.

DON'Ts :

DOs :

Structured review plan
Use a checklist or review template to make certain all key areas are covered.
Verify all facts, figures, and data.
Ensure that the document is compliant with applicable regulations and standards.

Provide constructive feedback and suggestions for improvement.
Test the usability of the document, particularly if it is intended for end-users.

Don’t overlook compliance issues or legal requirements.

Making changes without consulting the author or stakeholders is a big no.
Don’t ignore user feedback or suggestions for improvement.
Never fail to follow up or verify that changes have been made.

Documents or Artifacts

The "Software Requirement Specification" (SRS) serves as the key artifact for the walkthrough.

Lays the groundwork for the entire project and acts as a roadmap for the development process.
It details essential features, user interactions, technical constraints, and project timelines

Moderator

The moderator is a trained facilitator who leads the inspection meeting.
They are neutral and not the author of the document.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

REVIEWER

Reviewers are individuals with expertise in the subject matter related to the document under inspection.
They carefully examine the document, compare it with relevant standards, and identify defects, inconsistencies, or areas for improvement.

19XX

Lorem ipsum dolor sit

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Moderator

The moderator is a trained facilitator who leads the inspection meeting.
They are neutral and not the author of the document.

19XX

Lorem ipsum dolor sit

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Author/Producer

Individual or team responsible for creating the document or artifact under inspection.

They prepare the content and submit it for review during the inspection process.

19XX

Lorem ipsum dolor sit

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

This is a final review of a technical document review cycle done before publication or distribution. This technical document evaluation verifies that it complies with applicable regulations, standards, and guidelines. The purpose of compliance review is to ensure that the document meets all relevant requirements and is legally and ethically correct. The purpose of the final review is to check that the document is flawless, complete, and ready for publication.

RECORDER/SCRIBE

Responsible for documenting the defects identified during the inspection meeting.
Record each defect with a clear description, its location in the document, and any relevant references.

In any review process, self-review is mandatory and the writer should hold accountable to produce a quality document. Review for sentence clarity, typos, document structure/layout, grammatical errors, and style. Look at the document through the eyes of an end user and structure accordingly.

DOs :

DON'Ts :

Read the entire document thoroughly before beginning the review.
Verify all facts, figures, and data presented in the document.
Ensure that the document is compliant with applicable regulations and standards and consistent in terminology, formatting, and style.

Never rush through the review process.

Don’t assume that the document is accurate without verifying the information presented.
Never ignore inconsistencies in terminology, formatting, or style.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Author/Producer

Individual or team responsible for creating the document or artifact under inspection.

They prepare the content and submit it for review during the inspection process.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

19XX

Lorem ipsum dolor sit

TE AM

Team Members

The software development team consists of various experts from different disciplines, each contributing their unique expertise.

The members of the team actively participate by sharing their thoughts, pointing out any errors, uncertainties, or areas where they need further explanation, and giving feedback.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Peer review of a technical document by colleagues or subject matter experts in the same field. The purpose of peer review is to make sure that the document is accurate, complete, and compliant with applicable standards and guidelines. The editorial review also checks for the required style and format in the document to warrant that it meets the organization’s quality standards.

The responsibility for fixing identified defects lies with the document author or the development team responsible for creating the software artifact under review.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

SRS

Original Requirement (Section 4.3):"The system shall allow users to reset their password by answering security questions."

Duplicate Requirement (Another Section):"The system should provide users with the option to reset their password through security questions."

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Author of the Document

The lead developer assumes the role of the author.
Guides the team through the "Software Requirement Specification" (SRS) document.
Ensures that the team understands the project's scope, functionalities, and user requirements detailed in the SRS.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod.

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

Lorem ipsum dolor

Consectetur adipiscing elit

Lorem ipsum dolor sit amet.
Consectetur adipiscing elit.
Sed do eiusmod tempor incididunt ut.
Labore et dolore magna aliqua.

STATIC TESTING

Start designing with a free template

View

Corporate Christmas Presentation

View

Customer Service Manual

View

Business Results Presentation

View

Meeting Plan Presentation

View

Business vision deck

View

Economic Presentation

View

Tech Presentation Mobile

Transcript

Static Testing Techniques

Static Testing

Review

Static Analysis

Informal

Technical Review

Inspection

Walkthrough

Fivegoals

WALKTHROUGH

Benefits of Walkthroughs

01

02

03

04

What to Look for in a Technical Document Review:

Structure

Content

Format

Language

Consistency

Compliance

References

Usability

What to Look for in a Technical Document Review:

Content

Format

Structure

Language

What to Look for in a Technical Document Review:

Compliance

References

Consistency

Usability

Walkthrough

Technical Review

Purpose

Type

Led by

Document part

INTRODUCTION

STEPS

Planning

Preparation

Inspection Meeting

Logging & Documentation

Discussion Phase

Follow Up

Involves peers to examine the product

Rules and checklists are used during the preparation phase

The defects found are documented in a logging list or issue log.

Formal follow-up is carried out by the moderator applying exit criteria.

write your title here

Lorem ipsum dolor sit amet

Write a subtitle here

Lorem ipsum dolor sit amet

Lorem ipsum dolor sit amet

Lorem ipsum dolor sit amet

write your title here

Lorem ipsum dolor

43%

Lorem ipsum dolor

30%