STATIC TECHNIQUES
•Download as PPTX, PDF•
0 likes•117 views
Static test techniques provide a powerful way to improve the quality and productivity of software development. This chapter describes static test techniques, including reviews, and provides an overview of how they are conducted
Report
Share
Related slideshows
Recommended for you
Recommended for you
More Related Content
What's hot
What's hot (20)
Similar to STATIC TECHNIQUES
Similar to STATIC TECHNIQUES (17)
Recently uploaded
Recently uploaded (20)
STATIC TECHNIQUES
- 1. Name: fajar ayu ningrum Nim: 11453205077 majors: information system Fakulty: sains n teknology University: sultan syarif kasim riau
- 2. Static test techniques provide a powerful way to improve the quality and productivity of software development. This chapter describes static test techniques, including reviews, and provides an overview of how they are conducted. The fundamental objective of static testing is to improve the quality of software work products by assisting engineers to recognize and fix their own defects early in the software development process. While static testing techniques will not solve all the problems, they are enormously effective Static techniques can improve both quality and productivity by impressive factors. Static testing is not magic and it should not be considered a replacement for dynamic testing, but all software organizations should consider using reviews in all major aspects of their work including requirements, design, implementation, testing, and maintenance. Static analysis tools implement automated checks, e.g. on code.
- 3. 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)
- 4. 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. To summarize, the use of static testing, e.g. reviews, on software work products has various advantages:
- 5. 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)
- 6. Phases of a formal review 1. Planning In contrast to informal reviews, formal reviews follow a formal process. A typical formal review process consists of six main steps: 2. Kick-off 5. Rework 4. Review meeting 3. Preparation 6. Follow-up
- 7. 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.
- 8. Types 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.
- 9. Success factors for reviews Find a 'champion' A champion is needed, one who will lead the process on a project or organizational level. Pick things that really count Select the documents for review that are most important in a project. Explicitly plan and track review activities To ensure that reviews become part of the day-to-day activities, the hours to be spent should be made visible within each project plan. Train participants It is important 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 personal when they are not well managed by the moderator. 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.
- 10. 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)