<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Arunoda Prabodani on Medium]]></title>
        <description><![CDATA[Stories by Arunoda Prabodani on Medium]]></description>
        <link>https://medium.com/@aprabodani?source=rss-7891b6bbae46------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*aw6WdHE7gPdXiqnG</url>
            <title>Stories by Arunoda Prabodani on Medium</title>
            <link>https://medium.com/@aprabodani?source=rss-7891b6bbae46------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:36:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aprabodani/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[State Transition in Software Testing]]></title>
            <link>https://aprabodani.medium.com/state-transition-in-software-testing-c0bb4075ffa6?source=rss-7891b6bbae46------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0bb4075ffa6</guid>
            <category><![CDATA[software-test-design]]></category>
            <category><![CDATA[state-transition-model]]></category>
            <category><![CDATA[state-transition-testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Arunoda Prabodani]]></dc:creator>
            <pubDate>Thu, 05 Aug 2021 05:01:28 GMT</pubDate>
            <atom:updated>2021-08-05T05:01:28.744Z</atom:updated>
            <content:encoded><![CDATA[<p>State Transition Testing is a type of black box testing which helps to determine the change in state or output in the Application Under Test according to the changes made in input. This helps to test the application under different input parameters (Positive or negative inputs) and observe the system behavior.</p><h3>When to use State Transition?</h3><p>This type of testing is helpful when the tester needs to test the system for finite number of inputs. It can determine different system transitions for sequence of inputs. But, this is not suitable for exploratory testing and for systems that has an exponential growth in the input parameters as well. The tester always needs to have a clear vision on the inputs and respective output from the system.</p><h3>Components of State Transition model</h3><p>A State transition model consisted of two main components, such as <strong>State and Transition.</strong></p><p>State transition can be presented in a State <strong>Transition Diagram or State Transition Table</strong>. In a State Transition Diagram, the States are represented by a box and the transitions by arrows.</p><p>In the table states are described in the left, events are described on the top. Each cell represents the system state after the event is occurred.</p><p>Example: A login screen where the user has to provide the correct username and password to login to the system. User will be given three attempts to provide the correct credentials and if the the system will be locked if user is unable to provide correct credentials within these three attempts. Correct combination of username and password with grant access to the system</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rxm9Yax6F03oaSRhEGeQKQ.png" /><figcaption>Table 1 : State Transition Table</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dn-SuanudK7M3AJ_7bn5KQ.png" /><figcaption>Diagram 1: State Transition Diagram</figcaption></figure><h3>Advantages and Disadvantages of State Transition Testing</h3><p><strong>Advantages</strong></p><ol><li>State Transition Model provides a graphical or tabular representation of the System behavior which makes it easy to understand the testing scenarios for the tester. Hence, the testing team does not miss any path to test which makes it easy to verify the all conditions are covered and the results are captured.</li></ol><p><strong>Disadvantage</strong></p><p>1. This method is not suitable for exploratory testing.</p><p>2. If the System does not have finite number of inputs and outputs where the functionalities are in sequential order, this method is not practical.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0bb4075ffa6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Information and their characteristics]]></title>
            <link>https://aprabodani.medium.com/information-and-their-characteristics-f5cdb0c2ce14?source=rss-7891b6bbae46------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5cdb0c2ce14</guid>
            <category><![CDATA[big-data-analytics]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[information]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Arunoda Prabodani]]></dc:creator>
            <pubDate>Wed, 09 Jun 2021 13:41:49 GMT</pubDate>
            <atom:updated>2021-06-09T13:41:49.811Z</atom:updated>
            <content:encoded><![CDATA[<p>We are surrounded by information. We always work and deal with information everyday. But, have we thought where this information come from, or how this information is created. So, today let’s talk about What is information and how it is created.</p><p>Before, we start our journey on information, there is one more topic we need to focus on. It is <strong>Data. </strong>Data is as much as important as Information because it is the foundation of information. Without Data, no Information can be created.</p><h3><strong>What is Data?</strong></h3><p>Data is <strong>raw facts and figures. </strong>It can be numbers, characters, symbols or images which does not provide an exact meaning or properly organized. For an example, 12,10,45,7,3.5 are numbers. Does it give you a meaning? Or are these numbers properly organized? They are just few number which do not bear any relevance to anything particular. Or, let’s take some characters such as A, B, G, F, c, r, f or some symbols such as @, &amp;, $. Do they have any meaning? The answer is No. So, these types of raw facts can be considered <strong>Data</strong>. So, <strong>Data is meaningless and not properly organized.</strong></p><h3>What is Information?</h3><p>Information is data organized meaningfully. We use data as input in the process of creating information which is meaningful and properly organized. If I take the numbers I used as Data before; 12,10,45,7 , I can organize these data into meaningful information as follows.</p><p><strong>Marks for ICT subject of students of Grade 12 -A class</strong></p><p><strong>Ann-12, George-10, John-45,Mark-7</strong></p><p>Does this covey some meaning to you? Yes, isn’t it? So, this is called information. The raw figures which we obtained as Data is processed and well organized which gives us information.</p><h3>Data vs Information</h3><p>According to above example, you can understand that we can create information by processing data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/561/1*nwOs0NmHHSKSEvbzzGqwUQ.png" /></figure><p>Data alone is rarely useful. But, information created from data is highly valuable. This process of creating information is used everywhere. Since we are focusing on Computer Systems, let me give you an example.</p><p>Think about a Super Market. You buy different items and hand them over in the cashier. The person in the counter add the details of these items one by one into the Computer System and process the Unit Price, Number of Items, Total amount, discounted price, etc. Finally he hand you over a nicely printed bill which contains all the information you want. It is well organized. It provides meaning to you. The bill contains information which is processed through a Computer System which took Data as input. This is one simple example. There are millions of Computer Systems which does the same thing. Process Data and generate Information.</p><h3>Types of Data</h3><p>Data can be classified into two types.</p><ol><li>Qualitative Data — Qualitative Data can be defined as data which describes characteristics. It does not convey any numerical value. For an example if you are collecting data about quality rather than quantity, those data can be classified as Qualitative data such as Colour, Accuracy, Clarity, etc.</li><li>Quantitative Data — Quantitative Data as the word suggests, it is data which describes the numerical values. It is measurable and arranged in numerical order or subjected to arithmetic process. For an example, Marks obtained for ICT paper.</li></ol><h3>Characteristics of Information</h3><p>With all these explanation, you might have thought that all information is valuable. Yes. Information is valuable, but only if the information have following characteristics. Information with these characteristics help us making smart decisions.</p><ol><li>Relevance — Information should be relevant or suitable to the purpose for which it is required. So, if a manager requires information on marketing strategy of the company, but provide employee’s performance information instead, the relevance of information is not acquired. So, though the information is generated it will not be valuable.</li><li>Timeliness — Information should be produced in the correct time which is needed the most. If the information received after the due course is finished, the value of information is less.</li><li>Accuracy — The provided information should be accurate and realistic. If it is not, the decisions taken based on wrong information can lead to many issues.</li><li>Completeness — Information should contain all the details required by the user. Otherwise it may not be useful for the decision making process.</li><li>Understandability — Information should be put in a way users can perceive the intended meaning easily. It should be clear and unambiguous. If it is not understandable enough then the value of information is less.</li></ol><h3>The golden rule of Information</h3><p>The golden rule of information presents that the value of information at the highest at the time the information is created. With time, the value is gradually reduced.</p><figure><img alt="The golden rule of information" src="https://cdn-images-1.medium.com/max/224/1*uMkpo5wy3MkehjeJ4XrD1Q.png" /></figure><h3>Big Data Analytics</h3><p>Organizations such as large private companies and research institutes capture terabytes of data about their user’s activities in business and social media. They process these data and provide us with various suggestions based on our likings and expectations. For an example, when you visit YouTube, it suggests hundreds of videos which may interest you. Those information is captured based on the past videos and topics you have searched or watched frequently. And if you search on building or re-designing your home, some social media pages would suggest you pages, groups or ideas which is relevant to that. Interesting, isn’t it? This is called Big Data Analytics. It involved collecting data from various sources and manage and process them in a way where to fulfill the organization’s data requirements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5cdb0c2ce14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Test Estimation Techniques]]></title>
            <link>https://aprabodani.medium.com/test-estimation-techniques-fc8a88acd59f?source=rss-7891b6bbae46------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc8a88acd59f</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-software]]></category>
            <category><![CDATA[estimations]]></category>
            <category><![CDATA[test-estimation]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Arunoda Prabodani]]></dc:creator>
            <pubDate>Tue, 08 Jun 2021 12:40:42 GMT</pubDate>
            <atom:updated>2021-06-08T12:45:47.438Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What is Software Estimation?</strong></p><p>Estimation as the word suggests is a rough calculation of the value, number, quantity, or extent of something. In a Software project, estimation is planning and managing effort, time and cost that take to complete the project activities.</p><p><strong>What will happen without proper estimation?</strong></p><p>Poor estimation leads to dragged timeline, undesired product and finally an unsatisfied customer. The company will not be able to provide the expected product to the customer in the expected timeline and budget.</p><p>To overcome these issues, Software projects use different Estimation methods</p><p>Before we start estimating, we need to have a clear vision of <strong>What to Estimate</strong></p><p><strong>What to Estimate?</strong></p><p>1. <strong>Resources </strong>— We need to have enough resources to carry out our project activities. Resources can be people, hardware, software, facilities, etc. The project team need to have a clear idea on the quality and quantity of the resources needed in the project</p><p>2. <strong>Time </strong>— Time defines the success of a project. Even though the team provides the best solution, it is not provided during the desired timeline, the customer will not be satisfied. So, time is very important in a software project. Each project task needs to have a clear time to start and finish.</p><p>3. <strong>Human Skills</strong> — The skillset of everyone in the team affect the estimation. A team with high technical skills will finish the project in a less given time than a team with low technical skills.</p><p>4. <strong>Cost </strong>— The project team should have a clean understanding of how much it will cost for each activity in the project.</p><p><strong>The Estimation Process</strong></p><p>Same as other project activities, there is a process for Test Estimation too.</p><p><strong>Step 1: Divide the project into small tasks</strong></p><p><strong>Step 2: Assign each task a team member</strong></p><p><strong>Sep 3: Estimate effort for each task</strong></p><p><strong>Step 4: Estimate effort for total project</strong></p><p>It is always better to have the project divided into smaller tasks before we start our estimation process. It will make the estimation process simple and easy. You can use a work breakdown structure technique to divide the project into modules and modules into small tasks. Then, assign each task to a responsible person from the team. Now, we need to focus on how to estimate effort for each task. Let us go through few techniques that are used in the industry now.</p><h3><strong>Wideband Delphi technique</strong></h3><p>This method involves multiple estimators and obtain an overall estimate by combining their individual estimation. This method focuses more on experience rather than any statistical formula.</p><p>Wideband Delphi techniques consists of four steps.</p><h4>Step 1. Kickoff meeting</h4><p>The kickoff meeting describes the project and its requirements to all estimators. All the estimators agree on the same standard to follow in carrying out the estimation.</p><h4>Step 2. Individual Estimation</h4><p>Each estimator estimates the tasks.</p><h4>Step 3. Discussion Meeting</h4><p>All the estimators present their estimation and reasons for the estimation for each task and discuss problems and solutions which will be taken into consideration for the next round of estimation process.</p><h4>Step 4. Repeat</h4><p>Repeat Step 2 and 3 as many times as necessary until obtaining a clear and sufficient estimation which is agreed by all the estimators.</p><h3>Function Point/Testing Point Analysis</h3><p>This method involves dividing the system under test to smaller functionalities. The more complex the system is the more functionalities are there. After deciding the functional points the Test Manager has to give weightage to each functional point considering the complexity. Based on the weightage of each functional point we can decide the complexity of the module. For example, if the weightage of certain functional points are 2,5,3 and 3 , the total weightage of the module is 13. Based on the total weightage of each module, the complexity can be decided.</p><p>So, after you provide weightage to each functional point the testing duration (how much time needs to test) can be decided.</p><p>Based on the effort and time, the cost for each functionality also can be measured.</p><h3>3-Point Software Testing Estimation Technique</h3><p>This is one of the simple but useful technique followed by Project Manager. But it is mostly based on the experience level of the Project Manager.</p><p>In this method, each task is estimated based on <strong>three </strong>values.</p><p><strong>The best-case estimate</strong></p><p><strong>The most likely estimate</strong></p><p><strong>The worst case estimate</strong></p><p>The Project Manager needs to come up with testing duration for each task in all these three cases. And based on a statistical analysis the duration for the task can be determined.</p><h3>Percentage Distribution</h3><p>In this method all phases of Software Development Life Cycle are assigned effort in percentage (%) based on past data and experience. Then, percentage for all testing activities are further assigned.</p><h3>Test Estimation best practices</h3><ol><li>Have a buffer time</li></ol><p>What if one of your talented member suddenly quits the job, or testing environments gets delayed or unsupportive? Unpredictable things can happen within the project. So, we need to add some extra time for the Testing tasks when preparing the estimation</p><p>2. Plan for inevitable</p><p>What if the Test data you received are corrupted so you need to request them again from the customer which may take additional two days. What if some of your hardware or software gets corrupted so you need to replace them in the middle of testing. There is a risk in everything. So, you need to have a backup plan and risk mitigation plan with the estimations.</p><p>3. Follow your estimation</p><p>Unless there are major changes in the requirements or project plan, the estimation should not be changed time to time. You need to stick to your estimation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc8a88acd59f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>