STATIC TECHNIQUES Nailil Amani

11453201885
MAJORS INFORMATION SYSTEM
FAKULTY SAINS N TEKNOLOGY
UNIVERSITY SULTAN SYARIF KASIM RIAU
 Sta tic test techniques prov ide a pow erful way to i mprov e the qua lity
and productivity o f softw are develop ment . This chapter describes static test
techniques, including rev iew s, and pro v ides an ov erv iew of how they are
conducted . The funda menta l objective o f sta tic testing is to i mprov e the
qua lity o f so ftware w ork pro ducts by assist ing eng ineers to recog nize a nd fix
their ow n defects ea rly in the so ftw are dev elop ment process . While sta tic
testing techniques w ill no t so lv e a ll the proble ms, t hey are eno rmo usly
effective

Sta tic techniques ca n i mprove bo th qua lity and pro ductiv ity by
i mpressiv e fa cto rs . Sta tic testing is no t ma gic a nd it should no t be co nsidered
a repla ce ment for dy na mic testing , but all so ftw are o rga niza tio ns should
consider using rev iew s in a ll ma jor aspects o f their w ork includin g
require ments, design, i mple menta tio n, testing, a nd maintenance. Static
analysis tools implement automa ted checks, e.g. on code.
 REVIEWS AND THE TEST PROCESS

1
• Recognize software work products that can be
examined by different static techniques. (K1)

2
• Describe the importance and value of considering static
techniques for the assessment of software work products. (K2)

3
• Explain the difference between
static and dynamic techniques. (K2)
TO SUMMARIZE, THE USE OF STATIC TESTING ,
E.G. REVIEWS, ON SOFTWARE WORK PRODUCTS
HAS VARIOUS ADVANTAGES:

 Since static testing can start early in the life cycle, early feedback on
quality issues can be established, e.g. an early validation of user
requirements and not just late in the life cycle during acceptance testing.

 By detecting defects at an early stage, rework costs are most often

relatively low and thus a relatively cheap improvement of the quality of
software products can be achieved.

 Since rework effort is substantially reduced, development productivity

figures are likely to increase.

 The evaluation by a team has the additional advantage that there is an

exchange of information between the participants.

 Static tests contribute to an increased awareness of quality issues.

 REVIEW PROCESS

1
• Recall the phases, roles and responsibilities
of a typical formal review. (K1)

2
• Explain the differences between different types of review: informal
review, technical review, walkthrough and inspection. (K2)

3
• Explain the factors for successful
performance of reviews. (K2)
EXPLAIN THE FACTORS FOR SUCCESSFUL
PERFORMANCE OF REVIEWS. (K2)

In contrast to informal reviews, formal reviews follow a

formal process. A typical formal review process consists of six
main steps:

1. Planning

2. Kick-off

3. Preparation

4. Review meeting

5. Rework

6. Follow-up
 ROLES AND RESPONSIBILITIES

The moderator
The moderator (or review leader) leads the review process. He or she
determines, in co-operation with the author, the type of review, approach and the
composition of the review team.
The author
As the writer of the document under review, the author's basic goal should
be to learn as much as possible with regard to improving the quality of the document,
but also to improve his or her ability to write future documents.
The scribe
During the logging meeting, the scribe (or recorder) has to record each
defect mentioned and any suggestions for process improvement.
The reviewers
The task of the reviewers (also called checkers or inspectors) is to check any
material for defects, mostly prior to the meeting.
The manager
The manager is involved in the reviews as he or she decides on the
execution of reviews, allocates time in project schedules and determines whether
review process objectives have been met.
 T YPES OF REVIEW

Walkthrough
A walkthrough is characterized by the author of the document under review
guiding the participants through the document and his or her thought
processes, to achieve a common understanding and to gather feedback.
Technical review
A technical review is a discussion meeting that focuses on achieving consensus
about the technical content of a document.
Inspection
Inspection is the most formal review type.
 SUCCESS FACTORS FOR REVIEWS

 F ind a 'champion'
A champion is needed, one who will lead the process on a project or
organizational level.
 Pick t hings t hat really count
Select the documents for review that are most impor tant in a project.
 Explicitly plan and t rack review activities
To ensure that reviews become par t of the day -to-day activities, the
hour s to be spent should be made visible within each project plan.
 Train par ticipants
It is impor tant that training is provided in review techniques,
especially the more formal techniques, such as inspection.
 Manage people issues
Reviews are about evaluating someone's document. Some reviews
tend to get too per sonal when they are not well managed by the moderator.
 Follow t he rules but keep it simple
Follow all the formal rules until you know why and how to modify
them, but make the process only as formal as the project culture or maturity
level allows.
 STATIC ANALYSIS BY TOOLS

1. Describe the objective of static analysis and

compare it to dynamic testing. (K2)
2. Recall typical defects identified by static analysis
and compare them to reviews and dynamic testing.
(K1)
3. List typical benefits of static analysts. (K1)
4. List typical code and design defects that may be
identified by static analysis tools. (Kl)
Thankyou