 we will go through some of the test standards or it was told in the earlier session like the test standards we must for test that or the test will be in order to have a test plan, specification procedure, we will go through what is the test plan, sorry what is the test standard then we will try to apply what are the standards we will go use with an example and to recap some of the session inputs from the last class we went through the specification example just based on how to write how what is the format, what are the contents of test paper and how it is designed so what are the steps that is needed, similarly test procedure also we had discussed, test procedure should be 100% covering the test piece, we also went through the test procedure example which identified the grouping of the test paper test cases only we have identified in the test specification and that is grouping of the test procedure what we will do is we will lay out the practical steps of the test paper which we have laid out in the test case of the test procedure, very simple but then independent of the test paper which has mentioned the of the test and all line, the mapping to the test and all line with each of the procedure we will have to see the difference, in the end we will identify the various tools and setup and test bench whatever it is, it only there are two types, one is automated, the other one is manual type both are similar in terms of the tools and the rest except that manual testing we use the white box approach that means the embedded target procedure, in the earlier session we went to the example test procedure test procedure is organized as per the template and it will help into all the test cases which are given to the test procedure and we will refer some of the external document, interval document, system of supply document also we have discussed about automation testing, PC based application and manual testing also we have identified the tools used, the hardware tools and software tools we will not go through again all this, we will share all these templates and examples so that you have any questions you can take back from me on this example okay then we had discussed about the setup procedures how it should be laid out and to build a program on to the embedded and how we are going to do it etc also we came to know that test execution can be done through the scripts the scripts are developed based on the test procedure steps, test procedure steps can be part of an Excel sheet the spreadsheet can be used for automating the PC based testing then we had discussed about manual testing which has integrated development environment which has multi course methods to be developed various separate personal steps for manual testing these are the typical testing environment where in the tools and all that interfaces are driven through the PC the interface could be any of the interface connected with the target interface could be canned with the manual speed and to feed the real time values we use a break of box or test panel which will have all the test speeds and logs etc then we had fabricated automated test procedures the test flow will be written here and the script what we have done in the earlier stages could be inserted basically the script can be inserted or we can refer to the considered scripts here similarly the manual testing procedures how it should be this also can be done through the script as it is script also can be developed for an IDE that integrates with development environment which will have a connection on the debugger debugger accepts those commands automatically therefore we can have pretty conditions for the particular two tests those three conditions are in between the type of testing manually used before we start the test it could be setting some values or setting our own capacity so also we have a third example of automated test setup manual testing how it should be also we can have a test software build information inside the Android software as I said the software will be something like a special build which will allow user to monitor or track or get the data only from the target then we will highlight the tools function any special instructions to plug in the tools whether tools are qualified or those qualified data all will be implemented here then we will have a session called software download procedure it will allow us to download the software that is the both the test course here so we come to test standards for us to do all these activities there has to be a standard against which the test software against the test software also it has other information which will be used for evaluating or reviewing the tests which are done in the test exhibition space so the standards it establishes the embedded software system software test stage designing the specific standards applicable for the system and the test base if any variants that can be applied if any deviation or if any changes for a specific that needs to be done all these standards will be highlighted and it highlights the purpose of the test standards in terms of methods tools or any rules or guidelines that has to be used for this case for design and development so these standards will be frozen during test plan these standards have to be available when we are done with the test plan this is the software planning or test plan this is used by the testers for example the role is the response to a safety critical objective of 100% coverage of high level requirement that means this role can be the user of the testers has to cover 100% of the requirement and there will be some guidelines which will be method for the other participants the high level test case can have a normal range robustness etc so all these design also the test cases in terms of for testing course condition all these will be part of the test standard so we will go through an example test standard basic template will be test planning, test procedure where in all the stakeholders the tool chain and the revision and all these things so basically test standards will have an introduction with purpose responsibilities test control mechanism compliance and the reliability of the test as you can see the standard, the standard we will go through and then we will use the function so the next the selection of the test 해부 it is a problem this is the result How the system how the space should be we have single time frame, the same time frame ్ ప్త్శ చ్మారోఏని ఇ్లెం ప్మారోని ఇలో చ్యాస్ంంద్ ప్స్మారోని ప్స్టు గసిచిసిన్స్ చ్స్ంద్ సిక్ట్ ప్మాస్ప్యం �!బ్లా చాన్టి వ� చితాలింలి గార్ని. మ౨ియా. పోరిక్త్త్ పాలి మ౨్. ందాాలిమ౶కాట్చార్, చానార్నిమ౶ర్ మద్. పిర్గుర్నా. పిల్నిట్. పిక్టికాని. థావార వారజి, వాడి వాంితబి. పిసివాయెండి. గారర ది నివ్ల మి. ఇదిసిలి పిక్సి. ఆది . గ౒గరందియాల Darwin rock కార్ముర్రు చార్లులు నినాయాలిమిన్ల్లు లిమియు. దిర్పిందియాని దిలులోమారి. మౕందిదిను మనార్ను . పధోటిఇవార్. చివార్టి ఆర్ప ఇిని ఇర్ల్కోధింది. , కారంలేకెతకని కిచిపి ఇసాన౿కెకి . వట్బిలేకికాంది. మంచి నిమంటోచి మది పకండికి. మాతరి ముర్లాన్ప్. ఇలెలి ఴర్త్ల్. మాత్ల్లెర మాన్ర్లి కి మయాస్. సింిమాస్టా. ప్నిలి ప్ప్చి లానిలి ప్సఞి మాత్నకిలి ఆడిస్. పత్ so after high level test cases description shall comply with this document that means after this document pointers the high level test cases are to be done that means that the rules guidelines will compare to different in this document that will be followed to the level test cases on this document and this document talks about rules and guidelines what are the differences the rule is a response to safety criteria of this test guidance is formalisms and template constitute all this will be part of the this guidance will give a pointer to the user after step in terms of m methods what are the critical details about how test data should be developed it is a strictly a guidelines stop the rule is a mandatory stop the verification of the application of rules guidelines can be done that means once the test cases or procedures the execution is done that means to be verified against this document that is one of the rule 6 this is the one rule that is part of the rule 6 that now coming to methods and rules for design and development of this paper the aim of high level test cases description activity is the verification of executable update which complies with the software requirements executable update is robust with high level requirements that means the executable program or the program that is running on the embedded target should be complied with the software requirements it should come up to the SRF and it should be robust with the high level requirements and it should take care of all the robustness in terms of the test environment or the development and the executable object or if compatible with the target computer okay so next one is to verify that the embedded software product satisfies its high level requirement the software high level test cases should receive the following application that means all the test cases that is developed for a high level software requirements these are all a few examples can be tailored or a specific need of this update can be done requirements of hardware software and the service should be robust only in the best requirement those needs to be taken into into the experience or in the case of the requirement these should be these are all a life if someone wants to do an integration in the case of the aspects of the software the test cases activity as we call in the SRF this kind of document and this is the plan for all this that we consider as the input for development in the test case output of the test case activity is the software description document that is the test case document itself will be in the output of the test case development okay now coming to normal range test cases basically this section identifies what are the methods that are used for requirement test cases there are normal range there is well equivalent slots there is the limits value the table based logic equation or any specific cases or other steps all this will be highlighted this again depends on the target that is being under we will go through in some normal range test cases we will have normal range inputs of the normal range of testing for the specific the requirement follows the user to see that value is something like 1 to 10 the normal range is between 1 to 10 anything between 1 to 10 is called as normal range this 1 to 10 is normal range next as I said there should be an equivalent class that should be analyzed for that specific requirement so equivalent class will be applied on these inputs and also there is one point I think very important that a requirement can take only one input based on the condition it could try several or thank you for that so how are you going to do it how are you going to identify so we need to have consideration of the output also based on the input and other conditions this is very important so the equivalent class should be applied on both the input and the input as I said yesterday the input could be 1 it would be 5, 7, 8 and etc generally what we use is the boundary cases for that particular requirement as I mentioned so one definitely has to be there can have to be there because these are falling on the boundary there can be an intermediate value so that is 5 similarly that output of the requirement is 15 and 20 so both the needs should be exercise that means we should write a case in particular way that all the outputs that are derived out of a particular requirement should fall into one of this case design of course suppose 15, 20, 25, 3 outputs are there which will make sure that 15 and 25 are exercised definitely as a normal range and the need range as 20 so that we have exercised all this normal as the equivalent class okay next we have a limit values that means objective of this analysis is to verify the ability of the target system to respond to the input taken at the limits of the input what it means is that if there is an input of say 1 and the requirement says 1 plus or minus 0.1 that means 10 percent of that 1 is used then that needs to be exercise if we should have an ability to analyze the requirement in terms of the limit values that means 1 plus or minus 0.1 means it could be 1 minus 0.1 that means input can take 0.1 minus 0.1 that means input can take how much 0 1 minus 0.1 that means 9 and that will take 1 so this means to be used there are this is useful especially for the analog inputs where we use analog which have a power transfer etc that is very important after the limit values next we have a tables suppose there are inputs mentioned with the help of the table in a structure then at least one case should be created for each bounds of the table and one another should be created for an intermediate point which is similar to the normal table saying that if the requirement is pointing to the table table needs to be exercise in terms of either an input or also based on the bounds if a lower bound upper bound and it should be an intermediate point okay next one is the logic equations if there are any logical equations like this is our and etc etc we need to use ncdc function also to obtain the input I will tell you what is ncdc is one of the important aspects of invirect owner modify the condition and this is how I will explain what is that that needs to be considered especially for multiple inputs or multiple inputs and ed% etc ఀిలెన చగిందారుంచిందటిక౮ిపిaf. నిఆసారిసారేనుటికిందిందానిందారేటి. అమిమందిందిందిందిందిందారినినింది. ఠ ార్తోకిలె మరర్ ప౎ర్తోకినేనినింది. నివసి నింది సెరింద్లాదార తమారాయిందింది. సి మారింద౿ న౸ిందాపిని. మియvänd పింరెతఖరి ధి aney ఓలాయా క్యి టలికైతెబాబ�)] మంెఇ , సటినిల్జక, is an event which pouch and AP . yet move to different stage within the software. o踨arry that course we have a August next dish. ఆర్ర్ లెవార్ర్ర్యు ఇట్వ్ర్ పొవమాస్యర్లికొరార్ మ్ంరోకొర్రో. మ్రార్ స్ర్రంటన్లం పెరెత్టం పుత్త్తమ్నంనంనినంనిక్. న పిడి మత�이ికినిత౾సి థంతిస్టి. గామం. సిందాయస్ పట్టి. సిసితియస్టాని నిటినిసి. మతికా ఉట్నమండలంది నివార్చి ఆపినినిస్న్. ిలార్టిని. మార్టాపిచాత్లు నిరండ్, మర్. కిమా మార్టా మార్టి అపొర్. in సింి పౚ ఆల్యా కెయెవాసాలు సైతింది ఓట సంత్హి, హారాసిదెయా తీటాసిటార్ సారా సిఇ్యఋ సారంద్య మేందాక్ప్టి కెయెసంది సన్లూది వినolé ఆంరనినితికరి. మర్లిం ఇకోమలు. అగాార్లి. అగార్. నింరటంటీలు. పైనాచి నిమరంకోనం. పైపై. పికింబతిని. పైపైసిపెడిసి. పైరికిస్సం. దా The next one is the first is the perfect test case of the development standard for the goals that is required for the requirements that this test case shall be applied on each of the high level requirements that means every test case should fall into the standard we are coming. So for each requirement the following elements are in different inputs the inputs of the requirements and which means the decisions in the requirement text that causes the requirement test case, equivalence class inputs I think in this format we have all the test cases expected based on this what are the outputs it will be having different. All this information should be added to the test as I said the beginner should be here and the test case the next tool is for each function requirement tested I will tell you the requirement of the test case. Yes sir. It should follow the identity key format as the requirement shall be covered at least one test case. We correct one. As I said every requirement is to be tested whatever the way you want to do the automated way or manual way or manual way whatever doing that you need to do that. Yes sir. Definitely there has to be one test case for each of these requirements and this will be correct one. The next tool is each test case of a test case table shall be covered by one scenario and very correct one. The same as whatever we spoke on the test table and the boundary values and all the things I need to correct. For each test case to define the value of the inputs and outputs of the associated requirements of the time required. If there are any supported requirements that also needs to be time required. Typical example for this will be a derived requirement. Derived requirement is something like sometimes what will happen is the this is talking about the derived requirement or any supportive requirement. What will happen is the primary requirement may be sufficient to address the functionality. We need to have a supportive requirement or it is called as derived requirement something like we have a multiple inputs that needs to be defined in detail. What will happen is the primary requirement we may not be able to define it completely. What we will do is we will highlight in the primary requirement these are the inputs that we need. And in the supportive or derived requirement we are going to mention that those inputs will take the value of this value of that which is called this law. Why this derived requirement is needed? Because alphalation of the requirement is very important. This requirement has to be unique and it cannot be AND data. That means one requirement cannot have a multiple requirement. That is a significant role that has to be addressed with a follow especially in the aerospace segment as seen. One identification or one requirement will address only one requirement it will not have multiple requirements. If you want to have multiple requirements tagging to that requirement then you have to identify the next requirement. That is what is the associated requirement or if needed you can have a derived requirement. So that is about this rule. Next rule is each scenario. This case and of course here it should be qualified as normal thing or you can add more based on the need. Similarly this type of testing is used normal thing or this type of thing you have discussed. Some test procedure you may not be able to execute on the car. You should have an index code and you can identify how it will be reviewed. Next one is your procedure. How procedures are AND different? That is I think we have gone to the example test procedure. It is similar to that. So unique idea is named parent for each test procedure. We are AND different. Who is responsible? I have said what type it is. Normal course norms review case. And what is the precondition and review case? To satisfy the course start of the test procedure. In case any external inputs that is to be used for testing that particular requirement. Description means how I am going to test it. This should be a description para certificate. Or we can add all the steps that is required in terms of practical. One of the products we have used in the test sheet because it is impossible to specify one step, two steps, three steps. So this is a test certificate. We should have this in the test sheet which will identify all the steps for previous to modified option for an upcoming document for the course. There are three in here too. That is one of the projects we have used. Up to the user depending on the maintainability requirement. All these can be done. Of course in the test certificate results we will highlight the proof of correction for each of these options. All the tests are done. And test branch or test setup specification needs to be encountered here before the procedure. Guidelines. These are all rules. Rules have to be followed manually. Guidelines are based on the need. Some requirements may need one guideline. Other requirements may need other guidelines. Guidelines are the precision. Something like a general guideline. This guideline. So one example description of the scenario should be here and after. The expected result should be different for each scenario. The scenario should have an output. It should result in an output. The test setup specification should be different for each scenario. As I said, each scenario has to be identified for the test setup. All and all will be needed. The preconditions should be identified for each scenario. Some of the requirements may not have preconditions. Directly, it can be done with preconditions. By itself, it may not have preconditions. In the case, it may have not preconditions. So let's take a look at the guideline. And in the end, we have the tools used to produce the test case development time. Usually it will be a document template. In the case example, we have a pump already. The repetition of the same. So the test case should be identified. Covering of the subject requirement. The scenario should be different for each scenario. The test case should be identified. The test case should be identified. The appendix installed all the test cases in the specific dialect. This is also part of the test case. The static analysis of the test case, the manual of the test case. All that will be part of the coverage. That is about the test case standard. So now up till now we have gone through test case. For example, we started with a test plan. Test case or test specification. Test procedure development. And testing standard. So with the help of that I wish to give you the name of the test case. Simple example I had to develop the test case. So you all know whiteboard. So the whiteboard requirements I have put the four requirements. What will be the appendix test case? The whiteboard. So requirements are something like whiteboard shall have a length of three feet but whiteboard shall allow to write on it. Whiteboard shall allow to erase the written words. Whiteboard shall allow to write colors like black, blue, green and red. That is why it is called whiteboard. So what we call now? For this what are the test cases? The few test cases which I have already discussed. I shall be whiteboard. I am very clear that the end time width of the board is three feet first requirement. Next test case could be check whether one can be able to write on the board. That is the next test case. You should allow to write. So that is why we have to write the test case. The next requirement you have tested with check whether one can be able to write on it. We will use verify in short games. For each test we have verified with check what we have to do. So measure the whiteboard the next test case is on. So we have written words which is the different, we should have to write that is the first thing. Next thing will be, we should be visible both are very important, also you can add to me something like this, verify what is the supplement basically, we have a stress here black you భా్ర్ మెయ్చ్పయు పోముయు సిట్బ్ాలీ సిసిసిలియాస్హివం సిలా్స్రై సిజసార్స్ట్ని టార్చ్చ్న్ నాంటికరక్ట్ంట్ ముపేస్టార్ర్. తర కానకలి ఆవసంలింది. ఇండారంలి.iper champions. మటరండంలి బక౾. కం. నిల బకి ని. ఉని. వపరంలి మంన౿ చాండ మినానందా బ్ల్న్ మతాల మి the you can have a generalize the requirement because we know that what whiteboard we are testing so this case is interesting because of that right here is the words written and written you have to verify that the words are erased it is there good that we have all the requirements sometimes what will happen the intuition user may add more requirement because he has a good knowledge of the system the system is whiteboard so during the review what will happen this will result in modifying the requirement I have seen that or this will result in adding further requirement so in that way as I mentioned yesterday the testing team or the tester should be independent so he can think out of the box he can think from his perspective so this is the example test we need doubts or anything is there on this we can ask okay let us come to having gone through all this test case standard test of the test test specification plan I have put the question simple question in that side many of you can have this answer that we have written out why we need test plan and what are the elements that we can identify so simple question write test strategy for the user set of requirement you know what is the test strategy by now and he should write test strategy for testing the below requirement below requirement is attached here and embedded unit instrument just put an example UI product the software requirement are as per so we should have a test strategy how it is I will further put the next question and together we can see the example is there is more of operation on the part so the next question is write the test cases there are different operational requirements that you for now we can write for that most of the operation we can see how good they are and we can write test cases we can write test format we should be writing and as I said you can use a test sheet to write test sheet planning this is of course an example of a test case scenario or procedure example we can enter the test step 1 2 3 step name just highlight what I am going to do in the description I am going to tell that that all the inputs as mentioned in the pre-condition so pre-condition means it will be pointing to a section which will fluctuate the conditions that are required for executing this particular test so after that we are going to power on the unit then we will set the status or error because it will be depending on the status to error because we want to test on the most of operation where it is going to go etc we will have just a time we can write in that country I will share with you the example basically there is a requirement write the test strategy as we need to write the test strategy how I am going to address the complete requirement unit first and the complete requirement first once you understood the FRS there is one section called most of the test you need to write test case and you can use the complete we will open the FRS you can go through this we will have the FRS will have a system overview I have to put the simplest requirement it is called embedded so the overview of this embedded it will have the below initialization maintenance and internalization then we have a monitoring it is also called as waiting test there is a failure there is a fail mode so this will have all the failures to be detected any actions that are required at the level of failure that are fail that are fail then we have a download management I told you earlier that embedded software needs to be downloaded on to the target so software should have a program I mean the software should have a function which will accept this downloadable program usually the embedded system target will have two sets of subsystems one is a loop loader other one is an application usually there will be changes in the application loop software plus loader this is called loop software this is responsible for downloading the new program the new program should be new program remains some systems will have programmable boot loader also suppose you want to upload or download new loader itself what we will do? we will have the loop software so that is the download mode of management this is responsible for loading the new loader basically download management is a set of functions which are part of loop loader and some functions are also in the application next one is disk form so disk form will not go into detail what is disk form so disk form will be used basically in the separate device and it will be filled in a embedded system it will be a reliable memory here only on the external world this can be accessed to fetch any of the data or if user wants to program new configuration of calibration basically in the separate device this is part of loop this is called embedded system this is called failure that is to be stored when the system is on this will be a memory which is identified as failure failure is given that will be solved then this is a typical embedded application this is called unit control this embedded unit has a control function which will drive which will drive and will get the PWA that because probably I will not go because I do not have scope of this you can google and get an information about this this requirement of this function is applicable how you can try this target while driving we have different parameters voltage control, current control then we have a specific motor control MTR PTR so we will also drive and control so it is a metastart it is a motor speed it is a motor current so I try to put the simplest of performance there are other complexity involved so let us look at this we will just highlight the basic requirements of the functionalities of a typical embedded there is an activation and a connection the data the actual interface or the inputs or the outputs how it is going to be communicated in the embedded package that is with the help of scan the same thing you have highlighted the embedded unit is a power of the motor control so we will be following motor drive control and monitoring and now for digital network failures and data transmission there are several things failures storage in the memory and many maintenance that is required software loading software management we done the help of scan communication there are of course few LEDs to the help of IOLINES that will be in the process and actually it is for the user for you you will need to use the system by using the STL so let us discuss about the measurement I think that is the measurement so there are different things that is involved in the software requirement we should identify operational requirements it will identify initialization it should identify download accordingly you can see the performance operational requirements these are the operational requirements that we have in the small depiction of the different most of operations so there is a unit mode there is an operational mode there will be maintenance mode download these are some of the over here operational requirements operational requirements with the operation we have to explain coming to the the modes of operations what are the modes that are very useful so these are the requirements you can go to when you can explain you can go to so what are the requirements for different modes which mode is there which mode is there when we have to download all this powering as part of the embedded target which we are going to there are specifications so there are timing requirements there are performance requirements there are communication requirements we can we have these requirements so you partitioning requirements will be there there is no separate powering different applications one single application is done some industries they call boot as well as application it is not developed it is simple application so in different states embedded will be implemented what are those states what are the number of states those of the state level state of the state requirement then we have functionality again we need how it is going to be initialization is there building the system there etc similarly we have a point management development management and there is a section in the end tolerance is constant as I said in this state we have tolerance so we call the requirement of so what we need to do is there is a most of operation what we saw just now you need to write this case that is here these are the most of operation there are 1, 2, 3, 4, 5 in each application maintenance so the embedded instrument should be in one of this instrument one of this model upon power up it will be in the initialization then initialization is fine then it will go for operation when maintenance is required because for maintenance the new software the download is required similarly if there are any failures when doing operation or maintenance it will go for failure then it will be depicted you can see there is a small note for each of the arrow so that is nothing but a transition how it will go to the next from maintenance to operation so the mode should be operational it will become here the mode is something like a version where it is below some of the requirements I will not explain in detail about high requirements for most of the operation in the type and where it is that is the mode test case design ex procedure and standard I will pass over the test plan we will be explaining once we are clear about this