Testing & implementation system 3-wm
•Download as PPTX, PDF•
0 likes•33 views
Materi Static Technique http://sif.uin-suska.ac.id/ http://fst.uin-suska.ac.id/ http://www.uin-suska.ac.id/
Report
Share
More Related Content
What's hot
What's hot (20)
Similar to Testing & implementation system 3-wm
Similar to Testing & implementation system 3-wm (20)
Recently uploaded
Recently uploaded (20)
Testing & implementation system 3-wm
- 1. Chapter 3 Static Techniques Wiwik Muslehatin 11453201902 Dept. Information System State Islamic University of SUSKA RIAU Faculty of Science And Technology
- 2. Agenda : Reviews And The Test Process Phases of a formal review Roles and responsibilities Types of review Success factors for reviews
- 3. Reviews And The Test Process 1 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. 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.
- 4. To summarize, the use of static testing, e.g. reviews, on software work products has various advantages: 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. Reviews And The Test Process
- 5. “ Phases of a formal review A typical formal review process consists of six main steps: 1. Planning 2. Kick-off 3. Preparation 4. Review meeting 5. Rework 6. Follow-up.
- 6. The best formal reviews come from well-organized teams, guided by trained moderators (or review leaders). Within a review team, four types of participants can be distinguished: Moderator, Author, Scribe Reviewer. Roles and responsibilities
- 7. 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. This is especially useful if people from outside the software discipline are present, who are not used to, or cannot easily understand software development documents. Technical review A technical review is a discussion meeting that focuses on achieving consensus about the technical content of a document. Compared to inspections, technical reviews are less formal and there is little or no focus on defect identification on the basis of referenced documents, intended readership and rules. During technical reviews defects are found by experts, who focus on the content of the document. The experts that are needed for a technical review are, for example, architects, chief designers and key users. In practice, technical reviews vary from quite informal to very formal.
- 8. Types of review 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. In the inspection meeting the defects found are logged and any discussion is postponed until the discussion phase. This makes the inspection meeting a very efficient meeting.
- 9. Find a 'champion‘ Pick things that really count Explicitly plan and track review activities Train participants Manage people issues Follow the rules but keep it simple Continuously improve process and tools Report results Just do it! Success factors for reviews
- 10. Referensi : Graham, Dorothy, et al. “Foundation of software Testing ISTBQ Sertification”. Chapter 1 Fundamentals of Testing. 2011