Docsity
Log inSign up
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search Store documents

The best documents sold by students who completed their studies

Search through all study resources
Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

University Rankings

Discover the best universities in your country according to Docsity users

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

From our blog

Exams and Study
Go to the blog

Static and Dynamic Testing, Slides of Software Project Management

Kalinga Institute of Industrial TechnologySoftware Project Management

Subject: Software Testing Year:2024

Typology: Slides

2024/2025

Available from 09/03/2024

ashish-chandak
ashish-chandak 🇮🇳

11 documents

1 / 43

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Static Testing
•Static Testing do not execute code.
•It manually checks work documents to find errors in early stage.
•Static Testing, a software testing technique in which the software is
tested without executing the code. It has two parts as listed below:
•Review - Typically used to find and eliminate errors or ambiguities in
documents such as requirements, design, test cases, etc.
•Static analysis - The code written by developers are analyzed (usually
by tools) for structural defects that may lead to defects.
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b

Partial preview of the text

Download Static and Dynamic Testing and more Slides Software Project Management in PDF only on Docsity!

Static Testing

  • Static Testing do not execute code.
  • It manually checks work documents to find errors in early stage.
  • Static Testing, a software testing technique in which the software is tested without executing the code. It has two parts as listed below:
  • Review - Typically used to find and eliminate errors or ambiguities in documents such as requirements, design, test cases, etc.
  • Static analysis - The code written by developers are analyzed (usually by tools) for structural defects that may lead to defects.

Types of Testing

Types of Review

Informal Review

  • Informal reviews are applied many times during the early stages of the life cycle of the document.
  • A two person team can conduct an informal review.
  • In later stages these reviews often involve more people and a meeting.
  • The goal is to keep the author and to improve the quality of the document.
  • The most important thing to keep in mind about the informal reviews is that they are not documented.

Walkthrough

Characteristics

  • The meeting is led by author(s)
  • Scenarios and dry runs may be use to validate the content.
  • Separate pre meeting preparations for reviewers is optional.

Goals of Walkthrough

  • To present the documents both within and outside the software discipline in order to gather the information regarding the topic under documentation.
  • To explain or do the knowledge transfer and evaluate the contents of the document
  • To achieve a common understanding and to gather feedback.
  • To examine and discuss the validity of the proposed solutions

Characteristics of Peer Review

  • Peer Reviews are documented and uses a defect detection process that has peers and technical specialist as part of the review process.
  • The Review process doesn't involve management participation.
  • It is usually led by trained moderator who is NOT the author.
  • The report is prepared with the list of issues that needs to be addressed.

Goals of Technical Review

  • Asses value of technical value and alternative of product.
  • Establish consistency in the use and representation of technical concept.
  • Ensure at early stage technical concept are used correctly.
  • Inform participant of the technical content of document.

The Goals of Inspection are:

  • It helps the author to improve the quality of the document under inspection
  • It removes defects efficiently and as early as possible
  • It improve product quality
  • It create common understanding by exchanging information
  • It learn from defects found and prevent the occurrence of similar defects

Characteristics of Inspection

  • Led by trained moderator.
  • It uses defined roles during the process.
  • It involves peers to examine the product.
  • Rules and checklist are used during the preparation phase.
  • Defect are found and documented in logging list.
  • Metrics are gathered and analyzed to optimized the process.

Find a champion

  • Lead the process project or organizational Level
  • He must be expertise, enthusiastic and a practical mindset.
  • Authority of champion should be clear
  • Must have management support.

Pick things that really count

  • Select document for review that are most important for project.
  • Reviewing most critical, upstream documents like requirement and architecture will show benefits.

Explicitly plan and track review activities

  • To ensure that review become part of day to day activity, hours spent must be in record.
  • Tracking hours will improve planning of next review.

Train Participants

  • Training must be provided in review technique
  • Training must be provided to moderator and prepare them for critical role.