Please enable JavaScript.
Coggle requires JavaScript to display documents.
Static Techniques - Coggle Diagram
Static Techniques
3.1 Review and The process
How does software work products that can be examined by different
static techniques ?
Work Product are manually reviewed and commented by code or document, inspection, Walk-Through.
Dynamic testing and Static Testing
Dynamic and static testing are complementary and have the same objective which is identify defects.
Difference
Static testing via reviews find untestable requirements
Static testing via reviews find incorrect software/system design
Static testing via reviews find invalid or incomplete requirements
Static testing finds defects, i.e. causes of failures, whereas dynamic testing finds the failures
Static testing via reviews find incorrect UI designs
Static testing via reviews find deviations from regulations or standards
The importance and value of considering static techniques
Find causes of failures, rather than failures
Test software without executing the code
Usually used before dynamic techniques
Complementary to dynamic techniques
Manual reviews and automated static analysis
Static testing is based on for conducting manual reviews and evaluation of the product before the design of the software.so -> early testing-> reduces defect at dynamic techniques
static testing (kiểm thử tĩnh) là việc test các tài liệu hoặc phân tích cú pháp mà không thông qua việc chay các chương trình
Dynamic testing(kiểm thử động) la việc test các phần mềm thông qua việc chạy các chương trình.
3.2 Review Process
Success factors for reviews
Manage people issues
People issues and psychological aspects should be dealt with by the moderator and should be part of the review training, thus making the review a positive experience for the author.
Train participants
Special training should be provided to the moderators to prepare
them for their critical role in the review process.
Follow the 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.
Explicitly plan and track review activities
the hours to be spent should be made visible within each project plan.The engineers involved are prompted to schedule time for preparation and, very importantly, rework.
Continuously improve process and tools
based upon the ideas of participants, ensures the motivation of the engineers
involved. Motivation is the key to a successful change process.
Pick things that really count
Select the documents for review that are most important in a project.
Reviewing highly critical, upstream documents like requirements and architecture will most certainly show the benefits of the review process to the project.
Report results
Report quantified results and benefits to all those involved as soon as possible,
and discuss the consequences of defects if they had not been found this early.
Find a 'champion'
A champion is who will lead the process on a project or organizational level and They need expertise, enthusiasm and a practical mindset in order
to guide moderators and participants.
Just do it!
The process is simple but not easy. Each step of the process is clear, but experience is needed to execute them correctly. So, try to get experienced people to observe and help where possible. But most importantly, start doing reviews and start learning from every review.
3.2.1 Phase of a formal review
Formal Process(6 STEP)
Preparation
. During preparation, participants should not exceed this criterion. By collecting data and measuring the review process, company-specific criteria for checking rate and document size (see planning phase) can be set, preferably specific to a document type.
Review Meeting
:The meeting typically consists of the following elements (partly depending on the review type): logging phase, discussion phase and decision phase.
Kick off
kick-off meeting is An optional step in a review procedure. 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
Rework
Changes that are made to the document should be easy to identify during
follow-up. Therefore the author has to indicate where changes are made
Planning
the moderator take the role of checking compliance to standards, since this tends to
be a highly objective role, which leads to less discussion of the defects found. Moderator make a schedule
Follow up
In order to control and optimize the review process, a number of measurements are collected by the moderator at each step of the process. Examples of such measurements include number of defects found, number of defects found per page, time spent checking per page, total review effort, etc
3.2.3 Type of Review
Walk-Through
Technical Review
Inspection