tag:blogger.com,1999:blog-56939247951566109002024-02-19T14:00:59.608+05:30Software Testing BankBlog with the solutions of software testing interview Questions Most Frequently Asked.....Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.comBlogger114125tag:blogger.com,1999:blog-5693924795156610900.post-82208455613436746362010-01-19T16:42:00.000+05:302010-01-19T16:42:05.772+05:30Driver Testing Tips<span style="font-size: x-small;"></span><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;"><strong>1. Introduction</strong><br />
As we know, Windows drivers can run and work in either user mode or kernel mode. <br />
Kernel-mode drivers run as part of the operating system and possess the privileged abilities. The drivers reviewed below are the drivers of kernel level. As any software testing procedure, driver testing includes automatic and manual testing, but in this article we will focus mainly on the last one. <br />
Later we will review testing process for the followings types of drivers:<br />
• File System Filter Drivers<br />
• Network Redirection Drivers<br />
• Virtual Storage Drivers<br />
• USB Client Device Drivers<br />
<strong>2. General aspects of driver testing </strong><br />
<strong>First of all</strong>, I would like to say ?Don?t install the driver to be tested on your working system!? However, there are some exceptions on this occasion, for example:<br />
• You are looking for a reason to reinstall your system...<br />
• You don?t want to waste time on searching bugs on the clean test systems...<br />
• You are sure that the driver is stable... <br />
• You have to test the work of the connected devices...<br />
<strong>Secondly,</strong> driver tester must have a virtual machine installed on the working computer and at least one real test computer.<br />
<strong>Thirdly, </strong>before starting the testing procedure, it is necessary:<br />
1. To define the number of operating systems for which it is necessary to check the driver functionality. Usually, first of all you use the OS confirmed by the specification. Let?s suppose that a driver must successfully work under Windows 2000/XP/Server 2003/Vista accordingly to the requirements. Applying our experience in driver testing, we extend this list to the following:<br />
• Windows 2000<br />
• Windows 2000 sp4<br />
• Windows XP_sp0<br />
• Windows XP_sp1<br />
• Windows XP_sp2<br />
• Windows XP_(Windows is installed on FAT32) (obligatory system)<br />
• Windows Server 2003 Standard Edition <br />
• Windows Server 2003 Enterprise Edition<br />
• Windows Vista<br />
<strong>Additionally:</strong><br />
• Windows Server 2003 Small Business<br />
• Windows Server 2003 Enterprise EditionSp1<br />
At that, it is desirable for all of these systems to be Checked Build versions. Using the Checked version slows down Windows functioning, but multiplies probability of finding bug in the driver functioning. If there is no a single Checked Windows, it is necessary to purchase the Checked version of at least one system, for example from the Windows XP series.<br />
Thus Windows XP_Chk is added to the OS list. But you shouldn?t limit you work only to this list: the more the number of OS, under which driver passed the complete testing successfully, the better quality of product guaranteed. <br />
<strong>2. </strong>If possible, select test computers with as different hardware and configurations as possible. I recommend obligatory test on machines with single processor, single processor with Hyper-Threading, two-core processor and dual processor machines. <br />
<strong>3. </strong>To make the following settings for each OS where driver testing will be performed: in System Properties\Advanced\Startup and Recovery Settings\Write debugging information it?s necessary to select Kernel memory dump or Complete memory dump, and uncheck Automatically restart option for the case of you won?t be nearby in the moment of Blue Screen appearance. <br />
<strong>4. </strong>To set verification by standard Driver Verifier Manager of the system with all options, except for Low resource simulation. This is determined by the fact that at first you must obtain stable functioning of driver without the option of Low resource simulation, and then test the functioning with this option on smoke tests.<br />
<strong>5. </strong>To select antivirus software with which it is desirable to test the driver performance. Usually it?s recommended to take the most commonly used antivirus programs, such as DrWeb, Kaspersky Antivirus, V3, Symantec Norton Antivirus, NOD32. The list is not limited to these names, of course. The more programs you will test, the better driver performance will be; this will only increase the quality of product.<br />
<strong>6. </strong>To verify compatibility of your driver with other drivers, the system ones and the drivers by other producers. It is desirable for the last ones to be stable enough ? in this case it will be easier for you to discover reasons for improper work of the system or Blue Screen appearance, and to expose bugs in driver performance. <br />
The next general aspect of driver testing is verification of driver loading and unloading, i.e. you set the group of tests that are relevant to each driver:<br />
<strong>1. Driver installation.</strong> The script for driver installation can be written by programmer, but the tester verifies whether it?s done correctly. Here we check the following: <br />
a. Has the system crashed after driver installation or not?<br />
b. Has *.sys file been written in the C:\WINDOWS\system32\drivers directory?<br />
c. Have necessary keys been registered in Registry, if they are presented in our case?<br />
The driver installation not always supposes its start - it depends on implementation of driver. Some of them run after system restart and cannot be stopped during the process of work (usually these are File System Filter Drivers), therefore the following questions arise:<br />
d. Does system start correctly with installed driver?<br />
e. Does system crash when the driver is started manually? <br />
<strong>2. System Restart while the driver is working.</strong> System must be normally rebooted without Blue Screen; after system start, the driver and its settings must comply with the statuses described in the specification.<br />
<strong>3. System Reset while the driver is working.</strong> System must perform the Reset operation and start without Blue Screen; after system start the driver and its settings must comply with the statuses described in the specification.<br />
<strong>4. System shutdown while the driver is functioning.</strong> System must perform the Shut down operation successfully without Blue Screen.<br />
<strong>5. System Start with the pre-installed driver.</strong> System must be rebooted without Blue Screen; after the system starts, the driver and its settings must comply with the statuses described in the specification.<br />
Further work of driver tester includes functional testing of the testing object and search of BSOD, which features depend on the type of testing driver. <br />
<span style="text-decoration: underline;"><strong>3. File System Filter Drivers Testing</strong></span><br />
The drivers of this type are designed for enhancement of the file system functionality, for example for catching operations of OS in order to watch, forbid or permit certain processes, operations, files in certain disk space. The set of tests to verify the driver functionality is formed in accordance with the type of driver and here you have to pay special attention to the software products workings with network places.<br />
Let?s consider an example when we use a database with the multi-users connection status. Let?s suppose that the real multi-users DB1 is on the computer N1 and we can work with DB1 on the computer N2 without problems. Let?s install some File System Filter Driver on the computer N1 and computer N2. When trying to get access to DB1 from the computer N2 we can get such results:<br />
• DB1 on the computer N1 is not accessible for the computer N2;<br />
• N1 computer has crashed with BSOD;<br />
• N2 computer has crashed with BSOD; <br />
• DB1 remained accessible for using on the computer N2.<br />
It is necessary to test an access to Shared Folders from one machine to another. Thus you have to test standard operations of creation, deleting, copying, renaming, moving of small and large folders and files in Shared Folders.<br />
An insidious test is the starting of some *.exe file both from network space and locally. <br />
On the test system, it?s useful to run software products which perform file system indexing (for example, Google Desktop). BSOD or Dead Lock of system with installed File System Filter Driver can occur when such programs are started or functioning.<br />
System can work inadequately after installation of new Virtual Storage Driver (these drivers are developed for creation of virtual encrypted disks) or while it?s functioning. BSOD or noticeable slow down in system performance can happen as a result of File System Filter Driver and Virtual Storage Driver interaction ? naturally, it?s not good.<br />
In my opinion, this type of drivers is the hardest from the view of covering full set of tests, and the most unforeseeable in system crashes while driver is functioning. <br />
<span style="text-decoration: underline;"><strong>4. Network Redirection Drivers Testing</strong></span><br />
Network Redirection Driver is a network file system which gives access to the resources of remote computer. In practice, such drivers are used for creation of network disks, and we will examine such drivers in this paragraph. <br />
First of all, it?s necessary to select test data, so we will take:<br />
• Files and folders of small size (to 10?b);<br />
• Files and folders of large size(more than 600?b);<br />
• Folders containing some nested files and folders (one folder for one file);<br />
• Folders containing a great number of nested files and folders (nesting is equal to 5; the number of files (size to 1?) is more than 100 in each folder).<br />
In this case main tests are divided into the followings groups:<br />
<strong>Group #1</strong> is "Verification of network disk displaying". After connecting network disk that is implemented on the base of Network Redirection Driver, this disk must be displayed in all of the file managers.<br />
<strong>Group #2</strong> is "Verification of functionality"<br />
1. Testing the standard operations (opening, change, hiding, creation, deleting and other) with files and folders on a network disk.<br />
2. Testing the operations of copying, saving files and folders to/from a network disk from/to a local disk. It?s necessary to pay special attention to all of applications included in MSOffice package, MindManager and also to verify saving project of MS Visial Studio from local space to a network disk and compiling this project.<br />
3. Testing the operations of copying when size of copied files is changed and also when an operation of copying/saving files is interrupted incorrectly.<br />
4. Testing software product on the different language versions of OS, for example under English and Korean OS, and performing tests from the first three points of Group #2. The driver must automatically pick up the language of the system and successfully perform all available operations with files and folders. <br />
5. Testing search function on a network disk.<br />
6. Checking the data integrity when moving them from a local disk to a network one and vice versa.<br />
<strong>Group #3</strong> is "Verification of data exchange speed"<br />
1. Testing speed on every set from the group of test data when downloading to Network Disk from Local Disk.<br />
2. Testing speed on every set from the group of test data when unloading from Network Disk to Local Disk.<br />
At that, it is necessary to take into account the capabilities of data transfer over the local network and capabilities of network protocols both with data cashing and without it. If you can get an analogue product, then compare its speed with the speed of your product.<br />
<strong>Group #4</strong> is "Disconnect"<br />
1. Checking the reaction of the system to disconnecting the network cable with the network disk connected: <br />
a. during uploading of each set from the group of test data;<br />
b. during downloading of each set from the group of test data.<br />
2. Testing the reconnect of network disk after plugging connecting network cable to the computer.<br />
<strong>Group #5</strong> is "Users sessions"<br />
1. Testing network disk performance for different users in the terminal session of Windows Server2003.<br />
2. Testing network disk performance for different users with Switch option on Windows XP.<br />
3. Testing network disk performance for different users with Login switching on Windows Server2003.<br />
5. Virtual Storage Drivers Testing<br />
Virtual Storage Driver is virtual data storage (for example, it can use random-access memory or file). Usually it is used for implementation of virtual encrypted disks. <br />
<strong>Main points when testing this type of drivers are:</strong><br />
1. Standard operations (opening, change, hiding, creation, deleting and other) over files and folders on a virtual disk.<br />
2. Creation of image of maximum possible size; its formatting.<br />
3. Data safety when working with different encrypting algorithms. <br />
4. Driver speed (reading ? writing to/from a virtual disk).<br />
5. Place of images localization (USB memory, Network Disk, Local Disk) and ability to access it.<br />
6. Data integrity on repeated connection of image after incorrectly disabled access to image had happened. <br />
<span style="text-decoration: underline;"><strong>6. USB Client Device Drivers Testing</strong></span><br />
USB Client Device Driver manages USB device, interacts with it by means of USB packages (URB), for example, for redirecting requests to another computer. The real USB devices are always involved in testing of such drivers; therefore the critical errors occur mostly during interaction between the driver that is tested and devices? drivers. For example, BSOD can happen on a computer with USB Client Device Driver installed when the following actions are performed:<br />
a. connecting new USB device;<br />
b. correct removing of USB device;<br />
c. incorrect removing of USB device;<br />
d. installing drivers for USB devices;<br />
e. working with USB device.<br />
<strong>7. Conclusion</strong><br />
Remember that correctly chosen set of tests for the certain type of driver helps your to improve the quality of your product.</span><br />
</div>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-73664745359833243362010-01-14T11:34:00.000+05:302010-01-14T11:34:31.185+05:30Try Beta Testing !<span style="font-family: Verdana,sans-serif; font-size: x-small;"></span><div class="F_Mid" style="font-family: Verdana,sans-serif;"><span style="color: black; font-size: x-small;"><strong><u>What is a beta testing?</u></strong></span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;">A Beta test is a testing done for a piece of computer product prior to commercial release in the market. Beta testing can be considered the last stage of testing, and normally can involve sending the product to beta test sites outside the company for real-world exposure. Normally, a free trial version of the product is allowed to be downloaded over the Internet. Beta test versions of software are distributed to a wide range of users to get the software tested in different combination of hardware and associated software.</span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;"> </span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;"><strong><u>What is in for a fresher or freelancer?</u></strong></span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;">So what should we do as a fresher or a freelance software tester? Beta testing provides a platform for us to test some real world software. There are many companies which release beta version of their software before they ship it to the market for commercial selling. </span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;"> </span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;">By signing up as a beta tester and downloading a test version of the software, you can get a first hand preview of the software. It is an exciting experience to get the software free of cost before the world gets to see the product. If you can find few bugs or write some reviews (positive or negative) about the beta version of the software, most of the companies give a free licensed version of the product when they release in the market. </span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;"> </span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;"><strong><u>Benefits of beta testing to a fresher?</u></strong></span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;">Also as a fresher, you can show this experience of testing a beta product. You can list down what all defects or bugs you have submitted to the company. There are few companies which I know who pay for finding bugs in there products. Your resume will shine if you can prove that you earned few dollars by finding bugs for this and that company. </span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;"> </span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;"> </span></div><div style="font-family: Verdana,sans-serif;"><span style="font-size: x-small;"> </span></div><div style="font-family: Verdana,sans-serif;"><div><span style="font-size: x-small;"><img src="http://ajoysingha.info/images/utest.JPG" style="float: left; margin: 0px 10px 10px 0px;" /></span> <div class="F_Mid" id="ServicePage_Title2"><span style="font-size: x-small;"><b>uTest.com</b></span></div><hr style="height: 1px;" /><div id="ServicePage_MissionStatement"><span style="font-size: x-small;">Sign Up with <strong>uTest.com</strong> and get paid for finding bugs. I am sure there are lots of other companies which pay for pointing out their defects. </span><div style="clear: both;"><span style="font-size: x-small;"> </span></div></div></div><div class="F_Mid"><span style="font-size: x-small;"><b><img src="http://ajoysingha.info/images/microsoft%20logo.jpg" style="float: left; height: 85px; margin: 12px 12px 12px 0px; width: 207px;" /></b></span></div><div class="F_Mid"><span style="font-size: x-small;"> </span></div><div class="F_Mid"><span style="font-size: x-small;"><b>Beta products from Microsoft</b></span></div><hr style="height: 1px;" /><div id="ServicePage_MissionStatement1"><span style="font-size: x-small;">Microsoft also provides wide range of Beta software for testing. Sign up with them and start testing a free beta product today. </span></div><div><span style="font-size: x-small;"> </span></div><div><span style="font-size: x-small;"> </span></div><div><span style="font-size: x-small;"> </span></div><div><span style="font-size: x-small;"><strong>Here are some tips for running a Beta Test </strong> </span></div><ul><li><div><span style="font-size: x-small;">Take back up of your PC before you install a Beta version software. You never know when the software crashes.</span></div></li>
<li><div><span style="font-size: x-small;">Read the terms and conditions carefully. Find out which bugs have already been reported. You don’t want to waste time finding bugs which someone has already reported.</span></div></li>
<li><div><span style="font-size: x-small;">Get the specification or requirement document first. How do you test a product if you don’t know what it is supposed to do?</span></div></li>
<li><div><span style="font-size: x-small;">Create a network of Beta Testers. This will help you get informed of latest happenings around the world.</span></div></li>
</ul><span style="font-size: x-small;"><br />
</span></div>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com1tag:blogger.com,1999:blog-5693924795156610900.post-11608245046813670482010-01-13T12:01:00.003+05:302010-02-18T18:44:19.857+05:30Software Testing Resume - How to write the best resume for software testing.<div id="PressRelease_SampleRelease1Date"><b>10 Best Guidelines for a Good Resume -</b></div><span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span> </span></b></span></span></span>Do not write the word 'Resume', 'CV' etc on the top of the resume. Instead write your name in bold letters. You may include your mobile number and email id for ready reference.<br />
<span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span></span></b></span></span></span>Delete the career objective that you have copied from your friend's resume. Ask this to yourself – who does not want to work in a growth oriented company where he or she can utilize his or her skills to the fullest? Career object is just a waste of space and believe me, nobody reads that section. <br />
<span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span></span></b></span></span></span>Include a two liner summary about your experience, skills, tools etc. so that the person reading your resume can know about your profile in 10 seconds. <br />
<span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span></span></b></span></span></span>Remove all unnecessary information like father's name, hobbies, place of birth, schooling information etc. You will have enough time to give that information when you are selected.<br />
<span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span></span></b></span></span></span>Structure the content of the resume based on your past experience such as skills, projects, education etc.<br />
<span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span></span></b></span></span></span>Highlight your key skills and domain expertise. Talk about your USP and how you could add value to the organization that is recruiting you.<br />
<span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span></span></b></span></span></span>The purpose of a resume is to generate enough interest in you to have a prospective employer contact you for an interview. Don’t fill the resume with too much information. Nobody will read a resume for more than 2-3 pages at the max.<br />
<span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span></span></b></span></span></span>Use bullet points to convey information. Make information readily available to the recruiter. But be sure that whatever you have written in the resume, you will be able to explain it.<br />
<span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span></span></b></span></span></span>Use a single font throughout the resume (Garamond, 12pt – my favorite). Do not use too much underline, bold and highlight in the resume.<br />
<span style="color: #000066;"><span style="border-collapse: separate; color: black; font-family: 'Times New Roman'; font-size-adjust: none; font-size: 16px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span style="font-family: Verdana; font-size: 13px; text-align: left;"><b><span style="color: #00aa00; font-size: 180%;"><span style="color: #9999ff;">»</span></span></b></span></span></span>Get your resume reviewed by a friend or an expert. Take feedback and improve the resume. Use a good resume template suitable to your domain and update your resume frequently.Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-48830794145733369662010-01-12T15:29:00.000+05:302010-01-12T15:32:16.825+05:30ISTQB Preparation Guide<p style="font-family: verdana;"><span style="font-size:85%;color:#00ffff;"><span style="color:#aac1c9;"><span style="color:#558492;">ISTQB Preparation Guide</span></span></span></p><hr style="font-family: verdana; height: 2px;"><p style="font-family: verdana;"><span style="font-size:85%;color:#00ffff;"><span style="color:#aac1c9;"> </span></span></p><div style="font-family: verdana;"><span style="font-size:85%;"><strong><u><img src="http://ajoysingha.info/images/istqb%20logo.jpg" style="margin: 0px 10px 10px 0px; width: 122px; float: left; height: 96px;" />International Software Testing Qualification Board Exam Preparation Guide</u></strong> </span></div><div id="Home_Intro1" style="font-size: 16px; font-family: verdana;"><span style="font-size:85%;"><span><p align="left"> </p><p align="left">The ISTQB was officially founded as an International Testing Qualifications Board in Edinburgh in November 2002 and it is responsible for the "ISTQB Certified Tester", which is an international qualification scheme. ISTQB Certification is available in two stages, Foundation Level and Advanced Level. </p><p align="left">For details about ISTQB please visit <span style="color:#0000ff;"><span style="color:#0000ff;"><span style="color:#0000ff;"><span>www.istqb.org</span></span></span></span><span> </span></p></span></span><p align="left"><span style="font-size:85%;"><span> </span></span></p><p align="left"><span style="font-size:85%;"><span>Join ISTQB Exam Preparation <a href="http://www.orkut.co.in/Main#Community.aspx?cmm=92880393" target="_blank">Orkut Community</a>. You will find lots of information there.</span></span></p><hr style="height: 2px;"><p><span style="font-size:85%;"><strong>Remember</strong> - "<em>Certification exams do not measure the quality of a tester. Until they do, they merely facilitate discriminatory hiring practices." - </em><i><i><u><span style="color:#0000ff;">James Bach</span></u></i></i></span></p></div><span style="font-size:85%;"><br /><br /></span><div style="font-family: verdana;" id="Home_Intro2"><p><span style="font-size:85%;"><strong>» <u>which book to read for ISTQB Certification ?</u></strong></span></p><p><span style="font-size:85%;"> </span></p><p><span style="font-size:85%;color:#0000e3;">Foundations Of Software Testing ISTQB Certification</span></p><p><span style="font-size:85%;"><em>By -</em></span></p><p><span style="font-size:85%;"><em>Dorothy Graham<br />Erik van Veenendaal<br />Isabel Evans<br />Rex Black</em></span></p><p><span style="font-size:85%;"><br /></span></p><p><span style="font-size:85%;"><strong>» <u>General Guidelines for Preparing ISTQB Exam</u></strong></span> </p><ul><li><span style="font-size:85%;"><span style="font-size:85%;">40 Questions </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">65% pass mark </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">90 minutes </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Multiple choice questions </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Only one correct answer </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">No negative marking </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Paper/Pen based exam. Darken the appropriate circle </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Not online </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">All questions from syllabus </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Read the syllabus very carefully </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Question breakup<strong> </strong></span></span></li><ul><li><span style="font-size:85%;"><span style="font-size:85%;">50% K1 (remember, recall type) </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">30% K2 (Compare, contrast type) </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">20% K3 (Analyze, apply type. Numerical type as well) </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">See syllabus for details on K levels</span></span></li></ul></ul></div><hr style="font-family: verdana; height: 2px;"><p style="font-family: verdana;"><span style="font-size:85%;"><span style="font-size:85%;"><strong><p align="left">» <u>Syllabus Breakup for ISTQB Preparation Material</u></p><p align="left"> </p><p align="left">The principles of testing </p></strong></span></span></p><p style="font-family: verdana;"><span style="font-size:85%;"><span style="font-size:85%;">Terminology; why testing is necessary; fundamental test process; psychology of testing; re-testing and regression testing; expected results; prioritization.<br /><br /><strong>Testing throughout the life-cycle</strong></span></span></p><p style="font-family: verdana;"><span style="font-size:85%;"><span style="font-size:85%;">Models for testing; economics of testing; high level test planning; acceptance testing; integration testing in the large; functional and non-functional system testing; integration testing in the small; component testing; maintenance testing.<br /><br /><strong>Static testing </strong></span></span></p><p style="font-family: verdana;" align="left"><span style="font-size:85%;"><span style="font-size:85%;">Reviews and the test process; types of review; static analysis.</span></span></p><p style="font-family: verdana;" align="left"><span style="font-size:85%;"><span style="font-size:85%;"> </span></span></p><p style="font-family: verdana;"><span style="font-size:85%;"><span style="font-size:85%;"><strong>Test design techniques<br /></strong>Dynamic testing techniques, Black and white-box testing techniques; error guessing, BVA etc.</span></span></p><p style="font-family: verdana;"><span style="font-size:85%;"><span style="font-size:85%;"> </span></span></p><p style="font-family: verdana;" align="left"><span style="font-size:85%;"><span style="font-size:85%;"><span style="font-size:85%;"><span><span class="Apple-style-span" style="widows: 2; text-transform: none; text-indent: 0px; border-collapse: separate; font-style: normal; font-variant: normal; font-weight: normal; font-size: 16px; line-height: normal; font-size-adjust: none; font-stretch: normal; white-space: normal; orphans: 2; letter-spacing: normal; color: rgb(0, 0, 0); word-spacing: 0px;"><span class="Apple-style-span" style="text-align: left; font-size: 13px;"><strong><br /></strong></span></span></span></span></span></span></p><p style="font-family: verdana;" align="left"><span style="font-size:85%;"><span style="font-size:85%;"><br /><strong>Test management </strong></span></span></p><p style="font-family: verdana;" align="left"><span style="font-size:85%;"><span style="font-size:85%;">Organization; configuration management; test estimation, monitoring and control; incident management; standards for testing.<br /><br /><strong>Tool support for testing</strong> </span></span></p><p style="font-family: verdana;" align="left"><span style="font-size:85%;"><span style="font-size:85%;">Types of CAST tool (Computer-Aided Software Testing); tool selection and implementation.</span></span></p><hr style="font-family: verdana; height: 2px;"><p style="font-family: verdana;" align="left"><span style="font-size:85%;"><span><span class="Apple-style-span" style="widows: 2; text-transform: none; text-indent: 0px; border-collapse: separate; font-style: normal; font-variant: normal; font-weight: normal; font-size: 16px; line-height: normal; font-size-adjust: none; font-stretch: normal; white-space: normal; orphans: 2; letter-spacing: normal; color: rgb(0, 0, 0); word-spacing: 0px;"><span class="Apple-style-span" style="text-align: left; font-size: 13px;"><strong><span style="color:#00aa00;">»</span></strong></span></span></span></span><span style="font-size:85%;"><span style="font-size:85%;">Join <strong><a href="http://www.orkut.co.in/Main#Community?cmm=92880393" target="_blank"><strong>ISTQB Exam Preparation Orkut Community</strong></a></strong>. You will lots of active discussions going on to clear your doubts.<br /></span></span></p><span style="font-size:85%;"><br /><br /><strong style="font-family: verdana;"><p><span style="color:#00aa00;">»</span> <u>Sample Paper Download</u></p></strong></span><p style="font-family: verdana;"><span style="font-size:85%;">Free Download </span><span style="font-size:85%;color:#ff0000;">2500</span><span style="font-size:85%;"> ISTQB Sample Papers. Click on the set to download.</span></p><p style="font-family: verdana;"><span style="font-size:85%;"><strong>»</strong> <a href="http://ajoysingha.info/Documents/www.ajoysingha.info_ISTQB-Question-Papers_Set1.zip"><b>Download </b><u><span style="color:#0000ff;"><strong>Set 1</strong></span></u></a><strong> </strong>(Collection of 16 Sample Papers) </span></p><span style="font-size:85%;"><strong style="font-family: verdana;">»</strong><span style="font-family: verdana;"> </span><a style="font-family: verdana;" href="http://ajoysingha.info/Documents/www.ajoysingha.info_ISTQB-Question-Papers_Set2.zip"><b>Download </b><u><span style="color:#0000ff;"><strong>Set 2</strong></span></u></a><strong style="font-family: verdana;"> </strong><span style="font-family: verdana;">(Collection of 12 Sample Papers)</span><br /><br /><br /></span><table style="border: 1px solid rgb(119, 119, 119); margin: 10px; font-family: verdana;" class="iws_table" cellpadding="8"><tbody><tr><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1"><span style="font-size:85%;"><span><p>Chapter</p></span></span></td><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1" align="center"><span style="font-size:85%;"><span><p align="center">Number of Questions Expected from each chapter</p></span></span></td></tr><tr><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1"><span style="font-size:85%;"><span><p>The principles of testing</p></span></span></td><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1" align="center"><span style="font-size:85%;">7</span></td></tr><tr><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1"><span style="font-size:85%;"><span><p>Testing throughout the life-cycle</p></span></span></td><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1" align="center"><span style="font-size:85%;">6</span></td></tr><tr><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1"><span style="font-size:85%;"><span><p>Static testing</p></span></span></td><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1" align="center"><span style="font-size:85%;">3</span></td></tr><tr><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1"><span style="font-size:85%;"><span><p>Test design techniques</p></span></span></td><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1" align="center"><span style="font-size:85%;">12</span></td></tr><tr><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1"><span style="font-size:85%;"><span><p>Test management</p></span></span></td><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1" align="center"><span style="font-size:85%;">8</span></td></tr><tr><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1"><span style="font-size:85%;"><span><p>Tool support for testing</p></span></span></td><td style="border: 1px solid rgb(119, 119, 119);" colspan="1" rowspan="1" align="center"><span style="font-size:85%;">4</span></td></tr></tbody></table><p style="font-family: verdana;"><span style="font-size:85%;"> </span></p><p style="font-family: verdana;"><span style="font-size:85%;"><strong>»</strong> <u><strong>Tips and Tricks</strong></u></span> </p><div style="font-family: verdana;"><ul><li><span style="font-size:85%;"><span style="font-size:85%;">ISTQB Questions are simple but answers are confusing at times. </span></span><span style="font-size:85%;"><span style="font-size:85%;">More than one correct answers possible. Choose the one which is more correct or correct in more scenarios. </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Read the questions very carefully. Sometimes you might miss important words. Solve ISTQB Sample Papers frequently.</span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Do not jump to answer quickly. Go through all options before selecting one. </span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Look out for words like ALL, EVERY, NEVER etc. These might help you choose correct answer. For example, ALL bugs should be fixed is incorrect statement but bugs should be fixed is more correct and might indicate right choice.</span></span></li><li><span style="font-size:85%;"><span style="font-size:85%;">Download ISTQB dumps and read the complete ISTQB syllabus.</span></span></li><li><span style="font-size:85%;">Check ISTQB exam dates for your country and prepare in advance.</span></li></ul></div><hr style="font-family: verdana; height: 2px;"><p style="font-family: verdana;"><span style="font-size:85%;"><strong>»</strong> <u><strong>ISTQB Advanced Level</strong></u></span> </p><p style="font-family: verdana;"><span style="font-size:85%;">Exam Guidelines and ISTQB Advanced Level sample papers will be added soon. Keep visiting this page for updates.</span></p><p style="font-family: verdana;"><span style="font-size:85%;"> </span></p><p style="font-family: verdana;" align="left"><span style="font-size:85%;"><strong>» <u>ISTQB Training Institute</u></strong></span></p><p style="font-family: verdana;" align="left"><span style="font-size:85%;">Are you interested in taking coaching for ISTQB exam? Learn from the <a href="http://ajoysingha.info/training.aspx">Best ISTQB training institute</a>. </span></p><span style="font-size:85%;"><br /></span>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-31401104581282483352009-12-25T21:42:00.000+05:302009-12-25T21:58:22.030+05:30Software Testing Levels<span style="font-size:85%;"><span style="font-family: verdana;">Test Level 1 : Unit Testing</span><br /><br /><span style="font-family: verdana;">In programming, unit testing is a software design and development method where the programmer to verify that the units of source code are working properly. A unit is the smallest testable part of an application. In the programming of a unit of May an individual program, function, procedure, etc, while in object-oriented programming, the smallest unit is a method, which belongs to May in a base / super class abstract class or derived / child class. </span><br /><span style="font-family: verdana;"> Ideally, each test case is independent of others; Double objects like stubs, mock objects or false and the test harness can be used to assist testing a module in isolation. Unit testing is usually done by software developers to ensure that the code of other developers have written meets software requirements and behaves as the developer intended. </span><br /><br /><strong style="font-family: verdana;">Benefits</strong><br /><span style="font-family: verdana;"> The objective of the test is to isolate each part of the program and show that the parts are correct. A unit test provides a strict, a written contract that the piece of code must satisfy. Accordingly, it offers several advantages. Unit testing problems early in the development cycle. </span><br /><span style="font-family: verdana;"> * Unit testing allows the programmer to Refactor code at a later date, and make sure the module still works correctly (ie regression testing). The procedure is to write test cases for all functions and methods so that whenever a change causes a fault, it can be quickly identified and corrected. </span><br /><span style="font-family: verdana;"> * Readily available, unit tests make it easy for the programmer to check whether a piece of code works properly. Good product unit test design test cases that cover all paths of the unit carefully the conditions for a loop. </span><br /><span style="font-family: verdana;"> * In continuous unit testing environments, through the practice of maintaining inherent maintenance, unit tests will continue to accurately reflect the use of executable code from the face of change. According to the development practices in place and unit test coverage, the second of accuracy can be maintained. </span><br /><span style="font-family: verdana;"> * It helps eliminate uncertainty in the units themselves and can be used in a bottom-up testing style approach. By testing the parts of a program first, then testing the sum of its parts, integration testing is much easier. </span><br /><span style="font-family: verdana;"> * A widely debated question is in assessing the need for manual integration. While developing a hierarchy of unit tests in May appears to have achieved integration testing, which is a false sense of confidence since integration testing evaluates many other goals that can only be proved by the human factor. Some argue that a sufficient variety of test automation systems, integration of man by a group test is unnecessary. In fact, the real need ultimately depends on the characteristics of the product under development and its uses. In addition, the manual of the man or the test will depend largely on the availability of resources. </span><br /><span style="font-family: verdana;"> * It provides a way of life of the system documentation. Developers who want to know what functionality is provided by a unit and how the user can view the unit tests to gain a basic understanding of the unity of the API. </span><br /><span style="font-family: verdana;"> * Unit test cases embody characteristics that are essential to the success of the unit. These characteristics can indicate appropriate / inappropriate to use a unit as well as negative behaviors that must be trapped by the device. A unit test in itself, the essential characteristics of these documents, although many software development environments do not rely solely on the code of the document produced in development. </span><br /><span style="font-family: verdana;"> * On the other hand, documentation ordinary story is more sensitive to the drift of the implementation of the program and will become outdated (eg design changes, feature creep, relaxed practices for keeping documents up-to -date). </span><br /><strong style="font-family: verdana;">Limitations of tests</strong><br /><span style="font-family: verdana;"> Tests can not be taken for each error in the program - it is impossible to evaluate all execution paths, for all but the most trivial programs. The same is true for unit testing. Furthermore, by definition, the unit tests that test the functionality of the units themselves. Therefore, it will not catch integration errors, or larger system-level errors (such as functions performed in multiple units, or non-functional testing areas such as performance). Unit testing is more effective when used in conjunction with other test software. Like all forms of software testing, unit testing can not show the presence of errors, it can not demonstrate the absence of errors. </span><br /><span style="font-family: verdana;"> Software testing is a combinatorial problem. For example, each boolean decision statement requires at least two tests: one with a result of the "real" and the other with a score of "false". Accordingly, for each line of code written, programmers often need 3 to 5 lines of test code. </span><br /><span style="font-family: verdana;"> To obtain the benefits of unit testing, a sense of discipline is needed throughout the software development process. It is essential to keep careful records, not only tests have been performed, but also of all the changes that were made to the source code of this unit or any other in the software. Using a version control system is essential. If a newer version of the unit is not a test it had previously adopted, the version control software can provide a list of changes to source code (if any) that have been applied to the unit since that time. </span><br /><span style="font-family: verdana;"> It is also essential to implement a sustainable process to ensure that the test failures are reviewed daily and processed immediately. If such a process is not implemented and ingrained into the team, the application will evolve in sync with the unit test suite - more and more false positives and reduce the effectiveness of the test suite. </span><br /><br /><br /><span style="font-family: verdana;">Test Level 2 : Integration Testing</span><br /><br /></span> <p style="font-family: verdana;"><span style="font-size:85%;">"Integration test" (sometimes called Integration and Testing, abbreviated I & T) is the phase of software testing in various software modules that are combined and tested as a group. It follows unit testing and precedes the test system. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">Tests of integration as input modules that have been unit tested, groups larger aggregates, applies tests defined in a test plan for integration of these aggregates, and delivers its output data ready for integrated system testing.</span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Purpose </strong><br />The purpose of integration is to verify the functional tests, performance and reliability on the major design requirements of the articles. These "design objects", ie sets (or groups of units) shall be exercised through their black box using test interfaces, success and error cases simulated by appropriate parameter and data entry. Simulation of the use of shared data and areas of inter-process communication is tested and subsystems are exercised through their input interface. Test cases are constructed to verify that all components within assemblages interact correctly, for example through procedure calls or process activations, and this is done after the test individual modules, that is to say the unit tests. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">The general idea is a "building block" in the check assemblies that are added to a basic check, which is then used to support the integration of new test assemblies. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">Some types of integration tests are big bang, top-down and bottom-up. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Big Bang</strong><br />In this approach, all or most of the developed modules are combined to form a software system or a significant part of the system and then used for integration tests. The Big Bang is very effective method to save time in the integration testing process. However, if the test cases and their results are not properly registered, the whole process of integration will be more complex and prevent the May testing team to achieve the goal of integration. </span> </p> <p style="font-family: verdana;"><span style="font-size:85%;">A type of "Big Bang" integration tests is called usage model testing. Usage type of test can be used in software and hardware integration. The basis of this type of integration is to launch the user tests, as the workload of the user included in similar environments. By testing in this way, the environment is the test, while the individual components are proofed indirectly through their use. Usage type of test has a optimistic approach to the test, because it expects to have some problems with individual components. The strategy relies heavily on the developers of individual components to the test unit for their products. The objective of this strategy is to avoid repeating the tests carried out by developers, and instead of flesh on the problems caused by the interaction of components in the environment. For integration tests, the tests use type can be more efficient and provides better test coverage focused more traditional functional testing. To be more efficient and accurate, care must be used in the definition of the user, as the workload to create realistic scenarios in the exercise of the environment. This gives the integrated environment works as expected for the target audience. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><br /><strong>Bottom Up and Top Down</strong><br />There are two types of integration. </span> </p> <p style="font-family: verdana;"><span style="font-size:85%;">1. Bottom Up </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">2. Top Down. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><br /><strong>Bottom-Up Testing:</strong> An approach to integration testing where the lowest level components are tested first, and then used to facilitate testing of components at a higher level. The process is repeated until the element at the top of the hierarchy is tested. </span> </p> <p style="font-family: verdana;"><span style="font-size:85%;">All low or low-level modules, procedures or functions are integrated and tested. After the integration of lower level tests integrated modules, the next level of modules will be trained and can be used for integration tests. This approach is useful only when all or most of the modules of the same level of development loans. This method also allows to determine the levels of software and it is easier to report the progress of testing as a percentage. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Top Down</strong> is the procedure where the top integrated modules are tested and part of module testing, step by step, until the end of the relationship with the module. The main advantage of the database is easy to find bugs. Top to bottom, it is easy to find the missing link branch. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Limitations </strong><br />Any condition not specified in integration tests, apart from the confirmation of the execution of the design items are usually not tested.</span></p><span style="font-size:85%;"><br /><br /><span style="font-family: verdana;">Testing Level 3 : System testing</span><br /><br /><br /></span><p style="font-family: verdana;"><span style="font-size:85%;">System testing of software or hardware testing is performed on an integrated system to verify and assess the system with its requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the interior design of the code or logic. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">In general, the test system has, as its entry, all the "integrated" software components that have successfully passed the integration tests and the software itself incorporated into any applicable hardware system (s). Test system is a limiting type of testing, it seeks to detect defects both within the inter-assemblages "and also in the system as a whole. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">System testing is performed throughout the system as part of a functional specification (s) (FRS) and / or a System Requirement Specification (SRS). Test system is a phase of inquiry, where the emphasis is to have almost a destructive attitude and test not only the design but also the behavior and believed the same expectations. It is also intended to test and beyond the limits defined in the hardware / software specification (s). Test system includes load testing and stress testing. Once the load testing and stress tests are completed successfully, the next level of Alpha or Beta Testing Testing will proceed. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Types of system testing</strong></span> </p> <p style="font-family: verdana;"><span style="font-size:85%;">The following examples are the different types of tests that should be considered during the system test: </span></p> <ul style="font-family: verdana;"><li><span style="font-size:85%;">GUI software testing </span></li><li><span style="font-size:85%;">Usability testing </span></li><li><span style="font-size:85%;">Benchmarks </span></li><li><span style="font-size:85%;">Compatibility tests </span></li><li><span style="font-size:85%;">Error handling test </span></li><li><span style="font-size:85%;">Load test </span></li><li><span style="font-size:85%;">Volume test </span></li><li><span style="font-size:85%;">Stress tests </span></li><li><span style="font-size:85%;">Help for usability testing </span></li><li><span style="font-size:85%;">Testing for safety </span></li><li><span style="font-size:85%;">Scalability tests </span></li><li><span style="font-size:85%;">Capacity test </span></li><li><span style="font-size:85%;">Sanity testing </span></li><li><span style="font-size:85%;">Smoke tests </span></li><li><span style="font-size:85%;">Test </span></li><li><span style="font-size:85%;">Ad hoc tests </span></li><li><span style="font-size:85%;">Regression testing </span></li><li><span style="font-size:85%;">Reliability testing </span></li><li><span style="font-size:85%;">Recovery test </span></li><li><span style="font-size:85%;">Test facility </span></li><li><span style="font-size:85%;">Maintenance Test </span></li><li><span style="font-size:85%;">Accessibility tests</span></li></ul><span style="font-size:85%;"><br /><br /><span style="font-family: verdana;">Tsting Level 4 : System Integration Test</span><br /><br /><br /></span><p style="font-family: verdana;" dir="ltr"><span style="font-size:85%;">System Integration Test (SIT) in the context of systems and software<br /><br />engineering, is a testing process that exercises a software system coexistence with others. The integration of the system has multiple test systems that have made the system tests, tests for entry and their necessary interaction. After this process, the Deliverables are submitted to acceptance testing. </span> </p> <p style="font-family: verdana;" dir="ltr"><span style="font-size:85%;">System integration testing (SIT) is a testing phase occurs after the unit tests and<br /><br />prior to testing user acceptance (UAT). </span> </p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Some of the Features of SIT:</strong><br />System Integration Test (SIT) is the testing of the subsystems as a whole, to ensure that they function as a system. <br />The test should be guided by the requirement of the specification and system integration (SI) of the engineer's knowledge that the system should do. <br />No requirement to define the specifications of a system fully, they will always be gaps in what the requirement of the specification says and what is expected of a system. <br />This is where the experience of the engineer SI comes into play, because he / she carries out his work they need to keep your eyes open for any defects or problems. If the engineer must be aware that defects will be present, which there is through informal testing, ie the operating system and see what happens. <br />The SIT should ensure that the system meets the requirements of the specification of the formal and any implied or "common sense" requirements are met. <br />S.I.T. should also take place in different environments, for example, different temperatures. This should not be anything fancy, for example, a full environmental tests, but can be as little as possible of the airflow down, or a little, by turning the laboratory or thermostat down a little, it is amazing how small changes in the environment can affect the performance of a system.</span></p><!-- JOM COMMENT START --> <!-- Sharing toolbar --> <span style="font-size:85%;"><br /><br /><span style="font-family: verdana;">Testing Level 5 : Acceptance Testing</span><br /><br /><br /></span><p style="font-family: verdana;"><span style="font-size:85%;">In engineering and its various subdisciplines, acceptance testing is black-box testing of a system (eg software, lots of manufacture of mechanical parts, or batches of chemical products) prior to its delivery. In others, it is known that functional testing, black box testing, release acceptance, testing, quality assurance, application testing, confidence testing, testing, validation, testing of acceptance or factory. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">In software development, acceptance testing by the supplier of the system is often distinguished from acceptance testing by the customer (the user or the client) before accepting the transfer of ownership. In such environments, the trials to acceptance by the customer is known as the test user acceptance (UAT). This is also known as end-user testing, the site (acceptance) test or field (acceptance) testing. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Overview </strong><br />Acceptance testing generally involves running a series of tests on the completed system. Each test, known as cases, exercises a state of operation of the user's environment or feature of the system and will result in a pass or fail boolean outcome. There is generally no degrees of success or failure. The test environment is usually designed to be identical or as close as possible, provided the user to the environment, including such extremes. These test cases must each be accompanied by test case input data or a formal description of operational activities (or both) to achieve, to thoroughly exercise the specific case and a description of the results. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">Acceptance Tests / Criterion (in Agile Software Development) are usually created by customers and expressed in a business language. These are high-level tests to test the compliance of a story or user stories "played" during any sprint / iteration. These tests are created preferably through collaboration between customers, business analysts, testers and developers, but business customers (product owners) are the primary owners of these tests. When the user passes the stories of their acceptance criteria, business owners can be sure that the developers are progressing in the right direction on how the application was intended to work and it is therefore essential that These tests include tests of logic, and interface elements of validation (if required). </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">Acceptance of test cards are perfectly created during sprint planning and iteration planning meeting, before the development so that developers have a clear idea of what to develop. Sometimes (because of poor planning) tests in May of multiple stories (that are not implemented in the same sprint) and there are different ways to test them during the sprint. A popular technique is to mock external interfaces or data to mimick other stories that could not be played during an iteration (as these stories May were relatively lower priority). A history of the user is not considered complete until the acceptance tests have passed. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Process </strong><br />Following acceptance test is directed against the entry of data or by using a test script to direct acceptance testers. Then, the results are compared with the results. If there is a good match for all cases, the test suite is said to pass. If not, the system May be either accepted or rejected in conditions previously agreed between the developer and builder. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">The aim is to give confidence that the system of record of meeting the needs of both authors and users. The acceptance phase May also act as a gateway to the quality, where no quality defects to be detected in May uncovered. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;">A main goal of acceptance testing is that, once successfully completed, and provided that certain other (contract) are met acceptance criteria, the authors then sign on the system as satisfying the contract ( prior agreement between developer and manufacturer), and deliver final payment. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Types of acceptance testing</strong><br />The types of acceptance testing are </span> </p> <p style="font-family: verdana;"><span style="font-size:85%;"><strong>Acceptance testing by the user</strong><br />This May include acceptance testing at the factory, ie the testing facility by users before the plant is moved to its own site, after which the site acceptance testing be performed in May by users on the site.<br /><strong>Operational acceptance testing</strong><br />Also known as operational readiness test, it is the de facto control to a system to ensure that processes and procedures are in place to allow the system to be used and maintained. This May include controls to safeguard the facilities, procedures for disaster recovery, training for end users, maintenance procedures and safety procedures.<br /><strong>Contract and regulation acceptance testing</strong><br />Contract acceptance testing, a system is tested against the criteria for acceptance as a contract, before the system is accepted. In regulation acceptance testing, a system is tested to ensure it meets governmental, legal and safety standards.<br /><strong>Alpha and beta test</strong><br />Alpha testing is carried out at site developers, and testing of the operating system by the staff before it is delivered to external customers. Beta testing is done to clients sites, and testing by a group of customers who use the system to their own sites and feedback before the system is handed over to other customers. This is often called the "field testing".</span> </p><p style="font-family: verdana;"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;"><span style="font-size:85%;"><br /></span></p><span style="font-size:85%;"><br /></span>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-37324275618875843742009-09-04T11:14:00.000+05:302009-09-04T11:53:09.369+05:30Software QA and Testing Frequently-Asked-Questions<p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_1"><b> What makes a good Software Test engineer? </b></a><br />A good test engineer has a 'test to break' attitude, an ability to take the point of view of the customer, a strong desire for quality, and an attention to detail. Tact and diplomacy are useful in maintaining a cooperative relationship with developers, and an ability to communicate with both technical (developers) and non-technical (customers, management) people is useful. Previous software development experience can be helpful as it provides a deeper understanding of the software development process, gives the tester an appreciation for the developers' point of view, and reduce the learning curve in automated test tool programming. Judgement skills are needed to assess high-risk or critical areas of an application on which to focus testing efforts when time is limited. </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_2"><b> What makes a good Software QA engineer? </b></a><br />The same qualities a good tester has are useful for a QA engineer. Additionally, they must be able to understand the entire software development process and how it can fit into the business approach and goals of the organization. Communication skills and the ability to understand various sides of issues are important. In organizations in the early stages of implementing QA processes, patience and diplomacy are especially needed. An ability to find problems as well as to see 'what's missing' is important for inspections and reviews. </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_3"><b> What makes a good QA or Test manager? </b></a><br />A good QA, test, or QA/Test(combined) manager should: </span></p> <ul style="font-family:verdana;"><li><span style="font-size:85%;">be familiar with the software development process</span></li><li><span style="font-size:85%;">be able to maintain enthusiasm of their team and promote a positive atmosphere, despite what is a somewhat 'negative' process (e.g., looking for or preventing problems)</span></li><li><span style="font-size:85%;">be able to promote teamwork to increase productivity</span></li><li><span style="font-size:85%;">be able to promote cooperation between software, test, and QA engineers</span></li><li><span style="font-size:85%;">have the diplomatic skills needed to promote improvements in QA processes</span></li><li><span style="font-size:85%;">have the ability to withstand pressures and say 'no' to other managers when quality is insufficient or QA processes are not being adhered to</span></li><li><span style="font-size:85%;">have people judgement skills for hiring and keeping skilled personnel</span></li><li><span style="font-size:85%;">be able to communicate with technical and non-technical people, engineers, managers, and customers.</span></li><li><span style="font-size:85%;">be able to run meetings and keep them focused</span></li></ul> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_4"><b> What's the role of documentation in QA? </b></a><br />Generally, the larger the team/organization, the more useful it will be to stress documentation, in order to manage and communicate more efficiently. (Note that documentation may be electronic, not necessarily in printable form, and may be embedded in code comments, may be embodied in well-written test cases, user stories, etc.) QA practices may be documented to enhance their repeatability. Specifications, designs, business rules, configurations, code changes, test plans, test cases, bug reports, user manuals, etc. may be documented in some form. There would ideally be a system for easily finding and obtaining information and determining what documentation will have a particular piece of information. Change management for documentation can be used where appropriate. For agile software projects, it should be kept in mind that one of the agile values is "Working software over comprehensive documentation", which does not mean 'no' documentation. Agile projects tend to stress the short term view of project needs; documentation often becomes more important in a project's long-term context. </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_5"><b> What's the big deal about 'requirements'? </b></a><br />One of the most reliable methods of ensuring problems, or failure, in a large, complex software project is to have poorly documented requirements specifications. (Note that requirements documentation can be electronic, not necessarily in the form of printable documents, and may be embedded in code comments, may be embodied in well-written test cases, etc.) Requirements are the details describing an application's externally-perceived functionality and properties. Requirements should be clear, complete, reasonably detailed, cohesive, attainable, and testable. A non-testable requirement would be, for example, 'user-friendly' (too subjective). A more testable requirement would be something like 'the user must enter their previously-assigned password to access the application'. Determining and organizing requirements details in a useful and efficient way can be a difficult effort; different methods are available depending on the particular project. Many books are available that describe various approaches to this task. (See the section's 'Software Requirements Engineering' category for books on Software Requirements.) </span></p> <p style="font-family:verdana;"><span style="font-size:85%;"> Care should be taken to involve ALL of a project's significant 'customers' in the requirements process. 'Customers' could be in-house personnel or outside personnel, and could include end-users, customer acceptance testers, customer contract officers, customer management, future software maintenance engineers, salespeople, etc. Anyone who could later derail the project if their expectations aren't met should be included if possible. </span></p> <p style="font-family:verdana;"><span style="font-size:85%;"> Organizations vary considerably in their handling of requirements specifications. Often the requirements are spelled out in a document with statements such as 'The product shall.....'. 'Design' specifications should not be confused with 'requirements'; design specifications are ideally traceable back to the requirements. </span></p> <p style="font-family:verdana;"><span style="font-size:85%;"> In some organizations requirements may end up in high level project plans, functional specification documents, in design documents, or in other documents at various levels of detail. No matter what they are called, some type of documentation with detailed requirements will be needed by testers in order to properly plan and execute tests. Without such documentation, there will be no clear-cut way to determine if a software application is performing correctly. </span></p> <p style="font-family:verdana;"><span style="font-size:85%;"> 'Agile' approaches use methods requiring close interaction and cooperation between programmers and customers/end-users to iteratively develop requirements, user stories, etc. In the XP 'test first' approach developers create automated unit testing code before the application code, and these automated unit tests essentially embody the requirements. </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_6"><b> What steps are needed to develop and run software tests? </b></a><br />The following are some of the steps to consider: </span></p> <ul style="font-family:verdana;"><li><span style="font-size:85%;">Obtain requirements, functional design, and internal design specifications, user stories, and other available/necessary information</span></li><li><span style="font-size:85%;">Obtain budget and schedule requirements</span></li><li><span style="font-size:85%;">Determine project-related personnel and their responsibilities, reporting requirements, required standards and processes (such as release processes, change processes, etc.)</span></li><li><span style="font-size:85%;">Determine project context, relative to the existing quality culture of the product/organization/business, and how it might impact testing scope, aproaches, and methods.</span></li><li><span style="font-size:85%;">Identify application's higher-risk and mor important aspects, set priorities, and determine scope and limitations of tests.</span></li><li><span style="font-size:85%;">Determine test approaches and methods - unit, integration, functional, system, security, load, usability tests, etc.</span></li><li><span style="font-size:85%;">Determine test environment requirements (hardware, software, configuration, versions, communications, etc.)</span></li><li><span style="font-size:85%;">Determine testware requirements (automation tools, coverage analyzers, test tracking, problem/bug tracking, etc.)</span></li><li><span style="font-size:85%;">Determine test input data requirements</span></li><li><span style="font-size:85%;">Identify tasks, those responsible for tasks, and labor requirements</span></li><li><span style="font-size:85%;">Set schedule estimates, timelines, milestones</span></li><li><span style="font-size:85%;">Determine, where apprapriate, input equivalence classes, boundary value analyses, error classes</span></li><li><span style="font-size:85%;">Prepare test plan document(s) and have needed reviews/approvals</span></li><li><span style="font-size:85%;">Write test cases</span></li><li><span style="font-size:85%;">Have needed reviews/inspections/approvals of test cases</span></li><li><span style="font-size:85%;">Prepare test environment and testware, obtain needed user manuals/reference documents/configuration guides/installation guides, set up test tracking processes, set up logging and archiving processes, set up or obtain test input data</span></li><li><span style="font-size:85%;">Obtain and install software releases</span></li><li><span style="font-size:85%;">Perform tests</span></li><li><span style="font-size:85%;">Evaluate and report results</span></li><li><span style="font-size:85%;">Track problems/bugs and fixes</span></li><li><span style="font-size:85%;">Retest as needed</span></li><li><span style="font-size:85%;">Maintain and update test plans, test cases, test environment, and testware through life cycle</span></li></ul> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_6b"><b> What's a 'test plan'? </b></a><br />A software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. The following are some of the items that might be included in a test plan, depending on the particular project: </span></p> <ul style="font-family:verdana;"><li><span style="font-size:85%;">Title</span></li><li><span style="font-size:85%;">Identification of software including version/release numbers</span></li><li><span style="font-size:85%;">Revision history of document including authors, dates, approvals</span></li><li><span style="font-size:85%;">Table of Contents</span></li><li><span style="font-size:85%;">Purpose of document, intended audience</span></li><li><span style="font-size:85%;">Objective of testing effort</span></li><li><span style="font-size:85%;">Software product overview</span></li><li><span style="font-size:85%;">Relevant related document list, such as requirements, design documents, other test plans, etc.</span></li><li><span style="font-size:85%;">Relevant standards or legal requirements</span></li><li><span style="font-size:85%;">Traceability requirements</span></li><li><span style="font-size:85%;">Relevant naming conventions and identifier conventions</span></li><li><span style="font-size:85%;">Overall software project organization and personnel/contact-info/responsibilties</span></li><li><span style="font-size:85%;">Test organization and personnel/contact-info/responsibilities</span></li><li><span style="font-size:85%;">Assumptions and dependencies</span></li><li><span style="font-size:85%;">Project risk analysis</span></li><li><span style="font-size:85%;">Testing priorities and focus</span></li><li><span style="font-size:85%;">Scope and limitations of testing</span></li><li><span style="font-size:85%;">Test outline - a decomposition of the test approach by test type, feature, functionality, process, system, module, etc. as applicable</span></li><li><span style="font-size:85%;">Outline of data input equivalence classes, boundary value analysis, error classes</span></li><li><span style="font-size:85%;">Test environment - hardware, operating systems, other required software, data configurations, interfaces to other systems</span></li><li><span style="font-size:85%;">Test environment validity analysis - differences between the test and production systems and their impact on test validity.</span></li><li><span style="font-size:85%;">Test environment setup and configuration issues</span></li><li><span style="font-size:85%;">Software migration processes </span></li><li><span style="font-size:85%;">Software CM processes </span></li><li><span style="font-size:85%;">Test data setup requirements </span></li><li><span style="font-size:85%;">Database setup requirements</span></li><li><span style="font-size:85%;">Outline of system-logging/error-logging/other capabilities, and tools such as screen capture software, that will be used to help describe and report bugs</span></li><li><span style="font-size:85%;">Discussion of any specialized software or hardware tools that will be used by testers to help track the cause or source of bugs</span></li><li><span style="font-size:85%;">Test automation - justification and overview</span></li><li><span style="font-size:85%;">Test tools to be used, including versions, patches, etc.</span></li><li><span style="font-size:85%;">Test script/test code maintenance processes and version control</span></li><li><span style="font-size:85%;">Problem tracking and resolution - tools and processes</span></li><li><span style="font-size:85%;">Project test metrics to be used</span></li><li><span style="font-size:85%;">Reporting requirements and testing deliverables</span></li><li><span style="font-size:85%;">Software entrance and exit criteria</span></li><li><span style="font-size:85%;">Initial sanity testing period and criteria</span></li><li><span style="font-size:85%;">Test suspension and restart criteria</span></li><li><span style="font-size:85%;">Personnel allocation</span></li><li><span style="font-size:85%;">Personnel pre-training needs</span></li><li><span style="font-size:85%;">Test site/location</span></li><li><span style="font-size:85%;">Outside test organizations to be utilized and their purpose, responsibilties, deliverables, contact persons, and coordination issues</span></li><li><span style="font-size:85%;">Relevant proprietary, classified, security, and licensing issues.</span></li><li><span style="font-size:85%;">Open issues</span></li><li><span style="font-size:85%;">Appendix - glossary, acronyms, etc.</span></li></ul> <span style="font-size:85%;"><br /></span><p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_7"><b> What's a 'test case'? </b></a><br />A test case describes an input, action, or event and an expected response, to determine if a feature of a software application is working correctly. A test case may contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results. The level of detail may vary significantly depending on the organization and project context. </span></p> <p style="font-family:verdana;"><span style="font-size:85%;"> Note that the process of developing test cases can help find problems in the requirements or design of an application, since it requires completely thinking through the operation of the application. For this reason, it's useful to prepare test cases early in the development cycle if possible. </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_8"><b> What should be done after a bug is found? </b></a><br />The bug needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested, and determinations made regarding requirements for regression testing to check that fixes didn't create problems elsewhere. If a problem-tracking system is in place, it should encapsulate these processes. A variety of commercial problem-tracking/management software tools are available (see the section for web resources with listings of such tools). The following are items to consider in the tracking process: </span></p> <ul style="font-family:verdana;"><li><span style="font-size:85%;">Complete information such that developers can understand the bug, get an idea of it's severity, and reproduce it if necessary.</span></li><li><span style="font-size:85%;">Bug identifier (number, ID, etc.)</span></li><li><span style="font-size:85%;">Current bug status (e.g., 'Released for Retest', 'New', etc.)</span></li><li><span style="font-size:85%;">The application name or identifier and version</span></li><li><span style="font-size:85%;">The function, module, feature, object, screen, etc. where the bug occurred</span></li><li><span style="font-size:85%;">Environment specifics, system, platform, relevant hardware specifics</span></li><li><span style="font-size:85%;">Test case name/number/identifier</span></li><li><span style="font-size:85%;">One-line bug description</span></li><li><span style="font-size:85%;">Full bug description</span></li><li><span style="font-size:85%;">Description of steps needed to reproduce the bug if not covered by a test case or if the developer doesn't have easy access to the test case/test script/test tool </span></li><li><span style="font-size:85%;">Names and/or descriptions of file/data/messages/etc. used in test</span></li><li><span style="font-size:85%;">File excerpts/error messages/log file excerpts/screen shots/test tool logs that would be helpful in finding the cause of the problem</span></li><li><span style="font-size:85%;">Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common)</span></li><li><span style="font-size:85%;">Was the bug reproducible?</span></li><li><span style="font-size:85%;">Tester name</span></li><li><span style="font-size:85%;">Test date</span></li><li><span style="font-size:85%;">Bug reporting date</span></li><li><span style="font-size:85%;">Name of developer/group/organization the problem is assigned to</span></li><li><span style="font-size:85%;">Description of problem cause</span></li><li><span style="font-size:85%;">Description of fix</span></li><li><span style="font-size:85%;">Code section/file/module/class/method that was fixed</span></li><li><span style="font-size:85%;">Date of fix</span></li><li><span style="font-size:85%;">Application version that contains the fix</span></li><li><span style="font-size:85%;">Tester responsible for retest</span></li><li><span style="font-size:85%;">Retest date</span></li><li><span style="font-size:85%;">Retest results</span></li><li><span style="font-size:85%;">Regression testing requirements</span></li><li><span style="font-size:85%;">Tester responsible for regression tests</span></li><li><span style="font-size:85%;">Regression testing results</span></li></ul><span style="font-size:85%;"><span style="font-family:verdana;"> A reporting or tracking process should enable notification of appropriate personnel at various stages. For instance, testers need to know when retesting is needed, developers need to know when bugs are found and how to get the needed information, and reporting/summary capabilities are needed for managers. </span></span> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_9"><b> What is 'configuration management'? </b></a><br />Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes. (See the section for web resources with listings of configuration management tools. Also see the section's 'Configuration Management' category for useful books with more information.) </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_10"><b> What if the software is so buggy it can't really be tested at all? </b></a><br />The best bet in this situation is for the testers to go through the process of reporting whatever bugs or blocking-type problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules, and indicates deeper problems in the software development process (such as insufficient unit testing or insufficient integration testing, poor design, improper build or release procedures, etc.) managers should be notified, and provided with some documentation as evidence of the problem. </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_11"><b> How can it be known when to stop testing? </b></a><br />This can be difficult to determine. Most modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are: </span></p> <ul style="font-family:verdana;"><li><span style="font-size:85%;">Deadlines (release deadlines, testing deadlines, etc.)</span></li><li><span style="font-size:85%;">Test cases completed with certain percentage passed</span></li><li><span style="font-size:85%;">Test budget depleted</span></li><li><span style="font-size:85%;">Coverage of code/functionality/requirements reaches a specified point</span></li><li><span style="font-size:85%;">Bug rate falls below a certain level</span></li><li><span style="font-size:85%;">Beta or alpha testing period ends</span></li></ul><span style="font-size:85%;"><br /></span><p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_12"><b> What if there isn't enough time for thorough testing? </b></a><br />Use risk analysis, along with discussion with project stakeholders, to determine where testing should be focused.<br />Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include: </span></p> <ul style="font-family:verdana;"><li><span style="font-size:85%;">Which functionality is most important to the project's intended purpose?</span></li><li><span style="font-size:85%;">Which functionality is most visible to the user?</span></li><li><span style="font-size:85%;">Which functionality has the largest safety impact?</span></li><li><span style="font-size:85%;">Which functionality has the largest financial impact on users?</span></li><li><span style="font-size:85%;">Which aspects of the application are most important to the customer?</span></li><li><span style="font-size:85%;">Which aspects of the application can be tested early in the development cycle?</span></li><li><span style="font-size:85%;">Which parts of the code are most complex, and thus most subject to errors?</span></li><li><span style="font-size:85%;">Which parts of the application were developed in rush or panic mode?</span></li><li><span style="font-size:85%;">Which aspects of similar/related previous projects caused problems?</span></li><li><span style="font-size:85%;">Which aspects of similar/related previous projects had large maintenance expenses?</span></li><li><span style="font-size:85%;">Which parts of the requirements and design are unclear or poorly thought out?</span></li><li><span style="font-size:85%;">What do the developers think are the highest-risk aspects of the application?</span></li><li><span style="font-size:85%;">What kinds of problems would cause the worst publicity?</span></li><li><span style="font-size:85%;">What kinds of problems would cause the most customer service complaints?</span></li><li><span style="font-size:85%;">What kinds of tests could easily cover multiple functionalities?</span></li><li><span style="font-size:85%;">Which tests will have the best high-risk-coverage to time-required ratio?</span></li></ul> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_13"><b> What if the project isn't big enough to justify extensive testing? </b></a><br />Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed and the same considerations as described previously in apply. The tester might then do ad hoc testing, or write up a limited test plan based on the risk analysis. </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_14"><b> How does a client/server environment affect testing? </b></a><br />Client/server applications can be quite complex due to the multiple dependencies among clients, data communications, hardware, and servers, especially in multi-tier systems. Thus testing requirements can be extensive. When time is limited (as it usually is) the focus should be on integration and system testing. Additionally, load/stress/performance testing may be useful in determining client/server application limitations and capabilities. There are commercial tools to assist with such testing. (See the section for web resources with listings that include these kinds of test tools.) </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_15"><b> How can World Wide Web sites be tested? </b></a><br />Web sites are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to the interactions between html pages, web services, encrypted communications, Internet connections, firewalls, applications that run in web pages (such as javascript, flash, other plug-in applications), the wide variety of applications that could run on the server side, etc. Additionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes significant differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for web sites can become a major ongoing effort. Other considerations might include: </span></p> <ul style="font-family:verdana;"><li><span style="font-size:85%;">What are the expected loads on the server (e.g., number of hits per unit time?), and what kind of performance is required under such loads (such as web server response time, database query response times). What kinds of tools will be needed for performance testing (such as web load testing tools, other tools already in house that can be adapted, load generation appliances, etc.)?</span></li><li><span style="font-size:85%;">Who is the target audience? What kind and version of browsers will they be using, and how extensively should testing be for these variations? What kind of connection speeds will they by using? Are they intra- organization (thus with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide variety of connection speeds and browser types)?</span></li><li><span style="font-size:85%;">What kind of performance is expected on the client side (e.g., how fast should pages appear, how fast should flash, applets, etc. load and run)? </span></li><li><span style="font-size:85%;">Will down time for server and content maintenance/upgrades be allowed? how much?</span></li><li><span style="font-size:85%;">What kinds of security (firewalls, encryption, passwords, functionality, etc.) will be required and what is it expected to do? How can it be tested?</span></li><li><span style="font-size:85%;">What internationilization/localization/language requirements are there, and how are they to be verified? </span></li><li><span style="font-size:85%;">How reliable are the site's Internet connections required to be? And how does that affect backup system or redundant connection requirements and testing?</span></li><li><span style="font-size:85%;">What processes will be required to manage updates to the web site's content, and what are the requirements for maintaining, tracking, and controlling page content, graphics, links, etc.?</span></li><li><span style="font-size:85%;">Which HTML and related specification will be adhered to? How strictly? What variations will be allowed for targeted browsers?</span></li><li><span style="font-size:85%;">Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site?</span></li><li><span style="font-size:85%;">Will there be any development practices/standards utilized for web page components and identifiers, which can significantly impact test automation.</span></li><li><span style="font-size:85%;">How will internal and external links be validated and updated? how often? </span></li><li><span style="font-size:85%;">Can testing be done on the production system, or will a separate test system be required? How are browser caching, variations in browser option settings, connection variabilities, and real-world internet 'traffic congestion' problems to be accounted for in testing?</span></li><li><span style="font-size:85%;">How extensive or customized are the server logging and reporting requirements; are they considered an integral part of the system and do they require testing?</span></li><li><span style="font-size:85%;">How are flash, applets, javascripts, ActiveX components, etc. to be maintained, tracked, controlled, and tested?</span></li></ul><span style="font-size:85%;"><span style="font-family:verdana;"> Some sources of site security information include the Usenet newsgroup 'comp.security.announce' and links concerning web site security in the </span></span> <p style="font-family:verdana;"><span style="font-size:85%;"> Hundreds of web site test tools are available and more than 420 of them are listed in the . </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_16"><b> How is testing affected by object-oriented designs? </b></a><br />Well-engineered object-oriented design can make it easier to trace from code to internal design to functional design to requirements. While there will be little affect on black box testing (where an understanding of the internal design of the application is unnecessary), white-box testing can be oriented to the application's objects. If the application was well-designed this can simplify test design. </span></p> <p class="topmargin" style="font-family:verdana;"><span style="font-size:85%;"><a name="FAQ2_17"><b> What is Extreme Programming and what's it got to do with testing? </b></a><br />Extreme Programming (XP) is a software development approach for small teams on risk-prone projects with unstable requirements. It was created by Kent Beck who described the approach in his book 'Extreme Programming Explained' (See the ). Testing ('extreme testing') is a core aspect of Extreme Programming. Programmers are expected to write unit and functional test code first - before writing the application code. Test code is under source control along with the rest of the code. Customers are expected to be an integral part of the project team and to help develope scenarios for acceptance/black box testing. Acceptance tests are preferably automated, and are modified and rerun for each of the frequent development iterations. QA and test personnel are also required to be an integral part of the project team. Detailed requirements documentation is not used, and frequent re-scheduling, re-estimating, and re-prioritizing is expected. For more info on XP and other 'agile' software development approaches (Scrum, Crystal, etc.) see the resource listings in the section. </span></p>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-74553424992010493322009-09-03T20:41:00.000+05:302009-09-03T21:38:25.375+05:30Test Partner<center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">TestPartner - Introduction</span></h2></center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">IT managers charged with ensuring application quality are confronted with a number of critical business challenges:</span></p><ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;">Verify that <a id="KonaLink0" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">applications</span></span></a> function as expected and fulfill business requirements</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Test multiple heterogeneous application technologies</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Meet ever-more-rapid release schedules</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Achieve the right balance between risk and quality.</span></li></ul><span style="font-size:85%;"><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">If that weren't enough, IT struggles with limited resources, hard deadlines that squeeze testing cycles and late-breaking requirement changes.<br /><br />In the face of these <a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">business</span></span></a> demands, TestPartner's functional testing capabilities accelerate testing and enable successful application delivery outcomes on-time, at a lower cost, with higher quality than ever before. TestPartner achieves these results through a tiered approach to testing that enables developers, quality experts, and non-technical application users to collaborate and test more in the time available.<br /><br />TestPartner's visual, contextual approach to capturing business processes empowers non-technical application users to participate in the testing process. At the same time, TestPartner provides expert testers and software developers with access to Visual Basic for Applications, allowing them to solve even the most complex testing challenges. This flexibility and focus on usability allows quality teams to produce positive results even with minimal training.<br /><br />TestPartner enables IT to:</span></p><span style="font-size:85%;"><br /><br /></span><ol style="font-family: verdana;" class="text"><li><span style="font-size:85%;">Leverage non-technical as well as experienced testers to test applications more thoroughly in the time available</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Collaborate throughout the software development lifecycle, resulting in higher team efficiency and greater project effectiveness</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Automate regression testing to quicken acceptance of application patches, service packs, and other regular updates</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Clearly and unambiguously <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">document</span></span></a> test results, accelerating the identification and resolution of application issues</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Understand the results of testing, enabling confident delivery of applications that meet requirements and provide the expected business value</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Use test results to facilitate test maintenance, providing improved return on the test automation <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">investment</span></span></a></span></li><li><span style="font-size:85%;">Build quality into applications earlier in the <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">life </span><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">cycle</span></span></a>, leading to lower development and maintenance costs</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Accelerate quality efforts for a broad range of technology platforms, including Web, .NET, <a id="KonaLink5" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">Java</span></span></a>, SAP, Oracle and many other distributed Windows-based applications.</span></li><span style="font-size:85%;"><br /></span></ol> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">TestPartner's value is further enhanced through its tight integration with Compuware's Test Management solution, which improves application delivery by providing IT with the ability to more effectively assess and balance risk, cost, and schedule. TestPartner is also an integral component within Quality Management, which provides IT with the ability to control, measure, manage and continuously improve the delivery of higher quality applications. Quality Management's reporting and real-time insight into project quality status results in informed quality decisions, and allows IT to deploy applications with greater confidence.</span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">TestPartner - Product Preview</span></h2></center> <span style="font-size:85%;"><b style="font-family: verdana;">Automated, repeatable testing with TestPartner</b><span style="font-family: verdana;"> TestPartner is an automated testing tool that accelerates functional testing and facilitates the delivery of business-critical applications.</span><br /><br /><span style="font-family: verdana;">With TestPartner, you can more rapidly validate applications before going live, verify that application updates don't introduce regressions or even test nightly builds with automated smoke tests. TestPartner offers a storyboard-based visual approach to testing that lets application users confidently capture test scenarios. VBA scripting is available to enable advanced users to meet even the most demanding test cases. You build test assets earlier in the development </span><a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static; font-family: verdana;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">life </span><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">cycle</span></span></a><span style="font-family: verdana;">, test more thoroughly and deploy applications with confidence.</span><br /><br /><span style="font-family: verdana;">TestPartner's broad environment support means that enterprises with heterogeneous environments can be confident about easily validating </span><a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static; font-family: verdana;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="border-bottom: 1px solid blue; font-weight: 400; position: static; color: rgb(176, 0, 0);">Microsoft</span></span><span style="position: relative;" id="preLoadWrap2"><div style="position: absolute; z-index: 4000; top: -32px; left: -18px; display: none;" id="preLoadLayer2"><img style="border: 0px none ;" src="http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif" /></div></span></a><span style="font-family: verdana;">, Java, web, SAP, Oracle and many other distributed technologies with speed and consistency.</span><br /><br /><br /></span><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">TestPartner - Build tests without programming</span></h2></center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Unlike testing tools that require users to understand a programming language, TestPartner's Visual Navigator makes testing accessible to even novice users, allowing virtually anyone to be immediately productive.<br /></span></p><span style="font-size:85%;"><br /></span><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">TestPartner - Build tests without programming</span></h2></center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Unlike testing tools that require users to understand a programming language, TestPartner's Visual Navigator makes testing accessible to even novice users, allowing virtually anyone to be immediately productive.<br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Within the Visual Navigator, you access panes that provide a preview of each screen being tested, the pertinent test steps for each and a storyboard view that ties it all together. As each step is selected, the corresponding control within the screen preview is highlighted, which clearly defines the automation context.<br />Additionally, each test step has related properties that can be modified by the user or even populated via a data file to facilitate fully data-driven testing. Ultimately, this approach allows <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">application</span></span></a> users—who are intimately familiar with the application under test, but often lack the technical expertise to use automated testing tools—to comfortably and confidently capture business transactions, verify the proper functionality is tested and assist in updating the test when inaccuracies are found or the application changes.</span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><h1 style="font-family: verdana;" class="mainHeading"><span style="font-size:85%;">TestPartner - Modify and customize tests</span></h1><span style="font-size:85%;"><span style="font-family: verdana;">In addition to capturing a screenshot of each </span><a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static; font-family: verdana;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">application</span></span></a><span style="font-family: verdana;"> window, which is displayed within the screen preview pane,</span><br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> TestPartner records detailed information about the controls and properties for each screen. This means you can easily augment or modify an existing test based upon the information already captured.<br /><br />For example, you can:</span></p><span style="font-size:85%;"><br /><br /></span><ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;">insert new steps directly from the screen preview (or the application under test)</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">modify existing tests to perform different or additional steps</span></li></ul><ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;">change the action performed (e.g., replace single-click with a double-click) or the data being input</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">add verifications that weren't inserted during the initial record session</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">do all of this without having to re-record against the original application.</span></li><span style="font-size:85%;"><br /></span></ul> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">This "offline editing" capability is especially valuable for modern "workflow-driven" <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="border-bottom: 1px solid blue; font-weight: 400; position: static; color: rgb(176, 0, 0);">applications</span></span><span style="position: relative;" id="preLoadWrap3"><div style="position: absolute; z-index: 4000; top: -32px; left: -18px; display: none;" id="preLoadLayer3"><img style="border: 0px none ;" src="http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif" /></div></span></a>, where you might spend several minutes or more simply returning to the point where you can capture additional data or record new actions. With TestPartner, as long as the underlying application data hasn't changed, you achieve higher productivity by simply going right to the pertinent screen and making changes and additions as needed. </span></p><span style="font-size:85%;"><br /></span><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">TestPartner - Understand and document tests and results unambiguously</span></h2></center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">TestPartner removes abstraction to give users a better understanding of what the test should automate and the actual results. You no longer have to guess. You can see exactly what each step intends to automate.<br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Similarly, when a test exposes an application problem, the visual test results are much more efficient and effective in leading to a positive identification and resolution. You no longer have to struggle for hours to reproduce issues live.<br /><br />Additionally, tests can be printed to provide external <a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">documents</span></span></a> for manual testing, user documentation and training, or archived for process compliance and <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">auditing</span></span></a>. Similarly, test results can be printed to provide reports that can be reviewed at meetings, aid with troubleshooting or provide evidence supporting process compliance.</span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">TestPartner - Build in test "intelligence" with logic designers</span></h2><span style="font-size:85%;"><span style="font-family: verdana;">To test </span><a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static; font-family: verdana;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">applications</span></span></a><span style="font-family: verdana;"> thoroughly, it's important to do more than simply record and playback.</span><br /><br /><span style="font-family: verdana;">TestPartner comes with built-in wizards and logic designers that make it easy to build and execute sophisticated test cases.</span><br /><br /><span style="font-family: verdana;">These wizards and logic designers are instantly accessible through the Logic Toolbox or via right-click menus. Users can successfully fulfill even complex test cases by adding logic that allows:</span><br /><br /></span><ol style="font-family: verdana;" class="text"><li><span style="font-size:85%;">quick creation of data-driven tests</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;"><a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">testing</span></span></a> for the presence of text, images, properties, etc.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">steps to occur only when specific conditions are met</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">creation and use of variable data</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">repetition of test steps</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">testing and verification of actual and expected results</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">synchronization of the test with the application being tested</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">automatic error handling</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">and more.</span></li></ol><span style="font-size:85%;"><br /></span><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">TestPartner - Accelerate test maintenance</span></h2></center><span style="font-size:85%;"><span style="font-family: verdana;"> One of the biggest challenges with automated testing is maintaining the test assets over time.</span><br /><br /><span style="font-family: verdana;">When the </span><a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static; font-family: verdana;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="border-bottom: 1px solid blue; font-weight: 400; position: static; color: rgb(176, 0, 0);">application</span></span><span style="position: relative;" id="preLoadWrap2"><div style="position: absolute; z-index: 4000; top: -32px; left: -18px; display: none;" id="preLoadLayer2"><img style="border: 0px none ;" src="http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif" /></div></span></a><span style="font-family: verdana;"> changes, the test cases that correspond to that functionality need to be updated. TestPartner simplifies this effort in two ways.</span><br /><br /><span style="font-family: verdana;">First, you can view results with the Visual Navigator, TestPartner's built-in screen preview that shows both the original test screen and the screen that was captured at playback, allowing you to identify critical changes in the application immediately.</span><br /><br /><span style="font-family: verdana;">Second, TestPartner's one-click Update Screen feature allows application changes to be instantly captured into the visual test. For example, if you determined that a new field was added to an existing screen within the application under test, you could select the Update Screen to capture the new screen definition (along with associated properties) without having to re-record the test. By enabling you to spend less time on test maintenance and more time on testing the application thoroughly, TestPartner improves your </span><a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static; font-family: verdana;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="border-bottom: 1px solid blue; font-weight: 400; position: static; color: rgb(176, 0, 0);">return </span><span class="kLink" style="border-bottom: 1px solid blue; font-weight: 400; position: static; color: rgb(176, 0, 0);">on </span><span class="kLink" style="border-bottom: 1px solid blue; font-weight: 400; position: static; color: rgb(176, 0, 0);">investment</span></span><span style="position: relative;" id="preLoadWrap3"><div style="position: absolute; z-index: 4000; top: -32px; left: -18px; display: none;" id="preLoadLayer3"><img style="border: 0px none ;" src="http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif" /></div></span></a><span style="font-family: verdana;">.</span><br /><br /><br /></span><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">TestPartner - VBA scripting</span></h2><span style="font-size:85%;"><span style="font-family: verdana;">TestPartner's visual tests provide an approach to testing that requires no programming experience, and offers more advanced capabilities for expert users via </span><a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static; font-family: verdana;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">Microsoft</span></span></a><span style="font-family: verdana;"> Visual Basic for Applications.</span><br /><br /><br /><span style="font-family: verdana;">The availability of VBA-based tests means expert users can work at whatever level is best suited for a given project or test—use an entirely visual approach, integrate VBA routines with visual tests to enable customization and complex text cases, or work entirely with VBA.</span><br /><br /><br /><span style="font-family: verdana;">TestPartner's VBA and visual testing features are designed to work closely in conjunction, so testers can call VBA routines at any point within a visual test, passing and returning data as necessary to fulfill the test case.VBA's rich feature-set, which includes broad debugging capabilities and Microsoft auto-completing IntelliSense™, makes users more efficient and productive than with proprietary programming languages or other feature-poor development environments.</span><br /><br /><br /></span><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">TestPartner - VBA scripting</span></h2><span style="font-size:85%;"><span style="font-family: verdana;">TestPartner's visual tests provide an approach to testing that requires no programming experience, and offers more advanced capabilities for expert users via </span><a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static; font-family: verdana;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">Microsoft</span></span></a><span style="font-family: verdana;"> Visual Basic for Applications.</span><br /><br /><br /><span style="font-family: verdana;">The availability of VBA-based tests means expert users can work at whatever level is best suited for a given project or test—use an entirely visual approach, integrate VBA routines with visual tests to enable customization and complex text cases, or work entirely with VBA.</span><br /><br /><br /><span style="font-family: verdana;">TestPartner's VBA and visual testing features are designed to work closely in conjunction, so testers can call VBA routines at any point within a visual test, passing and returning data as necessary to fulfill the test case.VBA's rich feature-set, which includes broad debugging capabilities and Microsoft auto-completing IntelliSense™, makes users more efficient and productive than with proprietary programming languages or other feature-poor development environments.</span><br /><br /><br /></span><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">TestPartner - Collaborate to communicate and operate more effectively</span></h2></center><span style="font-size:85%;"><span style="font-family: verdana;"> As test teams get increasingly distributed and incorporate application users, testers and developers, clear and effective </span><a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static; font-family: verdana;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">communication</span></span></a><span style="font-family: verdana;"> becomes increasingly important.</span><br /><br /><span style="font-family: verdana;">To that end, TestPartner includes a team-oriented collaboration feature that allows users to flag and describe particular items of interest within a test or test result, and assign to another user as applicable. This allows work scenarios where, for example:</span><br /><br /></span><ol style="font-family: verdana;" class="text"><li><span style="font-size:85%;">An application user successfully captures a business process, and then flags and assigns it to a quality expert for inclusion within the test framework.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">A member of the quality team reproduces a defect, flags the point at which the problem occurs and assigns it to a developer for investigation.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">The test result appears to show a change in the application under test. A member of the quality team assigns the result to an application user to verify whether this is the expected behavior.</span></li></ol><span style="font-size:85%;"><br /></span><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">TestPartner Program</span></h2></center> <span style="font-size:85%;"><b style="font-family: verdana;">Transition Networks's Test Partner Program</b><span style="font-family: verdana;"> is a new kind of product testing program.</span><br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> The Test Partner Program consists of our <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">Technical </span><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">Support</span></span></a> staff and select Transition customers <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">working</span></span></a> together to insure that product supportability is designed into every Transition product. We do this by providing our Test Partner Program participants with final releases of products, and then working closely with the Test Partner to find ways to enhance/improve the product.<br /><br />Through Test Partners, Transition is able to isolate and resolve a problem, or define and determine the scope of a new feature or function, resulting in a win-win situation for Transition, our resellers and our customers.<br /><br />Test Partners are not expected to execute a laborious product acceptance test plan. We recognize that a Test Partner's resources may be limited. Test Partners can test the product any way they want to. The challenge is simple - break it if you can. We promise that all problems reported by a Test Partner will be Priority #1!<br /><br />Our Technical Support Department qualifies potential Test Partners on the basis of robustness of their networks, client count, eagerness to participate in the program, and the networking expertise of the Test Partner's technical contact person. Most importantly, the Test Partner must possess a "partner", rather than a "customer" mentality.<br /><br />Transition's Test Partner Program requirements are few, but important. Participants must: </span></p> <ol style="font-family: verdana;" class="text"><li><span style="font-size:85%;">provide a diagram of their network illustrating backbones, device and client count.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">capture a performance baseline before installation so that a comparison can be made.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">give this testing a reasonable amount of priority.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">provide as much detail as practical when reporting problems.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">allow Transition's Marketing Department an interview so that the prestige of their opinion can be shared.</span></li></ol><span style="font-size:85%;"><br /></span><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">Events</span></h2></center><span style="font-size:85%;"><span style="font-family: verdana;"> Events are unscheduled occurrences or conditions to which you want the target application to respond in a specified manner. Test Partner supports two categories of events: Wait and Whenever.</span><br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> A Wait event tells Test Partner to wait for a specified occurrence before proceeding. Wait events are useful in situations where you cannot anticipate the amount of time a response will take. An example of a Wait event would be waiting for a system login prompt. When your script is running against a network-based application that requires the <a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="border-bottom: 1px solid blue; font-weight: 400; position: static; color: rgb(176, 0, 0);">user</span></span><span style="position: relative;" id="preLoadWrap1"><div style="position: absolute; z-index: 4000; top: -32px; left: -18px; display: none;" id="preLoadLayer1"><img style="border: 0px none ;" src="http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif" /></div></span></a> to log in, the amount of time it takes for the login prompt to display may vary. To account for this variance, you can insert a Wait event that instructs your script to wait for the login prompt before proceeding to type a username and password.</span></p> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">A Whenever event tells Test Partner to watch for a specific occurrence and, if it occurs, perform a special set of steps. Whenever events are useful for trapping unexpected error conditions during a test run. For example, you can include events in your scripts to recognize when the connection to the <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">server</span></span></a></span> has been interrupted by a communications error or a network system message has been received, so that the script can report or work around the problem. In a script, Test Partner automatically inserts the Script_Whenever function by default to handle the whenever event. If a whenever event is inserted into a module, shared module, or class module, you must customize the whenever event handler code. Test Partner supports the following types of Events:</p> <span style="font-size:85%;"><b style="font-family: verdana;">i) Bitmap Event</b><span style="font-family: verdana;">:--</span></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> A bitmap event detects the presence, absence, or state of a graphic in a window.</span></p> <span style="font-size:85%;"><b style="font-family: verdana;">ii) Date/Time Event</b><span style="font-family: verdana;">:--</span></span><p style="font-family: verdana;" class="text"> <span style="font-size:85%;"><a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">date</span></span></a>/Time events enable you to define a date or time condition. Test Partner recognizes the event by monitoring the internal clock of the computer on which it and the target application are running.</span></p> <span style="font-size:85%;"><b style="font-family: verdana;">iii) Key Event</b><span style="font-family: verdana;">:-- </span></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Watch for the entry of a particular keystroke combination by the user. You can use key events to: </span></p> <ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;"> Build your own “hotkeys” to make Test Partner perform an action whenever the hotkey is used. </span></li><li><span style="font-size:85%;"> Interrupt a script to take manual control of the target application. </span></li><li><span style="font-size:85%;"> Pause a script until a particular key is used. </span></li><li><span style="font-size:85%;"> Prevent certain keys from being entered.</span></li></ul> <span style="font-size:85%;"><b style="font-family: verdana;">iv) Menu Events</b><span style="font-family: verdana;">:-- </span></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Watch for when a particular menu item is selected by the user.</span></p> <span style="font-size:85%;"><b style="font-family: verdana;">v) Mouse Events</b><span style="font-family: verdana;">:--</span></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> Watch for when one of the mouse buttons is clicked or released in a certain window.</span></p><span style="font-size:85%;"><b style="font-family: verdana;">vi) Screen Events</b><span style="font-family: verdana;">:-- </span></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">A screen event detects the presence or absence of text in a window. The most common use of screen events is to synchronize with host-based <a id="KonaLink5" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);"><span class="kLink" style="font-weight: 400; position: static; color: rgb(176, 0, 0);">applications</span></span></a> and to detect error messages.</span></p> <span style="font-size:85%;"><b style="font-family: verdana;">vii) Window Events</b><span style="font-family: verdana;">:--</span></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> A window event detects an action on a window; for example, its creation, destruction, movement, or its existence.</span></p> <span style="font-size:85%;"><b style="font-family: verdana;">Data Driven Test</b><span style="font-family: verdana;">:-- </span></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> The Test Partner Active Data Test Creation wizard provides a non-programmatic way to create data-driven tests. Such tests are useful for testing form-based applications. Using the wizard, you can record a test, choose the fields you want to include in your data file, then populate the data file itself using a data table. </span></p> <span style="font-size:85%;"><b style="font-family: verdana;">To create a data test</b><br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> 1. From the Script menu, choose Create Data Test. The Data Test wizard appears.<br />2. Read the instructions and click Next.<br />3. Follow the instructions in the Data Layout Assistant for the three steps necessary to define the scope of the test.<br />4. Enter a name for the Data Table.<br />5. Exclude any fields you do not want to include in the test by unchecking the Use checkbox and click Next.<br />6. Read the instructions and click Finish.</span></p><span style="font-size:85%;"><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">TestPartner shows the Data Table, which includes a column for each field you defined and one row of data. The data table also includes a column labelled Results Script, to specify a script to be run after the data driven test.</span></p><span style="font-size:85%;"><br /><b style="font-family: verdana;">To modify the data table</b><span style="font-family: verdana;">.</span><br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> 1. If you have just recorded a new data test and the data table is open, proceed to step 3.</span></p><span style="font-size:85%;"><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> 2. To modify an existing data test, select Modify Data Table on the Script menu and choose the data table you want to change.</span></p><span style="font-size:85%;"><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> 3. To add rows and populate the table with test data, right-click on the empty row labelled END ( or any other row) and select Insert on the context menu. Test Partner inserts a new row above the selected row.</span></p><span style="font-size:85%;"><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> 4. Enter test data into the cells of the new row.</span></p><span style="font-size:85%;"><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> 5. Alternatively, right-click the empty row and choose Import. You can import data from a tab-delimited text (.TXT) or comma-delimited (.CSV) file to populate the cells of the data table. If you select the END row in the table, TestPartner will add multiple rows if needed to accommodate the data.</span></p><span style="font-size:85%;"><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> 6. To delete rows from the table, right-click the row and choose Delete. To delete multiple rows, press the Ctrl or Shift (for contiguous rows) key while selecting rows to delete.</span></p><span style="font-size:85%;"><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> 7. To launch another script from the data test, insert the name of the script in the Results Script field in the table at any point(s) at which you want to run the script.</span></p><span style="font-size:85%;"><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">8. When you have finished editing the data table, click Save and Close to exit.</span></p><span style="font-size:85%;"><br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-53446804382955977572009-08-14T14:37:00.000+05:302009-08-14T14:53:30.706+05:30Costly Software Bugs<table style="font-family: verdana; text-align: left; margin-left: 0px; margin-right: auto;" width="1243" border="0" cellpadding="0" cellspacing="0"><tbody><tr></tr><tr><td height="232"><span style="font-size:85%;"><br /></span></td> <td colspan="5" valign="top"> <p><span style="font-size:85%;"><b>Software Bugs Cost U.S. Economy $59.6 Billion Annually, RTI Study Finds</b></span><span style="font-size:85%;"><br /> Research Triangle Park, NC -- Software bugs are costly both to software producers and users.<br />Extrapolating from estimates of the costs in several software-intensive industries, bugs may be<br />costing the U.S. economy $59.5 billion a year; about 0.6 percent of gross domestic product, says a<br />study conducted by RTI for the U.S. Department of Commerce's National Institute of Standards and<br />Technology (NIST).</span></p> <p><span style="font-size:85%;">"More than half of the costs are borne by software users, and the remainder by software developers<br />and vendors," NIST said in summarizing the findings. "More than a third of these costs … could be<br />eliminated by an improved testing infrastructure that enables earlier and more effective identification<br /> and removal of software defects."</span></p><p><span style="font-size:85%;"><br /></span></p><p><span style="font-size:85%;"><b>History's Worst Software Bugs </b></span></p> <p><span style="font-size:85%;">What seems certain is that bugs are here to stay. Here, in chronological order, is the Wired News list<br />of the 10 worst software bugs of all time … so far.</span></p> <p><span style="font-size:85%;"><b>July 28, 1962 -- Mariner I space probe</b>. A bug in the flight software for the Mariner 1 causes the<br />rocket to divert from its intended path on launch. Mission control destroys the rocket over the<br />Atlantic Ocean. The investigation into the accident discovers that a formula written on paper in<br />pencil was improperly transcribed into computer code, causing the computer to miscalculate the<br />rocket's trajectory.</span></p> <p><span style="font-size:85%;"><b>1982 -- Soviet gas pipeline</b>. Operatives working for the Central Intelligence Agency allegedly (.pdf)<br />plant a bug in a Canadian computer system purchased to control the trans-Siberian gas pipeline.<br />The Soviets had obtained the system as part of a wide-ranging effort to covertly purchase or steal<br />sensitive U.S. technology. The CIA reportedly found out about the program and decided to make it<br />backfire with equipment that would pass Soviet inspection and then fail once in operation. The<br />resulting event is reportedly the largest non-nuclear explosion in the planet's history.</span></p> <p><span style="font-size:85%;"><b>1985-1987 -- Therac-25 medical accelerator.</b> A radiation therapy device malfunctions and delivers<br /> lethal radiation doses at several medical facilities. Based upon a previous design, the Therac-25 was<br />an "improved" therapy system that could deliver two different kinds of radiation: either a low-power<br />electron beam (beta particles) or X-rays. The Therac-25's X-rays were generated by smashing high-<br />power electrons into a metal target positioned between the electron gun and the patient. A second<br />"improvement" was the replacement of the older Therac-20's electromechanical safety interlocks with<br />software control, a decision made because software was perceived to be more reliable.</span></p> <p><span style="font-size:85%;">What engineers didn't know was that both the 20 and the 25 were built upon an operating system <br />that had been kludged together by a programmer with no formal training. Because of a subtle bug<br />called a "race condition," a quick-fingered typist could accidentally configure the Therac-25 so the<br />electron beam would fire in high-power mode but with the metal X-ray target out of position. <br />At least five patients die; others are seriously injured.</span></p><p><span style="font-size:85%;"><br /></span></p><table width="1243" border="0" cellpadding="0" cellspacing="0"><tbody><tr></tr><tr><td height="569"><span style="font-size:85%;"><br /></span></td> <td colspan="5" valign="top"> <p><span style="font-size:85%;"><b>1988 -- Buffer overflow in Berkeley Unix finger daemon.</b> The first internet worm (the so-called<br /> Morris Worm) infects between 2,000 and 6,000 computers in less than a day by taking advantage<br />of a buffer overflow. The specific code is a function in the standard input/output library routine called<br />gets() designed to get a line of text over the network. Unfortunately, gets() has no provision to limit<br />its input, and an overly large input allows the worm to take over any machine to which it can connect. </span></p> <p><span style="font-size:85%;">Programmers respond by attempting to stamp out the gets() function in working code, but they <br />refuse to remove it from the C programming language's standard input/output library, where it remains<br />to this day. </span></p> <p><span style="font-size:85%;"><b>1988-1996 -- Kerberos Random Number Generator.</b> The authors of the Kerberos security system<br /> neglect to properly "seed" the program's random number generator with a truly random seed. As a<br />result, for eight years it is possible to trivially break into any computer that relies on Kerberos for<br />authentication. It is unknown if this bug was ever actually exploited. </span></p> <p><span style="font-size:85%;"><b>January 15, 1990 -- AT&T Network Outage</b>. A bug in a new release of the software that controls<br />AT&T's #4ESS long distance switches causes these mammoth computers to crash when they receive<br />a specific message from one of their neighboring machines -- a message that the neighbors send out<br />when they recover from a crash. </span></p> <p><span style="font-size:85%;">One day a switch in New York crashes and reboots, causing its neighboring switches to crash, then<br />their neighbors' neighbors, and so on. Soon, 114 switches are crashing and rebooting every six<br />seconds, leaving an estimated 60 thousand people without long distance service for nine hours. The<br />fix: engineers load the previous software release. </span></p> <p><span style="font-size:85%;"><b>1993 -- Intel Pentium floating point divide</b>. A silicon error causes Intel's highly promoted Pentium<br />chip to make mistakes when dividing floating-point numbers that occur within a specific range. For<br />example, dividing 4195835.0/3145727.0 yields 1.33374 instead of 1.33382, an error of 0.006 percent.<br />Although the bug affects few users, it becomes a public relations nightmare. With an estimated 3<br />million to 5 million defective chips in circulation, at first Intel only offers to replace Pentium chips for<br />consumers who can prove that they need high accuracy; eventually the company relents and agrees<br />to replace the chips for anyone who complains. The bug ultimately costs Intel $475 million. </span></p><p><span style="font-size:85%;"><br /></span></p><p><span style="font-size:85%;"><b>1995/1996 -- The Ping of Death.</b> A lack of sanity checks and error handling in the IP fragmentation<br />reassembly code makes it possible to crash a wide variety of operating systems by sending a<br />malformed "ping" packet from anywhere on the internet. Most obviously affected are computers<br />running Windows, which lock up and display the so-called "blue screen of death" when they receive<br />these packets. But the attack also affects many Macintosh and Unix systems as well. </span></p> <p><span style="font-size:85%;"><b>June 4, 1996 -- Ariane 5 Flight 501.</b> Working code for the Ariane 4 rocket is reused in the Ariane 5,<br />but the Ariane 5's faster engines trigger a bug in an arithmetic routine inside the rocket's flight<br />computer. The error is in the code that converts a 64-bit floating-point number to a 16-bit signed<br />integer. The faster engines cause the 64-bit numbers to be larger in the Ariane 5 than in the Ariane<br />4, triggering an overflow condition that results in the flight computer crashing. </span></p> <p><span style="font-size:85%;">First Flight 501's backup computer crashes, followed 0.05 seconds later by a crash of the primary<br /> computer. As a result of these crashed computers, the rocket's primary processor overpowers the<br />rocket's engines and causes the rocket to disintegrate 40 seconds after launch.</span></p> <p><span style="font-size:85%;"><b>November 2000 -- National Cancer Institute, Panama City.</b> In a series of accidents, therapy<br />planning software created by Multidata Systems International, a U.S. firm, miscalculates the proper<br />dosage of radiation for patients undergoing radiation therapy. </span></p> <p><span style="font-size:85%;">Multidata's software allows a radiation therapist to draw on a computer screen the placement of<br />metal shields called "blocks" designed to protect healthy tissue from the radiation. But the software<br />will only allow technicians to use four shielding blocks, and the Panamanian doctors wish to use five. </span></p> <p><span style="font-size:85%;">The doctors discover that they can trick the software by drawing all five blocks as a single large<br />block with a hole in the middle. What the doctors don't realize is that the Multidata software gives<br />different answers in this configuration depending on how the hole is drawn: draw it in one direction<br />and the correct dose is calculated, draw in another direction and the software recommends twice<br />the necessary exposure. </span></p> <span style="font-size:85%;">At least eight patients die, while another 20 receive overdoses likely to cause significant health <br />problems. The physicians, who were legally required to double-check the computer's calculations<br />by hand, are indicted for murder. </span></td></tr></tbody></table></td></tr></tbody></table>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-50459544470795577362009-08-10T12:31:00.000+05:302009-08-10T12:45:55.540+05:30Code Coverage - Typical features<span style="font-family: verdana;font-size:85%;" >he feature sets, quality and usability of code coverage products vary significantly.</span> <ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;"><i><b>Ant integration</b></i><br /></span><p class="text"><span style="font-size:85%;"> Probably most Java projects today are using Ant (or Maven) to manage their build process, including running unit tests (or functional tests).<br /></span> </p><center> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1249888506401&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1249887807&ga_hid=886361382&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Fcode-coverage%2Ftypical-features.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2F&lmt=1249888506&dt=1249888509206&cc=27&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=2&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center> <p class="text"><span style="font-size:85%;"> Thus, Ant integration is one of those features a code coverage tool cannot afford not to have. However, there are subtle differences in how nicely the code coverage related targets fit into an existing build script. Yes, we will see some examples later on. Of course, most tools also provide an alternative, standalone way of running the analysis, either from the command line or via a GUI application.<br /></span> </p></li><li><span style="font-size:85%;"><i><b>Report formats</b></i><br /></span> <p class="text"><span style="font-size:85%;"> Another obvious feature a code coverage tool must have is reports. Again, there are differences in the type and quality of supported reports. Some tools provide only textual summaries in Ant console output, others produce huge tables of names and numbers in HTML, and others produce nice pictures, others offer to render all this in PDF as well. We'll see examples of the main types of reports in the next section. </span></p></li><li><span style="font-size:85%;"><i><b>Source code linking</b></i><br /></span><p class="text"><span style="font-size:85%;">Somewhat related to the previous item, source code linking is something one can't live without once having gotten the taste of it. In practice, source code linking means that, as a part of the code coverage report, the tool has generated annotated copies of the actual source code, highlighting the parts which are not covered by your tests. I wouldn't be surprised if this particular feature was the single biggest benefactor in code coverage tools reaching critical mass. Seeing the code block that is causing your coverage to stay away from the "green" is a lot more efficient than seeing that a particular method contains some code that isn't covered by the tests. All of our selected examples include source code linking in their feature set.<br /></span> </p></li><li><span style="font-size:85%;"><i><b>Checks</b></i><br /></span><p class="text"><span style="font-size:85%;"> It doesn't take too long after someone has introduced a rule when someone else introduced the idea to enforce that rule. That has also happened to code coverage. Some tools provide a means to pull up the red flag if code coverage drops below a given level. In the context of Ant integration, the build script might typically fail the build until the tests have been reinforced to cover the naked parts of the code.<br /></span> </p></li><li><span style="font-size:85%;"><i><b>Historical reports</b></i><br /></span><p class="text"><span style="font-size:85%;"> Few tools provide a way to collect a history of coverage data and produce historical reports illustrating how your project's code coverage has been fluctuating in the course of time. This is also a nice feature, although some might consider it rather irrelevant.</span> </p></li></ul> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-BottomBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1249888506401&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&a2ids=%2C%2C&cids=%2C%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-BottomBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner%2COneStopTesting-BottomBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1249887807&ga_hid=886361382&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Fcode-coverage%2Ftypical-features.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2F&lmt=1249888506&dt=1249888509712&cc=27&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=2&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-75550937370809004682009-08-06T18:06:00.000+05:302009-08-06T18:13:03.874+05:30Testing Estimation Process<center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">Introduction</span><br /></h2></center><span style="font-family: verdana;font-size:85%;" ></span> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">In my opinion, one of the most difficult and critical activities in IT is the estimation process. I believe that it occurs because when we say that one project will be accomplished in such time by at such cost, it must happen.<br /></span></p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1249562464644&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1249562285&ga_hid=1738635689&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Festimation-process%2F&ref=http%3A%2F%2Fwww.onestoptesting.com%2Ffaqs%2Ffaq-categories%2Fdetails%2Ffaqs-in-configuration-management-28.asp&lmt=1249562464&dt=1249562465945&cc=28&u_h=1024&u_w=1280&u_ah=1024&u_aw=1280&u_cd=32&u_tz=330&u_his=6&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;"> If it does not happen, several things may follow: from peers' comments and senior management's warnings to being fired depending on the reasons and seriousness of the failure.<br /><br />Before even thinking of moving to Systems test at my organization, I always heard from the development group members that the estimations made by the Systems test group were too long and expensive. Then, when I arrived at my new seat, I tried to understand the testing estimation process.<br /><br />The testing estimation process in place was quite simple. The inputs for the process, provided by the development team, were: the size of the development team and the number of working days needed for building a solution before starting systems tests.<br /><br />The testing estimation process said that the number of testing engineers would be half of the number of development engineers and one third of the number of development working days.<br /></span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">A spreadsheet was created in order to find out the estimation and calculate the duration of tests and testing costs. They are based on the following formulas:<br /><br />Testing working days = (Development working days) / 3.<br /><br />Testing engineers = (Development engineers) / 2.<br /><br />Testing costs = Testing working days * Testing engineers * person daily costs.<br /><br />As the process was only playing with numbers, it was not necessary to register anywhere how the estimation was obtained.<br /><br />To exemplify how the process worked, if one development team said that to deliver a solution for systems testing it would need 4 engineers and 66 working days then, the systems test would need 2 engineers (half) and 21 working days (one third). So, the solution would be ready for delivery to the customer after 87 (66+21) working days.<br /><br />Just to be clear, in testing time, it was not included the time for developing the testcases and preparing the testing environment. Normally, it would need an extra 10 days for the testing team.</span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><h2 style="font-family: verdana; text-align: center;" class="sectionHeading"><span style="font-size:85%;">The Rules </span></h2><br /><span style="font-family: verdana;font-size:85%;" ><br /><b>1st Rule: Estimation shall be always based on the software requirements</b><br /></span> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">All estimation should be based on what would be tested, i.e., the software requirements.</span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> Normally, the software requirements were only established by the development team without any or just a little participation from the testing team. After the specification have been established and the project costs and duration have been estimated, the development team asks how long would take for testing the solution. The answer should be said almost right away. Then, the software requirements shall be read and understood by the testing team, too. Without the testing participation, no serious estimation can be considered. </span></p> <span style="font-family: verdana;font-size:85%;" ><b><br />2nd Rule: Estimation shall be based on expert judgment</b><br /></span> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Before estimating, the testing team classifies the requirements in the following categories:<br /><br />" Critical: The development team has little knowledge in how to implement it;<br /><br />" High: The development team has good knowledge in how to implement it but it is not an easy task;<br /><br />" Normal: The development team has good knowledge in how to implement.<br /><br />The experts in each requirement should say how long it would take for testing them. The categories would help the experts in estimating the effort for testing the requirements.</span> </p> <span style="font-family: verdana;font-size:85%;" ><b><br />3rd Rule: Estimation shall be based on previous projects</b><br /></span> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">All estimation should be based on previous projects. If a new project has similar requirements from a previous one, the estimation is based on that project.</span></p> <span style="font-family: verdana;font-size:85%;" ><b><br /><br />4th Rule: Estimation shall be based on metrics</b><br /></span> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">My organization has created an OPD, Organization Process Database, where the project metrics are recorded. We have recorded metrics from three years ago obtained from dozens of projects.<br /><br />The number of requirements is the basic information for estimating a testing project. From it, my organization has metrics that guide us to estimate a testing project. The table below shows the metrics used to estimate a testing project. The team size is 01 testing engineer.<br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><b><br /></b></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><b>Metric Value</b><br /><br />1.Number of testcases created for each requirement 4,53<br /><br />2.Number of testcases developed by Working day 14,47<br /><br />3.Number of testcases executed by Working day 10,20<br /><br />4.Number of ARs for testcase 0,77<br /><br />5.Number of ARs verified by Working day 24,64<br /><br />For instance, if we have a project with 70 functional requirements and a testing team size of 2 engineers, we reach the following estimates:<br /><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><b><br /></b></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><b>Metric Value</b><br /><br />Number of testcases - based on metric 1 317,10<br /><br />Preparation phase - based on metric 2 11 working days<br /><br />Execution phase - based on metric 3 16 working days<br /><br />Number of ARs - based on metric 4 244 ARs<br /><br />Regression phase - based on metric 5 6 working days<br /><br />The testing duration is estimated in 22 (16+6) working days. Plus, 11 working days for preparing it.</span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><b>5th Rule: Estimation shall never forget the past</b><br /></span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">I have not sent away the past. The testing team continues using the old process and the spreadsheet. After the estimation is done following the new rules, the testing team estimates again using the old process in order to compare both results.<br /></span> </p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1249562519586&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1249562285&ga_hid=964433312&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Festimation-process%2Fa.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Festimation-process%2Frules.asp&lmt=1249562519&dt=1249562521196&cc=28&u_h=1024&u_w=1280&u_ah=1024&u_aw=1280&u_cd=32&u_tz=330&u_his=8&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center> <p style="font-family: verdana;" class="text"> <span style="font-size:85%;">Normally, the results from the new estimate process are cheaper and faster than the old one in about 20 to 25%. If the testing team gets a different percentage, the testing team returns to the process in order to understand if something was missed.</span></p> <span style="font-family: verdana;font-size:85%;" ><b><br />6th Rule: Estimation shall be recorded</b><br /></span> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">All decisions should be recorded. It is very important because if requirements change for any reason, the records would help the testing team to estimate again. The testing team would not need to return for all steps and take the same decisions again. Sometimes, it is an opportunity to adjust the estimation made earlier.</span></p> <p style="font-family: verdana;" class="text"><span style="font-size:85%;"><b><br /></b></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><b>7th Rule: Estimation shall be supported by tools</b><br /></span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">A new spreadsheet has been created containing metrics that help to reach the estimation quickly. The spreadsheet calculates automatically the costs and duration for each testing phase.<br /><br />There is also a letter template that contains some sections such as: cost table, risks, and free notes to be filled out. This letter is sent to the customer. It also shows the different options for testing that can help the customer decides which kind of test he needs.</span> </p> <span style="font-family: verdana;font-size:85%;" ><b><br />8th Rule: Estimation shall always be verified</b><br /></span> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Finally, All estimation should be verified. I've created another spreadsheet for recording the estimations. The estimation is compared to the previous ones recorded in a spreadsheet to see if they have similar trend. If the estimation has any deviation from the recorded ones, then a re-estimation should be made.</span></p><p style="font-family: verdana;" class="text"><br /></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-81085083465529621702009-07-28T12:40:00.000+05:302009-07-28T12:43:11.813+05:30Test Matices Sample<span style="font-family: verdana;font-size:85%;" ><span style="font-size: 9pt;">You can measure the arrival and departure times of developers, if you have them clock in, but that won't tell you much since not all work is done in the office (and it doesn't mean that they're working when they're in the office). This is, however, still a metric.<br /> <br /> The same holds for a true "quality metric". The most familiar one is defects per thousand lines of (uncommented) code. But this metric assumes that:<br /> 1) you count the lines of code<br /> 2) the complexity of the code isn't an issue<br /> 3) the programmers aren't playing games (like using continuance characters<br /> so that what could have been written in one line isn't done in five lines)<br /> 4) all defects are uncovered in the code in a single pass<br /> 5) each defect discovered is all others<br /> 6) defects are uncovered in a linear manner between revisions or builds<br /> <br /> The fact is that first you need to know what your goal is. Then you need to<br /> discover or create a metric that will help you achieve that goal. Then you<br /> need to implement it and be prepared to adjust it.<br /> <br /> You can't use measurements (metrics) to find faults, at least not in software, so that's not a reasonable goal. You can use metrics to help determine if most of the defects have been discovered already. You can use them to tell you how much longer it will take to uncover a reasonable amount of defects. For either of these metrics you will need to know how previous projects of similar size and complexity (using similar languages, etc.) were done in order to get a reasonable comparison.</span><span style="font-size: 10pt;"><br /> <br /> </span><span style="font-size: 8pt;">Posted by Walter Gorlitz</span><span style="font-size: 10pt;"><br /> <br /> <table width="95%" border="1"> <tbody><tr> <td width="17%"><b><span style="font-size: 9pt;">Test Case: File Open #</span></b></td> <td width="21%"> <p align="center"><b><span style="font-size: 9pt;">Test<br /> Description</span></b> </p></td> <td width="16%"><b><span style="font-size: 9pt;">Test Cases/ Samples</span></b></td> <td width="8%"> <p align="center"><b><span style="font-size: 9pt;">Pass/<br /> Fail</span></b> </p></td> <td width="5%"> <p align="center"><b><span style="font-size: 9pt;">No. of<br /> Bugs</span></b> </p></td> <td width="17%"> <p align="center"><b><span style="font-size: 9pt;">Bug#</span></b> </p></td> <td width="16%"> <p align="center"><b><span style="font-size: 9pt;">Comments</span></b> </p></td> </tr> <tr> <td width="17%"> <p align="center"><span style="font-size: 8pt;">N/A</span> </p></td> <td width="21%"><span style="font-size: 8pt;">Setup for [Product Name]</span></td> <td width="16%"><span style="font-size: 8pt;">setup</span></td> <td width="8%"> <p align="center"><span style="font-size: 8pt;">-</span> </p></td> <td width="5%"> <p align="center"><span style="font-size: 8pt;">-</span> </p></td> <td width="17%"> <p align="center"><span style="font-size: 8pt;">-</span> </p></td> <td width="16%"> <p align="center"><span style="font-size: 8pt;"> </span> </p></td> </tr> <tr> <td width="17%"> <p align="center"><span style="font-size: 8pt;">1.1</span> </p></td> <td width="21%"><span style="font-size: 8pt;">Test that file types supported by the program can be opened</span></td> <td width="16%"> <p align="center"><span style="font-size: 8pt;">1.1</span> </p></td> <td width="8%"> <p align="center"><span style="font-size: 8pt;">P/F</span> </p></td> <td width="5%"> <p align="center"><span style="font-size: 8pt;">#</span> </p></td> <td width="17%"> <p align="center"><span style="font-size: 8pt;">#</span> </p></td> <td width="16%"> <p align="center"><span style="font-size: 8pt;"> </span> </p></td> </tr> <tr> <td width="17%"> <p align="center"><span style="font-size: 8pt;">1.2</span> </p></td> <td width="21%"><span style="font-size: 8pt;">Verify all the different ways to open file (mouse, keyboard and accelerated keys)</span></td> <td width="16%"> <p align="center"><span style="font-size: 8pt;"> 1.2</span> </p></td> <td width="8%"> <p align="center"><span style="font-size: 8pt;"> P/F</span> </p></td> <td width="5%"> <p align="center"><span style="font-size: 8pt;"> #</span> </p></td> <td width="17%"> <p align="center"><span style="font-size: 8pt;"> #</span> </p></td> <td width="16%"><span style="font-size: 8pt;"> </span></td> </tr> <tr> <td width="17%"> <p align="center"><span style="font-size: 8pt;">1.3</span> </p></td> <td width="21%"><span style="font-size: 8pt;">Verify files can be open from the local drives as well as network</span></td> <td width="16%"> <p align="center"><span style="font-size: 8pt;">1.3</span> </p></td> <td width="8%"> <p align="center"><span style="font-size: 8pt;"> P/F</span> </p></td> <td width="5%"> <p align="center"><span style="font-size: 8pt;">#</span> </p></td> <td width="17%"> <p align="center"><span style="font-size: 8pt;">#</span> </p></td> <td width="16%"><span style="font-size: 8pt;"> </span></td></tr></tbody></table></span><br /><br /><br /><b><span style="font-size: 8pt;">NOTE:</span></b><span style="font-size: 8pt;"> This is only a sample of a Test Matrices based on editor application. In real environments your Case's contents and layout most likely will be different, depends on your project and company requirements.</span><span style="font-size: 9pt;"><br /></span><br /><br /></span>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-51766166559841736642009-07-24T18:33:00.000+05:302009-07-24T19:04:53.074+05:30The Interview Guide for Testers<span style="font-family: verdana;font-size:85%;" >Software Testing is a discipline that requires varied skills. Interviewing <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >Software </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >Testers</span></span></a> for recruitment is not the same as interviewing for other Software Engineering discipline.<br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> This paper aims at uncovering the essential elements that the interviewers and interviewees need to be aware of during the Software Testing interviews. In my earlier paper, I had discussed about the essential skills that a tester needs to possess and they are as follows: Understanding, Listening, Observation, Test Planning, Test Designing, Test Execution, Defect Reporting and Analysis and Test Automation.<br /></span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">From the interviewer perspective, this paper discusses about how to evaluate software testers in an interview. From the interviewee perspective, this paper discusses about the necessary assertive skills that a tester needs to possess for getting through the interview.<br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">Evaluation of Understanding and Listening Skills</span></h2></center><span style="font-family: verdana;font-size:85%;" ><br />The first and foremost activity of Software Testing is to understand the system requirements of the <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >software</span></span></a> to be tested.<br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> The key references for these <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >system </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >requirements</span></span></a> in most of the projects are formal software requirements specification <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >documents</span></span></a> or software functional specification documents or the use case documents. In order to evaluate the tester’s skills in understanding these formal documents, a sample of this formal requirement specification document may be provided to the interviewee. The interviewer may request the interviewee to read/ understand the requirements and explain the same. The interviewee shall read/ understand the requirements and explain the same to the interviewer without any discrepancies and ambiguity.<br /></span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">If provided with any ambiguous requirements, the interviewee shall identify them and seek clarification from the interviewer. If provided with any missing requirements, the interviewee shall provide justification as to why he/she feels that there are few missing requirements and get them defined by the interviewer. If the interviewee finds any difficulty in understanding the requirements, he/ she may get them clarified from the interviewer. The interviewer shall welcome the assertive communication skills of the interviewee.<br /><br />Software Testing cannot be performed based on “assumed requirements” and all the requirements shall be explicitly defined (except for implicit requirements, which cannot be defined). The interviewee may emphasize this fundamental software testing standpoint during the interview. </span></p><span style="font-family: verdana;font-size:85%;" ><br /><br /></span><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">Requirement Example</span></h2></center><span style="font-family: verdana;font-size:85%;" ><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Let us take the case of the classical triangle software to be tested. The triangle software requires 3 positive integer inputs, which are the lengths of the 3 sides of the triangle (say A, B and C).<br /></span></p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1248442281821&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1248440702&ga_hid=1887426018&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Finterview-guide%2Frequirement-example.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Finterview-guide%2Fevaluation.asp&lmt=1248442281&dt=1248442283525&cc=27&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=4&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;"> The software evaluates the following the logical expression: A+B>C && B+C>A && C+A>B. If this logical expression evaluates to True, the software displays the status as green in the system console indicating that the inputs are valid lengths of the sides of the triangle and vice versa. </span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">The interviewer may provide the interviewee with a <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >document</span></span></a><a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >testing</span></span></a> standpoint during the interview. If the interviewee does not understand any of the sections in the requirement document or if the requirements are ambiguous, he/she shall get them clarified by the interviewer. The interviewer shall welcome those clarifications and shall not discourage the interviewee with respect to the clarifications sought. When the interviewee was asked to explain the software functionality, he/she shall explain it without any discrepancies. explaining the above mentioned requirement with few modifications to suit his/her need. To evaluate the understanding/ listening skills of the interviewee, the logical expression may not be mentioned in the document. When the interviewee was asked to read and understand the requirement, he/she shall raise this as an issue of missing requirement to the interviewer. The interviewee shall not assume anything about how the software validates the inputs and explain a new set of expressions such as C^2=A^2+B^2 (which applies only for right angle triangle) to the interviewer. “Defining Requirements” is always not a goal of Software Testing. The interviewee may emphasize this fundamental software </span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">Test Planning and Designing Skills </span></h2></center><span style="font-family: verdana;font-size:85%;" ><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Test Planning is an activity that focuses on establishing the path way for all the Software Testing activities.<br /></span></p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1248442313000&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1248440702&ga_hid=673757125&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Finterview-guide%2Ftest-planning.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Finterview-guide%2Frequirement-example.asp&lmt=1248442311&dt=1248442314579&cc=27&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=5&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;"> The <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >Software </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >Testers</span></span></a> shall keep abreast of his/her knowledge about the latest industrial trends of executing the software testing projects. The interviewer may request the interviewee to explain the industrial hot topics/ <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >news</span></span></a> and have a small talk about the same. The interviewer may not concentrate on asking straight forward questions such as “What is Regression Testing?”, “What is Defect Severity?”, “What is Functional Testing?”, “What is UAT?”, etc. These questions may be good for a university question paper but not during the recruitment interviews and that too exclusively. The interviews shall focus on the application side of it. The small talk/ discussion shall focus more on the “Why?”, “Where?” and “How?” of these terminologies along with “What?”. The interviewee shall be able to correlate the testing <a id="KonaLink5" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >methodologies</span></span></a> and techniques and devise the testing approach for the software under test and explain the same to the interviewer. For the triangle sample, the interviewee shall be able to devise the testing strategy and explain the same to the interviewer. The interviewer may request the interviewee to explain about the testing metrics that he/she need to capture in order to report the status and progress of the testing activities to the project management team.<br /></span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">The interviewer shall request the interviewee to explain about the test plan/ approach/ designing techniques for his/her current project. This is supposed to be illegal as these results in the dissemination of confidential information of the interviewee’s current organization to the public.<br /><br />To evaluate the test designing skills the interviewer may provide a sample requirement like the triangle sample and request the interviewee to design few tests for the testing the requirement and explain the techniques used for designing the tests. For the triangle sample, the interviewee shall use equivalence class partitioning, decision table technique and the multiple condition coverage technique for designing the tests. The interviewee shall be capable of explaining all these techniques and the tests to the interviewer. The interviewer may request the interviewee to write down few test cases for the sample requirements that he/she provided. The interviewee shall write the test cases clearly – the test steps shall have enough details up to the level of key presses and mouse clicks and the expected results shall be non-ambiguous.<br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">Test Execution and Defect Reporting Skills</span></h2></center><span style="font-family: verdana;font-size:85%;" ><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">To evaluate the test execution and defect reporting skills, the interviewer may request the interviewee to explain what he/she think to be the ideal process to be followed for test execution and defect reporting. As mentioned previously, the interviewer shall not request the interviewee to explain what he/she is currently following in his/her current project.<br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> The interviewer may initiate a small talk/ debate regarding the defect life cycle, defect attributes, defect <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >management </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >tools</span></span></a> and the test reporting tools. The interviewer may request the interviewee to write down a sample defect providing the defect details. The interviewee shall write the defect report clearly with detailed steps to reproduce, expected and actual results, non-ambiguously. </span></p> <span style="font-family: verdana;font-size:85%;" ><b>Test Automation Skills</b><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Test Automation is a wonderful phenomenon by which the <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >testing</span></span></a><br /><br />To evaluate the automation tool knowledge, the interviewer may initiate a small talk or discussion based on the respective <a id="KonaLink5" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >automation </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >tool</span></span></a>. As mentioned previously, the questions may not focus on the automation activities in the interviewees’ current project.<br />cost is drastically reduced. On the other side, if there is no proper planning for Automation Script Creation & Maintenance, there is a risk that the Automation Suite may get outdated and may not be usable. This renders ROI=0. The testers shall be aware of this business risk and identify the automation candidates accordingly. The interviewers may provide a set of test cases that includes automation candidates (simple & complex) and non-automation candidates, to the interviewees for identifying the automation candidates. The interviewees may ask for clarifications, if any, and they shall be able to identify the automation candidates successfully. The interviewer may request the interviewee to explain the various Automation metrics that he/she need to capture in order to report the Automation ROI and other figures of interest to the project management team.</span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><center style="font-family: verdana;"><h2 class="sectionHeading"><span style="font-size:85%;">Conclusion</span></h2></center><span style="font-family: verdana;font-size:85%;" ><br />The interviewer shall use several sample requirements and concentrate on evaluating the interviewees’ application of the software testing principles and techniques.<br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> This paper is purely a guideline and it talks about the basic things to focus on. The interviewers are requested to amend this guideline with their own approaches for conducting the interviews.<br /></span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">The interviewees shall reply answers aptly and boldly – bold enough to challenge the interviewer in case of any wrong questions put forth by the interviewer where he/she may expect you to put the question back to him in this case.</span></p>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-71552667033852616322009-07-15T18:31:00.000+05:302009-07-19T16:46:11.387+05:30UML<h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">Introduction</span></h2> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing, and documenting the artifacts of software <a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >systems</span></span></a>, as well as for business modeling and other non-software systems. The UML represents a collection of best engineering practices that have proven successful in the modeling of large and complex systems.1 The UML is a very important part of developing object oriented <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="border-bottom: 1px solid blue; color: blue ! important; font-weight: 400; position: static;color:#0000e0;" >software</span></span><span style="position: relative;" id="preLoadWrap2"><div style="position: absolute; z-index: 4000; top: -32px; left: -18px; display: none;" id="preLoadLayer2"><img style="border: 0px none ;" src="http://konac.kontera.com/javascript/lib/imgs/grey_loader.gif" /></div></span></a> and the software development process. The UML uses mostly graphical notations to express the design of software projects. Using the UML helps project teams communicate, explore potential designs, and validate the architectural design of the software.<br /></span></p><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">Goals of UML</span></h2><span style="font-family: verdana;font-size:85%;" >The primary goals in the design of the UML were: </span><ol style="font-family: verdana;" class="text"><li><span style="font-size:85%;">Provide <a id="KonaLink0" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >users</span></span></a> with a ready-to-use, expressive visual modeling language so they can develop and exchange meaningful models.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Provide extensibility and specialization mechanisms to extend the core concepts.</span></li><span style="font-size:85%;"><br /></span></ol> <center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247663146008&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1247663030&ga_hid=1954783438&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fgoals.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuml.asp&lmt=1247663145&dt=1247663147687&cc=26&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=7&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center> <p style="font-family: verdana;" class="text"> </p><ol style="font-family: verdana;" start="3"><li><p class="text"><span style="font-size:85%;">Be independent of particular <a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;"><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >programming </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >languages</span></span></a> and development processes.<br /></span></p></li><li><p class="text"><span style="font-size:85%;">Provide a formal basis for understanding the modeling language.<br /></span></p></li><li><p class="text"><span style="font-size:85%;">Encourage the growth of the OO tools market.<br /></span></p></li><li><p class="text"><span style="font-size:85%;">Support higher-level development concepts such as collaborations, frameworks, patterns and components.<br /></span></p></li><li><p class="text"><span style="font-size:85%;">Integrate best practices.</span></p></li></ol><span style="font-family: verdana;font-size:85%;" ><br /></span><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">Why Use UML?</span></h2> <p style="font-family: verdana;" class="text"><span style="font-size:85%;"> As the strategic value of software increases for many companies, the industry looks for techniques to automate the production of software and to improve quality and reduce cost and time-to-market. These techniques include component technology, visual <a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >programming</span></span></a>, patterns and frameworks. Businesses also seek techniques to manage the complexity of systems as they increase in scope and scale. </span></p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247663186553&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1247663030&ga_hid=1620308335&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuse.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuml.asp&lmt=1247663186&dt=1247663188061&cc=26&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=7&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;"> In particular, they recognize the need to solve recurring <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >architectural</span></span></a> problems, such as physical distribution, concurrency, replication, security, load balancing and fault tolerance. Additionally, the development for the World Wide Web, while making some things simpler, has exacerbated these architectural problems. The Unified Modeling Language (UML) was designed to respond to these needs.<br /></span></p><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">History of UML</span></h2> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Identifiable object-oriented modeling languages began to appear between mid-1970 and the late 1980s as various methodologists experimented with different approaches to object-oriented analysis and design. </span></p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247663208916&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1247663030&ga_hid=642170354&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fhistory.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuml.asp&lmt=1247663208&dt=1247663210326&cc=26&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=7&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">The number of identified modeling languages increased from less than 10 to more than 50 during the period between 1989-1994. Many users of OO methods had trouble finding complete satisfaction in any one modeling language, fueling the "method wars." By the mid-1990s, new iterations of these methods began to appear and these methods began to incorporate each other’s techniques, and a few clearly prominent methods emerged.<br /><br /></span> </p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> The development of UML began in late 1994 when Grady Booch and Jim Rumbaugh of Rational Software Corporation began their work on unifying the Booch and OMT (Object Modeling Technique) methods. In the Fall of 1995, Ivar Jacobson and his Objectory company joined Rational and this unification effort, merging in the OOSE (Object-Oriented Software Engineering) method.<br /><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> As the primary authors of the Booch, OMT, and OOSE methods, Grady Booch, Jim Rumbaugh, and Ivar Jacobson were motivated to create a unified modeling language for three reasons. First, these methods were already evolving toward each other independently. It made sense to continue that evolution together rather than apart, eliminating the potential for any unnecessary and gratuitous differences that would further confuse users. Second, by unifying the semantics and notation, they could bring some stability to the object-oriented marketplace, allowing projects to settle on one mature modeling language and letting tool builders focus on delivering more useful features. Third, they expected that their collaboration would yield improvements in all three earlier methods, helping them to capture lessons learned and to address problems that none of their methods previously handled well.<br /><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> The efforts of Booch, Rumbaugh, and Jacobson resulted in the release of the UML 0.9 and 0.91 documents in June and October of 1996. During 1996, the UML authors invited and received feedback from the general community. They incorporated this feedback, but it was clear that additional focused attention was still required.<br />While Rational was bringing UML together, efforts were being made on achieving the broader goal of an industry standard modeling language. In early 1995, Ivar Jacobson (then Chief Technology Officer of Objectory) and Richard Soley (then Chief Technology Officer of OMG) decided to push harder to achieve standardization in the methods marketplace. In June 1995, an OMG-hosted meeting of all major methodologists (or their representatives) resulted in the first worldwide agreement to seek methodology standards, under the aegis of the OMG process.<br /><br />During 1996, it became clear that several organizations saw UML as strategic to their business. A Request for Proposal (RFP) issued by the Object Management Group (OMG) provided the catalyst for these organizations to join forces around producing a joint RFP response. Rational established the UML Partners consortium with several organizations willing to dedicate resources to work toward a strong UML 1.0 definition. Those contributing most to the UML 1.0 definition included: Digital Equipment Corp., HP, i-Logix, IntelliCorp, IBM, ICON Computing, MCI Systemhouse, Microsoft, Oracle, Rational Software, TI, and Unisys. This collaboration produced UML 1.0, a modeling language that was well defined, expressive, powerful, and generally applicable. This was submitted to the OMG in January 1997 as an initial RFP response.<br /><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"> In January 1997 IBM, ObjecTime, Platinum Technology, Ptech, Taskon, Reich Technologies and Softeam also submitted separate RFP responses to the OMG. These companies joined the UML partners to contribute their ideas, and together the partners produced the revised UML 1.1 response. The focus of the UML 1.1 release was to improve the clarity of the UML 1.0 semantics and to incorporate contributions from the new partners. It was submitted to the OMG for their consideration and adopted in the fall of 1997.<br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">Writing a use case</span></h2> <span style="font-family: verdana;font-size:85%;" ><b>Degree of detail</b><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Alistair Cockburn, in <i>Writing Effective Use Cases</i>, identified three levels of detail in writing use cases:</span></p><span style="font-family: verdana;font-size:85%;" ><br /></span><ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;">A brief use case consists of a few sentences summarizing the use case. It can be easily inserted in a spreadsheet cell, and allows the other columns in the spreadsheet to record priority, technical complexity, release number, and so on.</span></li><span style="font-size:85%;"><br /></span><center> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247663263175&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1247663030&ga_hid=2030925571&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fwriting-cases.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuml.asp&lmt=1247663263&dt=1247663264674&cc=26&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=7&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center><li><span style="font-size:85%;">A casual use case consists of a few paragraphs of text, summarizing the use case.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">A fully dressed use case is a formal <a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >document</span></span></a> based on a detailed template with fields for various sections; and it is the most common understanding of the meaning of a use case. Fully dressed use cases are discussed in detail in the next section on use case templates.</span></li><span style="font-size:85%;"><br /></span></ul> <span style="font-family: verdana;font-size:85%;" ><b>Appropriate detail</b><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Some software development processes do not require anything more than a simple use case to define requirements. However, some other development processes require detailed use cases to define requirements. The larger and more complex the project, the more likely that it will be necessary to use detailed use cases.<br /><br />The level of detail in a use case often differs according to the progress of the project. The initial use cases may be brief, but as the development process unfolds the use cases become ever more detailed. This reflects the different requirements of the use case. Initially they need only be brief, because they are used to summarize the <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="border-bottom: 1px solid blue; color: blue ! important; font-weight: 400; position: static;color:transparent;" >business </span><span class="kLink" style="border-bottom: 1px solid blue; color: blue ! important; font-weight: 400; position: static;color:transparent;" >requirement</span></span><span style="position: relative;" id="preLoadWrap2"><div style="position: absolute; z-index: 4000; top: -32px; left: -18px; display: none;" id="preLoadLayer2"><img style="border: 0px none ;" src="http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif" /></div></span></a> from the point of view of users. However, later in the process, <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >software </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >developers</span></span></a> need far more specific and detailed guidance.<br /><br />Rational Unified Process invites developers to write a brief use case description in the use case diagram, with a casual description as comments and a detailed description of the flow of events in a textual analysis. All those can usually be input into the use <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >case </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >tool</span></span></a> (e.g., a UML Tool, SysML Tool), or can be written separately in a <a id="KonaLink5" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="border-bottom: 1px solid blue; color: blue ! important; font-weight: 400; position: static;color:transparent;" >text </span><span class="kLink" style="border-bottom: 1px solid blue; color: blue ! important; font-weight: 400; position: static;color:transparent;" >editor</span></span><span style="position: relative;" id="preLoadWrap5"><div style="position: absolute; z-index: 4000; top: -32px; left: -18px; display: none;" id="preLoadLayer5"><img style="border: 0px none ;" src="http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif" /></div></span></a>.</span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><span style="font-family: verdana;font-size:85%;" ><br /></span><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">Use case Templates</span></h2> <span style="font-family: verdana;font-size:85%;" ><b>Degree of detail</b><br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">There is no standard template for documenting detailed use cases. There are a number of competing schemes, and individuals are encouraged to use templates that work for them or the project they are on. Standardization within each project is more important than the detail of a specific template. There is, however, considerable agreement about the core sections; beneath differing terminologies and orderings there is an underlying similarity between most use cases.<br /><br /></span></p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247663298673&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1247663030&ga_hid=813212144&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuse-case-templates.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuml.asp&lmt=1247663298&dt=1247663300241&cc=26&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=7&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center><span style="font-family: verdana;font-size:85%;" > Typical sections include: </span><ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;"><b>Use case name</b><br /><br />A use case name provides a unique identifier for the use case. It should be written in verb-noun format (e.g., Borrow Books, Withdraw Cash), should describe an achievable goal (e.g., Register User is better than Registering User) and should be sufficient for the end user to understand what the use case is about.<br /><br />Goal-driven use case analysis will name use cases according to the actor's goals, thus ensuring use cases are strongly user centric. Two to three words is the optimum. If more than four words are proposed for a name, there is usually a shorter and more specific name that could be used.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;"><b>Version</b><br /><br />Often a version section is needed to inform the reader of the stage a use case has reached. The initial use case developed for business analysis and scoping may well be very different from the evolved version of that use case when the software is being developed. Older versions of the use case may still be current <a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >documents</span></span></a>, because they may be valuable to different <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >user </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >groups</span></span></a>.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;"><b>Goal</b><br /><br />Without a goal a use case is useless. There is no need for a use case when there is no need for any actor to achieve a goal. A goal briefly describes what the user intends to achieve with this use case.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;"><b>Summary</b><br /><br />A summary section is used to capture the essence of a use case before the main body is complete. It provides a quick overview, which is intended to save the reader from having to read the full contents of a use case to understand what the use case is about. Ideally, a summary is just a few sentences or a paragraph in length and includes the goal and principal actor.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;"><b>Actors</b><br /><br />An actor is someone or something outside the system that either acts on the system – a primary actor – or is acted on by the system – a secondary actor. An actor may be a person, a device, another system or sub-system, or time. Actors represent the different roles that something outside has in its relationship with the system whose functional requirements are being specified. An individual in the <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >real </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >world</span></span></a></span> can be represented by several actors if they have several different roles and goals in regards to a system.</li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;"><b>Preconditions</b><br /><br />A preconditions section defines all the conditions that must be true (i.e., describes the state of the system) for the trigger (see below) to meaningfully cause the initiation of the use case. That is, if the system is not in the state described in the preconditions, the behavior of the use case is indeterminate.<br /><br />Note that the preconditions are not the same thing as the "trigger" (see below): the mere fact that the preconditions are met does NOT initiate the use case.<br /><br />However, it is theoretically possible both that a use case should be initiated whenever condition X is met and that condition X is the only aspect of the system that defines whether the use case can meaningfully start. If this is really true, then condition X is both the precondition and the trigger, and would appear in both sections. But this is rare, and the analyst should check carefully that they have not overlooked some preconditions which are part of the trigger. If the analyst has erred, the module based on this use case will be triggered when the system is in a state the developer has not planned for, and the module may fail or behave unpredictably.</span></li><span style="font-size:85%;"><br /></span></ul> <span style="font-family: verdana;font-size:85%;" ><br /></span><ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;"><b>Triggers</b><br /><br />A 'triggers' section describes the event that causes the use case to be initiated. This event can be external, temporal or internal. If the trigger is not a simple true "event" (e.g., the customer presses a button), but instead "when a set of conditions are met", there will need to be a triggering process that continually (or periodically) runs to test whether the "trigger conditions" are met: the "triggering event" is a signal from the trigger process that the conditions are now met.<br /><br />There is varying practice over how to describe what to do when the trigger occurs but the preconditions are not met.</span></li><span style="font-size:85%;"><br /></span><ul class="text"><li><span style="font-size:85%;">One way is to handle the "error" within the use case (as an exception). Strictly, this is illogical, because the "preconditions" are now not true preconditions at all (because the behaviour of the use case is determined even when the preconditions are not met).</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Another way is to put all the preconditions in the trigger (so that the use case does not run if the preconditions are not met) and create a different use case to handle the problem. Note that if this is the local standard, then the use case template theoretically does not need a preconditions section!</span></li></ul><li><span style="font-size:85%;"><b>Basic course of events</b><br /><br />At a minimum, each use case should convey a <i>primary scenario</i>, or typical course of events, also called "basic flow" or "happy flow". The main basic course of events is often conveyed as a set of usually numbered steps. For example:</span></li><span style="font-size:85%;"><br /></span><ul class="text"><li><span style="font-size:85%;">The system prompts the user to log on.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">The user enters his name and password.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">The system verifies the logon information..</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">The system logs user on to system.</span></li></ul><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;"><b>Alternative paths</b><br /><br />Use cases may contain secondary paths or alternative scenarios, which are variations on the main theme. Each tested rule may lead to an alternate path and when there are many rules the permutation of paths increases rapidly, which can lead to very complex documents. Sometimes it is better to use conditional logic or activity diagrams to describe use case with many rules and conditions.<br /><br />Exceptions, or what happens when things go wrong at the system level, may also be described, not using the alternative paths section but in a section of their own. Alternative paths make use of the numbering of the basic course of events to show at which point they differ from the basic scenario, and, if appropriate, where they rejoin. The intention is to avoid repeating information unnecessarily.<br /><br />An example of an alternative path would be:</span></li><ol class="text"><li><span style="font-size:85%;">The system recognizes cookie on user's machine.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Go to step 4 (Main path)</span></li><span style="font-size:85%;"><br /></span><p class="text"><span style="font-size:85%;">An example of an exception path would be:</span></p><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">The system does not recognize user's logon information</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Go to step 1 (Main path)</span></li></ol><span style="font-size:85%;"><br /></span><p class="text"><span style="font-size:85%;">According to Anthony J H Simons and Ian Graham (who openly admits he got it wrong - using 2000 use cases at Swiss Bank), alternate paths were not originally part of use cases. Instead, each use case represented a <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >single</span></span></a> user's interaction with the system. In other words, each use case represented one possible path through the system. Multiple use cases would be needed before designs based on them could be made. In this sense, use cases are for exploration, not documentation.<br /><br />An Activity diagram can give an overview of the basic path and alternatives path.</span></p><li><span style="font-size:85%;"><b>Postconditions</b><br /><br />The <i>post-conditions</i> section describes what the change in state of the system will be after the use case completes. Post-conditions are guaranteed to be true when the use case ends.</span></li><span style="font-size:85%;"><br /><br /></span><li><span style="font-size:85%;"><b>Business rules</b><br /><br />Business rules are written (or unwritten) rules or policies that determine how an organization conducts its business with regard to a use case. Business rules are a special kind of requirement. Business rules may be specific to a use case or apply across all the use cases, or across the entire business. Use cases should clearly reference BRs that are applicable and where they are implemented.<br /><br />Business Rules should be encoded in-line with the Use <a id="KonaLink5" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >Case </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >logic</span></span></a></span> and execution may lead to different post conditions. E.g. Rule2. that a cash withdraw will lead to an update of the account and a transaction log leads to a post condition on successful withdrawal - but only if Rule1 which says there must be sufficient funds tests as true.</li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;"><b>Notes</b><br /><br />Experience has shown that however well-designed a use case template is, the analyst will have some important information that does not fit under a specific heading. Therefore all good templates include a section (eg "Notes to Developers") that allows less-structured information to be recorded.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;"><b>Author and date</b><br /><br />This section should list when a version of the use case was created and who documented it. It should also list and date any versions of the use case from an earlier stage in the development which are still current documents. The author is traditionally listed at the bottom, because it is not considered to be essential information; use cases are intended to be collaborative endeavors and they should be jointly owned.</span></li></ul><span style="font-family: verdana;font-size:85%;" ><br /></span><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">Benefits of use cases</span></h2><span style="font-family: verdana;font-size:85%;" ><br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Use cases are a mature model to capture user (person or <a id="KonaLink1" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >system</span></span></a>) proffered interaction requirements and begin to establish some of the functional requirements before construction of a new system begins. Proponents prefer them to large, monolithic <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >documents</span></span></a> which they believe cannot be simultaneously complete and meaningful, and regard them as an excellent technique for capturing the functional requirements of a system. Proponents cite these advantages:</span></p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247663336206&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1247663030&ga_hid=2050153515&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fbenefits.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuml.asp&lmt=1247663336&dt=1247663337809&cc=26&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=7&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center> <ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;">Well written Use cases have proven to be easily understandable by business users, and thus to act as a bridge between them and <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >software </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >developers</span></span></a>.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Uniquely identified use cases can be traced back to business requirements or stakeholder needs.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Use case partitioning can be used to organise and structure the requirements model, permitting common behaviour to be factored out.</span></li></ul> <ul style="font-family: verdana;" class="text"><span style="font-size:85%;">></span><li><span style="font-size:85%;">Use cases can serve as a basis for the estimating, scheduling, and validating efforts.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Use cases are reusable within a project - Citation needed A use case (like anything) can evolve at each iteration, from a method of capturing requirements, to development guidelines for programmers, to a test case and finally into user <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >documentation</span></span></a>.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Use cases make it easy to take a staged delivery approach to projects; they can be relatively easily added and removed from a software project as priorities change.</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Use cases that represent interactions between a user and a system (others will represent interactions between systems) make it possible for user interface designers to become involved in the development process before, or in parallel with, software developers (although use cases are also said to discourage inappropriate premature design).</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Use cases and use case diagrams recorded using UML can be maintained with widely available <a id="KonaLink5" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >CASE </span><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >tools</span></span></a>, and thus be fully integrated with other analysis and design deliverables created using a CASE tool. The result is a complete requirements, design, and implementation repository.<i>Citation needed</i></span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Test cases (system, user acceptance and functional) can be directly derived from use cases</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">Use cases are critical for the effective execution of Performance Engineering.</span></li></ul><span style="font-family: verdana;font-size:85%;" ><br /><br /></span><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">Limitations of use cases</span></h2><span style="font-family: verdana;font-size:85%;" ><br /><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">Use cases have limitations:</span></p> <ul style="font-family: verdana;" class="text"><li><p class="text"><span style="font-size:85%;">Use case flows are not well suited to easily capturing non-interaction based requirements of a <a id="KonaLink2" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >system</span></span></a> (such as algorithm or <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >mathematical</span></span></a> requirements) or non-functional requirements (such as platform, performance, timing, or safety-critical aspects). These are better specified declaratively elsewhere.</span></p></li><span style="font-size:85%;"><br /></span><center> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247663361903&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1247663030&ga_hid=1490618446&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Flimitations.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuml.asp&lmt=1247663359&dt=1247663363418&cc=26&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=7&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center><p class="text"> </p><li><span style="font-size:85%;">Use cases templates do not automatically ensure clarity. Clarity depends on the skill of the writer(s).</span></li><span style="font-size:85%;"><br /></span><li><p class="text"><span style="font-size:85%;">There is a learning curve involved in interpreting use cases correctly, for both end users and developers. As there are no fully standard definitions of use cases, each group must gradually evolve its own interpretation. Some of the relations, such as extends, are ambiguous in interpretation and can be difficult for stakeholders to understand.</span></p></li><span style="font-size:85%;"><br /></span><p class="text"> </p><li><p class="text"><span style="font-size:85%;">Proponents of Extreme <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >Programming</span></span></a> often consider use cases too needlessly document-centric, preferring to use the simpler approach of a user story.</span></p></li></ul> <p style="font-family: verdana;" class="text"> </p><ul style="font-family: verdana;" class="text"><li><p class="text"><span style="font-size:85%;">Use case developers often find it difficult to determine the level of user interface (UI) dependency to incorporate in a use case. While use case theory suggests that UI not be reflected in use cases, it can be awkward to abstract out this aspect of design, as it makes the use cases difficult to visualize.</span></p></li><span style="font-size:85%;"><br /></span><li><p class="text"><span style="font-size:85%;">Use cases can be over-emphasized. In <i>Object Oriented Software Construction</i> (2nd edition), Bertrand Meyer discusses issues such as driving the system design too literally from use cases and using use cases to the exclusion of other potentially valuable requirements analysis techniques.</span></p></li><span style="font-size:85%;"><br /></span><li><p class="text"><span style="font-size:85%;">Use cases have received some interest as a starting point for test design. Some use case literature, however, states that use case pre and postconditions should apply to all scenarios of a use case (i.e., to all possible paths through a use case) which is limiting from a test design standpoint. If the postconditions of a use case are so general as to be valid for all possible use case scenarios, they are likely not to be useful as a basis for specifying expected behavior in test design. For example, the outputs and final state of a failed attempt to withdraw cash from an ATM are not the same as a successful withdrawal: if the postconditions reflect this, they too will differ; if the postconditions don’t reflect this, then they can’t be used to specify the expected behavior of tests. An alternate perspective on use case pre & postconditions more suitable for test design based on model-based specification</span></p></li></ul><span style="font-family: verdana;font-size:85%;" ><br /></span><h2 style="font-family: verdana;" class="sectionHeading"><span style="font-size:85%;">Use Case Based Testing</span></h2><span style="font-family: verdana;font-size:85%;" ><br /><br /><b>Overview:</b></span> <p style="font-family: verdana;" class="text"><span style="font-size:85%;"> IBM Research has developed Use Case Based Testing (UCBT), which is a technique for generating test cases and recommended configurations for <a id="KonaLink3" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >system</span></span></a> level testing. In our approach, testers build a test model based on the standard UML notions of use cases, actors, and the <a id="KonaLink4" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="font-weight: 400; position: static;color:#b00000;" >relationships</span></span></a> between these elements. The use cases are enhanced with additional information, including the inputs from actors, the outputs to the actors, and how the use case affects the state of the system.<br /></span></p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script><script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247663395759&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1633699805.1247576548&ga_sid=1247663030&ga_hid=913557197&ga_fc=true&url=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuse-case-based-testing.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Ftest-cases%2Fuml.asp&lmt=1247663395&dt=1247663397593&cc=26&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=7&u_java=true&u_nplug=14&u_nmime=52&flash=0"></script> </center><span style="font-family: verdana;font-size:85%;" ><br />Newly developed algorithms use this model to generate a test suite which provides a specified level of coverage of each use case. We also generate workload configurations that combine the test cases according to requirements specified in the model. The generation algorithm performs minimization to reduce the number of test cases required to cover the system to the specified level. The workload configurations are based on desired percentages associated with each actor that the tester provides. These features form a powerful basis for model-based test case generation.<br /><br /><b>What testing phase does UCBT address?</b><br /><br />UCBT addresses phases where the tester is interested in exploring behavior that flows through multiple use cases, which are typically the late function, system, and solution phases of the test life cycle. In late function level test, the tester has tested the use cases individually, and is now interested in looking at combinations of the use cases. System test addresses the situation when all required functionality for the system is present, and the tester seeks to ensure the proper functioning of the system as a whole. An important component of system test is also ensuring that the system can handle customer-like scenarios and workloads. Solution test addresses the situation in which several complete systems are combined to provide complex functionality through some process that involves the systems. These processes can be captured, modeled, and tested using UCBT.<br /><b>What does the tester do in UCBT? </b><br /><br />To do UCBT, the tester needs to identify four things:<br /></span> <ol style="font-family: verdana;" class="text"><li><span style="font-size:85%;">the use cases of interest,</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">the actors involved in using the system,</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">the input, output, and system effects for the use cases,</span></li><span style="font-size:85%;"><br /></span><li><span style="font-size:85%;">the flows of interest between the use cases.</span></li><span style="font-size:85%;"><br /></span></ol> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">UA use case is a semantically meaningful function that provides some value from the user's point of view. For example, saving a file in a word processing system would be represented by the <a id="KonaLink5" target="undefined" class="kLink" style="text-decoration: underline ! important; position: static;" ><span style="font-weight: 400; position: static;color:#b00000;" ><span class="kLink" style="border-bottom: 1px solid blue; color: blue ! important; font-weight: 400; position: static;color:transparent;" >Save </span><span class="kLink" style="border-bottom: 1px solid blue; color: blue ! important; font-weight: 400; position: static;color:transparent;" >File</span></span><span style="position: relative;" id="preLoadWrap5"><div style="position: absolute; z-index: 4000; top: -32px; left: -18px; display: none;" id="preLoadLayer5"><img style="border: 0px none ;" src="http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif" /></div></span></a> use case. Each use case can have input parameters associated with it, and for each parameter, a set of logical partitions of the values that parameter can take may be identified. Finally, the use cases can be connected using flows that describe a sequence of use case that are performed to accomplish some goal.<br /><br /></span></p> <span style="font-family: verdana;font-size:85%;" ><b>What is produced by UCBT Tool?</b><br /></span><p style="font-family: verdana;" class="text"><span style="font-size:85%;">UCBT produces two types of test cases. The first type are abstract test cases, which are not executable. These are suitable for incorporation in a test plan and are provided in structured English. They show the ordering of use cases to be performed and the inputs and expected results that each use case should have during the test. The second type of test cases are in a format known as ATS, which can be used to create executable test cases using another tool known as TCBeans. TCBeans was developed by IBM Research in Haifa. The test suite produced by UCBT is minimized in size by performing a two pass optimization based upon the input parameter interactions that the tester specifies, as well as the flows of interest. This ensures that the number of test cases is reasonable, so execution and evaluation can be done with a feasible amount of effort.</span></p><span style="font-family: verdana;font-size:85%;" ><br /><br /><br /><br /></span>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-84451772578942242662009-07-14T18:22:00.000+05:302009-07-20T10:08:56.333+05:30General Testing Interview Questions<p style="font-family: verdana;font-family:verdana;" ><span style="font-size:85%;"><b>1.What is 'Software Quality Assurance'?</b><br /></span> </p><p style="font-family: verdana;font-family:verdana;" class="text"><span style="font-size:85%;">Software QA involves the entire software development Process - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with.<br /></span> </p><center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script> <script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247576032148&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1201289678.1247576032&ga_sid=1247576032&ga_hid=1752360306&ga_fc=false&url=http%3A%2F%2Fwww.onestoptesting.com%2Finterview-question%2Fgeneral%2F&ref=http%3A%2F%2Fwww.onestoptesting.com&lmt=1247576033&dt=1247576033851&cc=379&oe=windows-1252&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=2&u_java=true&u_nplug=0&u_nmime=0&flash=9.0.28.0"></script> </center> <p style="font-family: verdana;font-family:verdana;" class="text"><span style="font-size:85%;">It is oriented to 'prevention'. (See the Books section for a list of useful books on <a class="kLink" oncontextmenu="return false;" id="KonaLink1" onmouseover="adlinkMouseOver(event,this,1);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,1);" onmouseout="adlinkMouseOut(event,this,1);" target="_top"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);font-size:10;" ><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >Software </span><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >Quality </span><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >Assurance</span></span></a>.)</span></p><span style="font-family: verdana;font-family:verdana;font-size:85%;" ><br /><br /><b>2.What is 'Software Testing'?</b><br /></span> <p style="font-family: verdana;font-family:verdana;" class="text"><span style="font-size:85%;">Testing involves operation of a system or application under controlled conditions and evaluating the results (eg, 'if the user is in interface A of the application while using hardware B, and does C, then D should happen'). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should. It is oriented to 'detection'.<br /><br />Organizations vary considerably in how they assign responsibility for QA and testing. Sometimes they're the combined responsibility of one group or individual. Also common are project teams that include a mix of testers and developers who work closely together, with overall QA processes monitored by project managers. It will depend on what best fits an organization's size and business structure.</span></p><span style="font-family: verdana;font-family:verdana;font-size:85%;" ><br /><br /><b>3. What are some recent major computer system failures caused by software bugs?</b><br /><br /></span> <p style="font-family: verdana;font-family:verdana;" class="text"><span style="font-size:85%;">* Media reports in January of 2005 detailed severe problems with a $170 million high-profile U.S. government IT systems project. Software testing was one of the five major problem areas according to a report of the commission reviewing the project. Studies were under way to determine which, if any, portions of the project could be salvaged.<br /><br />* In July 2004 newspapers reported that a new government welfare management system in Canada costing several hundred million dollars was unable to handle a simple benefits rate increase after being put into live operation. Reportedly the original contract allowed for only 6 weeks of acceptance testing and the system was never tested for its ability to handle a rate increase.<br /><br />* Millions of bank accounts were impacted by errors due to installation of inadequately tested software code in the transaction processing system of a major North American bank, according to mid-2004 news reports. Articles about the incident stated that it took two weeks to fix all the resulting errors, that additional problems resulted when the incident drew a large number of e-mail <a class="kLink" oncontextmenu="return false;" id="KonaLink2" onmouseover="adlinkMouseOver(event,this,2);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,2);" onmouseout="adlinkMouseOut(event,this,2);" target="_top"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);font-size:10;" ><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >phishing </span><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >attacks</span></span></a> against the bank's customers, and that the total cost of the incident could exceed $100 million.<br /><br />* A bug in site management software utilized by companies with a significant percentage of worldwide web traffic was reported in May of 2004. The bug resulted in performance problems for many of the sites simultaneously and required disabling of the software until the bug was fixed.<br /><br />* According to news reports in April of 2004, a software bug was determined to be a major contributor to the 2003 Northeast blackout, the worst power system failure in North American history. The failure involved loss of electrical power to 50 million customers, forced shutdown of 100 power plants, and economic losses estimated at $6 billion. The bug was reportedly in one utility company's vendor-supplied power monitoring and management system, which was unable to correctly handle and report on an unusual confluence of initially localized events. The error was found and corrected after examining millions of lines of code.<br /><br />* In early 2004, news reports revealed the intentional use of a software bug as a counter-espionage tool. According to the report, in the early 1980's one nation surreptitiously allowed a hostile nation's espionage service to steal a version of sophisticated industrial software that had intentionally-added flaws. This eventually resulted in major industrial disruption in the country that used the stolen flawed software.<br /><br />* A major U.S. retailer was reportedly hit with a large government fine in October of 2003 due to web site errors that enabled customers to view one anothers' online orders.<br /><br />* News stories in the fall of 2003 stated that a manufacturing company recalled all their transportation products in order to fix a software problem causing instability in certain circumstances. The company found and reported the bug itself and initiated the recall procedure in which a software upgrade fixed the problems.<br /><br />* In January of 2001 newspapers reported that a major European railroad was hit by the aftereffects of the Y2K bug. The company found that many of their newer trains would not run due to their inability to recognize the date '31/12/2000'; the trains were started by altering the control system's date settings.<br /><br />* News reports in September of 2000 told of a software vendor settling a lawsuit with a large mortgage lender; the vendor had reportedly delivered an <a class="kLink" oncontextmenu="return false;" id="KonaLink3" onmouseover="adlinkMouseOver(event,this,3);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,3);" onmouseout="adlinkMouseOut(event,this,3);" target="_top"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);font-size:10;" ><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >online </span><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >mortgage</span></span></a><br /><br />* In early 2000, major problems were reported with a new computer system in a large suburban U.S. public school district with 100,000+ students; problems included 10,000 erroneous report cards and students left stranded by failed class registration systems; the district's CIO was fired. The school district decided to reinstate it's original 25-year old system for at least a year until the bugs were worked out of the new system by the software vendors.<br /><br /><br />* In October of 1999 the $125 million NASA Mars Climate Orbiter spacecraft was believed to be lost in space due to a simple data conversion error. It was determined that spacecraft software used certain data in English units that should have been in metric units. Among other tasks, the orbiter was to serve as a communications relay for the Mars Polar Lander mission, which failed for unknown reasons in December 1999. Several investigating panels were convened to determine the process failures that allowed the error to go undetected.<br /><br />* Bugs in software supporting a large commercial high-speed data network affected 70,000 business customers over a period of 8 days in August of 1999. Among those affected was the electronic trading system of the largest U.S. futures exchange, which was shut down for most of a week as a result of the outages.<br /><br />* January 1998 news reports told of software problems at a major U.S. telecommunications company that resulted in no charges for long distance calls for a month for 400,000 customers. The problem went undetected until customers called up with questions about their bills. processing system that did not meet specifications, was delivered late, and didn't work. </span></p><span style="font-family: verdana;font-family:verdana;font-size:85%;" ><br /><br /><b>4.Why is it often hard for management to get serious about quality assurance?</b><br /><br /></span> <p style="font-family: verdana;font-family:verdana;" class="text"><span style="font-size:85%;">* Solving problems is a high-visibility process; preventing problems is low-visibility. This is illustrated by an old parable: In ancient China there was a family of healers, one of whom was known throughout the land and employed as a physician to a great lord.<br /><br /><b>5.Why does software have bugs?</b><br /><br />* Miscommunication or no communication - as to specifics of what an application should or shouldn't do (the application's requirements).<br /><br />* Software complexity - the complexity of current software applications can be difficult to comprehend for anyone without experience in modern-day software development. Multi-tiered applications, client-server and distributed applications, data communications, enormous relational databases, and sheer size of applications have all contributed to the exponential growth in software/<a class="kLink" oncontextmenu="return false;" id="KonaLink4" onmouseover="adlinkMouseOver(event,this,4);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,4);" onmouseout="adlinkMouseOut(event,this,4);" target="_top"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);font-size:10;" ><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >system </span><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >complexity</span></span></a>.<br /><br />* Programming errors - programmers, like anyone else, can make mistakes.<br /><br />* Changing requirements (whether documented or undocumented) - the end-user may not understand the effects of changes, or may understand and request them anyway - redesign, rescheduling of engineers, effects on other projects, work already completed that may have to be redone or thrown out, hardware requirements that may be affected, etc. If there are many minor changes or any major changes, known and unknown dependencies among parts of the project are likely to interact and cause problems, and the complexity of coordinating changes may result in errors. Enthusiasm of engineering staff may be affected. In some fast-changing business environments, continuously modified requirements may be a fact of life. In this case, management must understand the resulting risks, and QA and test engineers must adapt and plan for continuous extensive testing to keep the inevitable bugs from running out of control - see 'What can be done if requirements are changing continuously?' in Part 2 of the FAQ. Also see information about 'agile' approaches such as XP, also in Part 2 of the FAQ.<br /><br />* Time pressures - scheduling of software projects is difficult at best, often requiring a lot of guesswork. When deadlines loom and the crunch comes, mistakes will be made.<br /><br />* egos - people prefer to say things like:<br /><br />* * 'no problem'<br /><br />* * 'piece of cake'<br /><br />* * 'I can whip that out in a few hours'<br /><br />* * 'it should be easy to update that old code'<br /><br />* instead of:<br /><br />* * 'that adds a lot of complexity and we could end up making a lot of mistakes'<br /><br />* * 'we have no idea if we can do that; we'll wing it'<br /><br />* * 'I can't estimate how long it will take, until I take a close look at it'<br /><br />* * 'we can't figure out what that old spaghetti code did in the first place'<br /><br />If there are too many unrealistic 'no problem's', the result is bugs.<br /><br />* Poorly documented code - it's tough to maintain and modify code that is badly written or poorly documented; the result is bugs. In many organizations management provides no incentive for programmers to document their code or write clear, understandable, maintainable code. In fact, it's usually the opposite: they get points mostly for quickly turning out code, and there's job security if nobody else can understand it ('if it was hard to write, it should be hard to read').<br /><br />* Software development tools - <a class="kLink" oncontextmenu="return false;" id="KonaLink5" onmouseover="adlinkMouseOver(event,this,5);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,5);" onmouseout="adlinkMouseOut(event,this,5);" target="_top"><span style="font-weight: 400; position: static; color: rgb(176, 0, 0);font-size:10;" ><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >visual </span><span class="kLink" style="font-weight: 400; position: relative; color: rgb(176, 0, 0);font-size:10;" >tools</span></span></a>, class libraries, compilers, scripting tools, etc. often introduce their own bugs or are poorly documented, resulting in added bugs.</span> </p><span style="font-family: verdana;font-family:verdana;font-size:85%;" ><br /><br /><b>6.How can new Software QA processes be introduced in an existing organization?</b><br /><br /></span> <p style="font-family: verdana;font-family:verdana;" class="text"><span style="font-size:85%;">* A lot depends on the size of the organization and the risks involved. For large organizations with high-risk (in terms of lives or property) projects, serious management buy-in is required and a formalized QA process is necessary.<br /><br />* Where the risk is lower, management and organizational buy-in and QA implementation may be a slower, step-at-a-time process. QA processes should be balanced with productivity so as to keep bureaucracy from getting out of hand.<br /><br />* For small groups or projects, a more ad-hoc process may be appropriate, depending on the type of customers and projects. A lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among customers, managers, developers, and testers.<br /><br />* The most value for effort will often be in (a) requirements management processes, with a goal of clear, complete, testable requirement specifications embodied in requirements or design documentation, or in 'agile'-type environments extensive continuous coordination with end-users, (b) design inspections and code inspections, and (c) post-mortems/retrospectives. </span></p><p style="font-family: verdana;font-family:verdana;" ><span style="font-size:85%;"><br /><br /><b>7.What is verification? validation?</b><br /><br /></span> </p><p style="font-family: verdana;font-family:verdana;" class="text"><span style="font-size:85%;">* Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings. Validation typically involves actual testing and takes place after verifications are completed. The term 'IV & V' refers to Independent Verification and Validation.<br /><br /><b>8.What is a 'walkthrough'?</b><br /><br /></span> </p><p style="font-family: verdana;font-family:verdana;" class="text"><span style="font-size:85%;">* A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required.</span></p>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-59935023498898004852009-07-10T17:42:00.000+05:302009-07-10T17:48:56.543+05:30Priority and Severity of the Bug<p style="color: rgb(0, 0, 0); font-family: verdana;" class="text"><span style="font-size:85%;">Let’s peek in on a discussion in a bug triage meeting.<br /><br />Tim, the <a class="kLink" oncontextmenu="return false;" id="KonaLink1" onmouseover="adlinkMouseOver(event,this,1);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,1);" onmouseout="adlinkMouseOut(event,this,1);" href="http://www.onestoptesting.com/articles/priority-severity/#" target="_top"><span style="font-weight: 400; font-size: 10px; color: blue ! important; font-family: verdana; position: static;"><span class="kLink" style="font-weight: 400; font-size: 10px; position: relative;">marketing </span><span class="kLink" style="font-weight: 400; font-size: 10px; position: relative;">manager</span></span></a>, is shaking his head. “That’s a high on the severity scale. It’s really bad, guys. You have to make it a high.”<br /><br /></span> </p><center style="color: rgb(0, 0, 0); font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script> <script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247228174168&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1902368081.1247228174&ga_sid=1247228174&ga_hid=628632586&ga_fc=false&url=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Fpriority-severity%2F&ref=http%3A%2F%2Fwww.onestoptesting.com%2F&lmt=1247228176&dt=1247228176214&cc=379&oe=windows-1252&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=3&u_java=true&u_nplug=0&u_nmime=0&flash=9.0.28.0"></script> </center> <p style="color: rgb(0, 0, 0); font-family: verdana;" class="text"><span style="font-size:85%;">Jordan, the development manager, is barely containing her frustration. Her eye is starting to twitch as she replies, “No, Tim. That’s not all that bad. It’s an inconvenience, I agree, but there’s an easy workaround.”<br /><br />“Inconvenience?!?” Tim says a bit more loudly than he intended. “You call not being able to print an inconvenience?!? That’s a disaster!”<br />“Yes, I call not being able to print from one particular type of printer without installing an upgraded driver from the vendor’s <a class="kLink" oncontextmenu="return false;" id="KonaLink2" onmouseover="adlinkMouseOver(event,this,2);" style="position: static; text-decoration: underline ! important; color: rgb(0, 0, 0);" onclick="adlinkMouseClick(event,this,2);" onmouseout="adlinkMouseOut(event,this,2);" href="http://www.onestoptesting.com/articles/priority-severity/#" target="_top"><span style="font-weight: 400; font-size: 10px; color: blue ! important; font-family: verdana; position: static;"><span class="kLink" style="font-weight: 400; font-size: 10px; position: relative;">website</span></span></a> an inconvenience. The user just needs…”<br /><br />“I know what the <a class="kLink" oncontextmenu="return false;" id="KonaLink3" onmouseover="adlinkMouseOver(event,this,3);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,3);" onmouseout="adlinkMouseOut(event,this,3);" href="http://www.onestoptesting.com/articles/priority-severity/#" target="_top"><span style="font-weight: 400; font-size: 10px; color: blue ! important; font-family: verdana; position: static;"><span class="kLink" style="font-weight: 400; font-size: 10px; position: relative;">user</span></span></a> needs,” Tim cut in. “The user needs to be able to print out of the box! You can fix this in our code, right?”<br /><br />Jordan nods, “Yes, but we’d just be working around the vendor’s…”<br /><br />“Then fix it.” Tim stood over Jordan, glaring.<br /><br />“But it’s a medium at best!” Jordan objected. “The user isn’t losing any data, doesn’t have to <a class="kLink" oncontextmenu="return false;" id="KonaLink4" onmouseover="adlinkMouseOver(event,this,4);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,4);" onmouseout="adlinkMouseOut(event,this,4);" href="http://www.onestoptesting.com/articles/priority-severity/#" target="_top"><span style="font-weight: 400; font-size: 10px; color: blue ! important; font-family: verdana; position: static;"><span class="kLink" style="font-weight: 400; font-size: 10px; position: relative;">reboot</span></span></a>, isn’t crashing. They just have to update a <a class="kLink" oncontextmenu="return false;" id="KonaLink5" onmouseover="adlinkMouseOver(event,this,5);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,5);" onmouseout="adlinkMouseOut(event,this,5);" href="http://www.onestoptesting.com/articles/priority-severity/#" target="_top"><span style="font-weight: 400; font-size: 10px; color: blue ! important; font-family: verdana; position: static;"><span class="kLink" style="font-weight: 400; font-size: 10px; position: relative;">driver</span></span></a>.”<br /><br />This argument could continue forever. I’ve seen many arguments like this go on and on. What’s really happening here? Why are Tim and Jordan about to be at each other’s throats?<br /></span></p><p style="color: rgb(0, 0, 0); font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="color: rgb(0, 0, 0); font-family: verdana;" class="text"><span style="font-size:85%;"><b>Priority is Business; Severity is Technical</b><br />Tim is looking at business priority:<br /></span> </p><center style="color: rgb(0, 0, 0); font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script> <script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247228232854&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1825564012.1247228233&ga_sid=1247228233&ga_hid=241590291&ga_fc=false&url=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Fpriority-severity%2Fpriority.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Fpriority-severity%2F&lmt=1247228236&dt=1247228236854&cc=379&oe=windows-1252&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=4&u_java=true&u_nplug=0&u_nmime=0&flash=9.0.28.0"></script> </center> <p style="color: rgb(0, 0, 0); font-family: verdana;" class="text"><span style="font-size:85%;">“How important is it to the business that we fix the bug?” Jordan is looking at technical severity: “How nasty is the bug from a technical perspective?” These two questions sometimes arrive at the same answer: a high severity bug is often also high priority, but not always. Allow me to suggest some definitions.<br /><b>Severity is levels:</b><br />* <i>Critical:</i> the <a class="kLink" oncontextmenu="return false;" id="KonaLink4" onmouseover="adlinkMouseOver(event,this,4);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,4);" onmouseout="adlinkMouseOut(event,this,4);" href="http://www.onestoptesting.com/articles/priority-severity/priority.asp#" target="_top"><span style="font-weight: 400; font-size: 10px; color: blue ! important; font-family: verdana; position: static;"><span class="kLink" style="border-bottom: 1px solid blue; font-weight: 400; font-size: 10px; position: relative; background-color: transparent;">software</span></span><span id="preLoadWrap4" style="position: relative;"> <div id="preLoadLayer4" style="display: none; z-index: 4000; left: -18px; position: absolute; top: -22px;"><img style="border: 0px none ;" src="http://kona.kontera.com/javascript/lib/imgs/grey_loader.gif" width="22" height="22" /></div></span></a> will not run<br />* <i>High:</i> unexpected fatal errors (includes crashes and <a class="kLink" oncontextmenu="return false;" id="KonaLink5" onmouseover="adlinkMouseOver(event,this,5);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,5);" onmouseout="adlinkMouseOut(event,this,5);" href="http://www.onestoptesting.com/articles/priority-severity/priority.asp#" target="_top"><span style="font-weight: 400; font-size: 10px; color: blue ! important; font-family: verdana; position: static;"><span class="kLink" style="font-weight: 400; font-size: 10px; position: relative;">data </span><span class="kLink" style="font-weight: 400; font-size: 10px; position: relative;">corruption</span></span></a>)<br />* <i>Medium:</i> a feature is malfunctioning<br />* <i>Low:</i> a cosmetic issue<br /><br />Now you see why Jordan was arguing that the Print bug was a medium: a feature was malfunctioning.<br /><br /><b>Priority levels:</b><br />* <i>Now:</i> drop everything and take care of it as soon as you see this (usually for blocking bugs)<br />* <i>P1:</i> fix before next build to test<br />* <i>P2:</i> fix before final release<br />* <i>P3:</i> we probably won’t get to these, but we want to track them anyway<br /><br />And now you can see why Tim was so adamant that the issue was a high. From his perspective, it was a P1 matter.<br /><br />They’re both right. It’s of medium severity, but P1 to fix.</span></p><p style="color: rgb(0, 0, 0); font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="color: rgb(0, 0, 0); font-family: verdana;" class="text"><span style="font-size:85%;"><b>Priority and Severity Don’t Mix</b><br />In response to Johanna’s column last week, some people suggested using both severity and priority to come up with a composite risk number.<br /></span> </p><center style="color: rgb(0, 0, 0); font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script> <script src="http://pubads.g.doubleclick.net/gampad/ads?correlator=1247228330790&output=json_html&callback=GA_googleSetAdContentsBySlotForSync&impl=s&prev_afc=3&a2ids=%2C&cids=%2C&client=ca-pub-4686307991865625&slotname=OneStopTesting-MidBanner&page_slots=OneStopTesting-TopBanner%2COneStopTesting-TopBanner-2%2COneStopTesting-MidBanner&cust_params=&cookie=ID%3Dc60c1ef587e73e39%3AT%3D1247228015%3AS%3DALNI_Maf2buZbo1RWSX16lTcZf7BmgW4dQ&ga_vid=1736333421.1247228331&ga_sid=1247228331&ga_hid=192519333&ga_fc=false&url=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Fpriority-severity%2Fmix.asp&ref=http%3A%2F%2Fwww.onestoptesting.com%2Farticles%2Fpriority-severity%2Fpriority.asp&lmt=1247228332&dt=1247228332618&cc=379&oe=windows-1252&u_h=1024&u_w=1280&u_ah=990&u_aw=1280&u_cd=32&u_tz=330&u_his=5&u_java=true&u_nplug=0&u_nmime=0&flash=9.0.28.0"></script> </center> <p style="color: rgb(0, 0, 0); font-family: verdana;" class="text"><span style="font-size:85%;">While this intuitively sounds like a way to resolve the priority-severity divide, I suggest using such an approach with extreme caution. It’s multiplying apples by oranges in an attempt to quantify bananas. Risk is yet a third type of information.<br /><br />The risk associated with any bug depends on the severity of the issue, certainly. But it also depends on the likelihood that the user will run into it as well as the possible losses that might occur. I don’t attempt to quantify all this when assessing the severity of an issue. In fact, I think that in most cases assessing the risk of a single issue takes more time than it’s worth. Only for potentially poisonous bugs involving dangerous fixes do I really want to weigh the risk of fixing it against the risk of not fixing it.<br /></span></p><p style="color: rgb(0, 0, 0); font-family: verdana;" class="text"><span style="font-size:85%;"><b>Establish Work Precedence</b><br />The best way to avoid confusion about what comes first is to ensure everyone in the organization takes their cues for work precedence from priority and nowhere else. Developers fix P1 defects first. Testers verify P1 fixes first. Technical writers document P1 issues first. Everyone works in priority order: the priority reflects importance to the business. Saying, “This bug is more severe than that one so I’ll work on it first” is as bad as saying, “I like this bug more, so I’ll work on it first.” The severity rating is technical information used by managers as a piece of the formula in determining the priority rating. The priority rating is the final word on the order in which the work is done by programmers, testers, and everyone else.<br /><br />The ultimate lesson here, regardless of the terms or levels you use to categorize your bugs, is that any classification scheme will only be effective if everyone agrees on definitions. So perhaps that’s the very first question to ask when an argument is brewing about severity, priority, or risk: “Help me understand exactly what information you’re using from each defect record and how you’re using it?”<br /></span></p>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-63988161898559174042009-07-09T18:08:00.000+05:302009-07-09T18:17:43.824+05:30Software Bugs And Spec Bugs<p class="MsoNormal" style="font-family:verdana;"><span style="font-size:85%;">Let's assume that the error message wasn't displayed. In this case, we have a <b style="">classic case of a </b><b style="">software bug; i.e., a bug born because of a mismatch between the <u>actual behavior</u> of the software and the <u>expected behavior</u> (which is usually specified in the spec)</b>.</span></p> <p class="MsoNormal" style="font-family:verdana;"><span style="font-size:85%;">If you paid a little bit of attention when you read item 2.1., you surely noticed (joke) that it wasn't clear what kind of error message is expected to be displayed-i.e., the decision on the actual text of error message is up to the programmer, and he or she can write code that will produce:</span></p> <p class="MsoNormal" style="text-indent: 0.5in;font-family:verdana;"><span style="font-size:85%;">- a NONinformative, irritating message: "<b style="">Error</b>", leaving the user to wonder what he or she has done wrong and cultivating a feeling of guilt in him or her, OR</span></p> <p class="MsoNormal" style="text-indent: 0.5in;font-family:verdana;"><span style="font-size:85%;">- an easy-to-understand message: "<b style="">Oops, error on page. ZIP code should have 5 digits</b>".</span></p> <p class="MsoNormal" style="font-family:verdana;"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p> <p class="MsoNormal" style="font-family:verdana;"><span style="font-size:85%;">Formally, the programmer will be right in both cases, because the specification doesn't elaborate about the text of the error message.</span></p><table face="verdana" color="white" style="width: 675px; height: 584px;" bg="" align="center" border="0" cellpadding="0" cellspacing="0"><tbody> <tr style="color: rgb(0, 0, 0);"> <td style="vertical-align: top;"><br /></td><td> <div style="border: 1pt solid black; padding: 1pt 4pt;"><span style="font-size:85%;">In early days of start-up when software changes very often, there is no need<br />to include <u>precise</u> text of error messages into the spec. The <b style="">idea</b> about error<br />message will do. For example: "Error message should state that ZIP code should<br />consist of 5 digits".</span></div> <p class="MsoNormal"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p> <p class="MsoNormal"><span style="font-size:85%;">Here we have a <b style="">situation where the spec itself is buggy</b>, because </span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p><p class="MsoNormal" style="text-indent: 0.5in;"><span style="font-size:85%;">- we reasonably <b style="">expect</b> that spec to give us details about the error message, and</span></p> <p class="MsoNormal" style="text-indent: 0.5in;"><span style="font-size:85%;">- the <b style="">actual</b> spec doesn't give us those details. </span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p> <p class="MsoNormal"><span style="font-size:85%;">Let's call this situation "<b style="">spec bug</b>." </span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p> <div style="border: 1pt solid black; padding: 1pt 4pt;"> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><b style="">Brain positioning<o:p></o:p></b></span></p><p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;">Each found bug (both in software and in specs) must be filed into the bug tracking system.<br /></span></p><p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;">There should be no exceptions. Bug reporting is one of the most important parts of our profession.</span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;">We'll have a separate lecture to talk about bug reporting and tracking.</span></p></div> <p class="MsoNormal"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p> <div style="border: 1pt solid black; padding: 1pt 4pt;"> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><b style="">Brain positioning<o:p></o:p></b></span></p><p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;">From the start, you must understand one very important thing: <b style="">when<br /></b></span></p><p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><b style="">you file a bug against someone, it doesn't mean that you hate<br /></b></span></p><p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><b style="">or disrespect that person. </b>It simply means: "I have found mismatch<br /></span></p><p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;">between actual and expected. Please, fix the problem."</span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><span style="font-size:12;"><o:p> </o:p></span></span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;">If somebody takes a bug personally, you must have the respect and<br /></span></p><p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;">patience to explain to him or her that there is nothing personal here -<br /></span></p><p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;">this is just a part of your job.</span></p></div></td></tr> <tr> <td style="vertical-align: top;"><br /></td><td> <table width="100%" bgcolor="#f0f1cf" cellpadding="0" cellspacing="0"> </table></td></tr></tbody></table>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-60913211228747184932009-07-09T18:02:00.000+05:302009-07-09T18:06:02.094+05:30Three Conditions Of A Bug's Existence<p style="font-family: verdana;" class="MsoNormal"><span style="font-size:85%;">A bug exists only if ALL of the following three conditions are met:</span></p> <p style="font-family: verdana;" class="MsoNormal"><span style="font-size:85%;"><b style=""><span style="font-size: 12pt;"><o:p> </o:p></span></b></span></p> <p style="font-family: verdana;" class="MsoNormal"><span style="font-size:85%;"><b style=""><span style=""> </span>1. We know the expected result<o:p></o:p></b></span></p> <p style="font-family: verdana;" class="MsoNormal"><span style="font-size:85%;"><b style=""><span style=""> </span>2. We know the actual result<o:p></o:p></b></span></p> <p style="font-family: verdana;" class="MsoNormal"><span style="font-size:85%;"><b style=""><span style=""> </span>3. We know that the actual result deviates from the expected result<br /></b></span></p><p style="font-family: verdana;" class="MsoNormal"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="MsoNormal"><span style="font-size:85%;">Every time you see a mismatch between the actual and expected, label that situation with the word "bug." As time goes on, you'll develop a habit, which will gradually grow into a reflex. Please note that for the sake of this training, it doesn't matter how futile, cheap, or temporary your expectations are - the main thing here is to gain the skill of <b style="">automatic bug recognition</b>.</span></p><div style="border: 1pt solid black; padding: 1pt 4pt; font-family: verdana;"> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><b style="">Example<o:p></o:p></b></span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><span style="font-size: 12pt;"><o:p> </o:p></span></span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;">Here are some more bugs from real life:</span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><span style="font-size: 12pt;"><o:p> </o:p></span></span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><span style=""> </span>1. A nice face backed by an ugly personality.</span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><span style=""> </span>2. Parrots say the nastiest words at absolutely inappropriate times.</span></p> <p class="MsoNormal" style="border: medium none ; padding: 0in;"><span style="font-size:85%;"><span style=""> </span>3. Hollywood story: reach fame and drink yourself to rehab.</span></p><span style="font-size:85%;"><br /></span><!--content end--></div>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-2300344160070181872009-07-08T13:11:00.000+05:302009-07-08T13:49:37.056+05:30The Big Bang Model<span style="font-size:85%;"><br /><span style="font-family: verdana;">The Big Bang is built upon three main tenets: </span></span><ol style="font-family: verdana;" class="text"><li><span style="font-size:85%;">the universe used to be very hot </span></li><li><span style="font-size:85%;">the universe used to be very dense </span></li><li><span style="font-size:85%;">the universe is expanding (which is why it isn't so hot or dense anymore) </span></li></ol> <center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script> </center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Note that the basic Big Bang Model does NOT say anything about the following questions: </span></p> <ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;">will the universe collapse again, or expand forever? <a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj53qBYAcCVXZUhPjAyIhn2H03OOXRFugaaGFpQKyAXLWZ9cBQ7SZhLXDnJnz1hgTurn79E5iQmcwLmJjpIJAbryb9HUeEDNzqhVHSRqTkS4sF3ywetA7rVjZBWiWQmkzRvL6w5lZCw_eCH/s1600-h/heavier.gif"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 118px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj53qBYAcCVXZUhPjAyIhn2H03OOXRFugaaGFpQKyAXLWZ9cBQ7SZhLXDnJnz1hgTurn79E5iQmcwLmJjpIJAbryb9HUeEDNzqhVHSRqTkS4sF3ywetA7rVjZBWiWQmkzRvL6w5lZCw_eCH/s320/heavier.gif" alt="" id="BLOGGER_PHOTO_ID_5355992339477423618" border="0" /></a></span></li><li><span style="font-size:85%;">is space curved or flat? </span></li><li><span style="font-size:85%;">how old is the universe? </span></li><li><span style="font-size:85%;">what is the matter density in the universe? </span></li><li><span style="font-size:85%;">what about dark matter? </span></li><li><span style="font-size:85%;">is there some mysterious "repulsive" force on large scales? </span></li><li><span style="font-size:85%;">how did galaxies form? </span></li></ul> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Some of these questions all depend upon the values of certain parameters in the model, which we may derive from observations. Others have nothing to do with the Big Bang itself. </span></p> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Our understanding of the laws of nature permit us to track the physical state of the universe back to a certain point, when the density and temperature were REALLY high. Beyond that point, we don't know exactly how matter and radiation behave. Let's call that moment the <b>starting point</b>. It doesn't mean that the universe "began" at that time, it just means that we don't know what happened before that point.</span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;">One of the primary successes of the Big Bang theory is its explanation for the chemical composition of the universe. Recall that the universe is mostly hydrogen and helium, with very small amounts of heavier elements. How does this relate to the Big Bang? </span></p> <center style="font-family: verdana;"> <script type="text/javascript"> GA_googleFillSlot("OneStopTesting-MidBanner"); </script> </center> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Well, a long time ago, the universe was <b>hot</b> and <b>dense</b>. When the temperature is high enough (a few thousand degrees), atoms lose all their electrons; we call this state of matter, a mix of nuclei and electrons, a <b>fully-ionized plasma</b>. If the temperature is even higher (millions of degrees), then the nuclei break up into fundamental particles, and one is left with a "soup" of fundamental particles: </span></p> <ul style="font-family: verdana;" class="text"><li><span style="font-size:85%;">protons </span></li><li><span style="font-size:85%;">neutrons </span></li><li><span style="font-size:85%;">electrons </span></li></ul> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Now, if the "soup" is very dense, then these particles will collide with each other frequently. Occasionally, groups of protons and neutrons will stick together to form nuclei of light elements ... but under extremely high pressure and temperature, the nuclei are broken up by subsequent collisions. The Big Bang theory postulates that the entire universe was so hot at one time that it was filled with this proton-neutron-electron "soup." </span></p> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">But the Big Bang theory then states that, as the universe expanded, both the density and temperature dropped. As the temperature and density fell, collisions between particles became less violent, and less frequent. There was a brief "window of opportunity" when protons and neutrons could collide hard enough to stick together and form light nuclei, yet not suffer so many subsequent collisions that the nuclei would be destroyed. This "window" appeared about three minutes after the starting point, and lasted for a bit less than a minute. </span></p> <p style="font-family: verdana;" class="text"><span style="font-size:85%;">Which nuclei would form under these conditions? Experiments with particle colliders have shown us that most of the possible nuclei are <b>unstable</b>, meaning they break up all by themselves, or <b>fragile</b>, meaning they are easily broken by collisions</span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEihSTaBce8QfpYirAN4QrnxaZpeuy1czAmLkVduzza5_pdzzNEixLi5svUtc-mDMjGBB-QtgABGXsQr2T4P4-Aik0P0o5wE1xnz-qazb4S5HVClh55o4qqjR-xt3ulxv9JVVUnWIZ2ik5pm/s1600-h/hy_he.gif"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 167px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEihSTaBce8QfpYirAN4QrnxaZpeuy1czAmLkVduzza5_pdzzNEixLi5svUtc-mDMjGBB-QtgABGXsQr2T4P4-Aik0P0o5wE1xnz-qazb4S5HVClh55o4qqjR-xt3ulxv9JVVUnWIZ2ik5pm/s320/hy_he.gif" alt="" id="BLOGGER_PHOTO_ID_5355991750502855506" border="0" /></a></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text" u92lg="0" ai0vu="1"><span style="font-size:85%;">Helium (the ordinary sort, with 2 protons and 2 neutrons) is by far the most stable and robust compound nucleus. Deuterium (one proton and one neutron) is easily destroyed, and so is helium-3 (2 protons, one neutron). </span></p> <p style="font-family: verdana;" class="text" u92lg="0" ai0vu="1"><span style="font-size:85%;">So, it seems that this period of hot, dense plasma would create a lot of helium. Could it create other, heavier elements, too?<br /></span></p><p style="font-family: verdana;" class="text" u92lg="0" ai0vu="1"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p><p style="font-family: verdana;" class="text" u92lg="2" ai0vu="1"><span style="font-size:85%;">Detailed models of Big Bang <b u92lg="0" ai0vu="1">nucleosynthesis</b> predict that the brief "window of opportunity" lasted only a minute or two. After that, about three and a half minutes after the starting point, the temperature and density dropped so much that collisions between particles were rare, and of such low energy that the electric forces of repulsion between positively-charged nuclei prevented fusion. The result is </span></p> <ul style="font-family: verdana;" class="text"><li u92lg="0" ai0vu="1"><span style="font-size:85%;">lots of hydrogen </span></li><li u92lg="0" ai0vu="1"><span style="font-size:85%;">some helium (ordinary helium-4) </span></li><li u92lg="0" ai0vu="1"><span style="font-size:85%;">tiny bits of deuterium </span></li><li u92lg="0" ai0vu="1"><span style="font-size:85%;">tiny bits of lithium </span></li><li u92lg="0" ai0vu="1"><span style="font-size:85%;">not much else </span></li></ul><p style="font-family: verdana;" class="text"><span style="font-size:85%;"><br /></span></p>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-43443000914605869172009-07-03T10:13:00.000+05:302009-07-03T10:14:44.947+05:30Testing Plan Template<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5CDIPTI%7E1.THA%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C05%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt;} h2 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:2; font-size:14.0pt; font-family:Arial; font-style:italic;} p.MsoCommentText, li.MsoCommentText, div.MsoCommentText {mso-style-noshow:yes; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.MsoHeader, li.MsoHeader, div.MsoHeader {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:center 3.0in right 6.0in; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.MsoFooter, li.MsoFooter, div.MsoFooter {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:center 3.0in right 6.0in; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.TemplateNote, li.TemplateNote, div.TemplateNote {mso-style-name:"Template Note"; margin-top:0in; margin-right:0in; margin-bottom:4.0pt; margin-left:0in; mso-pagination:none; page-break-after:avoid; background:#F3F3F3; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.bulls, li.bulls, div.bulls {mso-style-name:bulls; margin-top:3.0pt; margin-right:0in; margin-bottom:0in; margin-left:18.25pt; margin-bottom:.0001pt; text-indent:-18.25pt; mso-pagination:widow-orphan; mso-list:l1 level1 lfo2; tab-stops:list .25in; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.colhead, li.colhead, div.colhead {mso-style-name:colhead; margin-top:3.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; text-align:center; mso-pagination:widow-orphan; font-size:12.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; font-weight:bold; mso-bidi-font-weight:normal;} p.Heading1, li.Heading1, div.Heading1 {mso-style-name:Heading1; mso-style-parent:"Heading 1"; margin-top:12.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:20.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:black; font-weight:bold; mso-bidi-font-weight:normal;} p.Heading2, li.Heading2, div.Heading2 {mso-style-name:Heading2; mso-style-parent:"Heading 2"; margin-top:6.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:2; font-size:14.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; font-weight:bold;} p.heading3, li.heading3, div.heading3 {mso-style-name:heading3; margin-top:6.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; font-weight:bold;} span.msoIns {mso-style-type:export-only; mso-style-name:""; text-decoration:underline; text-underline:single; color:teal;} span.msoDel {mso-style-type:export-only; mso-style-name:""; text-decoration:line-through; color:red;} @page Section1 {size:8.5in 11.0in; margin:99.35pt 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-page-numbers:1; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1533374330; mso-list-type:hybrid; mso-list-template-ids:-332757522 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.25in; mso-level-number-position:left; margin-left:.25in; text-indent:-.25in; font-family:Symbol;} @list l1 {mso-list-id:2117019602; mso-list-type:hybrid; mso-list-template-ids:1814692874 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l1:level1 {mso-level-number-format:bullet; mso-level-style-link:bulls; mso-level-text:; mso-level-tab-stop:.25in; mso-level-number-position:left; margin-left:.25in; text-indent:-.25in; font-family:Symbol;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </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-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <p class="Heading1"><a name="ProjectOverview"></a><a name="_Toc524404851"></a><a name="_Toc446993005"><span style=""><span style="">Project Overview</span></span></a></p> <p class="TemplateNote">(Optional) In this section, briefly discuss the project background and objectives. The appropriate information can be copied from the Project Definition document.</p> <p class="Heading1"><a name="_Toc454961463"></a><a name="_Toc424135905"></a><a name="_Toc416585815"></a><a name="_Toc401103630"></a><a name="_Toc446993007"></a><a name="TestingRisks"></a><a name="_Toc524404852"></a><a name="_Toc501170237"></a><a name="_Toc501167723"><span style=""><span style=""><span style=""><span style=""><span style=""><span style=""><span style=""><span style="">Testing Risks</span></span></span></span></span></span></span></span></a><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></p> <p class="TemplateNote"><span style=""><span style=""><span style=""><span style=""><span style="">Testing risks are circumstances and events that may occur before or during testing that would have an adverse impact on the testing process. For each high- and medium-level risk, determine what activities you will do to ensure that the risk does not occur. These risk plan activities should also be moved to the project workplan.</span></span></span></span></span></p> <p class="MsoNormal" style="text-align: justify;"><span style=""><span style=""><span style=""><span style=""><span style=""><o:p> </o:p></span></span></span></span></span></p> <div align="center"> <table class="MsoNormalTable" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style="page-break-inside: avoid;"> <td style="border: 1pt solid windowtext; padding: 0in 4.25pt; background: rgb(230, 230, 230) none repeat scroll 0% 0%; width: 191.35pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="255"> <p class="colhead"><span style=""><span style=""><span style=""><span style=""><span style="">Testing Risk</span></span></span></span></span></p> </td> <span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> <td style="border-style: solid solid solid none; border-color: windowtext windowtext windowtext -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 4.25pt; background: rgb(230, 230, 230) none repeat scroll 0% 0%; width: 52.55pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="70"> <p class="colhead"><span style=""><span style=""><span style=""><span style=""><span style="">Level (H/M/L)</span></span></span></span></span></p> </td> <span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> <td style="border-style: solid solid solid none; border-color: windowtext windowtext windowtext -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 4.25pt; background: rgb(230, 230, 230) none repeat scroll 0% 0%; width: 237.75pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="317"> <p class="colhead"><span style=""><span style=""><span style=""><span style=""><span style="">Risk Plan</span></span></span></span></span></p> </td> <span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> </tr> <tr style="page-break-inside: avoid;"> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 4.25pt; width: 191.35pt;" valign="top" width="255"> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><span style=""><span style=""><span style=""><span style=""><b style=""><span style="">Example<o:p></o:p></span></b></span></span></span></span></span></p> <p class="MsoNormal"><span style=""><span style=""><span style=""><span style=""><span style="">The team is not familiar with the Web testing tools we will be using on this project.</span></span></span></span></span></p> </td> <span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 4.25pt; width: 52.55pt;" valign="top" width="70"> <p class="MsoHeader" style="margin-top: 3pt;"><span style=""><span style=""><span style=""><span style=""><span style="">H</span></span></span></span></span></p> </td> <span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 4.25pt; width: 237.75pt;" valign="top" width="317"> <p class="bulls"><span style=""><span style=""><span style=""><span style=""><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Try to find at least one person who has used the tools before.</span></span></span></span></span></p> <p class="bulls"><span style=""><span style=""><span style=""><span style=""><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Send at least two team members to formal training.</span></span></span></span></span></p> <p class="bulls" style=""><span style=""><span style=""><span style=""><span style=""><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span class="msoIns"><ins cite="mailto:Sarah%20Graf-Koto" datetime="2001-09-06T10:21"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></ins></span></span><!--[endif]-->Set up follow-up training sessions to cross-train the rest of the developers.</span></span></span></span></span></p> </td> <span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> </tr> <tr style="page-break-inside: avoid;"> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 4.25pt; width: 191.35pt;" valign="top" width="255"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> <p class="MsoNormal"><span style=""><span style=""><span style=""><span style=""><span style=""><o:p> </o:p></span></span></span></span></span></p> </td> <span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 4.25pt; width: 52.55pt;" valign="top" width="70"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> <p class="MsoNormal" style="text-align: center;" align="center"><span style=""><span style=""><span style=""><span style=""><span style=""><o:p> </o:p></span></span></span></span></span></p> </td> <span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 4.25pt; width: 237.75pt;" valign="top" width="317"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> <p class="MsoNormal"><span style=""><span style=""><span style=""><span style=""><span style=""><o:p> </o:p></span></span></span></span></span></p> </td> <span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span> </tr> </tbody></table> </div> <span style=""></span><span style=""></span><span style=""></span><span style=""></span><span style=""></span> <p class="Heading1"><a name="_Toc446993009"></a><a name="TestingSchedule"></a><a name="_Toc524404853"><span style=""><span style="">Testing Schedule</span></span></a><span style=""></span></p> <p class="TemplateNote"><span style="">This section contains a summary of the overall testing schedule. It is not at the activity level, but it should contain more detail than the major milestones included as a part of the Testing Strategy.</span></p> <p class="MsoNormal"><span style=""><o:p> </o:p></span></p> <table class="MsoNormalTable" style="border: medium none ; margin-left: 0.9pt; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style="page-break-inside: avoid;"> <td style="border: 1pt solid windowtext; padding: 0in 5.4pt; background: rgb(229, 229, 229) none repeat scroll 0% 0%; width: 297pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="396"> <p class="colhead"><span style="">Testing Milestone/Events</span></p> </td> <span style=""></span> <td style="border-style: solid solid solid none; border-color: windowtext windowtext windowtext -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 5.4pt; background: rgb(229, 229, 229) none repeat scroll 0% 0%; width: 1.25in; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="120"> <p class="colhead"><span style="">Date Started</span></p> </td> <span style=""></span> <td style="border-style: solid solid solid none; border-color: windowtext windowtext windowtext -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 5.4pt; background: rgb(229, 229, 229) none repeat scroll 0% 0%; width: 93.8pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="125"> <p class="colhead" style=""><span style="">Date Completed</span></p> </td> <span style=""></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 297pt;" valign="top" width="396"> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><b>Example<o:p></o:p></b></span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 1.25in;" valign="top" width="120"><span style=""></span> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><o:p> </o:p></span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 93.8pt;" valign="top" width="125"><span style=""></span> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><o:p> </o:p></span></p> </td> <span style=""></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 297pt;" valign="top" width="396"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">Testing Strategy</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 1.25in;" valign="top" width="120"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">05/15/YYYY</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 93.8pt;" valign="top" width="125"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">05/31/YYYY</span></p> </td> <span style=""></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 297pt;" valign="top" width="396"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">Testing Plan</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 1.25in;" valign="top" width="120"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">06/01/YYYY</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 93.8pt;" valign="top" width="125"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">06/30/YYYY</span></p> </td> <span style=""></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 297pt;" valign="top" width="396"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">Unit Testing</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 1.25in;" valign="top" width="120"> <p class="MsoHeader" style="margin-top: 3pt;"><span style="">08/15/YYYY</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 93.8pt;" valign="top" width="125"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">10/10/YYYY</span></p> </td> <span style=""></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 297pt;" valign="top" width="396"> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><i>—Test scripts turned in to project manager<o:p></o:p></i></span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 1.25in;" valign="top" width="120"><span style=""></span> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><o:p> </o:p></span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 93.8pt;" valign="top" width="125"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">10/10/XXXX</span></p> </td> <span style=""></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 297pt;" valign="top" width="396"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">Integration Testing</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 1.25in;" valign="top" width="120"><span style=""></span> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><o:p> </o:p></span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 93.8pt;" valign="top" width="125"><span style=""></span> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><o:p> </o:p></span></p> </td> <span style=""></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 297pt;" valign="top" width="396"> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><i>—Integration coordinators assigned<o:p></o:p></i></span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 1.25in;" valign="top" width="120"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">09/15/YYYY</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 93.8pt;" valign="top" width="125"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">09/23/YYYY</span></p> </td> <span style=""></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 297pt;" valign="top" width="396"> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><i>—Integration testing<o:p></o:p></i></span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 1.25in;" valign="top" width="120"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">10/01/YYYY</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 93.8pt;" valign="top" width="125"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">11/01/YYYY</span></p> </td> <span style=""></span> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 297pt;" valign="top" width="396"> <p class="MsoNormal" style="margin-top: 3pt;"><span style=""><i>—Integration tests approved and scripts turned in<o:p></o:p></i></span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 1.25in;" valign="top" width="120"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">10/20/YYYY</span></p> </td> <span style=""></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 93.8pt;" valign="top" width="125"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="">11/01/YYYY</span></p> </td> <span style=""></span> </tr> </tbody></table> <b style=""><span style="font-size: 20pt; font-family: Arial; color: black;">
<br /> </span></b> <p class="Heading1"><span style=""><a name="UnitTestingDesign"></a><a name="_Toc524404854"><span style="">Unit Testing Design</span></a></span></p> <p class="TemplateNote"><span style="">Unit testing is the first and most basic level of testing. The testing focuses on individual components and is usually performed by the person who developed the component.</span></p> <p class="heading3"><span style="">Person Responsible</span></p> <p class="TemplateNote"><span style="">Define the person responsible for the unit testing.</span></p> <p class="heading3"><span style="">Person(s) Approving</span></p> <p class="TemplateNote"><span style="">Define the person(s) or organization responsible for approving individual unit tests and for validating that the component is ready to be moved to the next level of testing.</span></p> <p class="heading3"><span style="">Test Environment</span></p> <p class="TemplateNote"><span style="">Describe any noteworthy features of the unit test environment, including location, equipment needed, software or tools used, etc.</span></p> <p class="heading3"><span style="">Testing Process and Validation</span></p> <p class="TemplateNote"><span style="">Describe the testing logistics in some detail. This includes the types of tests to be performed, what you are trying to validate, how you will know if you are successful, how you will report errors, how the errors will be retested, etc. (A formal validation may not be needed for unit testing.)</span></p> <p class="heading3"><span style="">Forms Used</span></p> <p class="TemplateNote"><span style="">Check the TechRepublic download library for unit test templates available in the future.</span></p> <b style=""><span style="font-size: 20pt; font-family: Arial; color: black;">
<br /> </span></b> <p class="Heading1"><span style=""><a name="_Toc465830026"></a><a name="IntegrationTestingDesign"></a><a name="_Toc524404855"><span style=""><span style="">Integration Testing Design</span></span></a></span></p> <p class="TemplateNote"><span style="">Integration testing involves combining the individual components into the complete solution. The purpose is to test the interfaces between the various components and to ensure that the entire solution works as a whole according to the business requirements.</span></p> <p class="heading3"><span style="">Person Responsible</span></p> <p class="TemplateNote"><span style="">Define the person responsible for the integration testing.</span></p> <p class="heading3"><span style="">Person(s) Approving</span></p> <p class="TemplateNote"><span style="">Define the person(s) or organization responsible for approving the integration test and for validating that the group of components is ready to be moved to the next level of testing.</span></p> <p class="heading3"><span style="">Test Environment</span></p> <p class="TemplateNote"><span style="">Describe any noteworthy features of the integration test environment, including location, equipment needed, software or tools used, etc.</span></p> <p class="heading3"><span style="">Testing Process and Validation</span></p> <p class="TemplateNote"><span style="">Describe the testing logistics in some detail. This includes the types of tests to be performed, what you are trying to validate, how you will know if you are successful, how you will report errors, how the errors will be retested, etc.</span></p> <p class="heading3"><span style="">Forms Used</span></p> <p class="TemplateNote"><span style="">Check the TechRepublic download library for integration test templates available in the future.</span></p> <b style=""><span style="font-size: 20pt; font-family: Arial; color: black;">
<br /> </span></b> <p class="Heading1"><span style=""><a name="_Toc465830027"></a><a name="SystemTestingDesign"></a><a name="_Toc524404856"><span style=""><span style="">System Testing Design</span></span></a></span></p> <p class="TemplateNote"><span style="">System testing is the most important and complex of the testing stages and can consist of multiple subtests. System testing validates the overall requirements of the solution in terms of quality, performance, and functionality. The system test may include subtests such as the following:</span></p> <p class="bulls" style="background: rgb(243, 243, 243) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><span style="">Requirements validation ensures that the solution satisfies the documented business requirements.</span></span></p> <p class="bulls" style="background: rgb(243, 243, 243) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Stress testing<span style=""> proves that the solution can handle heavy volumes of data, transactions, concurrent users, etc.<o:p></o:p></span></span></p> <p class="bulls" style="background: rgb(243, 243, 243) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Security testing ensures that the proper level of security and internal controls are in place.</span></p> <p class="bulls" style="background: rgb(243, 243, 243) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Disaster-recovery testing shows the solution’s ability to be recovered in case of disaster or massive failure.</span></p> <p class="bulls" style="background: rgb(243, 243, 243) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Usability testing <span style="">determines how well the user will be able to use and understand the application. It identifies areas of poor human factors design that may make the system difficult to use</span>.</span></p> <p class="bulls" style="background: rgb(243, 243, 243) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Procedures validation determines whether the user procedures and overall documentation is accurate and understandable.</span></p> <p class="heading3"><span style="">Person Responsible</span></p> <p class="TemplateNote"><span style="">Define the person or group responsible for the system testing.</span></p> <p class="heading3"><span style="">Person(s) Approving</span></p> <p class="TemplateNote"><span style="">Define the person(s) or organization responsible for approving the system testing and for validating that the solution is ready to be moved to the next level of testing.</span></p> <p class="heading3"><span style="">Test Environment</span></p> <p class="TemplateNote"><span style="">Describe any noteworthy features of the system test environment, including location, equipment needed, software or tools used, etc. Many tools, processes, and locations may be needed for system testing that will not be used elsewhere on the project.</span></p> <p class="heading3"><span style="">Testing Process and Validation</span></p> <p class="TemplateNote"><span style="">Describe the testing logistics in some detail. This includes the types of tests to be performed, what you are trying to validate, how you will know if you are successful, how you will report errors, how the errors will be retested, etc.</span><span style=""><span style="font-size: 12pt;"><o:p></o:p></span></span></p> <p class="heading3"><span style="">Forms Used</span></p> <p class="TemplateNote"><span style="">Check the TechRepublic download library for system test templates available in the future.</span></p> <b style=""><span style="font-size: 20pt; font-family: Arial; color: black;">
<br /> </span></b> <p class="Heading1"><span style=""><a name="_Toc465830028"></a><a name="AcceptanceTestingDesign"></a><a name="_Toc524404857"><span style=""><span style="">Acceptance Testing Design</span></span></a></span></p> <p class="TemplateNote"><span style="">Acceptance testing is designed for the customer to prove that the solution meets the original business requirement. In many cases, the customer is responsible for this testing since when the solution is completed successfully, it is expected that the customer will approve and accept it. Customers need to test the solution as they would expect to use it in production and then work with the project team to validate that the results come out as expected.</span></p> <p class="heading3"><span style="">Person Responsible</span></p> <p class="TemplateNote"><span style="">Define the person or group responsible for the acceptance testing.</span></p> <p class="heading3"><span style="">Person(s) Approving</span></p> <p class="TemplateNote"><span style="">Define the person(s) or organization responsible for approving the acceptance testing and for validating that the solution is ready to be moved into production. This level of approval should signify customer acceptance of the completed solution.</span></p> <p class="heading3"><span style="">Test Environment</span></p> <p class="TemplateNote"><span style="">Describe any noteworthy features of the acceptance test environment, including location, equipment needed, software or tools used, etc.</span></p> <p class="heading3"><span style="">Testing Process and Validation</span></p> <p class="TemplateNote"><span style="">Describe the testing logistics in some detail. This includes the types of tests to be performed, what you are trying to validate, how you will know if you are successful, how you will report errors, how the errors will be retested, etc.</span></p> <p class="heading3"><span style="">Forms Used</span></p> <span style=""></span> <p class="TemplateNote"><a name="_Toc521733471">Check the TechRepublic download library for acceptance test templates available in the future.</a></p> <p class="Heading1"><span style=""><a name="OptionalSections"></a><a name="_Toc524404858"><span style="">Optional Sections</span></a></span></p> <p class="TemplateNote">You can add the following sections to the Testing Strategy if they provide more perspective and value to the reader or if the information is needed within your company.</p> <p class="Heading2"><a name="TestingMethodologies"></a><a name="_Toc524404859"><span style="">Testing Methodology</span></a></p> <p class="TemplateNote">Describe any specific methodology or standards that will help the reader understand the rationale behind each part of the Testing Plan.</p> <p class="Heading2"><a name="TestingAssumptions"></a><a name="_Toc524404860"></a><a name="_Toc521733472"></a><a name="_Toc465830024"><span style=""><span style=""><span style="">Testing Assumptions</span></span></span></a></p> <p class="TemplateNote">Document any assumptions surrounding the testing plan.</p> <p class="MsoCommentText"><o:p> </o:p></p> <p class="MsoNormal" style="margin-left: 0.25in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Assumption #1</p> <p class="MsoNormal" style="margin-left: 0.25in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Assumption #2</p> <p class="MsoNormal" style="margin-left: 0.25in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Assumption #3</p> <p class="MsoNormal" style="margin-left: 0.25in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Etc.</p> <p class="Heading2"><a name="TestingMetrics"></a><a name="_Toc524404861"><span style="">Testing Metrics</span></a></p> <p class="TemplateNote">Describe any metrics you will capture as part of the testing process, such as total components tested, total defects per testing event, average time for defect correction, total number of hours spent on testing, total cost of testing, etc.</p> Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-38871179811827854832009-07-01T18:07:00.000+05:302009-07-01T18:26:04.803+05:30Testing Strategy Template<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5CDIPTI%7E1.THA%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.intro, li.intro, div.intro {mso-style-name:intro; margin-top:0in; margin-right:0in; margin-bottom:4.0pt; margin-left:0in; mso-pagination:none; page-break-after:avoid; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.bulls, li.bulls, div.bulls {mso-style-name:bulls; margin-top:3.0pt; margin-right:0in; margin-bottom:0in; margin-left:18.25pt; margin-bottom:.0001pt; text-indent:-18.25pt; mso-pagination:widow-orphan; mso-list:l0 level1 lfo1; tab-stops:list .25in; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.subhead, li.subhead, div.subhead {mso-style-name:subhead; margin-top:6.0pt; margin-right:0in; margin-bottom:6.0pt; margin-left:0in; line-height:15.0pt; mso-line-height-rule:exactly; mso-pagination:widow-orphan; font-size:13.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:black; font-weight:bold;} span.msoIns {mso-style-type:export-only; mso-style-name:""; text-decoration:underline; text-underline:single; color:teal;} span.msoDel {mso-style-type:export-only; mso-style-name:""; text-decoration:line-through; color:red;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:2117019602; mso-list-type:hybrid; mso-list-template-ids:-906205952 153267448 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-number-format:bullet; mso-level-style-link:bulls; mso-level-text:; mso-level-tab-stop:.25in; mso-level-number-position:left; margin-left:.25in; text-indent:-.25in; font-family:Symbol;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </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-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <p class="subhead"><span style="font-size:85%;">Introduction</span></p> <p class="intro"><span style="font-size:85%;">One of the basic principles of the testing process is to plan for testing early in the development life cycle. For large projects, this starts in the analysis phase with the formulation of the Testing Strategy, which you later translate into the lower-level Testing Plan.</span></p> <p class="intro"><span style="font-size:85%;">The Testing Strategy provides overall guidance and direction for the rest of the testing process. Preparing a Testing Strategy helps the project team think through the work at a high level, concentrating on the requirements of the testing events, the approach that will be used, and the resources necessary to complete the testing.</span></p> <p class="intro"><span style="font-size:85%;">Testing stages in the Testing Strategy include:</span></p> <p class="bulls"><!--[if !supportLists]--><span style="font-size:85%;"><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><b>Unit Testing</b>—The first testing is to ensure that the component meets expectations in terms of features and functionality. In almost all cases, the person that develops the component also does unit testing.</span><!--[endif]--></p> <p class="bulls"><!--[if !supportLists]--><span style="font-size:85%;"><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><b>Integration Testing</b>—After the components have been unit tested, they are executed together. This testing verifies that the interfaces work correctly and that data is processed in its entirety as expected.</span><!--[endif]--></p> <p class="bulls"><!--[if !supportLists]--><span style="font-size:85%;"><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><b>System Testing</b>—This is where the most rigorous testing takes place, to ensure that the solution meets the technical and environmental needs of the customer and that the solution behaves as it should. Many individual tests can be performed under the system test umbrella. These include stress testing, usability testing, security testing, performance testing, recovery testing, and multisite testing.</span><!--[endif]--></p> <p class="bulls"><!--[if !supportLists]--><span style="font-size:85%;"><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><b>Acceptance Testing</b>—This is the final set of tests to ensure that the solution meets the business objectives and requirements. The business customers may be responsible for this testing. It requires their active participation to work with the solution, as they will when it moves to production status.</span><!--[endif]--></p> <p class="intro" style="margin-top: 12pt;"><span style="font-size:85%;">This template is designed to help you draft your own Testing Strategy. Note that the shaded text in this template is explanatory only; you should delete these comments and the example text from your version of the document.</span></p><p class="intro" style="margin-top: 12pt;"><span style="font-size:85%;">
<br /></span></p><p class="intro" style="margin-top: 12pt;"><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5CDIPTI%7E1.THA%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C03%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt;} h2 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:2; font-size:14.0pt; font-family:Arial; font-style:italic;} p.MsoHeading9, li.MsoHeading9, div.MsoHeading9 {mso-style-next:Normal; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:9; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; font-weight:bold; mso-bidi-font-weight:normal;} p.MsoCommentText, li.MsoCommentText, div.MsoCommentText {mso-style-noshow:yes; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.MsoHeader, li.MsoHeader, div.MsoHeader {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:center 3.0in right 6.0in; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.MsoBodyText2, li.MsoBodyText2, div.MsoBodyText2 {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:blue; font-style:italic; mso-bidi-font-style:normal;} p.Notenonumber, li.Notenonumber, div.Notenonumber {mso-style-name:"Note no number"; margin:0in; margin-bottom:.0001pt; text-indent:0in; mso-pagination:none; font-size:12.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:blue; font-style:italic; mso-bidi-font-style:normal;} p.TemplateNote, li.TemplateNote, div.TemplateNote {mso-style-name:"Template Note"; margin-top:0in; margin-right:0in; margin-bottom:4.0pt; margin-left:0in; mso-pagination:none; page-break-after:avoid; background:#F3F3F3; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.bodycopy, li.bodycopy, div.bodycopy {mso-style-name:bodycopy; margin-top:0in; margin-right:0in; margin-bottom:4.0pt; margin-left:0in; text-indent:9.35pt; line-height:12.0pt; mso-line-height-rule:exactly; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.colhead, li.colhead, div.colhead {mso-style-name:colhead; margin-top:3.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; text-align:center; mso-pagination:widow-orphan; font-size:12.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; font-weight:bold; mso-bidi-font-weight:normal;} p.bulls, li.bulls, div.bulls {mso-style-name:bulls; margin-top:3.0pt; margin-right:0in; margin-bottom:0in; margin-left:18.25pt; margin-bottom:.0001pt; text-indent:-18.25pt; mso-pagination:widow-orphan; mso-list:l1 level1 lfo1; tab-stops:list .25in; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.Heading1, li.Heading1, div.Heading1 {mso-style-name:Heading1; mso-style-parent:"Heading 1"; margin-top:12.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:20.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:black; font-weight:bold; mso-bidi-font-weight:normal;} p.Heading2, li.Heading2, div.Heading2 {mso-style-name:Heading2; mso-style-parent:"Heading 2"; margin-top:6.0pt; margin-right:0in; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:2; font-size:14.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; font-weight:bold;} span.msoIns {mso-style-type:export-only; mso-style-name:""; text-decoration:underline; text-underline:single; color:teal;} span.msoDel {mso-style-type:export-only; mso-style-name:""; text-decoration:line-through; color:red;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1533374330; mso-list-type:hybrid; mso-list-template-ids:-332757522 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.25in; mso-level-number-position:left; margin-left:.25in; text-indent:-.25in; font-family:Symbol;} @list l1 {mso-list-id:2117019602; mso-list-type:hybrid; mso-list-template-ids:-906205952 153267448 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l1:level1 {mso-level-number-format:bullet; mso-level-style-link:bulls; mso-level-text:; mso-level-tab-stop:.25in; mso-level-number-position:left; margin-left:.25in; text-indent:-.25in; font-family:Symbol;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </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-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> </p><p class="Heading1"><span style="font-size:85%;"><a name="_Toc524421366"></a><a name="_Toc446993005"><span style="">Project Overview</span></a></span></p> <p class="TemplateNote"><span style="font-size:85%;">Briefly discuss the project background and objectives. The appropriate information can be copied from the Project Definition document.</span></p> <p class="Heading1"><span style="font-size:85%;"><a name="_Toc454961463"></a><a name="_Toc424135905"></a><a name="_Toc416585815"></a><a name="_Toc401103630"></a><a name="_Toc446993007"></a><a name="_Toc524421367"></a><a name="_Toc501170237"></a><a name="_Toc501167723"><span style=""><span style=""><span style=""><span style=""><span style=""><span style=""><span style="">
<br /></span></span></span></span></span></span></span></a></span></p><p class="Heading1"><span style="font-size:85%;"><a name="_Toc501167723"><span style=""><span style=""><span style=""><span style=""><span style=""><span style=""><span style="">Business Risks</span></span></span></span></span></span></span></a><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span></p> <p class="TemplateNote"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style="">These are high-level risks of the project that will affect the overall testing strategy. For instance, the risk of doing business on the Internet may drive the need for rigorous system tests of firewalls, technical architecture, and security. The risks can be classified in terms of high, medium, and low, depending on the nature and impact of the problem. For each high and medium risk, identify which elements in the overall testing approach will help ensure that the potential problem does not occur.</span></span></span></span></span></span></p> <p class="MsoNormal" style="text-align: justify;"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""><o:p> </o:p></span></span></span></span></span></span></p> <div align="center"> <table class="MsoNormalTable" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style="page-break-inside: avoid;"> <td style="border: 1pt solid windowtext; padding: 0in 4.25pt; background: rgb(230, 230, 230) none repeat scroll 0% 0%; width: 2.7in; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="259"> <p class="colhead"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style="">Risk Area</span></span></span></span></span></span></p> </td> <span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> <td colspan="2" style="border-style: solid solid solid none; border-color: windowtext windowtext windowtext -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 4.25pt; background: rgb(230, 230, 230) none repeat scroll 0% 0%; width: 49.5pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="66"> <p class="colhead"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style="">Level (H/M/L)</span></span></span></span></span></span></p> </td> <span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> <td style="border-style: solid solid solid none; border-color: windowtext windowtext windowtext -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 4.25pt; background: rgb(230, 230, 230) none repeat scroll 0% 0%; width: 237.75pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="317"> <p class="colhead"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style="">Risk Plan</span></span></span></span></span></span></p> </td> <span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> </tr> <tr style="page-break-inside: avoid;"> <td colspan="2" style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 4.25pt; width: 195.3pt;" valign="top" width="260"> <p class="MsoHeading9" style="margin-top: 3pt; page-break-after: auto;"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""><span style="">Example<o:p></o:p></span></span></span></span></span></span></span></p> <p class="MsoHeader" style="margin-top: 3pt;"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style="">Since this is our first system doing e-commerce on the Internet, there is a concern that security will not be tight enough.</span></span></span></span></span></span></p> </td> <span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 4.25pt; width: 48.6pt;" valign="top" width="65"> <p class="MsoHeader" style="margin-top: 3pt;"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style="">H</span></span></span></span></span></span></p> </td> <span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 4.25pt; width: 237.75pt;" valign="top" width="317"> <p class="MsoNormal" style="margin: 3pt 0in 0.0001pt; text-indent: 0in;"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Rigorously test security with our initial partners.</span></span></span></span></span></span></p> <p class="bulls"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Bring in subject matter experts to validate our security design.</span></span></span></span></span></span></p> <p class="bulls"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Set up tests for people to try to break in to the system or get around security features.</span></span></span></span></span></span></p> </td> <span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> </tr> <tr style="page-break-inside: avoid;"> <td colspan="2" style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 4.25pt; width: 195.3pt;" valign="top" width="260"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""><o:p> </o:p></span></span></span></span></span></span></p> </td> <span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 4.25pt; width: 48.6pt;" valign="top" width="65"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""><o:p> </o:p></span></span></span></span></span></span></p> </td> <span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 4.25pt; width: 237.75pt;" valign="top" width="317"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> <p class="bodycopy"><span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""><o:p> </o:p></span></span></span></span></span></span></p> </td> <span style="font-size:85%;"><span style=""><span style=""><span style=""><span style=""><span style=""></span></span></span></span></span></span> </tr> <!--[if !supportMisalignedColumns]--> <tr height="0"> <td style="border: medium none ;" width="259">
<br /></td> <td style="border: medium none ;" width="1">
<br /></td> <td style="border: medium none ;" width="65">
<br /></td> <td style="border: medium none ;" width="317">
<br /></td> </tr> <!--[endif]--> </tbody></table> </div> <span style="font-size:85%;"><span style=""></span><span style=""></span><span style=""></span><span style=""></span><span style=""></span></span> <p class="Heading1"><span style="font-size:85%;"><a name="_Toc446993009"></a><a name="_Toc524421368"><span style="">
<br /></span></a></span></p><p class="Heading1"><span style="font-size:85%;"><a name="_Toc524421368"><span style="">Testing Milestones</span></a><span style=""></span></span></p> <p class="TemplateNote"><span style="font-size:85%;"><span style="">This section contains the overall schedule at a major milestone level. The associated details will be broken down further in the Testing Plan. Since this document is created in the analysis phase, these dates are subject to later revision.</span></span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style=""><o:p> </o:p></span></span></p> <table class="MsoNormalTable" style="border: medium none ; margin-left: 0.9pt; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr> <td style="border: 1pt solid windowtext; padding: 0in 5.4pt; background: rgb(229, 229, 229) none repeat scroll 0% 0%; width: 4in; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="384"> <p class="colhead"><span style="font-size:85%;"><span style="">Testing Milestone</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> <td style="border-style: solid solid solid none; border-color: windowtext windowtext windowtext -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 5.4pt; background: rgb(229, 229, 229) none repeat scroll 0% 0%; width: 189pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" valign="top" width="252"> <p class="colhead"><span style="font-size:85%;"><span style="">Date Completed</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 4in;" valign="top" width="384"> <p class="MsoHeading9" style="margin-top: 3pt;"><span style="font-size:85%;"><span style=""><span style="">Example<o:p></o:p></span></span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 189pt;" valign="top" width="252"><span style="font-size:85%;"><span style=""></span></span> <p class="Notenonumber" style=""><span style="font-size:85%;"><span style=""><span style="color: windowtext; font-style: normal;"><o:p> </o:p></span></span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 4in;" valign="top" width="384"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><span style="">Testing Strategy</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 189pt;" valign="top" width="252"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><span style="">06/01/YYYY</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 4in;" valign="top" width="384"> <p class="MsoHeader" style="margin-top: 3pt;"><span style="font-size:85%;"><span style="">Testing Plan</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 189pt;" valign="top" width="252"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><span style="">07/01/YYYY</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 4in;" valign="top" width="384"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><span style="">Unit Testing</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 189pt;" valign="top" width="252"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><span style="">10/01/YYYY</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 4in;" valign="top" width="384"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><span style="">Integration Testing</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 189pt;" valign="top" width="252"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><span style="">11/01/YYYY</span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 4in;" valign="top" width="384"><span style="font-size:85%;"><span style=""></span></span> <p class="Notenonumber" style=""><span style="font-size:85%;"><span style=""><span style="color: black;"><o:p> </o:p></span></span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 189pt;" valign="top" width="252"><span style="font-size:85%;"><span style=""></span></span> <p class="Notenonumber" style=""><span style="font-size:85%;"><span style=""><span style="color: black;"><o:p> </o:p></span></span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 4in;" valign="top" width="384"><span style="font-size:85%;"><span style=""></span></span> <p class="Notenonumber" style=""><span style="font-size:85%;"><span style=""><span style="color: black;"><o:p> </o:p></span></span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 189pt;" valign="top" width="252"><span style="font-size:85%;"><span style=""></span></span> <p class="Notenonumber" style=""><span style="font-size:85%;"><span style=""><span style="color: black;"><o:p> </o:p></span></span></span></p> </td> <span style="font-size:85%;"><span style=""></span></span> </tr> </tbody></table> <p class="Heading1"><span style="font-size:85%;"><span style=""><a name="_Toc465830025"></a><a name="_Toc524421369"></a><a name="_Toc465830029"><span style=""><span style="">
<br /></span></span></a></span></span></p><p class="Heading1"><span style="font-size:85%;"><span style=""><a name="_Toc465830029"><span style=""><span style="">
<br /></span></span></a></span></span></p><p class="Heading1"><span style="font-size:85%;"><span style=""><a name="_Toc465830029"><span style=""><span style="">Testing Environment</span></span></a><span style=""></span></span></span></p> <p class="TemplateNote"><span style="font-size:85%;"><span style=""><span style="">Think through the technologies and facilities needed for the testing process. If the overall testing environment needs are understood up front, it will be easier to put the environment in place after the Test Plan is created. In addition, some parts of the environment may not be available and may need to be planned for and acquired well in advance.</span></span></span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style=""><span style=""><b style=""><span style=""><o:p> </o:p></span></b></span></span></span></p> <p class="MsoHeading9"><span style="font-size:85%;"><span style=""><span style=""><span style="">
<br /></span></span></span></span></p><p class="MsoHeading9"><span style="font-size:85%;"><span style=""><span style=""><span style="">Example<o:p></o:p></span></span></span></span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style=""><span style="">The developers will conduct unit testing from their offices, with no additional software required. Integration testing will also be conducted in the developer’s workspace, based on who is assigned to coordinate the major system components. System testing and user testing will be coordinated in the project war room. The war room will have six desktop machines installed, with Internet access and our standard testing tools. For system testing, we will also need access to the servers in the operations center….</span></span></span></p> <p class="Heading1"><span style="font-size:85%;"><span style=""><span style=""><a name="_Toc524421370">
<br /></a></span></span></span></p><p class="Heading1"><span style="font-size:85%;"><span style=""><span style=""><a name="_Toc524421370">
<br /></a></span></span></span></p><p class="Heading1"><span style="font-size:85%;"><span style=""><span style=""><a name="_Toc524421370">Testing Approach</a></span></span></span></p> <p class="TemplateNote"><span style="font-size:85%;"><span style=""><span style="">Describe the testing process at a high level, including how you will conduct unit testing, integration testing, system testing, and acceptance testing. This is where fundamental decisions are made about the type of testing that makes sense for your project. For instance, if you are implementing a packaged solution, the approach may start in system testing, with the vendor providing close support. If you are doing iterative development cycles, the testing approach will reflect this overall development life cycle. For system testing, define the major testing events such as stress testing, security testing, disaster-recovery testing, usability testing, and response-time testing.</span></span></span></p> <p class="Heading2"><span style="font-size:85%;"><span style=""><span style=""><a name="_Toc524421371">
<br /></a></span></span></span></p><p class="Heading2"><span style="font-size:85%;"><span style=""><span style=""><a name="_Toc524421371">
<br /></a></span></span></span></p><p class="Heading2"><span style="font-size:85%;"><span style=""><span style=""><a name="_Toc524421371">Unit Testing Approach</a></span></span></span></p> <p class="TemplateNote"><span style="font-size:85%;"><span style="">Describe the approach for conducting unit testing to ensure that each component works according to specifications.</span></span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style=""><b style=""><span style="">
<br /></span></b></span></span></p><p class="MsoNormal"><span style="font-size:85%;"><span style=""><b style=""><span style="">Example<o:p></o:p></span></b></span></span></p> <p class="MsoHeader" style=""><span style="font-size:85%;"><span style=""><span style="">Each developer is responsible for unit testing his or her programs as they are completed. The project manager will consider each assigned component to be completed when it has been developed and successfully unit tested. The developers will keep all test data, along with a document stating the expected results, so that these same cases can be used in the integration tests….<o:p></o:p></span></span></span></p> <p class="Heading2"><span style="font-size:85%;"><span style=""><a name="_Toc524421372">
<br /></a></span></span></p><p class="Heading2"><span style="font-size:85%;"><span style=""><a name="_Toc524421372">
<br /></a></span></span></p><p class="Heading2"><span style="font-size:85%;"><span style=""><a name="_Toc524421372">Integration Testing Approach</a></span></span></p> <p class="TemplateNote"><span style="font-size:85%;"><span style="">Integration testing validates that the individually tested components work correctly together.</span></span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style=""><b style=""><span style="">
<br /></span></b></span></span></p><p class="MsoNormal"><span style="font-size:85%;"><span style=""><b style=""><span style="">Example<o:p></o:p></span></b></span></span></p> <p class="MsoBodyText2"><span style="font-size:85%;"><span style=""><span style="color: windowtext; font-style: normal;">Specific developers will be assigned to coordinate the integration tests. The project manager will assign the specific parts of the system to be tested. The prior test cases created during unit testing will be used as the basis for integration testing, with new test cases added to fully test all the interfaces and dependencies. All databases should be loaded with a set of test data so that all logic can be initially tested. Reports will be created from the files that would normally be sent to our customers so that the data can be validated….<o:p></o:p></span></span></span></p> <p class="Heading2"><span style="font-size:85%;"><span style=""><a name="_Toc524421373">
<br /></a></span></span></p><p class="Heading2"><span style="font-size:85%;"><span style=""><a name="_Toc524421373">
<br /></a></span></span></p><p class="Heading2"><span style="font-size:85%;"><span style=""><a name="_Toc524421373">System Testing Approach</a></span></span></p> <p class="TemplateNote"><span style="font-size:85%;"><span style="">System testing is the time for fully testing all features and functions and for ensuring that production conditions are fully tested. This can include stress testing, requirements validation, security testing, customer testing, testing of the training material, etc.</span></span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style=""><b style=""><span style="">
<br /></span></b></span></span></p><p class="MsoNormal"><span style="font-size:85%;"><span style=""><b style=""><span style="">Example<o:p></o:p></span></b></span></span></p> <p class="MsoHeader" style=""><span style="font-size:85%;"><span style="">System testing will include many separate tests to ensure that the application will work as expected in production. The test cases from integration testing will be brought forward as the basis for system testing. During system testing, we will conduct a stress test to generate the number of transactions we feel are normal for one day and feed them through the online system within an hour. This will be in an environment that mirrors the ultimate production environment. As many tests as possible will be conducted with a subset of our trading partners, so that we can simulate the actual Web transactions going from our application to our partner’s environment….</span></span></p> <p class="Heading2" style="margin-top: 0.25in;"><span style="font-size:85%;"><span style=""><a name="_Toc524421374">
<br /></a></span></span></p><p class="Heading2" style="margin-top: 0.25in;"><span style="font-size:85%;"><span style=""><a name="_Toc524421374">Acceptance Testing Approach</a></span></span></p> <p class="TemplateNote"><span style="font-size:85%;"><span style="">Describe the approach for conducting business unit customer acceptance testing to ensure that the system satisfies requirements for operational functionality, procedures, and usability.<b><o:p></o:p></b></span></span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style=""><b style=""><span style="">
<br /></span></b></span></span></p><p class="MsoNormal"><span style="font-size:85%;"><span style=""><b style=""><span style="">Example<o:p></o:p></span></b></span></span></p> <p class="MsoNormal"><span style="font-size:85%;"><span style="">The customers will have access to all of the test data that has been generated previously, but they will ultimately be responsible for generating whatever sets of transactions are required to test the system to their satisfaction. For all intents and purposes, the system will be placed in a production status, including hardware and software. They will coordinate testing with the partners as well and ensure that the resulting transactions are as they expect</span>….</span></p> <p class="Heading1"><span style="font-size:85%;"><a name="_Toc524421375">
<br /></a></span></p><p class="Heading1"><span style="font-size:85%;"><a name="_Toc524421375">Optional Sections</a></span></p> <p class="MsoNormal"><span style="font-size:85%;">The following sections can be added to the Testing Strategy if it provides more perspective and value to the reader or if the information is needed within your company.</span></p> <p class="Heading2"><span style="font-size:85%;"><a name="_Toc524421376"></a><a name="_Toc465830024"><span style="">
<br /></span></a></span></p><p class="Heading2"><span style="font-size:85%;"><a name="_Toc465830024"><span style="">
<br /></span></a></span></p><p class="Heading2"><span style="font-size:85%;"><a name="_Toc465830024"><span style="">Business Assumptions</span></a></span></p> <p class="TemplateNote"><span style="font-size:85%;">Document any assumptions surrounding the testing strategy.</span></p> <p class="MsoCommentText"><span style="font-size:85%;"><o:p> </o:p></span></p> <p class="MsoNormal" style="margin-left: 0.25in; text-indent: -0.25in;"><span style="font-size:85%;"><a name="_Toc465830022"><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Assumption #1</a></span></p> <p class="MsoNormal" style="margin-left: 0.25in; text-indent: -0.25in;"><span style="font-size:85%;"><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Assumption #2</span></span></p> <p class="MsoNormal" style="margin-left: 0.25in; text-indent: -0.25in;"><span style="font-size:85%;"><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Assumption #3</span></span></p> <p class="MsoNormal" style="margin-left: 0.25in; text-indent: -0.25in;"><span style="font-size:85%;"><span style=""><!--[if !supportLists]--><span style="font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]-->Etc.</span></span></p> <p class="Heading2"><span style="font-size:85%;"><span style=""><a name="_Toc524421377">
<br /></a></span></span></p><p class="Heading2"><span style="font-size:85%;"><span style=""><a name="_Toc524421377">
<br /></a></span></span></p><p class="Heading2"><span style="font-size:85%;"><span style=""><a name="_Toc524421377">Testing Objectives</a></span></span></p> <p class="TemplateNote"><span style="font-size:85%;">The project should have a set of overall objectives to be achieved. Usually these overall objectives can be broken down into a specific set of testing objectives that will be accomplished through the testing process. You can state these in terms of the overall testing results, or you can break them down into objectives for the unit, integration, system, and acceptance testing. (Remove this comment section from final document.)</span></p> <p class="Heading2"><span style="font-size:85%;"><a name="_Toc524421378"></a><a name="_Toc465830023"></a><a name="_Toc457890197"><span style=""><span style="">
<br /></span></span></a></span></p><p class="Heading2"><span style="font-size:85%;"><a name="_Toc457890197"><span style=""><span style="">
<br /></span></span></a></span></p><p class="Heading2"><span style="font-size:85%;"><a name="_Toc457890197"><span style=""><span style="">Testing Organization</span></span></a></span></p> <p class="TemplateNote"><span style="font-size:85%;">In this section, define the high-level organization structure for testing. This might be especially helpful for large projects where many people will be involved in various aspects of the testing process. It also would be good if an independent testing organization has responsibility for portions of the testing process. An organization chart works well here, or you can just list the various groups involved. At this point, you may not have specific names, but you should know what groups will be needed.</span></p><p class="TemplateNote"></p><p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> <table class="MsoNormalTable" style="border: medium none ; margin-left: 5.4pt; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style="height: 14.8pt;"> <td style="border: 1pt solid windowtext; padding: 0in 5.4pt; background: rgb(229, 229, 229) none repeat scroll 0% 0%; width: 121.5pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; height: 14.8pt;" valign="top" width="162"> <p class="colhead"><span style="font-size:85%;">Testing Event</span></p> </td> <td style="border-style: solid solid solid none; border-color: windowtext windowtext windowtext -moz-use-text-color; border-width: 1pt 1pt 1pt medium; padding: 0in 5.4pt; background: rgb(229, 229, 229) none repeat scroll 0% 0%; width: 351pt; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; height: 14.8pt;" valign="top" width="468"> <p class="colhead"><span style="font-size:85%;">Organizations/People Involved</span></p> </td> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 121.5pt;" valign="top" width="162"> <p class="MsoHeading9" style="margin-top: 3pt;"><span style="font-size:85%;"><span style="">Example<o:p></o:p></span></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 351pt;" valign="top" width="468"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 121.5pt;" valign="top" width="162"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;">Unit Testing</span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 351pt;" valign="top" width="468"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;">Developers</span></p> </td> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 121.5pt;" valign="top" width="162"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;">Integration Testing</span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 351pt;" valign="top" width="468"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;">Developers, DBAs, project manager</span></p> </td> </tr> <tr> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 121.5pt;" valign="top" width="162"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;">System Testing</span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 351pt;" valign="top" width="468"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;">Testing organization, developers, partners, server administration,…</span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 121.5pt;" valign="top" width="162"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;">Acceptance Testing</span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 351pt;" valign="top" width="468"> <p class="MsoNormal" style="margin-top: 3pt;"><span style="font-size:85%;">Developers, customers,…
<br /></span></p> </td> </tr> </tbody></table> <p></p> Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-36831536439221955352009-06-30T17:55:00.000+05:302009-06-30T18:03:14.592+05:30Test-Design Specification<span style="font-size:85%;"><span style="font-family: verdana;"><span style="font-weight: bold;">1. Purpose. </span><br /><br />To specify refinements of the test approach and to identify the features to be tested by this design and its associated tests.</span><br /><span style="font-family: verdana;"><br /><span style="font-weight: bold;">2. Outline. </span><br />A test-design specification shall have the following structure:</span><br /><span style="font-family: verdana;">(1) Test-design-specification identifier</span><br /><span style="font-family: verdana;">(2) Features to be tested</span><br /><span style="font-family: verdana;">(3) Approach refinements</span><br /><span style="font-family: verdana;">(4) Test identification</span><br /><span style="font-family: verdana;">(5) Feature pass/fail criteria</span><br /><br /><span style="font-family: verdana;">The sections shall be ordered in the specified sequence. Additional sections may be included at the end. If some or all of the content of a section is in another document, then a reference to that material may be listed in place of the corresponding content. The referenced material must be attached to the test-design specification or available to users of the design specification.</span><br /><br /><span style="font-family: verdana;"><br />Details on the content of each section are contained in the following sections. </span><br /><br /><br /><span style="font-family: verdana;"><span style="font-weight: bold;">2.1 Test-Design-Specification Identifier. </span><br /><br /></span><span style="font-family: verdana;">Specify the unique identifierassigned to this test-design specification. Supply a reference to the associated test plan, if it exists.</span><br /><br /><span style="font-family: verdana;"><br /><span style="font-weight: bold;">2.2 Features to be Tested. </span><br /><br /></span><span style="font-family: verdana;">Identify the test items and describe the features and combinations of features which are the object of this design specification. Other features may be exercised, but need not be identified.</span><br /><span style="font-family: verdana;">For each feature or feature combination, a reference to its associated requirements in the</span><br /><span style="font-family: verdana;">item requirement specification or design description should be included.</span><br /><br /><span style="font-family: verdana;"><br /><span style="font-weight: bold;">2.3 Approach Refinements. </span></span><br /><br /><span style="font-family: verdana;">Specify refinements to the approach described in the test plan. Include specific test techniques to be used. The method of analyzing test results should be identified (for example, comparator</span><br /><span style="font-family: verdana;">programs or visual inspection). </span><br /><br /><span style="font-family: verdana;">Specify the results of any analysis which provides a rationale for test-case selection. For example, one might specify conditions which permit a determination of error tolerance (for example, those conditions which distinguish valid inputs from invalid inputs).</span><br /><br /><span style="font-family: verdana;">Summarize the common attributes of any test cases. This may include input constraints that must be true for every input in the set of associated test cases, any shared environmental needs, and any shared special procedural requirements, and any shared case dependencies.</span><br /><br /><br /><span style="font-family: verdana; font-weight: bold;"><br />2.4 Test Identification. </span><br /><br /><span style="font-family: verdana;">List the identifier and a brief description of each test case associated with this design. A articular</span><br /><span style="font-family: verdana;">test case may be identified in more than one test design specification. List the identifier and a brief description of each procedure associated with this test-design specification. </span><br /><br /><span style="font-family: verdana;"><br /><br /><span style="font-weight: bold;">2.5 Feature Pass/Fail Criteria. </span></span><br /><br /><span style="font-family: verdana;">Specify the criteria to be used to determine whether the feature or feature combination has passed or failed.</span><br /></span>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-69954074183803150012009-06-19T18:04:00.000+05:302009-06-19T20:20:53.992+05:30Guidelines For Matrics Calculations<span style="font-family:verdana;"><span style="font-size:85%;"><strong>Metrics Used In Testing</strong><br />In this tutorial you will learn about metrics used in testing, The Product Quality Measures - </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;"></span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">1. Customer satisfaction index, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">2. Delivered defect quantities, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">3. Responsiveness (turnaround time) to users, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">4. Product volatility, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">5. Defect ratios, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">6. Defect removal efficiency, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">7. Complexity of delivered product, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">8. Test coverage, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">9. Cost of defects, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">10. Costs of quality activities, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">11. Re-work, </span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;">12. Reliability and Metrics for Evaluating Application System Testing. </span></span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;"><span style="font-size:85%;"><strong></strong></span></span><br /><span style="font-family:verdana;"><span style="font-size:85%;"><strong>The Product Quality Measures:</strong><br /></span></span><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;"><strong>1. Customer satisfaction index<br /></strong>This index is surveyed before product delivery and after product delivery (and on-going on a periodic basis, using standard questionnaires).The following are analyzed:<br />Number of system enhancement requests per year<br />Number of maintenance fix requests per year<br />User friendliness: call volume to customer service hotline<br />User friendliness: training time per new user<br />Number of product recalls or fix releases (software vendors)<br />Number of production re-runs (in-house information systems groups)<br /><br /></span><span style="font-family:verdana;font-size:85%;"></span><span style="font-family:verdana;font-size:85%;"><strong>2. Delivered defect quantities </strong><br />They are normalized per function point (or per LOC) at product delivery (first 3 months or first year of operation) or Ongoing (per year of operation) by level of severity, by category or cause, e.g.: requirements defect, design defect, code defect, documentation/on-line help defect, defect introduced by fixes, etc.<br /></span><br /><span style="font-family:verdana;font-size:85%;"><strong>3. Responsiveness (turnaround time) to users<br /></strong>Turnaround time for defect fixes, by level of severity<br />Time for minor vs. major enhancements; actual vs. planned elapsed time </span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;"><strong>4. Product volatility </strong><br />Ratio of maintenance fixes (to repair the system & bring it into compliance with specifications), vs. enhancement requests (requests by users to enhance or change functionality)<br /><strong></strong></span><br /><span style="font-family:verdana;font-size:85%;"><strong>5. Defect ratios </strong><br />Defects found after product delivery per function point.<br />Defects found after product delivery per LOC<br />Pre-delivery defects: annual post-delivery defects<br />Defects per function point of the system modifications<br /></span><br /><span style="font-family:verdana;font-size:85%;"><strong>6. Defect removal efficiency<br /></strong>Number of post-release defects (found by clients in field operation), categorized by level of severity<br />Ratio of defects found internally prior to release (via inspections and testing), as a percentage of all defects All defects include defects found internally plus externally (by customers) in the first year after product delivery<br /></span><br /><span style="font-family:verdana;font-size:85%;"><strong>7. Complexity of delivered product<br /></strong>McCabe's cyclomatic complexity counts across the system<br />Halstead’s measure<br />Card's design complexity measures<br />Predicted defects and maintenance costs, based on complexity measures<br /></span><br /><span style="font-family:verdana;font-size:85%;"><strong>8. Test coverage<br /></strong>Breadth of functional coverage<br />Percentage of paths, branches or conditions that were actually tested<br />Percentage by criticality level: perceived level of risk of paths<br />The ratio of the number of detected faults to the number of predicted faults.<br /><br /></span><span style="font-family:verdana;font-size:85%;"></span><span style="font-family:verdana;font-size:85%;"><strong>9. Cost of defects </strong></span><br /><span style="font-family:verdana;font-size:85%;">Business losses per defect that occurs during operation<br />Business interruption costs; costs of work-arounds<br />Lost sales and lost goodwill<br />Litigation costs resulting from defects<br />Annual maintenance cost (per function point)<br />Annual operating cost (per function point)<br />Measurable damage to your boss's career<br /></span><br /><span style="font-family:verdana;font-size:85%;"><strong>10. Costs of quality activities<br /></strong>Costs of reviews, inspections and preventive measures<br />Costs of test planning and preparation<br />Costs of test execution, defect tracking, version and change control<br />Costs of diagnostics, debugging and fixing<br />Costs of tools and tool support<br />Costs of test case library maintenance<br />Costs of testing & QA education associated with the product<br />Costs of monitoring and oversight by the QA organization (if separate from the development and test organizations)<br /><strong></strong></span><br /><span style="font-family:verdana;font-size:85%;"><strong>11. Re-work </strong><br />Re-work effort (hours, as a percentage of the original coding hours)<br />Re-worked LOC (source lines of code, as a percentage of the total delivered LOC)<br />Re-worked software components (as a percentage of the total delivered components)<br /></span><br /><span style="font-family:verdana;font-size:85%;"><strong>12. Reliability<br /></strong>Availability (percentage of time a system is available, versus the time the system is needed to be available)<br />Mean time between failure (MTBF).<br />Man time to repair (MTTR)<br />Reliability ratio (MTBF / MTTR)<br />Number of product recalls or fix releases<br />Number of production re-runs as a ratio of production runs </span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;"><strong><span style="font-size:100%;">Metrics for Evaluating Application System Testing:<br /></span></strong></span><br /><span style="font-family:verdana;font-size:85%;">Metric = Formula<br /></span><br /><span style="font-family:verdana;font-size:85%;">Test Coverage = Number of units (KLOC/FP) tested / total size of the system. (LOC represents Lines of Code)<br /></span><br /><span style="font-family:verdana;font-size:85%;">Number of tests per unit size = Number of test cases per KLOC/FP (LOC represents Lines of Code).<br /></span><br /><span style="font-family:verdana;font-size:85%;">Acceptance criteria tested = Acceptance criteria tested / total acceptance criteria<br /></span><br /><span style="font-family:verdana;font-size:85%;">Defects per size = Defects detected / system size<br /></span><br /><span style="font-family:verdana;font-size:85%;">Test cost (in %) = Cost of testing / total cost *100<br /></span><br /><span style="font-family:verdana;font-size:85%;">Cost to locate defect = Cost of testing / the number of defects located<br /></span><br /><span style="font-family:verdana;font-size:85%;">Achieving Budget = Actual cost of testing / Budgeted cost of testing<br /></span><br /><span style="font-family:verdana;font-size:85%;">Defects detected in testing = Defects detected in testing / total system defects<br /></span><br /><span style="font-family:verdana;font-size:85%;">Defects detected in production = Defects detected in production/system size<br /></span><br /><span style="font-family:verdana;font-size:85%;">Quality of Testing = No of defects found during Testing/(No of defects found during testing + No of </span><br /><span style="font-family:verdana;font-size:85%;">acceptance defects found after delivery) *100<br /></span><br /><span style="font-family:verdana;font-size:85%;">Effectiveness of testing to business = Loss due to problems / total resources processed by the system.<br /></span><br /><span style="font-family:verdana;font-size:85%;">System complaints = Number of third party complaints / number of transactions processed<br /></span><br /><span style="font-family:verdana;font-size:85%;">Scale of Ten = Assessment of testing by giving rating in scale of 1 to 10<br /></span><br /><span style="font-family:verdana;font-size:85%;">Source Code Analysis = Number of source code statements changed / total number of tests.<br /></span><br /><span style="font-family:verdana;font-size:85%;">Effort Productivity = Test Planning Productivity = No of Test cases designed / Actual Effort for Design and Documentation<br /></span><br /><span style="font-family:verdana;font-size:85%;">Test Execution Productivity = No of Test cycles executed / Actual Effort for testing </span>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-87463607560733125812009-06-18T20:48:00.000+05:302009-06-18T20:59:07.130+05:30Software MetricsSoftware metrics are an integral part of the state-ofthe-practice in software engineering. More and more customers are specifying software and/or quality metrics reporting as part of their contractual requirements. Industry standards like ISO 9000 and industry models like the Software Engineering Institute’s (SEI) Capability Maturity Model Integrated (CMMI®) include measurement. Companies are using metrics to better understand, track, control and predict software projects, processes and products.<br /><br />The term software metrics means different things to different people. When we buy a book or pick up an article on software metrics, the topic can vary from project cost and effort prediction and modeling, to defect tracking and root cause analysis, to a specific test coverage metric, to computer performance modeling. These are all examples of metrics when the word is used as a noun. I prefer the activity based view taken by Goodman. He defines software metrics as, "The continuous application of measurement-based techniques to the software development process and its products to supply meaningful and timely management information, together with the use of those techniques to improve that process and its products." [Goodman-93] Figure 1, illustrates an expansion of this definition to include software-related services such as installation and responding to customer issues. Software metrics can provide the information needed by engineers for technical decisions as well as information required by management.<br /><br />If a metric is to provide useful information, everyone involved in selecting, designing, lementing,<br />collecting, and utilizing it must understand its definition and purpose.Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-5312324632611779102009-06-15T18:58:00.000+05:302009-06-15T20:49:31.201+05:30Function Point Analysis<span style="font-family:verdana;font-size:85%;"><strong>Introduction To Function Point Analysis </strong><br />Software systems, unless they are thoroughly understood, can be like an ice berg. They are becoming more and more difficult to understand. Improvement of coding tools allows software developers to produce large amounts of software to meet an ever expanding need from users. As systems grow a method to understand and communicate size needs to be used. Function Point Analysis is a structured technique of problem solving. It is a method to break systems into smaller components, so they can be better understood and analyzed.<br /><br />Function points are a unit measure for software much like an hour is to measuring time, miles are to measuring distance or Celsius is to measuring temperature. Function Points are an ordinal measure much like other measures such as kilometers, Fahrenheit, hours, so on and so forth<br /><br />Reboot! Rethinking and Restarting Software Development - Online book<br />Online self paced function point training.<br /><br />Human beings solve problems by breaking them into smaller understandable pieces. Problems that may appear to be difficult are simple once they are broken into smaller parts -- dissected into classes. Classifying things, placing them in this or that category, is a familiar process. Everyone does it at one time or another -- shopkeepers when they take stock of what is on their shelves, librarians when they catalog books, secretaries when they file letters or documents. When objects to be classified are the contents of systems, a set of definitions and rules must be used to place these objects into the appropriate category, a scheme of classification. Function Point Analysis is a structured technique of classifying components of a system. It is a method to break systems into smaller components, so they can be better understood and analyzed. It provides a structured technique for problem solving.<br /><br />In the world of Function Point Analysis, systems are divided into five large classes and general system characteristics. The first three classes or components are External Inputs, External Outputs and External Inquires each of these components transact against files therefore they are called transactions. The next two Internal Logical Files and External Interface Files are where data is stored that is combined to form logical information. The general system characteristics assess the general functionality of the system.<br /><br /><strong>Brief History<br /></strong>Function Point Analysis was developed first by Allan J. Albrecht in the mid 1970s. It was an attempt to overcome difficulties associated with lines of code as a measure of software size, and to assist in developing a mechanism to predict effort associated with software development. The method was first published in 1979, then later in 1983 . In 1984 Albrecht refined the method and since 1986, when the International Function Point User Group (IFPUG) was set up, several versions of the Function Point Counting Practices Manual have been published by IFPUG. The current version of the IFPUG Manual is 4.1. A full function point training manual can be downloaded from this website.<br /><br /></span><br /><span style="font-family:verdana;font-size:85%;"><strong>Objectives of Function Point Analysis<br /></strong>Frequently the term end user or user is used without specifying what is meant. In this case, the user is a sophisticated user. Someone that would understand the system from a functional perspective --- more than likely someone that would provide requirements or does acceptance testing.<br /><br />Since Function Points measures systems from a functional perspective they are independent of technology. Regardless of language, development method, or hardware platform used, the number of function points for a system will remain constant. The only variable is the amount of effort needed to deliver a given set of function points; therefore, Function Point Analysis can be used to determine whether a tool, an environment, a language is more productive compared with others within an organization or among organizations. This is a critical point and one of the greatest values of Function Point Analysis.<br /><br />Function Point Analysis can provide a mechanism to track and monitor scope creep. Function Point Counts at the end of requirements, analysis, design, code, testing and implementation can be compared. The function point count at the end of requirements and/or designs can be compared to function points actually delivered. If the project has grown, there has been scope creep. The amount of growth is an indication of how well requirements were gathered by and/or communicated to the project team. If the amount of growth of projects declines over time it is a natural assumption that communication with the user has improved.<br /><br /><strong>Characteristic of Quality Function Point Analysis </strong><br />Function Point Analysis should be performed by trained and experienced personnel. If Function Point Analysis is conducted by untrained personnel, it is reasonable to assume the analysis will done incorrectly. The personnel counting function points should utilize the most current version of the Function Point Counting Practices Manual,<br /><br />Current application documentation should be utilized to complete a function point count. For example, screen formats, report layouts, listing of interfaces with other systems and between systems, logical and/or preliminary physical data models will all assist in Function Points Analysis.<br /><br />The task of counting function points should be included as part of the overall project plan. That is, counting function points should be scheduled and planned. The first function point count should be developed to provide sizing used for estimating.<br /><br /><strong></strong></span><br /><span style="font-family:verdana;font-size:85%;"><strong>The Five Major Components<br /></strong>Since it is common for computer systems to interact with other computer systems, a boundary must be drawn around each system to be measured prior to classifying components. This boundary must be drawn according to the user’s point of view. In short, the boundary indicates the border between the project or application being measured and the external applications or user domain. Once the border has been established, components can be classified, ranked and tallied.<br /><br />External Inputs (EI) - is an elementary process in which data crosses the boundary from outside to inside. This data may come from a data input screen or another application. The data may be used to maintain one or more internal logical files. The data can be either control information or business information. If the data is control information it does not have to update an internal logical file. The graphic represents a simple EI that updates 2 ILF's (FTR's).<br /></span><br /><span style="font-family:verdana;font-size:85%;">External Outputs (EO) - an elementary process in which derived data passes across the boundary from inside to outside. Additionally, an EO may update an ILF. The data creates reports or output files sent to other applications. These reports and files are created from one or more internal logical files and external interface file. The following graphic represents on EO with 2 FTR's there is derived information (green) that has been derived from the ILF's</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">External Inquiry (EQ) - an elementary process with both input and output components that result in data retrieval from one or more internal logical files and external interface files. The input process does not update any Internal Logical Files, and the output side does not contain derived data. The graphic below represents an EQ with two ILF's and no derived data.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Internal Logical Files (ILF’s) - a user identifiable group of logically related data that resides entirely within the applications boundary and is maintained through external inputs.<br /></span><br /><span style="font-family:verdana;font-size:85%;">External Interface Files (EIF’s) - a user identifiable group of logically related data that is used for reference purposes only. The data resides entirely outside the application and is maintained by another application. The external interface file is an internal logical file for another application.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;"><strong>Summary of benefits of Function Point Analysis</strong></span><br /><span style="font-family:verdana;font-size:85%;"><br />Function Points can be used to size software applications accurately. Sizing is an important component in determining productivity (outputs/inputs).<br />They can be counted by different people, at different times, to obtain the same measure within a reasonable margin of error.<br />Function Points are easily understood by the non technical user. This helps communicate sizing information to a user or customer.<br />Function Points can be used to determine whether a tool, a language, an environment, is more productive when compared with others.<br /></span><span style="font-family:verdana;font-size:85%;"></span>Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0tag:blogger.com,1999:blog-5693924795156610900.post-44444846226890889682009-06-10T18:11:00.000+05:302009-06-10T18:13:54.058+05:30Introduction to Rational<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link style="font-family: verdana;" rel="File-List" href="file:///C:%5CDOCUME%7E1%5CDIPTI%7E1.THA%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:1627421319 -2147483648 8 0 66047 0;} @font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:536871559 0 0 0 415 0;} @font-face {font-family:AdobePiStd; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-alt:"Arial Unicode MS"; mso-font-charset:134; mso-generic-font-family:auto; mso-font-format:other; mso-font-pitch:auto; mso-font-signature:1 135135232 16 0 262144 0;} @font-face {font-family:"\@AdobePiStd"; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-charset:134; mso-generic-font-family:auto; mso-font-format:other; mso-font-pitch:auto; mso-font-signature:1 135135232 16 0 262144 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-update:auto; mso-style-parent:""; mso-style-next:"List Bullet 3"; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Tahoma; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-ansi-language:NL;} p.MsoListBullet3, li.MsoListBullet3, div.MsoListBullet3 {margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.75in; margin-bottom:.0001pt; text-indent:-.25in; mso-pagination:widow-orphan; mso-list:l0 level1 lfo1; tab-stops:list .75in; font-size:10.0pt; font-family:Tahoma; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-ansi-language:NL;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:-126; mso-list-type:simple; mso-list-template-ids:1068387460;} @list l0:level1 {mso-level-number-format:bullet; mso-level-style-link:"List Bullet 3"; mso-level-text:; mso-level-tab-stop:.75in; mso-level-number-position:left; margin-left:.75in; text-indent:-.25in; font-family:Symbol;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </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-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} table.MsoTableGrid {mso-style-name:"Table Grid"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; border:solid windowtext 1.0pt; mso-border-alt:solid windowtext .5pt; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-border-insideh:.5pt solid windowtext; mso-border-insidev:.5pt solid windowtext; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <table class="MsoTableGrid" style="border: medium none ; border-collapse: collapse; font-family: verdana;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td colspan="2" style="border: 1pt solid windowtext; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">Introduction To Rational<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">1)<o:p></o:p></b></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">Requisite Pro<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">2)<o:p></o:p></b></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">Rose<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">3)<o:p></o:p></b></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">Purify, Quantify, Pure Coverage<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">4) <o:p></o:p></b></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">Robot<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">5)<o:p></o:p></b></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">ClearCase<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">6)<o:p></o:p></b></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">ClearQuest<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">7)<o:p></o:p></b></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">SoDA<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> </tr> <tr style=""> <td colspan="2" style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:85%;">1<b style="">) Requisite Pro</b><o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">RequisitePro lets you organize, prioritize, trace relationships, and easily track changes to your requirements.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">RequisitePro combines both document-centric and database-centric approaches. By deeply integrating Microsoft Word with a multi-user database.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">The program’s unique architecture and dynamic links make it possible for you to move easily between the requirements in the database and their presentation in Word documents.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Why Use RequisitePro?<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">1.1<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Team Collaboration and User Satisfaction<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">A product development team typically includes a large number of individuals with diverse roles, such as business analysts, project leaders, product marketing managers, development managers, QA managers, developers, and testers.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">each person on your team has access to critical requirements information and is able to manage those requirements, team efficiency and effectiveness are promoted and project risk is reduced.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">1.2<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Flexibility Through the Web Component<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">RequisiteWeb offers a Web-based client for RequisitePro.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">RequisiteWeb allows users to access RequisitePro requirements information across an intranet. By using browsers—Netscape Navigator<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">or Microsoft Internet Explorer—RequisiteWeb provides a thin client solution to access project documents and data. No Rational application-specific files need to be installed on the user’s machine.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Using RequisiteWeb, you can modify the name, text, and attributes of requirements directly in the database and from within documents, and you can create, delete, and query requirements and assign new parents to them.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">following are the main features of RequisiteWeb:<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">- Viewing documents
<br /> - Modifying requirements (in documents or database)<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">- Creating requirements in the database<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">- Setting your own user password<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">- Viewing, modifying, and creating hierarchical relationships<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">- Creating traceability links within and across projects<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">- Filtering and sorting requirements<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">- Creating and replying to discussions<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">1.3<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Change Management<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Change occurs in practically every development project, but it does not have to<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">consume project resources or throw the project off course.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">RequisitePro enable you to establish and maintain dependencies between different requirements. As change occurs, these traceability relationships are flagged as suspect, so you can understand how change affects the entire project.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">For each requirement a change history is maintained, capturing the who, what, when, and why of the change.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">1.4<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Comprehensive Process Support<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">RequisitePro can help you meet your objectives of delivering precise, quality software. RequisitePro provides industry standard project templates and attributes.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">it can also import existing documents and be customized to support existing projects.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Whether your team follows a rigorous requirements management process, such as IEEE, SEI CMM, or Unified Modeling Language-driven use-case approaches, or is just beginning to define a formal process, RequisitePro can help you meet your objectives<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">A Quick Tour of Key Concepts in RequisitePro<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">overview of RequisitePro concepts and defines some terms that will help you get started.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Requirements
<br /> Requirement Type<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Requirement Attributes<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Project<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Project Database<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Project Version Control<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Project List<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Explorer<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Views<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Documents<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Document Type<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Hierarchical Relationships<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Traceability Relationships<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Suspect Relationships<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> </tr> <tr style=""> <td colspan="2" style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">2) Rose</b><o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Rose provides support for two essential elements of modern software engineering: component-based development and controlled iterative development.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Rose’s model-diagram architecture facilitates use of the Unified Modeling Language (UML), Component Object Modeling (COM), Object Modeling Technique (OMT), and Booch ‘93 method for visual modeling.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Visual modeling is the mapping of real world processes of a system to a graphical representation. Models are useful for understanding problems, communicating with everyone involved with the project (customers, domain experts, analysts, designers, etc.), modeling complex systems,<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">As software systems become more complex, we cannot understand them in their entirety. To effectively build a complex system, the developer begins by looking at the big picture without getting caught up in the details. A model is an ideal way to portray the abstractions of a complex problem by filtering out nonessential details.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Diagrams :
<br /> - UseCase Diagrams
<br /> - Seqence Diagrams
<br /> - Class Diagram
<br /> - State Transition Diagram
<br /> - Component Diagram
<br /> - Deploymnet Diagram<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Rose is the visual modeling software solution that lets you create, analyze, design, view, modify, and manipulate components.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Rose provides the collaboration diagram as an alternative to a use-case diagram.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Features<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Rose provides the following features to facilitate the analysis, design, and iterative construction of your applications:<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Use-Case Analysis<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ Object-Oriented Modeling<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ User-Configurable Support for UML, COM, OMT, and Booch ‘93<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ Semantic Checking<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ Support for Controlled Iterative Development<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ Round-Trip Engineering<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ Parallel Multiuser Development Through Repository and Private Support<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ Integration with Data Modeling Tools<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ Documentation Generation<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ Rational Rose Scripting for Integration and Extensibility<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ OLE Linking<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ OLE Automation<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">_ Multiple Platform Availability<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> </tr> <tr style=""> <td colspan="2" style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:85%;">3<b style="">) Purify, Quantify, Pure Coverage</b><o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Collecting Diagnostic Information During Playback<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Diagnostic Tools To :<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">- Perform runtime error checking
<br /> - Profile Application Performance
<br /> - Analyze code coverage during playback<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">3.1<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Purify :<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Automatically pinpoints runtime errors & memory leacks in all components of application and ensures that code is reliable.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">3.2<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Quantify : <o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Performance Profiler<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Provides Application performance Analysis<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">3.3<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Pure Coverage <o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Code Coverage Analysis Tool<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Provides details application Analysis<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Prevanting untested code from reaching the end user.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> </tr> <tr style=""> <td colspan="2" style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">4)<span style=""> </span>Robot</b><o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Rational Robot is a complete set of components for automating the testing of<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Microsoft Windows client/server and Internet applications running under<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Windows NT 4.0, Windows XP, Windows 2000, Windows 98, and Windows Me.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">The main component of Robot lets you start recording tests in as few as two mouse clicks. After recording, Robot plays back the tests in a fraction of the time it would take to repeat the actions manually.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Use Robot to:<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Perform full functional testing. Perform full performance testing<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Create and edit scripts using the SQABasic and VU scripting environments.<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:85%;">Test applications developed with IDEs Collect diagnostic information about an application during script playback.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">The Object-Oriented Recording technology in Robot lets you generate scripts by simply running and using the application-under-test.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> </tr> <tr style=""> <td colspan="2" style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">5) ClearCase</b><o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Central Repository for storing all articles<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Maintains Software Version Control<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Allows Developers to work in parallel by giving them their individual workspaces <o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Integrate all the changed code into baselines<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Ability to tack changes<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Manage the supporting files for each script<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> </tr> <tr style=""> <td colspan="2" style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">6) <span style=""> </span>ClearQuest</b><o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Is a change-reuest management tool<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Tracks and manages defects and changes requests througout the development process<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Manage every type of change activity associated with software development<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Submit defect directly from the Test Manager log or Site Check<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Modify and Track defects and change-request <o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Analyze projects progress by running queries, charts, and reports.<o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> </td> </tr> <tr style=""> <td colspan="2" style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:85%;"><b style="">7) SoDA</b><o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Use SoDA to create reports that extracts information from one or more tools in Rational Suite.
<br /> eg. You can use SoDA to retrieve information from different information sources such as Test Manager to create documents or reports <o:p></o:p></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 24.75pt;" valign="top" width="33"> <p class="MsoNormal"><span style="font-size:85%;">-<o:p></o:p></span></p> </td> <td style="border-style: none solid solid none; border-color: -moz-use-text-color windowtext windowtext -moz-use-text-color; border-width: medium 1pt 1pt medium; padding: 0in 5.4pt; width: 418.05pt;" valign="top" width="557"> <p class="MsoNormal"><span style="font-size:85%;">Reports :
<br /> - Analysis Documents
<br /> - Design Documnets
<br /> - Test Documnets
<br /> - Status Reports<o:p></o:p></span></p> </td> </tr> </tbody></table> <p style="font-family: verdana;" class="MsoNormal"><span style="font-size:85%;"><o:p> </o:p></span></p> Testingsolutionshttp://www.blogger.com/profile/09720545045002757220noreply@blogger.com0