Riauly Putra 11453105436 Sistem Informasi Sains Dan Teknologi UIN SUSKA RIAU

1. Testing Dan Implementasi Sistem
Chapter 3 Static Techniques
UIN SUSKA RIAU
SISTEM INFORMASI
Riauly Putra
12/11/2017

2. REVIEWS AND THE TEST PROCESS
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.
This testing option is not applicable for the majority of the software work products.

3. REVIEWS AND THE TEST PROCESS,…
2. Phases of A Formal Review
a. Planning
The review process for a particular review begins with a 'request for review' by the author to the moderator (or
inspection leader). On a project level, the project planning needs to allow time for review and rework activities,
thus providing engineers with time to thoroughly participate in reviews.
b. 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.
c. Preparation
A critical success factor for a thorough preparation is the number of pages checked per hour. This is called the
checking rate. The optimum checking rate is the result of a mix of factors, including the type of document, its
complexity, the number of related documents and the experience of the reviewer.

4. REVIEWS AND THE TEST PROCESS,…
d. Review Meeting
The meeting typically consists of the following elements (partly depending on the review type): logging phase,
discussion phase and decision phase. During the logging phase the issues, e.g. defects, that have been identified
during the preparation are mentioned page by page, reviewer by reviewer and are logged either by the author
or by a scribe.
e. Rework
Based on the defects detected, the author will improve the document under review step by step. Not every
defect that is found leads to 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.
f. Follow-up
The moderator is responsible for ensuring that satisfactory actions have been taken on all (logged) defects,
process improvement suggestions and change requests. Although the moderator checks to make sure that the
author has taken action on all known defects, it is not necessary for the moderator to check all the corrections in
detail. If it is decided that all participants will check the updated document, the moderator takes care of the
distribution and collects the feedback.

5. REVIEWS AND THE TEST PROCESS,…
3. Roles and Responsibilities
a. 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.
b. The Author
The author's task is to illuminate unclear areas and to understand the defects found.
c. The Scribe
During the logging meeting, the scribe (or recorder) has to record each defect mentioned and any suggestions
for process improvement.
d. The Reviewers
The task of the reviewers (also called checkers or inspectors) is to check any material for defects, mostly prior to
the meeting.

6. REVIEWS AND THE TEST PROCESS,…
e. 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.
4. Types of Review
a. 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.
b. Technical Review
A technical review is a discussion meeting that focuses on achieving consensus about the technical content of a
document.

7. REVIEWS AND THE TEST PROCESS,…
c. Inspection
Inspection is the most formal review type. The document under inspection is prepared and checked thoroughly
by the reviewers before the meeting, comparing the work product with its sources and other referenced
documents, and using rules and checklists.
5. Success Factors
a. Find a Champion
b. Pick Things that Really Count
c. Explicitly Plan and Track Review Activities
d. Train Participants
e. Manage People Issues
f. Follow the Rules but Keep it Simple
g. Continuosly Improve Process and Tools
h. Report Result
i. Just Do it

8. STATIC ANALYSIS BY TOOLS
1
•Coding Standards
2
•Code Metrics

9. 1
• Coding Standards
• Checking for adherence to coding standards is certainly the most
well-known of all features. The first action to be taken is to define
or adopt a coding standard. Usually a coding standard consists of a
set of programming rules (e.g. 'Always check boundaries on an
array when copying to that array'), naming conventions (e.g.
'Classes should start with capital C) and layout specifications (e.g.
'Indent 4 spaces').
2
• Code Metrics
• As stated, when performing static code analysis, usually information is
calculated about structural attributes of the code, such as comment
frequency, depth of nesting, cyclomatic number and number of lines of
code. This information can be computed not only as the design and code
are being created but also as changes are made to a system, to see if the
design or code is becoming bigger, more complex and more difficult to
understand and maintain. The measurements also help us to decide among
several design alternatives, especially when redesigning portions of existing
code.

10. Reference
Graham, D., et al.2006.Foundations of Software Testing : ISTQB
Certification.London, UK :International Thomson Business Press

11. Link
http://sif.uin-suska.ac.id/
https://fst.uin-suska.ac.id/
http://www.uin-suska.ac.id/

12. End of Presentation
Thankyou for your attention
Giving your question 
Slide by Riauly Putra
Testing Dan implementasi kelas E 2017
Sistem Informasi UIN SUSKA RIAU
Lecture : M.Jazman S.Kom, M.Infosys