tag:blogger.com,1999:blog-41491001134237787802024-03-13T03:55:38.997-07:00Janith Gunasekara's blogJanith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.comBlogger20125tag:blogger.com,1999:blog-4149100113423778780.post-33715179103838808702015-01-28T03:49:00.001-08:002015-01-28T04:59:33.493-08:00Roles of a Team Lead<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhVcUGouVW0InWbaraeuVFMRXC0WPx_f38pqZYn2UN_NEhfDfE5oJ25lSLKUW9vNGuVNuPqKDzMupZMtxghU5gQ_pusD3biG4oYodSgfL1uKBqob8a6C3RNC4gaFzM8D7LYrSl3i7I7X0_2/s1600/istock_000006679858xsmall.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhVcUGouVW0InWbaraeuVFMRXC0WPx_f38pqZYn2UN_NEhfDfE5oJ25lSLKUW9vNGuVNuPqKDzMupZMtxghU5gQ_pusD3biG4oYodSgfL1uKBqob8a6C3RNC4gaFzM8D7LYrSl3i7I7X0_2/s1600/istock_000006679858xsmall.jpg" /></a></div>
<br />
As a team lead you may need to fulfill many different roles in a team. In this post, I’ll highlight few of the roles which will be useful from Mintzberg's Management Roles theory. Let’s see how we can use these to improve team performance.<br />
<h3>
<span style="color: #3d85c6;"><br /></span></h3>
<h3>
<span style="color: #3d85c6;">Figurehead Role </span></h3>
<div style="text-align: justify;">
This is a ceremonial role which involved humans. As a team lead in Software firm you are required to get involved with two parties who are knowledge workers. Those parties they are, the customer and the team. In the modern world, I believe people interaction is a key and you shouldn't play this role as a rule or part of your routine job. It has to be more informal approach. Hence you need to please both parties to have successful deliveries.</div>
<br />
<br />
<a name='more'></a><br /><br />
<h3>
<span style="color: #3d85c6;">Leader Role </span></h3>
<div style="text-align: justify;">
There is a saying stating that ‘people leave managers not the company’. You have to be a manger who will lead the team. That’s where you need to come up with your leadership skills to lead the team. As a team lead you need to lead the customer as well. As a leader you are responsible to lead by example. When you set examples it’s easy for you to lead the team to the desired objectives.</div>
<br />
<div style="text-align: justify;">
As a leader it’s important to motivate and encourage the team due to the fact that the software industry is a place where it involves lot of stress. Therefore team might end up in stressful situations. Hence a Leader should lead them to overcome their challengers and get back on to the right track, if not team will not be able to move in the right direction</div>
<br />
<h3>
<span style="color: #3d85c6;">Liaison Role </span></h3>
<div style="text-align: justify;">
It’s important to extend your reach to the outside world as a responsible person. This will help you build up your personal branding. These type of personalities will be considered as brand ambassadors of a company. How can you do this;</div>
<br />
<ul>
<li>Do external sessions at professional gathering and Universities</li>
<li>Attend professional gatherings</li>
<li>Actively involved in panel discussions at profession gatherings</li>
</ul>
<br />
<br />
<h3>
<span style="color: #3d85c6;">Monitor Role</span></h3>
<div style="text-align: justify;">
Monitoring is one of the main roles you need to play as a team Leader. The main areas of monitoring involves customer delivery, the effectiveness and the efficiency of the team and managing new team members.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Deliveries could happen in every couple of weeks/months, thus monitoring the progress is very important. You need to make sure the progress is between controlled levels. Another aspect of the monitoring is the Quality of delivery. It’s important to make sure that you deliver the expected quality every time. There are measurements for this which needs to be referred to, and also gain an understanding where there are outliers which will be hazards.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Monitoring team effectiveness and efficiency is another important aspect. There can be drops. So therefore it’s important to understand the environment. Environment has official aspects as well as the team members’ personal aspects. Therefore a Lead will have to scan and monitor all these aspects. Other than the KPI for monitoring I use techniques such as having discussions with the team.</div>
<br />
<h3>
<span style="color: #3d85c6;">Disseminator Role </span></h3>
<div style="text-align: justify;">
This is a role of a person who makes sure the information flows to all the necessary parties. When you are working with a team and the team is just focused on the team deliveries, they tend to lose the focus of the organization happenings.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
It’s therefore important to update the team on the company information such as company goals, objectives, business decisions, and new standards to follow. This will help the team to understand the changes to be made and how to contribute to value additions. This will help to with aligning career goals with company goals.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Sometimes this role can be named as a facilitator role where this role bridges the gap between employees and the management. </div>
<br />
<h3>
<span style="color: #3d85c6;">Entrepreneur Role</span></h3>
<div style="text-align: justify;">
You need to consider your team as an organization and you have set up goals and objectives to the team. In order to achieve this the team need to have discussions regularly about these goals and its progress. </div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
To achieve great success you need to make sure that you free up the space where team members can come up with ideas to improve their existing work </div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
So Therefore at the end of every year you need to review the year performance and use these learnings to plan the following year. </div>
<br />
<h3>
<span style="color: #3d85c6;">Disturbance Handler Role </span></h3>
<div style="text-align: justify;">
The role can be called as a ‘protector’ to minimize the disturbance to the team. When a disturbance happens, the team will be under pressure and that’s a recipe to get more issues. Thus, it’s important to handle issues and disturbances. These disturbance comes in different forms and I should be vigilant enough to understand these.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
When the disturbance are controlled, team has the environment to work effectively and efficiently </div>
<br />
<h3>
<span style="color: #3d85c6;">Negotiator Role </span></h3>
This is a role a lead will play knowingly or unknowingly every day. There are many situations to negotiate. There are 3 parties where negotiation could take place;<br />
<br />
<ul>
<li>Team members</li>
<li>Customer</li>
<li>Management and other employees</li>
</ul>
<br />
<br />
<div style="text-align: justify;">
If you look at above parties, they don’t have the same level of problems and they don’t have the same level of characteristics. So it’s important to understand them and change the negotiation strategies based on the situation.</div>
<br />
Reference: Mintzberg's Management Roles<br />
<div>
<br /></div>
Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-48011041816365234242012-10-29T11:00:00.002-07:002015-01-28T05:00:02.296-08:00Interviews and Fresh Graduates<br />
<div class="MsoNormal">
</div>
<div class="MsoNormal">
After conducting several interviews with fresh graduates it was evident that most didn’t do well due to small mistakes. Since they are graduates, they are obviously knowledgeable candidates but lacking in experience. Whenever possible I have suggested areas of improvement which can benefit them in the future. </div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
So I thought of jotting down my “5 cents worth“ for fresh graduates who want to start their career as an engineer in Product Quality.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<b>1. Bust the myths</b> </div>
<div class="MsoNormal">
</div>
<ul>
<li>Testing is a very easy job.</li>
<li>Testing is a job you should select if you don’t get a proper job</li>
<li>You don’t need to get ready for interviews</li>
<li>Recognition is very low as a Quality/Test engineer than a Developer</li>
</ul>
<br />
<div class="MsoNormal">
Consider the points above, they are myths! I won’t go into detail but will give a brief outline on overcoming them.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Testing is only a task. There are many tasks that we need to perform to assure product quality. What is product quality? It’s the customer expectation of a product. For e.g. when you want to buy a phone, you look at a particular brand. This is because branded phones are considered to be of good quality. So as Product Quality Engineers (Test Engineers), this is our role. Do you think this is an easy job?</div>
<div class="MsoNormal">
<br />
<a name='more'></a><br /></div>
<div class="MsoNormal">
<b>2. Knowing the basics</b></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Now you know that this is not easy, so when you have an interview it’s very important to be prepared.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
First you need to be knowledgeable about the post and the skills and expectations if you haven’t already obtained this knowledge through your curriculum. If you have gained the knowledge then you need to brush up. You need to be aware of the basic terminologies such as Quality Assurance, Quality Control, Testing Types, Test Cases, Cost of Quality, Automation, etc.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
This doesn’t mean that you should learn everything or parrot it out. Simply, know your basics.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
May be you are applying simply to find a job rather than because you have a passion towards Product Quality. Either way, you need to prepare for the interview.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<b>3. Understand the quality aspect of a product</b></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
To become a Product Quality Engineer , you should be able to see the quality aspects of a product. Especially in product development we have to work with new products most of the time. So we need to be able to see the quality of the products and to know how to measure it. </div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
As consumers we look at this aspect a lot before we buy products. So we need to do the same thing when assuring quality in our work as well.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Let me give you an example, consider a pen. You are asked to check on the quality of the product. What you should look for? </div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
</div>
<ul>
<li>Verify that the pen is built according the specifications.</li>
<li>Usability aspects such as grip, clip, size, point etc.,</li>
<li>The quality of the ink</li>
<li>Performance of the ink and point</li>
<li>All printed/embossed texts on the pen are spell checked</li>
</ul>
<br />
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<b>4. Get certified</b></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
If you are really passionate about being a Test Engineer/Product Quality Engineer, then you could follow a basic course. Most recognized entry level certifications are</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
</div>
<ul>
<li>ISTQB - Foundation Certification – Certified Tester Foundation Level</li>
</ul>
<br />
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<a href="http://www.sl-stb.org/about_slstb.html" target="_blank">http://www.sl-stb.org/about_slstb.html</a></div>
<div class="MsoNormal">
<a href="http://www.sl-stb.org/foundation_certification.html" target="_blank">http://www.sl-stb.org/foundation_certification.html</a></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
</div>
<ul>
<li>QAI - Certified Associate in Software Testing</li>
</ul>
<br />
<div class="MsoNormal">
<a href="http://www.qaiglobalinstitute.com/innerpages/Content.asp?ID=100">http://www.qaiglobalinstitute.com/innerpages/Content.asp?ID=100</a></div>
<div class="MsoNormal">
<a href="http://www.softwarecertifications.org/qai_cast.html">http://www.softwarecertifications.org/qai_cast.html</a></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
So to all fresh graduates, I can say, push your paddles on these areas and the job will be yours. </div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
These points will help you in getting a start on your careers, but there are still more skills to be learnt in order to sustain and grow in the industry.</div>
<div class="MsoNormal">
<br /></div>
<div>
<br /></div>
<br />Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-66375325313084170382012-06-25T03:46:00.000-07:002015-01-28T05:00:17.610-08:00Things to know when testing Mobile applicationsWhen testing using the traditional method on windows/web applications, we all know that we need to test functionality. The same concepts apply for Mobile applications for smart phones as well. As testing experts we should ensure the functionally of the application. While we perform functional testing we need to consider the following points as well.<br />
<br />
<b>Testing matrix</b><br />
<br />
In the mobile market there are more than 835 million smart phones available and it is ever increasing. The testing matrix is complex and it is important to select the correct testing matrix as the test environment. Therefore the points below should be helpful:<br />
<br />
<ul>
<li> OS and Browser </li>
<li> Device model </li>
<li> Wireless connectivity </li>
<li> Location </li>
<li> Network bandwidths </li>
<li> Audience </li>
</ul>
<b></b><br />
<a name='more'></a><b><br /></b><br />
<b>Screen size </b><br />
<br />
In general we can categorize the screen size in to three.<br />
<br />
<ul>
<li>Small</li>
<li>Large</li>
<li>Xlarge </li>
</ul>
<br />
<br />
Not only the size but, we need to consider of the Dots Per Inch (DPI) of a screen as well. This is illustrated in the image below:
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgYuW_Bvtz70kivZm8cVSp3b1WxpVwtqWp-jTRUOZ9fnuDR8zNUIQd8v2nt14DG7MWDbscjTZX1pU-WEQpesuTgFa7widQCn_TH7EIccVUM9uGbTzHjqTK6UD3BiGkzc78D4hZ-NRg60gat/s1600/Screen.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgYuW_Bvtz70kivZm8cVSp3b1WxpVwtqWp-jTRUOZ9fnuDR8zNUIQd8v2nt14DG7MWDbscjTZX1pU-WEQpesuTgFa7widQCn_TH7EIccVUM9uGbTzHjqTK6UD3BiGkzc78D4hZ-NRg60gat/s400/Screen.jpg" height="125" width="400" /></a></div>
<br />
<div class="MsoNormal">
This is important because the icons and texts of an
application will be fine on a small screen but, when the same application is loaded
on a device that has more resolution and a big screen, the output will be
totally unexpected. So the ‘Application Under Test’ (AUT) should be tested for these
categories. <o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<o:p><br /></o:p></div>
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
<b>Screen layout
(portrait vs. landscape)<o:p></o:p></b></div>
<div class="MsoNormal">
<b><br /></b></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal">
Another important aspect in testing mobile applications is when
the devices support orientation switches. Two things to consider are:<o:p></o:p></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l0 level1 lfo1; tab-stops: list .5in; text-indent: -.25in;">
</div>
<ul>
<li><span style="font-family: Arial, sans-serif; text-indent: -0.25in;"><span style="font-family: 'Times New Roman'; font-size: 7pt;"> </span></span><span style="text-indent: -0.25in;">Resizing
UI controls</span></li>
<li><span style="text-indent: -0.25in;">UI
resolution</span></li>
</ul>
<div>
How this will affect the quality of the application is that
UI controls should change the location and resize to suite the new screen size.
This is dynamic and subjective from device to device. Therefore selecting a correct
testing environment is very important.</div>
<br />
<div class="MsoNormal">
</div>
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal">
<b>Native feature<o:p></o:p></b></div>
<div class="MsoNormal">
<b><br /></b></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal">
Native feature is when the AUT accesses device features such as SMS, Email,
Camera, Gallery, etc. <o:p></o:p></div>
<div class="MsoNormal">
How AUT accesses these features are totally different from
OS to OS. So it’s really important to consider and give priority where the
native features/Native code is involved in.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal">
<b>Input methods<o:p></o:p></b></div>
<div class="MsoNormal">
<b><br /></b></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal">
This is about how characters are inserted to the
application. Different devices have different keyboards. Some phones have
physical keyboards and some have virtual keyboards. Still others have different
key arrangements such as QWERTY, Numeric keypad, Mini QWERTY etc. Some Oss’
provide features such as auto suggestion of words. Therefore this is an
important aspect to be tested.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Another important area is physical devices such as track
ball and stylus and these differ according to devices. It’s important to
simulate the usage behavior around these to improve the end product quality.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal">
<b>Disruptions<o:p></o:p></b></div>
<div class="MsoNormal">
<b><br /></b></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal">
Reliability of the AUT is important when disruptions occur. Some
disruptions are:<o:p></o:p></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal" style="margin-left: .25in;">
</div>
<ul>
<li>Network delays</li>
<li>Connectivity losses (mobile/WIFI/Bluetooth)</li>
<li>Receiving calls, SMS and other
alerts</li>
</ul>
<div>
These are real life situations and are highly likely to
occur. Improving reliability of AUT will increase the user experience. </div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<div class="MsoNormal">
<b>Operating system
updates<o:p></o:p></b></div>
<div class="MsoNormal">
<b><br /></b></div>
<div class="MsoNormal">
</div>
<div class="MsoNormal">
OS venders are empowering users to update their devices with
the latest OS updates which are released often. This is important in applications
which are already in the market. Performing this compatibility test early will
prompt release updates of AUT so the end user will experience the quality of
the application<a href="https://www.blogger.com/blogger.g?blogID=4149100113423778780" name="_GoBack"></a>.<o:p></o:p></div>
</div>
<div>
<div class="MsoNormal">
<o:p></o:p></div>
</div>
<o:p></o:p><br />
<div class="MsoNormal" style="margin-left: .25in;">
<o:p></o:p></div>
<div class="MsoNormal" style="margin-left: .25in;">
<o:p></o:p></div>
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com7tag:blogger.com,1999:blog-4149100113423778780.post-70908255880573533612011-10-11T00:02:00.000-07:002015-01-28T04:59:00.058-08:00Cost of Quality<div class="MsoNormal">
This time I thought of discussing about a concept about Cost of Quality in a product. </div>
<div class="MsoNormal" style="text-align: justify;">
What is cost of Quality? The simple answer is to the cost involved in maintain or add quality to a product/service that you are providing to a customer. So how it’s important to an organization? Cost is directly involved with the profit. When cost goes down, profit will go up where revenue is constant.</div>
<div class="MsoNormal">
Now let’s talk this topic in detail.</div>
<div class="MsoNormal">
When discussing the Cost of Quality, there are 3 costing types involved.</div>
<div class="MsoNormal">
</div>
<ol>
<li>Prevention cost</li>
<li>Appraisal cost</li>
<li>Failure cost</li>
</ol>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<b>Prevention Costs</b></div>
<div class="MsoNormal" style="text-align: justify;">
Cost involved in preventing failures is prevention cost. There are many tasks which are performed in order to capture failures soon in the life cycle. It can be any product development methods. </div>
<div class="MsoNormal">
Let’s have list of tasks which will cost in prevention of occurring failures,</div>
<div class="MsoListParagraphCxSpFirst" style="mso-list: l0 level1 lfo1; text-indent: -.25in;">
</div>
<ul>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="font: 7.0pt "Times New Roman";"> </span></span>Establishing a process</li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="font: 7.0pt "Times New Roman";"> </span></span>Planning for quality</li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="font: 7.0pt "Times New Roman";"> </span></span>Acquiring new tools and use them</li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="font: 7.0pt "Times New Roman";"> </span></span>Trainings to improve competency</li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="font: 7.0pt "Times New Roman";"> </span></span>Adopt best practices and leanings from past experience</li>
</ul>
<!--[if !supportLists]--><br />
<div class="MsoNormal">
<o:p> </o:p></div>
<div class="MsoNormal">
<b></b></div>
<a name='more'></a><b><br /></b><br />
<div class="MsoNormal">
<b>Appraisal Costs</b></div>
<div class="MsoNormal" style="text-align: justify;">
Cost involved in capturing bugs/issues in requirements, Code and the developed product before it goes to the production (end user).</div>
<div class="MsoNormal">
Let’s have list of tasks which will cost in capturing of bugs/issues,</div>
<div class="MsoNormal">
</div>
<ul>
<li>Perform requirement reviews, code reviews, inspections</li>
<li>Performing different validation types such as Unit, Integration, System testing, etc</li>
<li>Fix identified bugs/issues</li>
</ul>
<div class="MsoNormal">
<o:p> </o:p></div>
<div class="MsoNormal">
<b><br /></b></div>
<div class="MsoNormal">
<b>Failure Costs</b></div>
<div class="MsoNormal" style="text-align: justify;">
Cost involved in all associated tasks after a defective product released to the production (end user). </div>
<div class="MsoNormal">
Let’s have list of tasks which will cost in failure,</div>
<div class="MsoNormal">
</div>
<ul>
<li>Cost in correcting the product requirements if those didn’t meet first time</li>
<li>Cost of maintain the product</li>
<li>Having a help desk</li>
<li>Paying penalties for defective products</li>
<li>Law penalties due to Safety issues</li>
</ul>
<div>
<br /></div>
<div>
<br /></div>
<div style="text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhdgepqN5-B7f0ToAUwFyHjaaZOXyQOhYHlYlAu0mw2nU7SXB6cs8lo5TE-mHs-AunYf_FFxHhVubGe_nuM0Xl4B-0vBAMyClKVUGNaoekV0W4OXxxJN8uS3LV3LkhJedo5-t3iupCIsStJ/s1600/Cost+of+quality.png" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhdgepqN5-B7f0ToAUwFyHjaaZOXyQOhYHlYlAu0mw2nU7SXB6cs8lo5TE-mHs-AunYf_FFxHhVubGe_nuM0Xl4B-0vBAMyClKVUGNaoekV0W4OXxxJN8uS3LV3LkhJedo5-t3iupCIsStJ/s320/Cost+of+quality.png" id="BLOGGER_PHOTO_ID_5662129198295347922" style="cursor: hand; cursor: pointer; height: 208px; width: 320px;" /></a></div>
<div style="text-align: center;">
<br /></div>
<div style="text-align: left;">
<span class="Apple-style-span">Reference: CBOK 6.2</span></div>
<br />Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-27582981956744546222011-07-30T00:32:00.000-07:002011-07-30T08:01:38.820-07:00How to be a leader<div>This time I’m sharing my ideas about how you can be a successful leader. There are two questions that I want to pop out.</div><div><br /></div><div> 1.How you can be a leader?</div><div> 2.How you can earn the respect as a leader?</div><div><br /></div><div>I like to quote one of favorite mottos from our CEO. “Leaders are not born, Leaders are trained”. I believe the saying. But you should have a proper set of skills to become a good leader. Anyone can be a leader but everyone can’t be a successful leader. </div><div><br /></div><div>Leadership is coming with great responsibilities. So it’s not a jewelry that you can wear and show off to people as well as it is not about the authority. So handle these responsibilities with care.</div><div><br /></div><div>If you want to be a leader to show off, don’t ever try to be one. Then your team or the company will reject you and you will be in a deep trouble. Another issue in some people is that they try to control people or try to show their authority. People try to show their authority when they can’t lead the team by setting examples. Another weakness of some people is that they try to be leaders by back stabbing. If you are in one of these categories, it’s time to re think. Otherwise your team will not move a single bit towards objectives.</div><div><br /></div><div> </div><div>Leaders should be people who facilitate the required environment and providing necessary guidance to achieve the set of objectives for a team. So to archive those objectives, you can’t do it by yourself. You need to guide your team to archive that and you need to lead the way by showing examples. Most importantly the credit should go to the team. You shouldn’t expect the credit for archive objectives. People who are not good leaders, they try to get the credit for the work which done by the team and try to sustain by using those.</div><div><br /></div><div>So how you can become a leader? You need to work for that, you need to be trained for that. So you need to train on the required skills and you need to use those skills. While you excel those skills, you will automatically become a leader. People will gather around you and they will look for you. This is where people will start to respect and treat you as a leader.</div><div><br /></div><div>If you can’t expert the required skill set due to the lack of commitment, then you should not deserve that role. First, you need to understand your strengthsas well as weaknesses and then you need to work on those areas where you need improvements. If you can do these adjustments, believe me you can be a successful leader sooner.</div><div><br /></div><div>Please think again and react before you become a pain to someone.</div><div><br /></div><div>I end this article with couple quotes and i will meet you again with an article of 'Required skill set for a successful leader'</div><div><br /></div><div>“And when we think we lead, we are most led.”</div><div>~Lord Byron</div><div><br /></div><div>“A leader is one who knows the way, goes the way, and shows the way.”</div><div>~John C. Maxwell </div><div><br /></div>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-76302786809464160322011-05-30T22:51:00.000-07:002011-05-30T22:56:01.386-07:00Criticism in officeWhen i was adding some comments to our company discussion forum, I have commented on a topic on 'criticism'. So i thought of sharing that comment in my blog. <div><br /></div><div><div>In any culture, each and every one should respect others, when that happens around you, you will be comfortable in the env and you feel that you are in a free and open culture. </div><div><br /></div><div style="text-align: justify;">Criticism is another good aspect of an open culture. The criticism should be done in professional manner. If not it will lead to lot’s of problems. Why it leads to problems? That’s an area where lots of people feel personally. So it’s really important how you do it. If you do that publicly then people may get offended, may be de motivated and may lead to conflicts. It’s really important how you put it out. So you should not do criticism, you should do Constructive Criticism. </div><div><br /></div><div>I extracted below theory from CSTE CBOK on how you do Constructive Criticism. </div><div><br /></div><div>“In giving constructive criticism, you should incorporate the following tactics: </div><div><br /></div><div>•<span class="Apple-tab-span" style="white-space:pre"> </span>Do it Privately </div><div><br /></div><div style="text-align: justify;">Criticism should be given on a one-on-one basis. Only the individual being criticized should be aware that criticism is occurring. It is best done in a private location. Many times it is more effective if it is done in a neutral location, for example, in a conference room or while taking someone to lunch, rather than in the boss' office. </div><div><br /></div><div>•<span class="Apple-tab-span" style="white-space:pre"> </span>Have the Facts </div><div><br /></div><div style="text-align: justify;">General statements of undesired performance are not very helpful. For example, statements such as "That proposal is not clear, fix it" or "Your program does not make best use of the language or technology" leave people feeling confused and helpless. Before criticizing someone’s performance, have specific items that are causing the deficiency or undesirable performance. </div><div><br /></div><div>•<span class="Apple-tab-span" style="white-space:pre"> </span>Be Prepared to Help the Worker Improve His Performance </div><div><br /></div><div style="text-align: justify;">It is not good enough to ask the worker to "fix it.” You must be prepared to help fix it. Be prepared to train the subordinate in the area of deficiency. For example, in a proposal, indicate that a return-on-investment calculation was not made; or if a program failed to use the language properly, state specifically how it should and should not be used. You should not leave an individual feeling that they have performed poorly or unsure as to how to correct that performance. </div><div><br /></div><div>•<span class="Apple-tab-span" style="white-space:pre"> </span>Be Specific on Expectations </div><div><br /></div><div style="text-align: justify;">Be sure your subordinate knows exactly what you expect from him or her now and in the future. Your expectations should be as clear as possible so there can be no confusion. Again, in a proposal, indicate that you expect a return-on-investment calculation included in all proposals. Most people will try to do what they are expected to do—if they know what those expectations are. </div><div><br /></div><div>•<span class="Apple-tab-span" style="white-space:pre"> </span>One last recommendation for criticism: </div><div><br /></div><div style="text-align: justify;">Avoid making threats about what will happen if the performance does not change. This will not cause any positive behavior change to occur and normally produces negative behavior. Leave the individual with the assumption that he or she has the capability for improvement, and that you know he or she will improve.” </div><div><br /></div><div>When you do criticism acceptably, you will respect the other party and you will gain the respect from others. </div><div><br /></div><div>“He has a right to criticize, who has a heart to help.” ~ Abraham Lincoln</div></div><div><br /></div>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-25472808678172076502011-05-03T20:57:00.000-07:002011-05-06T00:07:46.804-07:00How to motivate your self<p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">If I ask you about a person performance based following statistics, what will be your judgement?<o:p></o:p></span></strong></p> <p class="MsoNormal" style="text-align: justify;"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">There is one person who performed the same task 62850 times and the success of those tasks was 1334. What you think of his performances? Was he performed well? Or was he underperformed.<o:p></o:p></span></strong></p> <p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">The person is none other than our spin legend Murali.<o:p></o:p></span></strong></p> <p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">He has bowled 62850 deliveries to get his 1334 wickets in both formats, ODI and Test.<o:p></o:p></span></strong></p> <p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">He never feared to bowl, he never gave up, bowl by bowl he focused, improved his performance and became a legend<o:p></o:p></span></strong></p> <p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">When it comes to our work, </span></strong><strong><span lang="EN-GB" style="font-size:10.5pt;line-height:115%;font-family:"Georgia","serif"; mso-bidi-font-family:"Times New Roman";mso-bidi-theme-font:minor-bidi; color:#353535;mso-ansi-language:EN-GB">Don’t fear your failures</span></strong><strong><span lang="EN-GB" style="font-size:10.5pt;line-height:115%;font-family:"Georgia","serif"; mso-bidi-font-family:"Times New Roman";mso-bidi-theme-font:minor-bidi; color:#353535;mso-ansi-language:EN-GB;font-weight:normal;mso-bidi-font-weight: bold">. <o:p></o:p></span></strong></p> <p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">That’s my first point of how you can motivate you self in your work life.<o:p></o:p></span></strong></p> <p class="MsoNormal" style="text-align: justify;"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">If you look at our lives, we do the same thing over n over for years, this induce us to get de motivate our self. There are many factors you can consider to be motivated such as money and power, but I believe to be motivated to be success, money and other external things not that much matters. <o:p></o:p></span></strong></p> <p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">So when you fail, take it as a pillar to be success. If Murali gave up his bowling, then there won’t be a legend.<o:p></o:p></span></strong></p> <p class="MsoNormal" style="text-align: justify;"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">The second point is that </span></strong><strong><span lang="EN-GB" style="font-size:10.5pt;line-height:115%;font-family:"Georgia","serif"; mso-bidi-font-family:"Times New Roman";mso-bidi-theme-font:minor-bidi; color:#353535;mso-ansi-language:EN-GB">do</span></strong><strong><span lang="EN-GB" style="font-size:10.5pt;line-height:115%;font-family:"Georgia","serif"; mso-bidi-font-family:"Times New Roman";mso-bidi-theme-font:minor-bidi; color:#353535;mso-ansi-language:EN-GB;font-weight:normal;mso-bidi-font-weight: bold"> </span></strong><strong><span lang="EN-GB" style="font-size:10.5pt; line-height:115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB">all your tasks positively</span></strong><strong><span lang="EN-GB" style="font-size:10.5pt; line-height:115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">. </span></strong><span class="apple-style-span"><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";color:#353535;mso-ansi-language:EN-GB">Learn to let go negative thoughts of tasks before they have a chance to take hold of you. You might not be able to be positive all the time, but it’s really good being positive all the time, which helps you to be open minded. When you approach to perform a task with mind set like that, you will complete the task or will find solutions for complex tasks. When Murali was dried up with wickets he always took that challenge positively and produce new deliveries to take wickets.<o:p></o:p></span></span></p> <p class="MsoNormal" style="text-align: justify;"><span class="apple-style-span"><span lang="EN-GB" style="font-size:10.5pt;line-height:115%;font-family:"Georgia","serif"; color:#353535;mso-ansi-language:EN-GB">When a task is huge or complex, break it down to small chunks. You can complete them piece by piece, by the end of the day you have completes whole task or at least you have completed some. That feels good. Believe me. <b style="mso-bidi-font-weight:normal">Break your task in to small pieces</b>, that’s my third point.<o:p></o:p></span></span></p> <p class="MsoNormal" style="text-align: justify;"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">Next point is </span></strong><strong><span lang="EN-GB" style="font-size:10.5pt;line-height:115%;font-family:"Georgia","serif"; mso-bidi-font-family:"Times New Roman";mso-bidi-theme-font:minor-bidi; color:#353535;mso-ansi-language:EN-GB">Remember your successes</span></strong><strong><span lang="EN-GB" style="font-size:10.5pt;line-height:115%;font-family:"Georgia","serif"; mso-bidi-font-family:"Times New Roman";mso-bidi-theme-font:minor-bidi; color:#353535;mso-ansi-language:EN-GB;font-weight:normal;mso-bidi-font-weight: bold">. The reason behind this is when thoughts of successes flow in your mind you will be energetic and will be in good frame of mind to do complete tasks. You feel positive because you believe you r self because of the successes you had. <o:p></o:p></span></strong></p> <p class="MsoNormal" style="text-align: justify;"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">Final point of the day will be to have fun, </span></strong><strong><span lang="EN-GB" style="font-size:10.5pt; line-height:115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB">whatever you do, make sure you have fun</span></strong><strong><span lang="EN-GB" style="font-size:10.5pt;line-height:115%;font-family:"Georgia","serif"; mso-bidi-font-family:"Times New Roman";mso-bidi-theme-font:minor-bidi; color:#353535;mso-ansi-language:EN-GB;font-weight:normal;mso-bidi-font-weight: bold">. It’s always possible to do what you most like to do during weekends or whenever a holiday is there. It’s always good to do exercises as a part of you life with other fun activities. When your mind says get a break, it’s the right time to get a break<o:p></o:p></span></strong></p> <p class="MsoNormal" style="text-align: justify;"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">Even you can have breaks in between while you perform your tasks daily. I prefer to play TT with my friends at office which refresh my mind continue the remaining tasks. Personally I felt that playing TT refreshes me on a packed day.<o:p></o:p></span></strong></p> <p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">Every day you need to ask yourself whether you are motivated and satisfied enough.<o:p></o:p></span></strong></p> <p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:10.5pt;line-height: 115%;font-family:"Georgia","serif";mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;color:#353535;mso-ansi-language:EN-GB; font-weight:normal;mso-bidi-font-weight:bold">And it’s all about, stay hungry stay foolish<o:p></o:p></span></strong></p>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-53782384972164395752010-09-06T22:53:00.001-07:002010-09-07T01:54:21.263-07:00Why I Became a tester?<div><div>Why I became a tester?</div><div><br /></div><div>Hmm… a good question to ask after all these years. Is it because I didn't have a choice? Is it because this was the first opportunity that i got? Is it because of an inspiration or is it because developing software instead was too difficult at the time?</div><div><br /></div><div>I asked myself these questions and to be honest I have to say that it was an opportunity that came my way. When I was looking for a job during the final year of my degree, I got a chance to go for an interview in a reputed company. They offered me a job in the Quality Assurance (QA) track and I jumped at the chance, because it was a good opportunity to start my career in an internationally reputed company.</div><div><br /></div><div>While I was involved with the day to day activities of the job, I realized that this is what i learnt in the Quality Assurance module during my course work. Then I got the hang of Testing and started to read more about Testing and the QA concepts.</div><div><br /></div><div>The very first thing that I enjoyed in Testing was the moment when I broke the application that I was testing. I believe that was the moment, when i started to like testing.</div><div><br /></div><div>As time passed, I gained an immense and immeasurable amount of experience at my current work place. By studying and sitting for exams and learning new strategies I became more passionate about testing. Although I must admit that I still get an adrenaline rush when I am able to break an application!</div><div><br /></div><div>Even though I became a tester because of the opportunity I was given, now I am a tester because I feel passionately about Testing and Quality Assurance.</div></div>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com1tag:blogger.com,1999:blog-4149100113423778780.post-11478372222787824952010-09-06T21:11:00.000-07:002010-09-06T22:47:19.504-07:00Future of Testing<span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Hi All,<br /><br />It's time to break the silence of this blog. This the first post after the long break.<br /><br />I have found an article on ‘Future of testing’ and it gives a brief, how we should prepare for the future as testers. This is something we should think and be proactive.<br /><br /></span></span><span class="Apple-style-span" style="font-size: medium;"><span class="Apple-style-span" style="color:#000099;">Introduction</span></span><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /><br /></span></span><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Trends in the industry suggest that software testing in the future will look very different than it does today. Businesses are leading change and transformation projects and application development is changing to support it; current trends include:</span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><div><ul><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Web based applications</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Service Oriented Architectures (SOA)</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Software as a Service (SaaS)</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Wireless technologies</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Mobile technologies</span></span></li></ul></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Each of these trends is further complicated by a more agile approach to software development and an increasing emphasis on the 4Rs; repeatability, reliability, re-use and robustness.This paper investigates how testing will need to change to accommodate these trends and become a business led activity.</span></span></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size: medium;"><span class="Apple-style-span" style="color:#000099;">Predictions about the Future of Software Testing</span></span></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div style="text-align: justify;"><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">This paper attempts to predict how testing can become more effective and efficient so that it can keep pace with, and support the changing trends in software development.</span></span></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">In order to drive these changes in effective and efficient application development of quality systems, more emphasis must be placed on improving the Analysis and Design phases and ensuring early engagement of testing in these areas.</span></span></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">To date, analysis and design have been people based activities with Business Analysts and Systems Architects producing a combination of natural language, models and diagramming techniques (such as Data Flow Diagrams, Logical Data Structures, Logical Data Models and Process Data Diagrams) and some structured language techniques (such as Use Cases and UML). This has led to business requirements and functional designs which do not meet the four key criteria which make the resultant systems “testable”; clear, assumption free, unambiguous and complete.</span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">In the future, if we are to enable the production of quality applications, in less time and at lower cost, we will see more structured and more automated analysis and design techniques, with Static Testing (reviews, inspections and walkthroughs) becoming “robotized” and built in as part of the analysis and design requirements capture tools. This will result in clarity, the eradication of assumptions and ambiguity and a greater likelihood of completeness which will in turn enable:</span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><div><ul><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Executable specifications</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Auto generated code and systems configurations</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Model-based test generation</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Model-based bug prevention</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">System simulation</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Fault tolerance developing into self-testing, self monitoring, self healing software</span></span></li><li><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Performance optimization “designed in” and “on the fly”</span></span></li></ul></div></div></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">So what will it mean for Testing and QA? Well the products should be more reliable, more reusable and more robust. Automatically generated test scripts with full branch and decision tree coverage at the early test execution stages; unit test and “integration in the small”, combined with the development of fault tolerance into self-testing, self monitoring, self healing software will result in defects being found and eradicated earlier in the lifecycle. As a result,fewer defects should be found at the System Testing and “Integration in the large” stages and businesses will be able to concentrate on Acceptance Testing (User, Operational and Performance) in a fully integrated target environment and do full end to end testing of business processes and model office scenarios. In this way, businesses will be able to leverage their investment in technology to realize true business benefits and competitive advantage through creative integration and deployment of reliable, re-usable, robust components; the way in which the components are integrated and deployed will be the differentiator, not the components/systems themselves. In turn, this will enable business to concentrate on business propositions, and go to market services and products, supported by the ability to deal with high volumes, provide excellent customer service and quickly enable high margin/low volume services etc.</span></span></div></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><div><span class="Apple-style-span" style="color:#000099;"><span class="Apple-style-span" style="font-size: medium;">Testing Robots? What about Professional Testers?</span></span></div></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Software testing in the era of mainframe systems was merely executing a series of steps manually and punching various key strokes as an attempt to break the application. This was followed by the event-driven client-server environment in which applications were deployed on multiple hardware platforms in conjunction with various other applications. As a result, the scope of testing has increased as failures and unexpected behaviors have become more prominent. </span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">The recent development of web applications, where multilayered designs were architected in order to hold complex business logic, which are to be supported on numerous browser types and various platforms and different network structures, further increases the potential areas of failure. In addition, web applications say something about the integrity of business operations to a large audience of external users (i.e. customers, business partners) and can have a major impact on brand and reputation.</span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">New and emerging technologies, such as Service Oriented Architectures (SOA) are significantly changing the trends in the application testing. SOA in particular has major implications for how tests are esigned and performed. Software as a Service (SaaS) also has a totally different view of software testing. We can conclude that new and more complex technology/architecture creates greater risk.</span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">So, how will the new approaches postulated in the predictions in the previous section of this paper manifest themselves and what will it feel like to be a Test Professional in an increasingly automated and “robot” driven software engineering environment?</span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Testing mitigates risk and despite automation and “robot” driven testing techniques, the Testing Professional will continue to be pivotal in the Software Engineering Lifecycle. Working in multi-disciplinary teams alongside Subject Matter Experts, Business Analysts, Systems Architects and End Users they will continue to play the roles of; arbitrator,mediator, translator, negotiator between the other parties, ensuring that their ideas are not only effectively specified and designed, but that the criteria required for effective quality and testing are captured and articulated into the models and tools so that tests are accurately generated by the “robots” to verify the design and validate the requirements.</span></span></div></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">In this new world, the Professional Tester will concentrate on adding value to the business and the software development lifecycle and will operate in a new and elevated position where the combination of their structured process driven approach, creativity, destructive inquisitiveness and ability to articulate and define quality and testing criteria into the models will be critical to the success of the business implementation of technology.</span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><span class="Apple-style-span" style="font-size: medium;"><span class="Apple-style-span" style="color:#000099;">Summary and Conclusion</span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Change is a given and we can be sure that it will come in larger amounts and at increasing pace. No industry, least of all software engineering, is immune from change and therefore none is immune from risk. The changes in software development will require software testing to develop in parallel. Of one thing we can be sure, the role of the Professional Tester will become more interesting and more essential in both the definition of model based testing criteria and the facilitation of Acceptance Testing (User, Operational and Performance), testing of business processes and model office scenarios alongside Subject Matter Experts and End Users and ultimately realizing business benefits.</span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br /></span></span></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">Testing and Quality Assurance will become more important and add more value as we move into architectures and technologies that support the business in their goals of bringing products and services to the market as rapidly as possible, with minimal risk. We will see a shift towards testing the transformed business operation, the business </span></span><span class="Apple-style-span"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">processes, the way people interact with the systems and processes and the information it provides, and therefore </span></span></span><span class="Apple-style-span"><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;">mitigating the risks and increasing the benefits of business change.</span></span></span></div></div><div><span class="Apple-style-span" style="font-size:small;"><span class="Apple-style-span" style="color:#333333;"><br />Reference: AppLabs</span></span><br /></div>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-21738306817776973032009-12-25T11:06:00.000-08:002009-12-25T11:11:03.385-08:00New Year New ArticlesI couldn't publish any article last two months because i had a busy calender. So guys there will be new articles lined up for 2010.....<br /><br />Wishing you a <span style="font-weight:bold;">Merry Christmas</span> and <span style="font-weight:bold;">Happy new year</span>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-25666365694263733332009-10-02T00:13:00.000-07:002009-10-04T21:05:08.053-07:00Test Automation Benefits & PrioritiesI have listed out few points about automation below. These points will elaborate how important an automation tool in testing is.<br /><br /><span style="font-weight: bold;font-size:130%;" >Test Automation Benefits</span><br /><ul><li>Improves testing efficiency </li><li>Consistent and repeatable testing process </li><li>Supports quality metrics for test optimization </li><li>Improved regression tests - decrease cost of change </li><li>More tests can be run in less time - better coverage and shorter time </li><li>24/7 operation - better use of resources </li><li>Human resources are free to perform advanced manual tests </li><li>Objective and measurable performance and stress tests </li><li>Execution of tests that can't be done manually </li><li>Tests can access system parameters that are not visible to tester </li><li>Simple reproduction of found defects </li><li>Testing costs decrease with reuse </li></ul><span style="font-weight: bold;font-size:130%;" >Test Automation Priorities </span><br /><br /><br /><ul><li>Right selection of test procedures for automation is critical. </li></ul><ul><li>The test automation project should prove its usefulness to the organization by providing maximum impact for minimum effort from the start. </li></ul><ul><li>The following list represents recommended candidates for the first automation stage:<br />- simplest to automate tests<br />- frequently running tests<br />- critical set tests<br /></li></ul><ul><li>Good for system "smoke test" execution</li></ul>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-13966681848383471112009-09-17T02:48:00.001-07:002009-09-17T03:48:56.741-07:00Test Automation Introduction<div style="text-align: justify;"><span style="font-weight: bold; color: rgb(0, 153, 0);">Test Automation</span> is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions. Commonly, test automation involves automating a manual process already in place that uses a formalized testing process.<br /><br />Many test automation tools provide record and playback features that allow users to record interactively user actions and replay it back<br /><br /><br /><span style="font-weight: bold;">Types of Test Automation</span><br /><br /><ul><li>Functional Testing</li><li>Performance Testing</li><li>Stress Testing</li><li>Load Testing</li></ul><br /><span style="font-weight: bold;">Functional testing</span><br /><br />Functional testing is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.<br /><br /><span style="font-size:100%;"><span style="font-weight: bold;">Tools</span></span><ul><li>WinRunner</li><li>IBM Rational Functional Tester </li><li>Silk Test</li></ul><br /><span style="font-weight: bold;">Performance Testing</span><br /><br />Performance Testing is testing that is performed, from one perspective, to determine how fast some aspect of a system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability and reliability.<br />demonstrate that the system meets performance criteria.<br />impossible to exactly replicate this workload variability of a real time system<br /><br />Tools<br /><ul><li>OpenSTA</li><li>LoadRunner</li><li>Silk Performer</li></ul><br /><span style="font-weight: bold;">Stress Testing/Load Testing</span><br /><br /><span style="font-weight: bold;">Stress Testing</span> is a form of testing that is used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. Stress testing may have a more specific meaning in certain industries.<br />stress testing often refers to tests that put a greater emphasis on robustness, availability, and error handling under a heavy load, than on what would be considered correct behavior under normal circumstances.<br /><br /><span style="font-weight: bold;">Load Testing</span> is the process of creating demand on a system or device and measuring its response.<br />Load testing generally refers to the practice of modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.<br /><br />Tools<br /><ul><li>LoadRunner</li><li>Visual Studio Team Test </li><li>Application Center Test </li><li>Silk Performer</li></ul><br /></div>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com1tag:blogger.com,1999:blog-4149100113423778780.post-89902743555218530632009-09-16T23:09:00.000-07:002009-09-16T23:28:08.768-07:00Risk Based Testing<span style="font-weight: bold;">What is RBT</span><br /><br /><div style="text-align: justify;">Risk based Testing (RBT) is a type of software testing that prioritize the features and functions to e tested based on priority /importance and likelihood or impact of failure. In theory, since there are an infinite number of possible tests, any set of tests must be a subset of all possible tests.</div><br />Most of the people consider James Bach to be the 'father of Risk based testing.<br /><br /><span style="font-weight: bold;">Activities involved in RBT</span><br /><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYI-RJDsRBYooQ7AqyPFEA4j75GPwAwLOlXGNt9m5IgNln-bPlDEpkctM8aWKONIPundA9zIPeZrNs7PtB0lwS-DYMfErVhlqSTbXht2_74Rws6SLFYf3oBg8WfQ4fxM0Jv8YxN-nNaRsx/s1600-h/RBT_diag.jpg"><img style="cursor: pointer; width: 400px; height: 248px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYI-RJDsRBYooQ7AqyPFEA4j75GPwAwLOlXGNt9m5IgNln-bPlDEpkctM8aWKONIPundA9zIPeZrNs7PtB0lwS-DYMfErVhlqSTbXht2_74Rws6SLFYf3oBg8WfQ4fxM0Jv8YxN-nNaRsx/s400/RBT_diag.jpg" alt="" id="BLOGGER_PHOTO_ID_5382315668593834594" border="0" /></a><br /><br /><span style="font-weight: bold;">Risk Identification</span> involves collecting information about the project and classifying it to detemine the amount of potential risk in the test phase and in production.<br /><br /><span style="font-weight: bold;">Risk Strategy </span>involves the identification and assessment of risks and the development of the contingency plans for for possible alternative project or the mitigation of all risks.<br /><br /><span style="font-weight: bold;">Risk assessment</span> means determining the effect (including cost) of potential risks.<br /><br /><span style="font-weight: bold;">Risk Mitigation</span> is based on information gained from the previous actives of identifying, planning and assessing risks. Risk mitigation/avoidance activities or minimize their impact<br /><br /><span style="font-weight: bold;">Risk Reporting </span>is based on information obtained from the previous topics and it's very often done in standard graphs.<br /><br />Risk Predication involves forecasting risks using the history and knowledge of previously identified risksJanith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-7910816565803091352009-08-02T22:13:00.000-07:002009-08-02T22:47:26.277-07:00What is Usability TestingWhat is Usability Testing - Part 2<br /><br /><br /><strong>Planning a Test</strong><br /><div align="justify"><br />The first thing to know about planning a usability test is that every test is different in scope, and results will vary a lot depending on the purpose and context of the test. Testing a single new feature will look very different from testing several key scenarios in a new Application.</div><br /><strong>What Are You Going to Test?</strong><br /><div align="justify"><br />Next, you need to decide what you’re going to test. The best way to do this is to meet with the design and development team and choose features that are new, frequently used, or considered troublesome or especially important. After choosing these features, prioritize them and write task scenarios based on them. A task scenario is a story that represents typical user activities and focuses on a single feature or group of related features. Scenarios should be:</div><div align="justify"><br />- <strong>Short - </strong>Time is precious during usability testing, so you don’t want to spend too much time on reading or explaining scenarios. </div><div align="justify"><br />- <strong>Specific -</strong> The wording of the scenario should be unambiguous and have a specific end goal. </div><div align="justify"><br />- <strong>Realistic - </strong>The scenario should be typical of the activities that an average user will do on the Application. </div><div align="justify"><br />- <strong>In the user’s language and related to the user’s context - </strong>The scenario should explain the task the same way that users would. This emphasizes the importance of the pre-session discussion, which gives you the opportunity to understand the participant’s relationship with the Application. </div><div align="justify"><br />Here’s an example scenario for an Application that sells images:</div><br /><div align="justify">Ex: You’re looking for an image that you can use on your company’s support Application. Find an appropriate image and add it to your basket. Be sure to let me know when you’re done.</div><div align="justify"><br /><strong>Who is going to evaluate the Application?</strong></div><div align="justify"><br />Who you choose to evaluate the Application will have a massive effect on the outcome of the research. It’s very important to develop a thoughtful screener for recruiting your participants.</div><div align="justify"><br />Imagine that you’re creating an Application that sells images. Your customers are people who want to buy images—a huge group of people. Narrow your focus to a short and concise user profile, a picture of your ideal test participants. This profile should be based on your primary user (customer) segment and contain characteristics that those users share.</div><div align="justify"><br />In this scenario, our participants are graphic designers or other people who use graphic design software and purchase images online. Create and order a list of these users’ characteristics. While you’re creating the user profile, you may realize that you have two or more equally important subgroups—people who buy images for business use and people who buy images for home use. This is fine as long as you can justify the relevance of each subgroup to the features that you’ll be testing.</div><div align="justify"><br /><strong></strong>- <strong>Test with a reasonable number of participants </strong>—The best results come from testing no more than 5 users and running as many small tests as you can afford. </div><br /><br /><div align="justify"><img id="BLOGGER_PHOTO_ID_5365602739576210914" style="DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 320px; CURSOR: hand; HEIGHT: 154px; TEXT-ALIGN: center" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjp2T4w3paumoIbi5n0LYpvP6-Hp4wDvjvYKGgQvWmoEFNr9f6ntpDcVkSWgsRf_C9A8W83aR2qhjHmNt_PEWqxrDbNOYevRw8hysqGACQHCfZ5hcAqUhNXfvXUJuboQVflOFcDVn-CrJTF/s320/Image01.jpg" border="0" /><br />The most striking truth of the curve is that <strong>zero users give zero insights</strong>. </div><div align="justify"><br />As soon as you collect data from a <strong>single test user</strong>, your insights shoot up and you have already learned almost a third of all there is to know about the usability of the design. The difference between zero and even a little bit of data is astounding. </div><div align="justify"><br />When you test the <strong>second user</strong>, you will discover that this person does some of the same things as the first user, so there is some overlap in what you learn. People are definitely different, so there will also be something new that the second user does that you did not observe with the first user. So the second user adds some amount of new insight, but not nearly as much as the first user did. </div><div align="justify"><br />The <strong>third user</strong> will do many things that you already observed with the first user or with the second user and even some things that you have already seen twice. Plus, of course, the third user will generate a small amount of new data, even if not as much as the first and the second user did. </div><div align="justify"><br />As you <strong>add more and more users</strong>, <strong>you learn less and less </strong>because you will keep seeing the same things again and again. There is no real need to keep observing the same thing multiple times, and you will be very motivated to go back to the drawing board and redesign the Application to eliminate the usability problems. </div><div align="justify"><br />After the fifth user, you are wasting your time by observing the same findings repeatedly but not learning much new. </div><div align="justify"><br />You need to test additional users when the Application has <strong>several highly distinct groups of users</strong></div><div align="justify"><strong></strong></div><div align="justify"></div><div align="justify"><strong></strong></div><div align="justify">Article is prepared by:<br />Anushka Wickramaratne<br />Senior QA Engineer </div>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-18561260294566052932009-07-27T03:13:00.000-07:002009-07-27T03:25:57.867-07:00What is Usability Testing<span style="font-weight: bold;">What is Usability Testing</span> - Part 1
<br /><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link style="font-weight: bold;" rel="File-List" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link style="font-weight: bold;" rel="Edit-Time-Data" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><link style="font-weight: bold;" rel="themeData" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link style="font-weight: bold;" rel="colorSchemeMapping" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-GB</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>X-NONE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} </style> <![endif]--><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link style="font-weight: bold;" rel="File-List" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link style="font-weight: bold;" rel="themeData" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link style="font-weight: bold;" rel="colorSchemeMapping" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-GB</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>X-NONE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} </style> <![endif]--> <p style="text-align: justify;" class="MsoNormal"><span style=";font-family:";font-size:85%;" lang="EN-US" >
<br /></span></p><p style="text-align: justify;" class="MsoNormal"><span style=";font-family:";font-size:85%;" lang="EN-US" ><span style="color: rgb(0, 153, 0);">Usability testing</span> is a technique for ensuring that the intended users of a syste</span><span style=";font-family:";font-size:85%;" lang="EN-US" >m can carry out the intended tasks efficiently, effectively and satisfactorily. In other words, Usability testing should be an iterative practice, completed several times during the design and development life-cycle. The end result is an improved product and a better understanding of the users that we’re designing it for.</span></p><p style="text-align: justify;" class="MsoNormal">
<br /><span style=";font-family:";font-size:85%;" lang="EN-US" ><o:p></o:p></span> </p><p style="text-align: justify;" class="MsoNormal"><span style=";font-family:";font-size:85%;" lang="EN-US" ><o:p> </o:p></span></p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="MsoNormal"><span style=";font-family:";font-size:85%;" lang="EN-US" >Main steps in the usability testing process are <b>Planning</b>, <b>Gathering</b> <b>Data</b> and <b>Reporting results.</b></span></p><p class="MsoNormal" style="text-align: justify;">
<br /></p><p class="MsoNormal" style="text-align: justify;"><span style=";font-family:";font-size:85%;" lang="EN-US" ><b>
<br /></b></span></p><p class="MsoNormal" style="text-align: justify;"><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEin3jJiT4A6v-zXesuxIqmP39f1s8_3nLrAAj8p-gwKDgCrnuncHemodqydXpvcZxvoJZTEFb-OMTJO69dN6kXbEsDSNB1dcAvrg-Ulb-B7O7YBYcXgWCQbKtms9yJDdZV2Mgthi3ZycZUN/s1600-h/UTimage1.jpg"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 192px; height: 201px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEin3jJiT4A6v-zXesuxIqmP39f1s8_3nLrAAj8p-gwKDgCrnuncHemodqydXpvcZxvoJZTEFb-OMTJO69dN6kXbEsDSNB1dcAvrg-Ulb-B7O7YBYcXgWCQbKtms9yJDdZV2Mgthi3ZycZUN/s320/UTimage1.jpg" alt="" id="BLOGGER_PHOTO_ID_5363081503829975666" border="0" /></a></p><p class="MsoNormal" style="text-align: justify;">
<br /></p><p class="MsoNormal" style="text-align: justify;"><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CEURCOL%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:trackmoves/> <w:trackformatting/> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:donotpromoteqf/> <w:lidthemeother>EN-GB</w:LidThemeOther> <w:lidthemeasian>X-NONE</w:LidThemeAsian> <w:lidthemecomplexscript>X-NONE</w:LidThemeComplexScript> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> <w:splitpgbreakandparamark/> <w:dontvertaligncellwithsp/> <w:dontbreakconstrainedforcedtables/> <w:dontvertalignintxbx/> <w:word11kerningpairs/> <w:cachedcolbalance/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathpr> <m:mathfont val="Cambria Math"> <m:brkbin val="before"> <m:brkbinsub val="--"> <m:smallfrac val="off"> <m:dispdef/> <m:lmargin val="0"> <m:rmargin val="0"> <m:defjc val="centerGroup"> <m:wrapindent val="1440"> <m:intlim val="subSup"> <m:narylim val="undOvr"> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"> <w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"> <w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"> <w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"> <w:lsdexception locked="false" priority="39" name="toc 1"> <w:lsdexception locked="false" priority="39" name="toc 2"> <w:lsdexception locked="false" priority="39" name="toc 3"> <w:lsdexception locked="false" priority="39" name="toc 4"> <w:lsdexception locked="false" priority="39" name="toc 5"> <w:lsdexception locked="false" priority="39" name="toc 6"> <w:lsdexception locked="false" priority="39" name="toc 7"> <w:lsdexception locked="false" priority="39" name="toc 8"> <w:lsdexception locked="false" priority="39" name="toc 9"> <w:lsdexception locked="false" priority="35" qformat="true" name="caption"> <w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"> <w:lsdexception locked="false" priority="1" name="Default Paragraph Font"> <w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"> <w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"> <w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"> <w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"> <w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"> <w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"> <w:lsdexception locked="false" unhidewhenused="false" name="Revision"> <w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"> <w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"> <w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"> <w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"> <w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"> <w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"> <w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"> <w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"> <w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"> <w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"> <w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"> <w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"> <w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"> <w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"> <w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"> <w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"> <w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"> <w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"> <w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"> <w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"> <w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"> <w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"> <w:lsdexception locked="false" priority="37" name="Bibliography"> <w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:"Century Gothic"; panose-1:2 11 5 2 2 2 2 2 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:647 0 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; mso-style-unhide:no; mso-style-qformat:yes; margin-top:0cm; margin-right:0cm; margin-bottom:10.0pt; margin-left:36.0pt; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1499538649; mso-list-type:hybrid; mso-list-template-ids:-2141703220 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} @list l0:level1 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level2 {mso-level-tab-stop:72.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level3 {mso-level-tab-stop:108.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level4 {mso-level-tab-stop:144.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level5 {mso-level-tab-stop:180.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level6 {mso-level-tab-stop:216.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level7 {mso-level-tab-stop:252.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level8 {mso-level-tab-stop:288.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level9 {mso-level-tab-stop:324.0pt; mso-level-number-position:left; text-indent:-18.0pt;} ol {margin-bottom:0cm;} ul {margin-bottom:0cm;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";} </style> <![endif]--> </p><p class="MsoNormal" style="margin-bottom: 6.25pt; line-height: 140%; vertical-align: top;"><span style="line-height: 140%;font-family:";font-size:85%;" lang="EN-US" >There are two scenarios for usability testing:
<br /></span></p> <p class="MsoListParagraph" style="margin-bottom: 1.9pt; text-align: justify; text-indent: -18pt; line-height: 140%; vertical-align: top;">1. <span style="line-height: 140%;font-family:";font-size:85%;" lang="EN-US" >If you are a software product vendor, testing real users of your product means you are evaluating for design. Based on how you have designed the application, can users complete the tasks they need to do? Testing real users doing real tasks can also point out if the UI guidelines you are following are working within the context of your product, and when consistency helps or hinders the users’ ability to do their work.</span></p><p class="MsoListParagraph" style="margin-bottom: 1.9pt; text-align: justify; text-indent: -18pt; line-height: 140%; vertical-align: top;"><span style="line-height: 140%;font-family:";font-size:85%;" lang="EN-US" >
<br /></span></p> <p class="MsoListParagraph" style="text-align: justify; text-indent: -18pt; line-height: 140%; vertical-align: top;">2. <span style="line-height: 140%;font-family:";font-size:85%;" lang="EN-US" >If you are a software product purchaser, you can do usability testing to evaluate a product for purchase. For example, your company might consider buying a product for their twenty thousand employees. Before the company spends its money, it wants to make sure that the product in question will really help employees do their jobs better. Usability testing can also be useful to see if the proposed application follows published UI style guidelines (internal or external). It’s best to use UI guidelines as an auxiliary, rather than primary, source of information for making purchase decisions. <o:p></o:p></span></p> <p class="MsoNormal" style="line-height: 140%; vertical-align: top;"><span style="line-height: 140%;font-family:";font-size:85%;" lang="EN-US" >This Guide is discussing on the first scenario ‘evaluating for design’.</span></p><p class="MsoNormal" style="line-height: 140%; vertical-align: top;">
<br /><span style="line-height: 140%;font-family:";font-size:85%;" lang="EN-US" ><o:p></o:p></span></p> <p class="MsoNormal" style="line-height: 140%; vertical-align: top;"><span style="line-height: 140%;font-family:";font-size:85%;" lang="EN-US" ><o:p> </o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:85%;"><b><span style=";font-family:";" lang="EN-US">When Usability Testing is appropriate?</span></b></span></p><p class="MsoNormal" style="">
<br /><span style="font-size:85%;"><b><span style=";font-family:";" lang="EN-US"><o:p></o:p></span></b></span></p> <p class="MsoListParagraph" style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size:85%;"><b><span style=";font-family:";" lang="EN-US"><o:p> </o:p></span></b></span></p> <p class="MsoNormal" style="text-align: justify;"><span style=";font-family:";font-size:85%;" lang="EN-US" >Usability testing is carried out pre-release so that any significant issues identified can be addressed. It can be carried out at various stages of the design process as well. In the early stages, however, techniques such as walkthroughs are often more appropriate.</span></p><p class="MsoNormal" style="text-align: justify;">
<br /></p><p class="MsoNormal" style="text-align: justify;">
<br /></p><p class="MsoNormal" style="text-align: justify;">Article is prepared by:</p><p class="MsoNormal" style="text-align: justify;">Anushka Wickramaratne</p><p class="MsoNormal" style="text-align: justify;">Senior QA Engineer
<br /></p><p class="MsoNormal" style="text-align: justify;">
<br /><span style=";font-family:";font-size:10pt;" lang="EN-US" ><o:p></o:p></span></p>
<br /><span style=";font-family:";font-size:10pt;" lang="EN-US" ><o:p></o:p></span><p></p> Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-83926285585967149272009-07-25T08:38:00.000-07:002009-08-22T13:11:35.956-07:00What is a Test Case<p class="MsoNormal">In simple terms, test cases are<span style=""> </span>how the testers validate that software meets customer requirements. It’s a tool which helps testers to test a product.</p><p class="MsoNormal"><br /></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><b></b></span></p><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><b><p class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;">Test case <span class="Apple-style-span" style="font-weight: normal;"><span class="Apple-style-span" style="color: rgb(0, 0, 0);">is a set of conditions organized in a manner which determines a requirement is met in the product by testers. Then testers can decide whether the test is passed or failed based on the output of the test case. If the output is passed the conclusion is that the tested requirement is functioning correctly. If test case failed then that requirement needs a code change to fix the issue. When a test case is failed, testers called it as bug/issue* of the system. </span></span></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p><span class="Apple-style-span" style="font-weight: normal;"><span class="Apple-style-span" style="color: rgb(0, 0, 0);"> </span></span></o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"><span class="Apple-style-span" style="font-weight: normal;"><span class="Apple-style-span" style="color: rgb(0, 0, 0);">The main inputs for test cases are requirements of the system. This can in format of a requirement document which represents using deferent techniques such as use cases. Then it’s testers’ responsibility to design test cases to cover all requirements. There are tests to cover the positive test and the negative test for a requirement as the minimum. </span></span></p></b></span><p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">There are several information required for a complete test case and those are,</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Test case ID</span></b> – to identify a test case, it should have a unique number.</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><br /></span></b></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Test case description</span></b> – This includes the description of the feature or the requirement that’s going to test by this test case.</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><br /></span></b></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Steps</span></b> – steps should be included to guide the tester to execute the desired test case</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><br /></span></b></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Input data</span></b> – If the test case requires the specific data, those can be included here. When designing the test case, it’s acceptable to include the test data among the steps.</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><br /></span></b></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Reference</span></b> – this will link the test case to the requirement which has documented in requirement document.</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><br /></span></b></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Expected result</span></b> – this the expected output of the test case and how the feature/requirement should function in the product.</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><br /></span></b></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Testing status</span></b>– this will contain information whether the test case is passed or failed after execution of the test.</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><br /></span></b></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Author</span></b> – This will contain information who has designed the test cases.</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><br /></span></b></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Date</span></b> – this will hold the information when the test cases are designed.</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><br /></span></b></p><p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Change history</span></b>- this will give an idea what has been changing in the test cases after creation of it.<span style=""> </span></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">Author, Date and change history can be single entry for a set of test cases.</p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"><span class="Apple-style-span" style="color:#FF9966;"><br /></span></p> <p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;">*Bug/Issue will be discussed in detail in another post.</p>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com2tag:blogger.com,1999:blog-4149100113423778780.post-89517176324076227232009-07-25T08:28:00.000-07:002009-07-27T03:32:36.820-07:00Vocabulary...<p class="MsoNormal" style="text-align: justify; line-height: normal;"><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><b></b></span></p><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><b><p class="MsoNormal"><span class="Apple-style-span" style="color: rgb(0, 0, 0);">Followings are some of the words that will be useful for the next topic.</span></p></b></span><p></p><p class="MsoNormal" style="text-align: justify; line-height: normal;"><span class="Apple-style-span" style="color: rgb(0, 153, 0);"><b><br /></b></span></p><p class="MsoNormal" style="text-align: justify; line-height: normal;"><b><span lang="EN-GB"><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Risk</span></span></b><span lang="EN-GB"> is the potential loss to an organization, as for example, the risk resulting from the misuse of its computer. This may involve unauthorized disclosure, unauthorized modification, and/or loss of information resources, as well as the authorized but incorrect use of a computer. Risk can be measured by performing risk analysis.</span></p><p class="MsoNormal" style="text-align: justify; line-height: normal;"><span lang="EN-GB"><br /></span></p> <p class="MsoNormal" style="text-align: justify;"><span lang="EN-GB"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align: justify; line-height: normal;"><b style=""><span lang="EN-GB"><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Risk Analys</span><span class="Apple-style-span" style="color: rgb(0, 153, 0);">is</span></span></b><span lang="EN-GB"> is an analysis of an organization’s information resources, its existing controls, and its remaining organization and computer system vulnerabilities. It combines the loss potential for each resource or combination of resources with an estimated rate of occurrence to establish a potential level of damage in dollars or other assets.</span></p><p class="MsoNormal" style="text-align: justify; line-height: normal;"><span lang="EN-GB"><br /></span></p> <p class="MsoNormal" style="text-align: justify;"><span lang="EN-GB"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align: justify; line-height: normal;"><span lang="EN-GB">A<b style=""> </b><b><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Threat</span></b> is something capable of exploiting vulnerability in the security of a computer system or application. Threats include both hazards and events that can trigger flaws.<br /></span></p><p class="MsoNormal" style="text-align: justify; line-height: normal;"><span lang="EN-GB"><br /></span></p> <p class="MsoNormal" style="text-align: justify;"><span lang="EN-GB"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align: justify;"><b><span lang="EN-GB"><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Vulnerability</span></span></b><span lang="EN-GB"> is a design, implementation, or operations flaw that may be exploited by a threat; the flaw causes the computer system or application to operate in a fashion different from its published specifications and to result in destruction or misuse of equipment or data.</span></p><p class="MsoNormal" style="text-align: justify;"><span lang="EN-GB"><br /></span></p> <p class="MsoNormal" style="text-align: justify;"><span lang="EN-GB"><o:p> </o:p></span></p> <p class="MsoNormal" style="text-align: justify;"><b style=""><span lang="EN-GB"><span class="Apple-style-span" style="color: rgb(0, 153, 0);">Contro</span><span class="Apple-style-span" style="color: rgb(0, 153, 0);">l</span></span></b><span lang="EN-GB"> is anything that tends to cause the reduction of risk. Control can accomplish this by reducing harmful effects or by reducing the frequency of occurrence.</span></p><p class="MsoNormal" style="text-align: justify;"><span lang="EN-GB"><br /></span></p><p class="MsoNormal" style="text-align: justify;"><br /></p><p class="MsoNormal" style="text-align: justify;"><span class="Apple-style-span" style="font-size:x-small;">Reference: CSTE CBOk v 6.2</span></p>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-69718891370635951392009-07-10T11:22:00.000-07:002009-07-10T12:49:15.939-07:00Clear doubts about QC vs QA<b><span class="Apple-style-span" style="font-size:medium;">Quality Assurance Versus Quality Control</span></b><div><span class="Apple-style-span" style="font-size:medium;"><br /></span></div><div><span class="Apple-style-span" style="font-size: small;">What you guess? it does mean same? any guess?</span></div><div><p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="font-size: small;">The following statements help differentiate quality control from quality assurance:</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality control relates to a specific product or service.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality control verifies whether specific attribute(s) are in, or are not in, a specific product or service.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality control identifies defects for the primary purpose of correcting defects.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality control is the responsibility of the team/worker.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal"><span style=" line-height: 115%; "><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality control is concerned with a specific product.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality assurance helps establish processes.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality assurance sets up measurement programs to evaluate processes.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality assurance identifies weaknesses in processes and improves them.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality assurance is a management responsibility, frequently performed by a staff function.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality assurance is concerned with all of the products that will ever be produced by a</span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">process.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality assurance is sometimes called quality control over quality control because it evaluates whether quality control is working.</span><span class="Apple-style-span" style="font-size: small;"><o:p></o:p></span></span></p> <p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height: normal;mso-layout-grid-align:none;text-autospace:none"><span><span class="Apple-style-span" style="white-space: pre;"><span class="Apple-style-span" style="font-size: small;"> </span></span><span class="Apple-style-span" style="font-size: small;">• Quality assurance personnel should never perform quality control unless it is to validate quality control.</span></span></p></div><div><br /></div><div><br /></div><div><span class="Apple-style-span" style="font-size: x-small;">Reference: CSTE CBOK v6.2</span></div>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-87430826356319609152009-07-06T22:36:00.000-07:002009-07-06T22:37:17.307-07:00My idea of this.............My idea of this blog is to publish the knowledge of QA that I gathered thorough my leanings and experience to anyone who is interested. Further I’m planning to add articles of new concepts in Quality Assurance/Quality Control.Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0tag:blogger.com,1999:blog-4149100113423778780.post-8735587884935707182009-07-06T22:27:00.000-07:002009-07-20T23:13:55.656-07:00Vocabulary in Software TestingWhat is Quality<br /><br />A product is a quality product if it is defect free. To the producer, a product is a quality product if it meets or conforms to the statement of requirements that defines the product. This statement is usually shortened to: quality means meets requirements. From a customer’s perspective, quality means “fit for use.”<br /><br /><br />What is Quality Assurance (QA)<br /><br />The set of support activities (including facilitation, training, measurement, and analysis) needed to provide adequate confidence that processes are established and continuously improved to produce products that meet specifications and are fit for use.<br /><br /><br />What is Quality Control (QC)<br /><br />The process by which product quality is compared with applicable standards, and the action taken when nonconformance is detected. Its focus is defect detection and removal. This is a line function; that is, the performance of these tasks is the responsibility of the people working within the process.<br /><br /><br /><span style="font-size:85%;"><span style="font-size:78%;">Reference: CSTE CBOK v6.2</span><br /></span>Janith Gunasekarahttp://www.blogger.com/profile/04026057208865436817noreply@blogger.com0