The document describes the six phases of a formal review process:
1. Planning involves assigning a moderator and scheduling the review.
2. Kick-off is an optional meeting to align participants on the document and time commitment.
3. Preparation includes checking documents at a defined rate, usually 5-10 pages per hour.
4. The review meeting logs defects, discusses severity, and decides if exit criteria are met.
5. Rework is done by the author to address defects found before another review.
6. Follow-up ensures all defects were adequately addressed before the document is finalized.
This document provides an overview of Failure Mode and Effects Analysis (FMEA). It discusses that FMEA is a systematic group activity to recognize and evaluate potential failures, identify actions to address failures, and document findings. The document outlines the different types of FMEAs, including Design FMEA and Process FMEA. It also describes the typical steps to conduct a Process FMEA, including developing a process flow, identifying failure modes and their causes and effects, and estimating the risk priority number. The FMEA is presented as a team tool to prevent failures.
CADmantra Technologies Pvt. Ltd. is one of the best Cad training company in northern zone in India . which are provided many types of courses in cad field i.e AUTOCAD,SOLIDWORK,CATIA,CRE-O,Uniraphics-NX, CNC, REVIT, STAAD.Pro. And many courses
Contact: www.cadmantra.com
www.cadmantra.blogspot.com
www.cadmantra.wix.com
PFMEA, Risk Reduction and Effectiveness – Advance (AIAG FMEA #4 Edition)
Is your FMEA performing for you?
This is advance level of PFMEA, Have basic understanding fo Core IATF Tools before refering to this presentation.
A Process Failure Modes and Effects Analysis (PFMEA) is a structured analysis that uses a cross-functional team to identify potential failures in a process, determine their causes and effects, and identify actions to address potential failures. The document outlines how to conduct an effective PFMEA, including establishing objectives, choosing team members, conducting a failure modes analysis, identifying corrective actions, and documenting results. It also describes how to organize the PFMEA team and the forms used to document the analysis.
The document provides information on various quality models and standards including Six Sigma, Total Quality Management (TQM), ISO 9001. It discusses the goals, methodology, and evolution of Six Sigma. It explains the key principles and structure of TQM and ISO 9001. It also provides a case study on how Toyota has implemented TQM based on principles of customer focus, continuous improvement, and total participation.
This document provides an overview of Failure Mode and Effects Analysis (FMEA). FMEA is a systematic process used to evaluate potential failures in a design, manufacturing or process and identify actions to address or prevent these failures. It involves identifying potential failure modes and ranking them based on severity, occurrence likelihood and ability to detect. Actions are then recommended to reduce the highest risk failures based on their Risk Priority Number. FMEA is intended to be preventative and identify issues before they occur.
The document discusses improving the quality of Process Failure Mode and Effects Analyses (PFMEAs). It begins by providing context on the importance of PFMEAs in ensuring robust products and processes. It then outlines common errors seen in PFMEAs, such as not starting them until production equipment is operational, only considering Risk Priority Numbers when prioritizing actions, and inconsistencies in severity or detection rankings. The document also discusses the supplier PFMEA audit developed to evaluate PFMEA quality in a standardized, objective manner. It aims to accelerate PFMEA improvement by sharing best practices and ensuring cross-functional input.
System testing involves testing the entire integrated software system to evaluate whether it meets its required specifications. This includes recovery testing to ensure the system can recover from failures, security testing to check protection mechanisms against unauthorized access, stress testing to evaluate performance under abnormal stressful situations, and performance testing to determine if the system meets non-functional requirements for runtime performance.
This document summarizes key aspects of quality management and software engineering based on a textbook. It discusses definitions of software quality, types of quality (design and conformance), the costs of quality, software quality assurance techniques like reviews and inspections, roles of a software quality assurance group, metrics for reviews, standards like ISO 9001, change management, software configuration management, and baselines.
Nowadays, increasing reliability and safety were very important in hardware and software development to avoid errors. Reliability is the degree to which and assessment tool produces stable and consistent result.
Safety is being protected from harm or other non-desirable outcomes. Roughly about increasing reliability and safety is more about software that can perform their task consistently and safe from any harm that can bring error in the software.
Model checking is a formal verification technique that employs a model of a system to check that the system meets its desired specifications. It works by systematically checking all possible states of a modeled system to verify its behavior. Model checking is effective at finding potential design errors early in the development process and is widely used to verify hardware, software, security protocols, and safety-critical systems like transportation systems. An important part of model checking involves building a transition system model of a system's states and the transitions between those states labeled with actions and atomic propositions.
software testing is necessary to make sure the product or application is defect free, as per customer specifications. Software testing identifies fault whose removal increases the software Quality and Increases the software reliability.Testing effort is directly proportional to the complexity of the program.
This document discusses statistical process control and quality improvement techniques. It defines quality and explains that quality improvement aims to reduce variability in processes. It describes seven major statistical process control tools including control charts. Control charts graph process data over time and are used to distinguish between chance variation and assignable causes of variation. The document outlines the basic principles of control charts, including how to establish control limits and select rational subgroups. It also covers analysis of patterns on control charts and specific chart types like X-bar and R charts for variables data and P, U, and C charts for attributes data. Finally, it discusses process capability, measurement systems capability, and control chart performance in terms of average run length.
Control charts and statistical process control (SPC) allow companies to monitor processes, detect issues, and enact improvements. Control charts display process data over time and help identify when processes are behaving unusually due to "special causes." SPC uses statistics to set control limits on charts and determine whether a process is in or out of statistical control. Implementing control charts involves selecting processes and variables to measure, collecting baseline data to create charts, training operators, and continuously monitoring and improving processes.
The document discusses Process Failure Mode and Effects Analysis (PFMEA), which is a risk assessment tool used to analyze potential failures in a process. It calculates a Risk Priority Number (RPN) to prioritize risks. The RPN is calculated by multiplying ratings for the potential severity, occurrence, and detection of different failure modes. Conducting an effective PFMEA involves identifying failure modes and their effects, agreeing on severity, occurrence, and detection ratings, and implementing actions to reduce risks with high RPNs.
The document discusses the key elements of project management: people, product, process, and project. It focuses on the importance of:
- Engaging the right stakeholders and cultivating a motivated software team led by competent leaders,
- Clearly defining the product objectives and scope before planning,
- Using the appropriate software process as the framework to establish a comprehensive development plan, and
- Planning and controlling the project to manage complexity and avoid common causes of failure like cost overruns.
1. The document discusses techniques for reviewing Process FMEAs (PFMEAs) on the shopfloor, including identifying potential failure modes, their causes and effects, and adjusting occurrence and detection ratings based on actual process performance data.
2. It provides examples of how to measure severity, occurrence, detection, and RPN, and lists inputs like process flow diagrams that are needed to conduct a PFMEA.
3. The document emphasizes that the primary focus should be on preventing defects by reducing occurrence ratings, rather than just improving detection, and provides guidance on selecting appropriate detection methods based on occurrence rankings.
Software engineering quality assurance and testingBipul Roy Bpl
The presentation discusses software quality assurance and testing. It covers topics such as the importance of software quality, types of software quality (functional and non-functional), software testing principles and processes. The testing process involves test planning, analysis and design, implementation and execution, evaluating results, and closure activities. The presentation emphasizes that testing is a critical part of the software development process to improve quality and find defects.
Integration testing is the phase in software testing in which individual software modules are combined and tested as a group. Read complete guide of integration testing types and tools here.
In order to plan for automated or manual regression test execution, it's always efficient in the long run to prepare your regression testing framework. This paper presents a simple framework which can be followed on systems with any level of complexity.
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.
YAHDI SANDRA
11453104752
Program Studi S1 Sistem Informasi
Fakultas Sains dan Teknologi
Universitas Islam Negeri Sultan Syarif Kasim Riau
http://sif.uin-suska.ac.id/
http://fst.uin-suska.ac.id/
http://www.uin-suska.ac.id/
Formal reviews follow a six step process: 1) Planning, 2) Kick-off, 3) Preparation where reviewers identify defects individually, 4) Review meeting where defects are logged and discussed, 5) Rework by the author to address defects, and 6) Follow-up by the moderator to ensure defects were addressed. Key roles include the moderator who leads the process, author of the document, reviewers who identify defects, and scribe who logs defects discussed.
Static techniques such as reviews can improve both quality and productivity in software development. Static testing examines software work products like requirements and design documents manually or with tools before execution, finding defects early. Dynamic testing executes software with test cases. The two techniques are complementary, as static testing finds defects like missing requirements or design flaws while dynamic testing finds failures from execution. Using static testing from early in the development lifecycle provides advantages like early feedback, low rework costs, increased productivity, and greater awareness of quality issues.
The document discusses static testing techniques, specifically reviews. It describes the review process, which typically involves 6 phases: planning, kick-off, preparation, review meeting, rework, and follow-up. Key roles in a review include the moderator, author, scribe, and reviewers. The moderator leads the process, while the author's goal is to improve the document. Reviews can find defects early and improve quality and productivity.
Static techniques provide powerful ways to improve software quality and productivity. Static testing finds defects early by reviewing work products like requirements, design, code, and documentation. Reviews can be informal or formal, following a defined process. Formal reviews typically involve planning, a kickoff meeting, individual preparation, a group review meeting, reworking by the author, and follow up by a moderator. The goal is to improve quality by identifying and fixing defects early in development.
The document summarizes the review process for documents. It discusses the phases of a formal review process including planning, kick-off, preparation, review meeting, rework, and follow-up. It also describes the roles and responsibilities of those involved in the review including the moderator, author, scribe, and reviewers. Finally, it outlines different types of reviews including walkthroughs and technical reviews.
This document discusses static testing techniques, including reviews. It describes the review process and roles involved in reviews. The review process consists of six main phases: planning, entry check, kick-off meeting, preparation, review meeting, rework, and follow-up. Key roles include the moderator, author, scribe, and reviewers. The goal of reviews is to improve quality and productivity by finding defects early.
Static testing techniques like reviews can improve both the quality and productivity of software development. The objectives of static testing are to improve software quality by helping engineers find and fix defects early. While static testing won't solve all problems, it is very effective at finding certain types of defects without executing the software. Organizations should consider using reviews of requirements, design, code, testing and maintenance work products to gain these benefits.
The document discusses static techniques for testing software work products like code, requirements, and design specifications. Static techniques like reviews and static analysis aim to find defects early before testing to improve productivity and reduce costs. Reviews involve examining documentation for defects, while static analysis checks code complexity, errors, and other issues without executing the code. Formal reviews follow steps like planning, kickoff meetings, preparation, review meetings, reworking defects, and follow up. Roles include managers, moderators, authors, reviewers, and scribes.
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
The document discusses static and dynamic testing methods. Static testing involves analyzing code or documentation without executing the software, while dynamic testing executes the software. Both methods find different types of defects. Key aspects of static testing include review processes, which can be informal or formal. Formal reviews involve several phases: planning, kick-off, preparation, review meeting, rework, and follow-up. The review meeting itself includes logging defects, discussing them, and deciding on next steps. Roles in the review include moderator, author, scribe, and reviewers. Different review types are described.
The document discusses static techniques and the software review process. It describes the phases of a formal review process: planning, kick-off, preparation, review meeting, rework, and follow-up. It explains the difference between static and dynamic techniques, and describes different types of reviews like informal reviews, technical reviews, walkthroughs, and inspections.
Static techniques like reviews and static analysis tools can find defects in software work products like requirements, design, and code without executing the software. Reviews vary in formality from informal discussions to more structured inspections and walkthroughs. Static analysis examines software artifacts automatically using tools to identify defects before dynamic testing begins.
The document discusses various techniques for static testing of software, including reviews. It describes the advantages of static testing such as early detection of defects, lower rework costs, and improved productivity. The document outlines the review process and roles involved, including moderator, author, scribe, and reviewers. Different types of reviews are described like informal reviews, formal reviews with six phases (planning, kick-off, preparation, meeting, rework, follow-up), and specific review types including walkthroughs. Walkthroughs aim to establish common understanding through explanation of documents to diverse stakeholders.
Static techniques allow for examining software work products like requirements, design documents, and source code manually or with tools, without executing the software. This is known as static testing. Static testing can evaluate all software work products early in the development lifecycle through review techniques. Reviews involve examining documents for defects and quality issues in a team setting. This allows information sharing and helps focus testing. Reviews have been shown to improve productivity and quality by reducing defects found later.
abdurrahimradhin Program Studi S1 Sistem Informasi Fakultas Sains dan Teknologi Universitas Islam Negeri Sultan Syarif Kasim Riau
http://sif.uin-suska.ac.id/
http://fst.uin-suska.ac.id/
http://www.uin-suska.ac.id/
Referensi ke Graham et.al (2006)
Mitigating the Impact of State Management in Cloud Stream Processing SystemsScyllaDB
Stream processing is a crucial component of modern data infrastructure, but constructing an efficient and scalable stream processing system can be challenging. Decoupling compute and storage architecture has emerged as an effective solution to these challenges, but it can introduce high latency issues, especially when dealing with complex continuous queries that necessitate managing extra-large internal states.
In this talk, we focus on addressing the high latency issues associated with S3 storage in stream processing systems that employ a decoupled compute and storage architecture. We delve into the root causes of latency in this context and explore various techniques to minimize the impact of S3 latency on stream processing performance. Our proposed approach is to implement a tiered storage mechanism that leverages a blend of high-performance and low-cost storage tiers to reduce data movement between the compute and storage layers while maintaining efficient processing.
Throughout the talk, we will present experimental results that demonstrate the effectiveness of our approach in mitigating the impact of S3 latency on stream processing. By the end of the talk, attendees will have gained insights into how to optimize their stream processing systems for reduced latency and improved cost-efficiency.
Best Programming Language for Civil EngineersAwais Yaseen
The integration of programming into civil engineering is transforming the industry. We can design complex infrastructure projects and analyse large datasets. Imagine revolutionizing the way we build our cities and infrastructure, all by the power of coding. Programming skills are no longer just a bonus—they’re a game changer in this era.
Technology is revolutionizing civil engineering by integrating advanced tools and techniques. Programming allows for the automation of repetitive tasks, enhancing the accuracy of designs, simulations, and analyses. With the advent of artificial intelligence and machine learning, engineers can now predict structural behaviors under various conditions, optimize material usage, and improve project planning.
Coordinate Systems in FME 101 - Webinar SlidesSafe Software
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights.
During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to:
- Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value
- Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems
- Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors
- Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported
- Look Ahead: Gain insights into where FME is headed with coordinate systems in the future
Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
How Social Media Hackers Help You to See Your Wife's Message.pdfHackersList
In the modern digital era, social media platforms have become integral to our daily lives. These platforms, including Facebook, Instagram, WhatsApp, and Snapchat, offer countless ways to connect, share, and communicate.
Best Practices for Effectively Running dbt in Airflow.pdfTatiana Al-Chueyr
As a popular open-source library for analytics engineering, dbt is often used in combination with Airflow. Orchestrating and executing dbt models as DAGs ensures an additional layer of control over tasks, observability, and provides a reliable, scalable environment to run dbt models.
This webinar will cover a step-by-step guide to Cosmos, an open source package from Astronomer that helps you easily run your dbt Core projects as Airflow DAGs and Task Groups, all with just a few lines of code. We’ll walk through:
- Standard ways of running dbt (and when to utilize other methods)
- How Cosmos can be used to run and visualize your dbt projects in Airflow
- Common challenges and how to address them, including performance, dependency conflicts, and more
- How running dbt projects in Airflow helps with cost optimization
Webinar given on 9 July 2024
RPA In Healthcare Benefits, Use Case, Trend And Challenges 2024.pptxSynapseIndia
Your comprehensive guide to RPA in healthcare for 2024. Explore the benefits, use cases, and emerging trends of robotic process automation. Understand the challenges and prepare for the future of healthcare automation
Blockchain technology is transforming industries and reshaping the way we conduct business, manage data, and secure transactions. Whether you're new to blockchain or looking to deepen your knowledge, our guidebook, "Blockchain for Dummies", is your ultimate resource.
Details of description part II: Describing images in practice - Tech Forum 2024BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
Advanced Techniques for Cyber Security Analysis and Anomaly DetectionBert Blevins
Cybersecurity is a major concern in today's connected digital world. Threats to organizations are constantly evolving and have the potential to compromise sensitive information, disrupt operations, and lead to significant financial losses. Traditional cybersecurity techniques often fall short against modern attackers. Therefore, advanced techniques for cyber security analysis and anomaly detection are essential for protecting digital assets. This blog explores these cutting-edge methods, providing a comprehensive overview of their application and importance.
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
Measuring the Impact of Network Latency at TwitterScyllaDB
Widya Salim and Victor Ma will outline the causal impact analysis, framework, and key learnings used to quantify the impact of reducing Twitter's network latency.
Fluttercon 2024: Showing that you care about security - OpenSSF Scorecards fo...Chris Swan
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge.
You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter.
The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
論文紹介:A Systematic Survey of Prompt Engineering on Vision-Language Foundation ...Toru Tamaki
Jindong Gu, Zhen Han, Shuo Chen, Ahmad Beirami, Bailan He, Gengyuan Zhang, Ruotong Liao, Yao Qin, Volker Tresp, Philip Torr "A Systematic Survey of Prompt Engineering on Vision-Language Foundation Models" arXiv2023
https://arxiv.org/abs/2307.12980
論文紹介:A Systematic Survey of Prompt Engineering on Vision-Language Foundation ...
Phases of a formal review
1. Program Studi S1 Sistem Informasi
Fakultas Sains dan Teknologi
Universitas Islam Negeri Sultan Syarif
Kasim Riau
1
2. 2 2
Phases of a formal review
1
Planning
2
Kick-Off
3
Preparation
4
Review
Meeting
1
Rework
1
Follow-up
Sistem Informasi – UIN SUSKA RIAUZuliar Efendi
3. 3 3
1
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
Although more and other entry criteria can be applied, the
following can be regarded as the minimum set for
performing the entry check:
A short check of a product sample by the moderator
(or expert) does not reveal a large number of major
defects. For example, after 30 minutes of checking, no
more than 3 major defects are found on a single page
or fewer than 10 major defects in total in a set of 5
pages.
The document to be reviewed is available with line
numbers.
The document has been cleaned up by running any
automated checks that apply.
References needed for the inspection are stable and
available.
The document author is prepared to join the review
team and feels confident with the quality of the
document.
Phases of a
formal review
Sistem Informasi – UIN SUSKA RIAUZuliar Efendi
4. 4 4
2
Kick-Off
An optional step in a review procedure is
a kick-off meeting. 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. Also the
result of the entry check and defined exit
criteria are discussed in case of a more
formal review.
Phases of a formal review
Sistem Informasi – UIN SUSKA RIAUZuliar Efendi
5. 5 5
3
Preparation
A critical success factor for a thorough preparation is the
number of pages checked per hour. This is called the
checking rate. The optimum checking rate is the result of
a mix of factors, including the type of document, its
complexity, the number of related documents and the
experience of the reviewer. Usually the checking rate is in
the range of five to ten pages per hour, but may be much
less for formal inspection, e.g. one page per hour. 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.
Phases of a formal review
Sistem Informasi – UIN SUSKA RIAUZuliar Efendi
6. 6 6
4
Review
Meeting
The meeting typically consists of the following elements
(partly depending on the review type): logging phase,
discussion phase and decision phase.
Every defect and its severity should be logged. The
participant who identifies the defect proposes the severity.
Severity classes could be:
Critical: defects will cause downstream damage; the
scope and impact of the defect is beyond the
document under inspection.
Phases of a formal review
Sistem Informasi – UIN SUSKA RIAUZuliar Efendi
Major, defects could cause a downstream effect (e.g. a fault in a design can result
in an error in the implementation).
Minor, defects are not likely to cause downstream damage (e.g. non-compli ance
with the standards and templates). ,
7. 7 7
4
Review
Meeting
At the end of the meeting, a decision on the document
under review has to be made by the participants,
sometimes based on formal exit criteria. The most
important exit criterion is the average number of critical
and/or major defects found per page (e.g. no more than
three critical/major defects per page). If the number of
defects found per page exceeds a certain level, the
document must be reviewed again, after it has been
reworked. If the document complies with the exit criteria,
the document will be checked during follow-up by the
moderator or one or more participants. Subsequently, the
document can leave the review process.
If a project is under pressure, the moderator will sometimes be forced to skip re-reviews
and exit with a defect-prone document. Setting, and agreeing, quantified exit level criteria
helps the moderator to make firm decisions at all times.
Phases of a formal review
Sistem Informasi – UIN SUSKA RIAUZuliar Efendi
8. 8 8
5
Rework
Based on the defects detected, the author will improve
the document under review step by step. Not every defect
that is found leads to rework. It is the author's
responsibility to judge if a defect has to be fixed. If
nothing is done about an issue for a certain reason, it
should be reported to at least indicate that the author has
considered the issue.
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 (e.g. using 'Track
changes' in word-processing software).
Phases of a formal review
Sistem Informasi – UIN SUSKA RIAUZuliar Efendi
9. 9 9
6
Follow-Up
The moderator is responsible for ensuring that satisfactory
actions have been taken on all (logged) defects, process
improvement suggestions and change requests. Although
the moderator checks to make sure that the author has
taken action on all known defects, it is not necessary for
the moderator to check all the corrections in detail. If it is
decided that all participants will check the updated
document, the moderator takes care of the distribution
and collects the feedback. For more formal review types
the moderator checks for compliance to the exit criteria.
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. It is the responsibility of the moderator to ensure that the
information is correct and stored for future analysis.
Phases of a formal review
Sistem Informasi – UIN SUSKA RIAUZuliar Efendi
To use this title animation slide with a new image simply 1) move the top semi-transparent shape to the side, 2) delete placeholder image, 3) click on the picture icon to add a new picture, 4) Move semi-transparent shape back to original position, 5) Update text on slide.