Marjuni.
•Download as PPTX, PDF•
0 likes•17 views
Program Studi S1 Sistem Informasi Fakultas Sains dan Teknologi Universitas Islam Negeri Sultan Syarif Kasim Riau
Report
Share
Related slideshows
Recommended for you
Recommended for you
Recommended for you
More Related Content
What's hot
What's hot (20)
Similar to Marjuni.
Similar to Marjuni. (20)
Recently uploaded
Recently uploaded (20)
Marjuni.
- 1. Testing throughout the software life cycle Marjuni 11453105146 Sistem Informasi Sains dan Teknologi
- 2. Static techniques 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.
- 3. REVIEWS AND THE TES PROCESSReducing the number of defects early in the product life cycle also means that less time has to be spent on testing and maintenance. To summarize, the use of static testing, e.g. reviews, on software work products has various advantages: • 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 prod ucts can be achieved. • Since rework effort is substantially reduced, development productivity figures are likely to increase. • Static tests contribute to an increased awareness of quality issues.
- 4. REVIEW PROCESS 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: – 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.
- 5. Roles and responsibilitiesThe moderator The moderator (or review leader) leads the review process. He or she deter-mines, 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, in order to control the quality of the input and output of the review process. 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.
- 6. 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.
- 7. Cont.... Technical review A technical review is a discussion meeting that focuses on achieving con-sensus about the technical content of a document. Compared to inspec-tions, technical reviews are less formal and there is little or no focus on defect identification on the basis of referenced documents, intended read-ership and rules.
- 8. Cont.... Inspection Inspection is the most formal review type. The document under inspection is prepared and checked thoroughly by the reviewers before the meeting, compar-ing the work product with its sources and other referenced documents, and using rules and checklists
- 9. Success factors for reviews Finda 'champion' A champion is needed, one who will lead the process on a project or organiza-tional level. They need expertise, enthusiasm and a practical mindset in order to guide moderators and participants. Pickthingsthatreallycount Select the documents for review that are most important in a project. Reviewing highly critical, upstream documents like requirements and architec-ture will most certainly show the benefits of the review process to the project. These invested review hours will have a clear and high return on investment.
- 10. Cont.... – Continuously improve process and tools Continuous improvement of process and supporting tools (e.g. checklists), based upon the ideas of participants, ensures the motivation of the engineers involved. Motivation is the key to a successful change process. There should also be an emphasis, in addition to defect finding, on learning and process improvement. – 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. Costs should of course be tracked, but benefits, especially when problems don't occur in the future, should be made visible by quantifying the benefits as well as the costs. – Just do it! The process is simple but not easy. Each step of the process is clear, but expe- rience 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.
- 11. STATIC ANALYSIS BY TOOLS Static analysis is an examination of requirements, design and code that differs from more traditional dynamic testing in a number of important ways: – Static analysis is performed on requirements, design or code without actually executing the software artifact being examined. – Static analysis is ideally performed before the types of formal review dis cussed in Section 3.2. – Static analysis is unrelated to dynamic properties of the requirements, design and code, such as test coverage. – 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.
- 12. Codingstandards 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 stan-dard. 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 specifica-tions (e.g. 'Indent 4 spaces'). Code metrics As stated, when performing static code analysis, usually information is calculated about structural attributes of the code, such as comment fre- quency, depth of nesting, cyclomatic number and number of lines of code.
- 13. Cont.... The important thing for the tester is to be aware that the above mentioned static analysis measures can be used as early warning signals of how good the code is likely to be when it is finished. In summary the value of static analysis is especially for: – early detection of defects prior to test execution; – early warning about suspicious aspects of the code, design or requirements; – identification of defects not easily found in dynamic testing;