Streamline your digital sales process for Quality Assurance

How to create outlook signature

so i guess it's time to introduce our first speaker um uh tina tinteriqueza will be first speaker tico can you hear me well yes it's okay okay great uh so tikkun i guess it's your turn and i will be let me share presentation okay uh good evening dear audience it's great pleasure uh to be here and taking part in such a nice webinar i would like to express my gratitude to exactpro for their effort in initiating and preparing for such a nice event let me introduce myself i am tina tinterick then my educational background is information technology and i have been working in software quality assurance direction more than 13 years in a different sphere now i'm in charge of software quality assurance direction at liberty bank at the same time i represent motivated id professionals group georgia software testing qualification sport who wants to establish software quality assurance in georgia in this way we can contribute our countries for their development i have divided uh today i would like to uh give overview how to impact digital digital product quality on business and i have divided my presentation into three main parts first of all uh i would i will be looking at uh what is digital quality and next i will go on how to assure it and last i will be focused on its impact on business uh let's uh start what is digital product quality moving to the more digitally embedded society the influence of software is far bigger this day it contributes um to upscale life standards enhance the business prospects and involves the smart world in addition to the industrial commercial in fact today software plays a critical role across over the week waste of common people however all it requires is a smooth and pale fail-proof functionality of the software in today's technology-driven world many enterprises are catching on the way for the disruption there are many drivers of this disruption they could be about the change technological environment involving business dynamics increasingly intense competition and such like disruption is a widespread concern for enterprises such a technology competition is on the verge of the disruption disrupting business model polaroid is a classic example a pioneer in digital imaging in the 1960s the company did not make a necessary investment to the whole the lead in the 1960s when digital photography over look filled although no one can predict the exact impact and expand of disruption of the next five years a recent study found that companies facing disruption generally take longer to respond than they expect despite having an effective response available with them given this enterprises must transform their way of working and product development such a technology is undergoing a major transformation using emerging technologies and artificial intelligence to innovate and develop new products and services is a fast becoming and new battleground for enterprises concepts such a data analytics boards blockchains and artificial intelligence are enhancing the product offering of enterprises and transforming the way products are developed in the context of software product development the typical dimension of product development are define design develop detect deploy and debrief define is focused on the requirement elicitation and analysis design and develop our focus on product development and architecture detect focus on quality assurance why deploy and debrief focus on development and maintenance of the product i would like to highlight software quality software quality in products is defined in terms of its fitness of purpose that is quality a quality product does uh precisely what the user wants is to do for software products the fitness of for for a purpose um use the fitness of use is generally explained in terms and terms or satisfaction of the requirement laid down in the crc document sorry although fitness of purpose is satisfactory interpretation of quality for many devices such a car mobile phone uh and etc for software products fitness of purpose is not wholly satisfactory definition of quality to better understand uh the topic of this topic let's use the analogy of the chair if you need new chair for our dining room we go to the store this is a different type of chairs and feel lost how to find the right model which cheer can we describe as a having good quality different people mention different things for me it's important that the cheer feed the rest of the interior decor and they and that they are stable and easy to clean uh for my daughter it's important that she can swing only without the fear of falling backwards the best way to address these needs it is to create a list of requirements do we need the arm sets should they be uh stackable uh what kind of materials and colors and etc uh we do the same with soft tour we create a list of requirement and measure the degree of compliance the biggest problem is that software requirement is very complex complex process and many customers lack of understanding of it the modern quality associated with a software product software products our quality models such as a following software device is set to be portable if it can be freely made to work in a various operating system uh environment in a multiple machine with other software products and etc a software product has better usability if a various categories of users can easily invoke the function of products a software product has excellent reusability if different model of product can quickly be re used to develop new products a software product is correct if various requirement as a specified in the crc document have been correctly implemented and the software product is maintable if bugs can be easily corrected as and when they show up new tasks can be easily added to the product and functionality of the product can be easily modified in practice the real relative importance of particular software characteristics typically depends on software domain uh product type and intending usage that software characteristics should be defined for and use it used to guide to the use to guide the development of each product uh dear audience please share um your uh your experience will be very interesting which criteria do you think is effective uh please share it with a slider oh we have one minute for this oh it's very interesting okay it's enough i think thank you usability yes as expected thank you for involving and sharing your uh insights uh let's uh continue our uh presentation and move now let's move to how to uh ensure software product quality uh quality assurance is a very important subject in the complex world of the software development we observe our software and find that it has discrepancies with the customer expectations a discrepancy in software is called a bug if we remove the bug from the software it does not automatically mean that it um now works flawlessly a requirement is the terms for customers expectation for a system and it could be um that the bug hides there there as well sounds difficult right uh that's so why we need dedicated uh qa engineers let's start with the assurance part in the keyway nowaday in the industry can ensure that your software is flawless every software application has at least one bug the question is do we know what is eat where is the eat and how do we want to um and uh do we want to let others find it uh how all that we accept that we can move on how can we ensure that we know about all the relevant but in our thought here we test the software we can also test all kind of documents designed and code testers have a comprehensive toolbox on how to collect information about the system in the test after the some time of testing you will now notice that there is a pattern of some kind on how bugs a fear appear on a appear or a repair when you discover the pattern um one thing you need to want to do is to reduce the number of known bugs or bug types from your product in the future we can divide this process into two steps first step is to analyze bug in software with the aim of finding the source uh right and how did a defect find a way in terms of your uh possible questions to ask is your system architecture too complex um a bad technical documentation a vague or contradictory requirement do our people have the necessary skill to design employment test the software uh the second step is to define a set of actions and procedures to avoid appearance of the same bugs in the future a typical approach might be define a set of guidelines and standards to prevent this type of failure in the future improve the quality of requirement by creating a checklist of what good requirements should cover or use a specific tool to help us to summarize with the help of analytical techniques that we collect information about software with the help of constructive software quality assurance methods we prevent reappearance of bugs from the known source uh so quality assurance requires the process and structure in order to analyze and improve software quality i took great to create to blackout that took place in the year 19 the 2003 2003 in the northeast of ua usa for causing 1 billion dollar loss was due to error in the million of the line of code and the total bugs cost also incurred a very heavy loss in the reputation of the business this is a just an example of what consequences people and business had to face due to the failure to the higher quality assurance control and management there are many such a consequences business phase even today not being able to deliver quality products incidents like this like have marked the importance of quality assurance more information than ever now what is a solution one of the most important and widely discussed trend with the software testing community is the shift left testing which means to start qr activities in the year or yearly stage of software development life cycle instead of overloading the quality team with task as the last stages of the development the solution is to start testing yearly so the qa team will get enough time to test software application so they don't need to squeeze testing time with the product team full of designers product managers developers and keyway testers it can be too challenging to convince everyone that it's necessary for everyone to be on the same page to the involucia kill early in the um in the cycle i believe that i believe that most of you know the basic difference between testing and quality testing is about identifying or uncovering the defect in the functionality and quality is about meeting the user's requirement it's also referred to the fit of purpose a shifting left in a keyway is all about applying our thinking on the lines of the feet of purpose no process can be a hundred percent perfect but we are using this approach to overcome our problems um through continuous uh shift lifting the testing and the brainstorming session um what the block areas bottlenecks and possible performance failures are identified in advance even though these discovers may lead to new design alternatives they are improved version of the original idea with this approach qa can provide feedback on user stories which can help to resolve logical conflicts and discrepancies in requirement uh shift left testing gives them more brain breathing room to tackle mistakes immediately after they are spotted with kiwi is involved uh yearly we can rest assure that the project will progress smoothly more defect will be identified earlier in the project requirements will be groomed more quickly and money and time restraints can be made more easily a shift left approach just dial does not end with the testers alone writing test cases before the code actually comes to comes into the testing stage will also allow to developers to take more ownership of their code and increase their responsibilities on testing this extra layer of the testing also creates positive vibes on the team it is more expensive to fix the um to fix things later in software testing software development life cycle therefore getting killed in wall as soon as possible allows issues to fix when it's less expensive to do once we plan a better uh we will get extra time and while uat is going on qa can continue to do exploratory testing this will ensure that the overall project is successful uh tester can accelerate project delivery by finding the facts earlier in the software development life cycle minimizing the time between release and thereby gaining organizational trust to conclude conclude it should be also mentioned that achieving quality is a team responsibility by team i mean everyone involved in creation of the feature of product developer test their project manager product owner and stakeholder each of this role is critical to software quality and process used to take it from the conception to the deployment uh introducing new ideas and process can be uh frightening for spam teams because change is hard uh we'll make mistake and um there uh could uh could be some lesson learned while execution but they uh but uh the key uh take away uh here is a shift left is much more than process change it is mindset and culture culture shift to setup [Music] to the subtle differences between software testing as of uh quality assurance are too significant significant uh to overlook when software testing emphasizes on technical aspect of the system quality assurance deal with the software specification it is a comprehensive and systematic method to ensure the quality of products delivered further quality assurance practice evaluate the development and test cycle including the techniques tools and process and standardize standardized quality assurance process verifies the standard of software components with other quite quality reviews also the process involved in process data collections and documentation procedures it's process oriented quality governance course rather than product centric supervision uh it focuses more on uh pre preventive measures than um rest restorative practices so now we should discuss why koi is essential for any business quality assurance plays a vital role in the accomplishing the expectation and demand of the clients it helps in saving costs as well as fixing the errors before they become major issues thus it is useful in maintaining quality standards if quality assurance is done are perfect it is useful for providing confidence testing the product there is a wide array of reasons why quality assurance is considered to be effective to your business take a look when quality assurance is done perfectly it plays a vital role in the growth of business it also beneficial in introducing the additional cost which comes while re replacing the retesting as the well as a reselling product [Music] having errors if the customers are not satisfied with the products of the company the backlash would result in demanding the reputation of the business besides this it's also affect the future product negatively uh furthermore um quality assurance saves your organization uh the organization from spending on legal expenses primary when the product does not meet the industry standards quality assurance is considered to be to be the best option to the ensure the product you are launching in the market is free from error and bugs in addition to this it's also beneficial in adding valid to the customers it also attracts your potential audience towards your brand or wide scale high quality of software application which is free from errors and banks can enhance the credibility and reputation of business thus the owners of business will be capable of boosting the profits as well as uh the growth of business uh regardless of the type of type of software you are producing it's a prerequisite that the software or application allows the user to make the task easy the software tester makes an assessment of the different aspects of the software from the perspective of it of end user in addition to eliminating all type of all type of performance and the uh bug issue software testing is useful in bringing an improvement in the user experience in a significant significant manner the improved user experience is useful in enhance the popularity sales and profit profitability of the application there is an instance when a malware at attack has reduced in the enterprises to stop a mobile application and website temporarily such a type of disruption would be a meter affect the uh reputation of the business continuous testing plays a vital role in the improvement to the weaker uh pieces of code uh besides this it's also beneficial in maintaining the security of the of any business um every end user um had option to select from a wide array of the software application with which features similar functionality and feature the owners of the visa business uh opted for every possible marketing options for the promotion of the software it is also useful in uh beating the competition if the software application is found to be flawless it becomes really easy for the market to go for the promotion of the application more confidently they highlight the user experience and quality of the software which helps them in the selling at selling it [Music] next benefit of every business organization uh looks so forward to find a base of happy customers in spite of launching a good quality of application and promoting the same with the aid of effective promotional campaigns as you offer premium quality of the software application that are free from errors and bugs you will gain success in keeping the customers happy and satisfied it's also useful in retaining your customers for a longer period the user experience is known to encourage to the end user in the promoting the application by a world of mouse there is a cell there is wide of assortment of companies that have earned a high reputation of offering top quality software testing services as you can make the products of your business flowers and the free from the errors with software testing you can find a boost in the property a profit pro profile profitability of your business so if we sum up my topic uh i would like to highlight that uh digital uh product development is a complex process which involves specialists from a different domain quality assurance is a discipline um which shadows software development starting with the gathering of the requirement and ending with testing worldwide scenarios with the aim of finding errors as soon as possible analyze them and improve the process to reduce eliminates those type of works and errors uh why do we do all these uh because prevention and reduction of drawbacks as early as proposed possible uh costs less than rework involved in fixing the bug in this case we can talk about building quality it's smart business decision to invest in effective quality assurance uh thank you uh for your attention dear ordered auditory it was last part of my presentation if you have any question i'm ready to answer them uh just to remind you you can write the questions in the chat and i will uh tell the question to tina tien and she will answer them orally so we are waiting for the questions from you um we have one question from anna okay is it possible to change the software quality after it has been compiled well it's good question now the question i think you mean to us if it is possible to improve the quality of the software after it has been deployed i would say yes it is possible to improve uh the quality but we need to know what the quality was before the change was the change is that is being called contemplated the purpose of the change and what quality factors have been accomplished already or not accomplished already before we can say if the change improves the quality ultimately the user has the final world on quality so uh they will be the final world on weather quality has improved but we can make an educated guess about their response by having the information listed previously so we can make a decision about whether the change should uh be made or not the nature of the change the size and scope of the change and what aspects of quality is how hoping to be changed all factors into into decision uh color changes or logo placement may be a lot easier to change and improve the quality of the software with a opposed to previously unreleased and new security module for example so as it is for so much of software the answer really is it depends uh sorry i wasn't muted um anna uh i hope that the question was clear if you have any other questions you're welcome to uh ask them okay yeah i see that it's clear uh tico thank you if you have an additional question for your report yeah uh you can still ask the questions in the chat and tico will go straightly to the chat and answer them directly there thank you tico once again you