DELICIA GENERIS HUMANI 11453205433 PROGRAM STUDI SISTEM INFORMASI FAKULTAS SAINS DAN TEKNOLOGI UNIVERSITAS ISLAM SULTAN SYARIF KASIM RIAU

1. STATIC TECHNIQUES
Delicia Generis Humani
11453205433
DEPARTEMENT OF INFORMATION SYSTEM
FACULTY OF SCIENCE AND TECHNOLOGY
STATE ISLAMIC UNIVERSITY OF SULTAN SYARIF KASIM RIAU
2017

2. The definition of testing outlines objectives that relate to
evaluation, revealing defects and quality. As indicated in the
definition two approaches can be used to achieve these objectives,
static testing and dynamic testing.
With dynamic testing methods, software is executed using a set
of input values and its output is then examined and compared to
what is expected. During static testing, software work products are
examined manually, or with a set of tools, but not executed. As a
consequence, dynamic testing can only be applied to software
code. Dynamic execution is applied as a technique to detect
defects and to determine quality attributes of the code.
REVIEWS AND THE TEST PROCESS
Delicia Generis Humani (11453205433)

3. REVIEWS PROCESS
A. Phases of a formal review
In contrast to informal reviews, formal reviews follow a formal process. A typical formal
review process consists of six main steps:
1. Planning
 The review process for a particular review begins with a 'request for review' by the author to
the moderator (or inspection leader). A moderator is often assigned to take care of the
scheduling (dates, time, place and invitation) of the review.
Delicia Generis Humani (11453205433)

4. 2. Kick-off
An optional step in a review procedure is a kick-off meeting. The goal of this meeting is to get everybody on the
same wavelength regarding the document under review and to commit to the time that will be spent on checking.
Also the result of the entry check and defined exit criteria are discussed in case of a more formal review.
Delicia Generis Humani (11453205433)
Cont..
3. Preparation
The participants work individually on the document under review using the related documents, procedures, rules and
checklists provided. The individual participants identify defects, questions and comments, according to their understanding
of the document and role. All issues are recorded, preferably using a logging form.
4. Review meeting
The meeting typically consists of the following elements (partly depending on the review type):
logging phase, discussion phase and decision phase. Every defect and its severity should be
logged. The participant who identifies the defect proposes the severity. Severity classes could be:
a. Critical: defects will cause downstream damage; the scope and impact of the defect is
beyond the document under inspection.
b. Major, defects could cause a downstream effect (e.g. a fault in a design can result in an
error in the implementation).
c. Minor, defects are not likely to cause downstream damage (e.g. non-compliance with the
standards and templates). ,

5. 5. Rework
It is the author's responsibility to judge if a defect has to be fixed. If nothing is done about
an issue for a certain reason, it should be reported to at least indicate that the author has
considered the issue.
6. Follow-up
The moderator is responsible for ensuring that satisfactory actions have been
taken on all (logged) defects, process improvement suggestions and change
requests.
Cont..
Delicia Generis Humani (11453205433)

6. B. Roles and Responsibilities
1. 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 moderator Performs the entry
check and the follow-up on the rework.
2. 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.
3. The Scribe
The scribe (or recorder) has to record each defect mentioned and any
suggestions for process improvement. In practice it is often the author who
plays this role, ensuring that the log is readable and understandable.
Delicia Generis Humani (11453205433)

7. Cont…
4. The reviewers
The task of the reviewers (also called checkers or inspectors) is
to check any material for defects, mostly prior to the meeting.
5. 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.
Delicia Generis Humani (11453205433)

8. C. Types of Review
Delicia Generis Humani (11453205433)
1. 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.
2. Technical Review
A technical review is a discussion meeting that focuses on
achieving consensus about the technical content of a document.
3. Inspection
Inspection is the most formal review type. In the inspection meeting
the defects found are logged and any discussion is postponed until the
discussion phase.

9. D. Success Factors For Reviews
Delicia Generis Humani (11453205433)
1. Find a 'champion'
2. Pick things that really count
3. Explicitly plan and track review activities
4. Train participants
5. Manage people issues
6. Follow the rules but keep it simple
7. Continuously improve process and tools
8. Report results & Just do it!

10. Static analysis is an examination of requirements, design and
code that differs from more traditional dynamic testing in a
number of important ways:
a. Static analysis is performed on requirements, design or code
without actually executing the software artifact being
examined.
b. Static analysis is ideally performed before the types of formal
review discussed in Section 3.2.
c. Static analysis is unrelated to dynamic properties of the
requirements, design and code, such as test coverage.
d. The goal of static analysis is to find defects, whether or not
they may cause failures. As with reviews, static analysis finds
defects rather than failures.
STATIC ANALYSIS BY TOOLS
Delicia Generis Humani (11453205433)

11. BIBLIONGRAPHY :
Graham et.al. (2011). ISTQB-Fondation of Software
Testing. London: Cengage Learning EMEA.
LINK :
1.https://sif.uin-suska.ac.id
2.https://fst.uin-suska.ac.id
3.https://www.uin-suska.ac.id
BIBLIONGRAPHY & LINK
Delicia Generis Humani (11453205433)

12. THANK YOU
Delicia Generis Humani (11453205433)