Abstract— improving performance of software, sites and services is a holy grail of software industry. A new approach for implementation of Poka-Yoke method in software performance engineering is proposed. Poka-Yoke is a mistake proofing technique used in product design. The effectiveness of Poka-Yoke in software development was evaluated using two case studies: product redesign mini-project given to six groups of students and a survey of online services in the software industry. Both quantitative and qualitative evaluation was done. Our proposed five-step mistake proofing technique for software development using Poka-Yoka evaluation demonstrated the effectiveness. The results showed that an implementing Poka-Yoke technique improves the software
…show more content…
Harry Robinson introduced Poka-Yoke (mistake-proofing) into the Hewlett Packard’s software process and he claims they have been able to prevent literally hundreds of software localization defects from reaching their customers. As per Gojko Adzic, author of Impact Mapping “software classes should not allow us to proceed and blow up when something goes wrong. Exceptions can be an effective way of giving more documentation, but the signal should be clean and unambiguous, in order not to mislead users or client-developers. Software must be designed to prevent a complete crash, even in the face of system failure. Auto-save features are a good example. It’s not often that the power gets cut, but when it does, our users will surely appreciate that we saved most of their work” [11]. Much of the research focus is for ZOC, quality control, identifying defects. However, the limitation that associated research brings is not applying Poka- Yoke in …show more content…
PROPOSAL FOR SOFTWARE PERFORMANCE ENGINEERING
Here are the Poka-Yoke based 5 steps (model) we can adapt (in parts or full) to Prevent and/or Detect performance problems at the right time and fix it as depicted in the Table 1 [18].
A. Focus/Strategy
The first step for this would be to include performance as part of the strategy and focus. Considering performance as
Key part of the deliverable is important. “Like security& accessibility, we should consider performance as integral part of any feature. Performance cannot be an afterthought-
If we do not focus performance from the beginning – it might be too late to fix it and in some cases we might miss the
Harry Robinson introduced Poka-Yoke (mistake-proofing) into the Hewlett Packard’s software process and he claims they have been able to prevent literally hundreds of software localization defects from reaching their customers. As per Gojko Adzic, author of Impact Mapping “software classes should not allow us to proceed and blow up when something goes wrong. Exceptions can be an effective way of giving more documentation, but the signal should be clean and unambiguous, in order not to mislead users or client-developers. Software must be designed to prevent a complete crash, even in the face of system failure. Auto-save features are a good example. It’s not often that the power gets cut, but when it does, our users will surely appreciate that we saved most of their work” [11]. Much of the research focus is for ZOC, quality control, identifying defects. However, the limitation that associated research brings is not applying Poka- Yoke in …show more content…
PROPOSAL FOR SOFTWARE PERFORMANCE ENGINEERING
Here are the Poka-Yoke based 5 steps (model) we can adapt (in parts or full) to Prevent and/or Detect performance problems at the right time and fix it as depicted in the Table 1 [18].
A. Focus/Strategy
The first step for this would be to include performance as part of the strategy and focus. Considering performance as
Key part of the deliverable is important. “Like security& accessibility, we should consider performance as integral part of any feature. Performance cannot be an afterthought-
If we do not focus performance from the beginning – it might be too late to fix it and in some cases we might miss the