More Related Content
What's hot
What's hot (20)
Similar to Static techniques
Similar to Static techniques (20)
Recently uploaded
Recently uploaded (20)
Static techniques
- 1. Static techniques Nama : Ade Afsa Nim : 11453201937 Sistem Informasi Fakultas Sains dan Teknologi Uin Suska Riau
- 2. Static techniques 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. A. REVIEWS AND THE TEST PROCESS • Recognize software work products that can be examined by different static techniques. (K1) • Describe the importance and value of considering static techniques for the assessment of software work products. (K2) • Explain the difference between static and dynamic techniques. (K2) Dynamic testing and static testing are complementary methods, as they tend to find different types of defects effectively and efficiently. Types of defects that are easier to find during static testing are: deviations from standards, missing requirements, design defects, non-maintainable code and inconsistent interface specifications. Note that in contrast to dynamic testing, static testing finds defects rather than failures.
- 4. B. Review Process The formality of a review process is related to factors such as the maturity of the development process, any legal or regulatory requirements or the need for an audit trail. In practice the informal review is perhaps the most common type of review. Informal reviews are applied at various times during the early stages in the life cycle of a document. A two-person team can conduct an informal review, as the author can ask a colleague to review a document or code. In later stages these reviews often involve more people and a meeting. This normally involves peers of the author, who try to find defects in the document under review and discuss these defects in a review meeting. The goal is to help the author and to improve the quality of the document. Informal reviews come in various shapes and forms, but all have one characteristic in common – they are not documented.
- 5. In contrast to informal reviews, formal reviews follow a formal process. A typical formal review process consists of six main steps: • Planning • Kick-off • Preparation • Review meeting • Rework • Follow-up. Phases of a formal review
- 6. Roles and responsibilities In the case of an inspection or technical review, participants should have been properly trained as both types of review have proven to be far less successful without trained participants. This indeed is perceived as being a critical success factor. Within a review team, four types of participants can be distinguished: moderator, author, scribe and reviewer. In addition management needs to play a role in the review process.
- 7. Types of review A single document may be the subject of more than one review. If more than one type of review is used, the order may vary. For example, an informal review may be carried out before a technical review, or an inspection may be carried out on a requirements specification before a walkthrough with customers. The main review types, their main characteristics and common objectives it is : 1. Walkthrough 2. Technical review 3. Inspection
- 8. Success factors for reviews Implementing (formal) reviews is not easy as there is no one way to success and there are numerous ways to examples fail : 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 9. Just do it!
- 9. C. STATIC ANALYSIS BY TOOLS • Describe the objective of static analysis and compare it to dynamic testing. (K2) • Recall typical defects identified by static analysis and compare them to reviews and dynamic testing. (K1) • List typical benefits of static analysts. (K1) • List typical code and design defects that may be identified by static analysis tools. (Kl)
- 10. REVIEW From Section 3.1 you should be able to explain the importance and advantages of static testing. You should know the difference between static testing and dynamic testing, and also understand the concept of reviews. You should be able to recognize the software work products that can be examined by static testing. You should know the glossary terms static testing, dynamic testing and reviews.
- 11. From Section 3.2, you should understand the difference between formal and informal reviews. You should be able to recall the main phases of a typical formal review. The main roles within reviews and their responsibilities should be clear to you. You should know the glossary terms entry criteria, exit criteria, formal review, informal review, inspection, moderator, reviewer, scribe, technical review and walkthrough.
- 12. From Section 3.3 you should understand the objective of static analysis and be able to compare it to static and dynamic testing. You should be able to describe the main features of static analysis and recall typical defects that can be found using static analysis. Finally, you should be able to recall the benefits of using static analysis. You should know the glossary terms compiler, cyclomatic complexity, control flow, data flow and static analysis.