WEBVTT 00:00:07.353 --> 00:00:09.052 Welcome to our MES video 00:00:09.155 --> 00:00:11.917 About model-based development or MBD for short 00:00:13.203 --> 00:00:14.774 In this video we will discuss 00:00:14.837 --> 00:00:17.472 The 10 biggest problems developers and companies face 00:00:17.544 --> 00:00:18.774 When it comes to MBD 00:00:18.900 --> 00:00:20.980 And offer solutions to these challenges 00:00:21.661 --> 00:00:24.716 MBD is state of the art for today's software development 00:00:24.867 --> 00:00:26.821 Especially in the automotive field 00:00:26.899 --> 00:00:31.859 Increasingly complex software in cars has called for front loading of Quality Assurance 00:00:31.962 --> 00:00:33.397 Throughout the development cycle 00:00:33.540 --> 00:00:36.473 And model-based development has shown that it can deliver. 00:00:36.906 --> 00:00:40.318 The increase in productivity in using auto code generation 00:00:40.469 --> 00:00:43.326 Can yield up to 50% less implementation time 00:00:44.155 --> 00:00:46.790 There is significant improvement of software quality 00:00:46.861 --> 00:00:49.182 With up to 40% less software errors 00:00:49.297 --> 00:00:52.566 And overall a reduction of development time and costs 00:00:52.773 --> 00:00:57.456 Up to 30% time and cost savings as compared to code-based development 00:00:58.037 --> 00:01:01.290 However, model-based development also comes at a price 00:01:02.132 --> 00:01:03.917 Nobody said it would be easy 00:01:04.346 --> 00:01:06.647 There are still some challenges you might face 00:01:06.679 --> 00:01:08.647 When implementing model-based development 00:01:09.257 --> 00:01:13.407 Today we will discuss 10 exemplary challenges in model-based development 00:01:13.582 --> 00:01:15.085 And the approaches to solve them 00:01:15.756 --> 00:01:20.192 We will have a look at mismanaged projects due to improper resource allocation 00:01:20.478 --> 00:01:23.922 On-time deliveries that are hindered by overly complex models 00:01:24.031 --> 00:01:26.904 Inefficiencies that come from inconsistent models 00:01:27.285 --> 00:01:28.928 Error-prone modeling styles 00:01:29.427 --> 00:01:32.475 Disorganized testing and reporting of test results 00:01:32.642 --> 00:01:35.411 Poorly formatted and ambiguous requirements 00:01:35.586 --> 00:01:38.839 Development teams that are not reporting their current status 00:01:39.046 --> 00:01:42.657 The problem of accurate and timely status to upper management 00:01:42.784 --> 00:01:44.831 Poorly trained engineers for Simulink 00:01:45.409 --> 00:01:49.172 And non-compliant processes to ISO 26262 00:01:52.633 --> 00:01:54.181 Let's start with the first point 00:01:54.364 --> 00:01:58.173 Mismanaged projects due to improper resource allocations 00:01:58.395 --> 00:02:01.093 Have you ever felt drowned in a complex project 00:02:01.363 --> 00:02:02.998 And maybe even missed a deadline 00:02:03.188 --> 00:02:05.751 If you answered yes was it at least partly 00:02:05.798 --> 00:02:09.203 Due to under estimating the size of the effort that was still needed 00:02:09.632 --> 00:02:12.505 Well MES has a tool that can assist with these challenges 00:02:12.806 --> 00:02:16.417 MES M X-RAY can provide objective metrics 00:02:16.583 --> 00:02:20.544 These metrics can actually evaluate the size or the volume of your model 00:02:20.900 --> 00:02:22.662 We call it global complexity 00:02:23.329 --> 00:02:27.495 Global complexity can be shown in a table with regards to the root model itself 00:02:27.725 --> 00:02:31.598 As well as subsystems and the content ordered by complexity 00:02:31.702 --> 00:02:34.662 These numbers here the global complexity 00:02:34.797 --> 00:02:38.360 Can indicate the relative amount of effort for a specific task 00:02:38.757 --> 00:02:42.194 You can use this number and absolute data from experience 00:02:42.274 --> 00:02:45.400 That you have from previous projects in order to calibrate 00:02:45.678 --> 00:02:47.217 Let's have a look at an example 00:02:47.344 --> 00:02:50.336 Maybe from an existing project with these numbers here 00:02:50.534 --> 00:02:52.955 You know that a model that has a global complexity 00:02:53.019 --> 00:02:56.414 Of roughly 25,000 halstead model volume 00:02:56.629 --> 00:02:59.899 May take the testing team five days to test for ASIL A 00:03:00.002 --> 00:03:02.311 Or twelve days to test for ASIL D 00:03:02.454 --> 00:03:05.826 Additionally your review team may need another day 00:03:05.851 --> 00:03:07.914 And your calibration team will need another week 00:03:07.977 --> 00:03:11.992 So if you have another project that also yields 25,000 in volume 00:03:12.135 --> 00:03:14.667 You already have some numbers that you can compare 00:03:14.953 --> 00:03:19.189 This allows you to make informed decisions about the amount of feasible changes 00:03:19.214 --> 00:03:21.182 To make in order to still meet the deadline 00:03:21.618 --> 00:03:24.579 You will get an overview of how much still needs to be done 00:03:24.761 --> 00:03:27.713 Or if you have a fixed amount of required features 00:03:27.745 --> 00:03:29.618 That have to be solved within the deadline 00:03:30.070 --> 00:03:31.975 You can calculate what you still need to do 00:03:35.007 --> 00:03:36.030 Problem number two 00:03:36.620 --> 00:03:40.221 Untimed deliveries that are hindered by overly complex models 00:03:40.681 --> 00:03:45.022 Models even with the best initial design may become complex over time 00:03:45.276 --> 00:03:49.612 They may even become overly complex due to added bug fixes and new features 00:03:50.001 --> 00:03:53.540 Statistically speaking, the more complex a part of the model is, 00:03:53.834 --> 00:03:57.143 The higher the chance that a bug may be present in that part of the model 00:03:57.302 --> 00:04:02.381 Therefore, reducing the complexity makes finding and fixing a potential bug easier 00:04:02.595 --> 00:04:04.309 We already had a look at M X-RAY 00:04:04.404 --> 00:04:06.753 One of our tools that can also help with this problem 00:04:06.983 --> 00:04:11.467 In particular it can help you to identify the most complex part of the model 00:04:11.554 --> 00:04:14.268 And enable you to make informed decisions 00:04:14.879 --> 00:04:19.593 MES M X-RAY can provide a list of the most complex subsystems 00:04:19.657 --> 00:04:24.083 You can then use this list to prioritize the next steps or actions you want to take 00:04:24.432 --> 00:04:26.879 You can have a list of all your subsystems here 00:04:27.172 --> 00:04:30.410 See the local complexity so the most complex first 00:04:30.457 --> 00:04:33.444 And you can also see additional model metrics and properties 00:04:33.484 --> 00:04:35.237 That can help with your decision here 00:04:35.388 --> 00:04:38.988 For example the number of interface inputs and outputs 00:04:39.107 --> 00:04:40.424 Elementary signals 00:04:40.535 --> 00:04:41.789 Global complexity 00:04:41.868 --> 00:04:45.193 The cohesion or incoherence on that specific level 00:04:45.265 --> 00:04:47.892 The ratio of functional and structural blocks 00:04:48.059 --> 00:04:52.765 So you have a quick overview and can see what parts of the model need to be addressed 00:04:52.876 --> 00:04:56.106 To make the best use of your limited time and resources 00:04:56.193 --> 00:04:59.512 Even better the list is really quick and easy to create 00:05:02.133 --> 00:05:03.221 Problem number three 00:05:03.324 --> 00:05:06.435 Inefficiencies that result from inconsistent models 00:05:06.895 --> 00:05:08.918 There is probably some truth when you say that 00:05:08.990 --> 00:05:11.847 There are at least ten ways to do anything in Simulink 00:05:12.316 --> 00:05:14.355 There is a lot of freedom in using Simulink 00:05:14.689 --> 00:05:17.712 But the benefits of this freedom may also be dwarfed 00:05:17.855 --> 00:05:20.220 By considering the many different consumers 00:05:20.275 --> 00:05:22.696 That actually have to work with your model afterwards 00:05:22.823 --> 00:05:25.727 These consumers could be the development team itself 00:05:25.814 --> 00:05:30.166 Or review teams, a calibration team, a test team and so on 00:05:30.261 --> 00:05:34.479 Each new modelling style will require each of these consumers additional time 00:05:34.479 --> 00:05:36.721 To understand what's going on in the model 00:05:36.903 --> 00:05:38.625 And understanding the model itself 00:05:38.808 --> 00:05:42.808 Choosing and adhering to one modeling style that you decide on together 00:05:43.109 --> 00:05:46.022 Will increase efficiency for everybody involved 00:05:46.363 --> 00:05:51.458 The MES Model Examiner or MXAM ensures that you stick to one modeling style 00:05:52.164 --> 00:05:56.423 The MES Model Examiner allows you to enforce consistent modeling styles 00:05:56.486 --> 00:05:59.565 And identify and correct non-compliant model patterns 00:05:59.740 --> 00:06:01.343 The list of topics of guidelines 00:06:01.390 --> 00:06:03.937 They give you recommendations on the modeling styles 00:06:04.040 --> 00:06:08.325 And the modeling pattern are checked with the tool automatically as you can see here 00:06:08.389 --> 00:06:11.508 And any deviation will be listed as a failed finding 00:06:11.785 --> 00:06:15.150 You can see details about why a specific failure occurred 00:06:15.753 --> 00:06:17.824 Why the modeling style was not fulfilled 00:06:18.340 --> 00:06:22.014 And more details about how to enforce and how to solve this issue 00:06:22.332 --> 00:06:25.522 You can even use auto repair on many of these guidelines 00:06:25.562 --> 00:06:27.244 To automatically repair your model 00:06:27.689 --> 00:06:29.308 This brings us to the fourth problem 00:06:31.308 --> 00:06:33.061 Error-prone modeling styles 00:06:33.251 --> 00:06:34.387 As I already mentioned 00:06:34.412 --> 00:06:36.681 There are several ways to do something in Simulink 00:06:36.926 --> 00:06:38.576 It is very flexible and powerful 00:06:38.719 --> 00:06:41.895 But sometimes some of the options can be very subtle 00:06:42.117 --> 00:06:43.480 Very difficult to find 00:06:43.560 --> 00:06:47.456 And can cause misunderstandings for the reviewers of a model for example 00:06:47.845 --> 00:06:49.178 Let me give you an example 00:06:49.511 --> 00:06:53.598 A summation block can be configured to saturate on integer overflow 00:06:53.630 --> 00:06:54.971 In some instances 00:06:55.328 --> 00:06:56.876 But not in other instances 00:06:57.005 --> 00:07:01.576 Such implicit configurations can easily lead to wrong assumptions about the model 00:07:01.671 --> 00:07:04.084 And also risk possible errors in the model 00:07:04.456 --> 00:07:06.734 MES Model Examiner can help here as well 00:07:06.964 --> 00:07:10.274 MXAM enforces defensive implementation techniques 00:07:10.417 --> 00:07:11.988 The use of language subsets 00:07:12.234 --> 00:07:15.940 And also the consistent and explicit data and control flow 00:07:16.170 --> 00:07:19.027 A large library of guidelines and checks on these topics 00:07:19.066 --> 00:07:20.765 Are included with the tool as well 00:07:20.800 --> 00:07:23.133 A starter set will let you get right down 00:07:23.158 --> 00:07:25.649 To using the model examiner on your models right away 00:07:28.286 --> 00:07:29.365 Problem number 5 00:07:29.643 --> 00:07:32.873 Disorganized testing and reporting of test results 00:07:33.166 --> 00:07:35.873 How well-organized is your testing process 00:07:35.960 --> 00:07:38.196 Are you able to repeat all the same tests 00:07:38.221 --> 00:07:40.364 That have gone through a formal review process 00:07:40.425 --> 00:07:42.980 Many companies have random testing practices 00:07:43.004 --> 00:07:44.448 That are not very well documented 00:07:44.631 --> 00:07:46.924 If you want to increase your testing efficiency 00:07:47.043 --> 00:07:49.900 And even the ISO 26262 compliance 00:07:49.925 --> 00:07:52.115 The MES Test Manager can help you 00:07:52.480 --> 00:07:55.400 The MES Test Manager or MTest for short 00:07:55.781 --> 00:07:58.710 Is a framework to support requirements based testing 00:07:58.995 --> 00:08:03.464 The automated interface analysis allows automatic testbed generation 00:08:03.580 --> 00:08:06.432 And supports MiL, SiL and Pil simulation 00:08:06.519 --> 00:08:10.344 Any change in the interface can also be automatically adapted 00:08:10.542 --> 00:08:15.057 The MES Test Manager allows requirements traceability to test cases 00:08:15.168 --> 00:08:16.588 And to the evaluation 00:08:16.652 --> 00:08:21.739 It comes with a flexible empty CD language to model test cases and test scenarios 00:08:22.215 --> 00:08:26.072 There is automated regression and back to back testing with reference data 00:08:26.175 --> 00:08:27.230 And last but not least 00:08:27.294 --> 00:08:31.309 Comprehensive reporting and documentation of the tests 00:08:31.571 --> 00:08:36.150 You will have a list of all the data, input and output signals, test vectors 00:08:36.213 --> 00:08:38.816 As well as coverage data on your structural coverage 00:08:39.395 --> 00:08:42.903 On assessments and requirements, as well as test cases 00:08:45.744 --> 00:08:46.919 Problem number six 00:08:47.133 --> 00:08:49.736 Poorly formatted and ambiguous requirements 00:08:49.823 --> 00:08:51.370 Now this is a tricky part 00:08:51.601 --> 00:08:52.878 Many companies will admit 00:08:52.910 --> 00:08:55.910 That their requirements could be much better in terms of clarity 00:08:56.140 --> 00:08:57.823 And how well formatted they are 00:08:58.735 --> 00:09:02.060 In order to solve this problem MES presents MARS 00:09:02.417 --> 00:09:07.600 A semi-formal syntax to ensure well formatted and unambiguous requirements 00:09:08.163 --> 00:09:11.161 MARS also is a source to generate assessments 00:09:11.186 --> 00:09:13.575 For the automated validation of requirements 00:09:13.639 --> 00:09:18.115 And MARS can help you to generate logic test cases to test the requirements 00:09:18.655 --> 00:09:20.272 Let's have a look at MARS 00:09:20.447 --> 00:09:23.464 The MTest Accessable Requirements Syntax 00:09:24.051 --> 00:09:26.789 If we have a look at a typical prose requirement 00:09:27.185 --> 00:09:32.130 Glide-slope control is armed when Glide-slope is commanded and enabled 00:09:32.728 --> 00:09:37.116 Notice the first things armed commanded enabled 00:09:37.350 --> 00:09:42.762 Apparently they are states of signals that are not more defined or identified 00:09:42.904 --> 00:09:45.919 So first of all your requirement is lacking the information 00:09:45.951 --> 00:09:48.911 Which signal is meant the actual name of the signal 00:09:48.990 --> 00:09:53.299 In the interface of the model to let the tester know what input to stimulate 00:09:53.609 --> 00:09:57.910 And what are the definitions of armed commanded and enabled 00:09:58.164 --> 00:10:00.608 While Mars provides a syntax format 00:10:00.798 --> 00:10:02.981 Just like a questionnaire that you can fill out 00:10:03.417 --> 00:10:06.543 When does something apply what shall be assessed 00:10:06.774 --> 00:10:08.853 And how shall the system react 00:10:09.234 --> 00:10:12.623 You can see for the typical requirement here 00:10:12.837 --> 00:10:14.987 We can rewrite it in MARS Syntax 00:10:15.075 --> 00:10:18.606 Saying while the signal GS command is equal to true 00:10:19.003 --> 00:10:21.876 And the signal GS signal is equal to true 00:10:22.519 --> 00:10:27.177 The signal armed shall always be true for example within one time step 00:10:27.851 --> 00:10:32.485 You see you can also identify the parts that come from the original pros requirement 00:10:32.739 --> 00:10:36.302 Some parts that have to do with the actual implementation in the model 00:10:36.381 --> 00:10:40.588 And some additional clarification that is important especially for the test team 00:10:40.643 --> 00:10:44.222 On how strictly you need to follow this specific requirement 00:10:44.754 --> 00:10:47.944 In editor syntax the requirement could look like this 00:10:48.484 --> 00:10:52.785 Now the MARS requirement can be the base for generating a logical test case 00:10:53.206 --> 00:10:55.954 To simulate a specific situation in the model 00:10:55.985 --> 00:10:59.588 In order to test whether the requirement is actually fulfilled or not 00:10:59.842 --> 00:11:02.802 This test case is generated from a truth table 00:11:02.827 --> 00:11:06.573 That analyzes the possible combinations of model stimuli 00:11:06.652 --> 00:11:08.557 In order to trigger a requirement 00:11:08.866 --> 00:11:11.627 MARS is also the basis for creating assessments 00:11:11.652 --> 00:11:15.239 That follow the original requirement and generates a comparison vector 00:11:15.271 --> 00:11:17.929 To understand whether the requirement is fulfilled 00:11:18.024 --> 00:11:20.612 At any given time during the simulation 00:11:20.802 --> 00:11:22.435 In the overview in the report 00:11:22.460 --> 00:11:25.667 You will have a very quick understanding of a specific assessment 00:11:25.873 --> 00:11:29.380 Whether in a test case the requirement is fulfilled or not fulfilled 00:11:29.507 --> 00:11:32.205 You have traceability in test cases here 00:11:32.308 --> 00:11:35.316 As well as error messages in case there is a fail 00:11:37.093 --> 00:11:38.339 Problem number seven 00:11:38.553 --> 00:11:41.862 Development teams that are not reporting their current status 00:11:42.116 --> 00:11:45.290 If you're a project manager maybe you've already had the experience 00:11:45.346 --> 00:11:49.592 That sometimes getting a status update from your team is similar to pulling teeth 00:11:49.671 --> 00:11:52.710 So why not relieve your team from this task in particular 00:11:53.163 --> 00:11:55.163 Why not just have it done automatically 00:11:55.409 --> 00:11:59.059 The MES Quality Commander or MQC can do that for you 00:11:59.853 --> 00:12:01.995 The MES Quality Commander can be used 00:12:02.020 --> 00:12:05.734 To show quality data from report data gathered automatically 00:12:06.019 --> 00:12:10.114 You can set up the tool environment for automatic reporting of the status 00:12:10.193 --> 00:12:13.257 For example in continuous integration with Jenkins 00:12:13.431 --> 00:12:17.494 You can automate the Quality Assurance and report generation in such a setup 00:12:17.621 --> 00:12:22.152 Gather and display the report information at a glance in the MES Quality Commander 00:12:22.724 --> 00:12:24.851 A typical page could look like this 00:12:24.962 --> 00:12:26.866 You have your project overview here 00:12:26.906 --> 00:12:29.985 And your artifacts the different models in your project 00:12:30.985 --> 00:12:34.942 You can also see the development of your project over time in terms of quality 00:12:35.363 --> 00:12:37.561 Good acceptable and bad 00:12:38.148 --> 00:12:42.314 As for a specific Quality Assurance measure here for example testing 00:12:42.584 --> 00:12:45.465 You can see the detailed tool specific data as well 00:12:45.981 --> 00:12:49.409 These two pages are available with the MES Quality Commander 00:12:49.434 --> 00:12:53.631 For all typical Quality Assurance tools of the software development cycle 00:12:57.210 --> 00:12:59.412 Problem number eight is a related one 00:12:59.591 --> 00:13:03.932 The need of accurate and timely status updates to upper management 00:13:04.051 --> 00:13:07.422 Have you ever had to provide a spontaneous status update 00:13:07.471 --> 00:13:09.756 To someone who has higher up in the company than you 00:13:09.797 --> 00:13:13.662 Someone who is less interested in the minute details of your project 00:13:13.693 --> 00:13:16.876 But more in a quick summary overview and outlook 00:13:16.939 --> 00:13:20.002 Well the MES Quality Commander can help you here as well 00:13:20.027 --> 00:13:24.110 The quality assessment with MQC is based on a quality model 00:13:24.348 --> 00:13:25.792 This quality model defines 00:13:25.817 --> 00:13:30.420 How to combine all the low-level details from reports and QA measures 00:13:30.459 --> 00:13:32.769 And how much impact each one should have 00:13:33.046 --> 00:13:35.935 The data finally accumulates in a single number 00:13:36.157 --> 00:13:39.022 This is the overall quality status of your project 00:13:39.371 --> 00:13:41.276 The overview could look like this 00:13:41.633 --> 00:13:43.474 You have your detailed data here 00:13:43.895 --> 00:13:47.744 You have the accumulated data for your artifacts or quality properties 00:13:47.807 --> 00:13:49.076 Or for your whole project 00:13:49.180 --> 00:13:51.242 You can even see the trend over time 00:13:51.267 --> 00:13:54.067 Either by Quality Assurance method or by artifact 00:13:54.092 --> 00:13:56.449 And the total evaluation over time as well 00:13:56.537 --> 00:14:00.846 And even better a PowerPoint report can be created really quickly as well 00:14:02.655 --> 00:14:03.671 Number nine 00:14:03.973 --> 00:14:06.187 Poorly trained engineers for Simulink 00:14:06.393 --> 00:14:07.789 Is your company growing 00:14:07.869 --> 00:14:10.233 Has there been a large number of current hires 00:14:10.258 --> 00:14:12.353 Well many companies are growing fast 00:14:12.876 --> 00:14:16.376 But whether recent college graduate or mid-level engineer 00:14:16.756 --> 00:14:21.597 It takes some time to come up to speed with the company's policies and defined processes 00:14:22.303 --> 00:14:26.898 And unfortunately not all colleagues have a strong MBD curriculum 00:14:27.088 --> 00:14:30.509 Or are very awesome Simulink modelers when they graduate 00:14:30.890 --> 00:14:34.549 The MES Academy has a number of training classes to support you here 00:14:35.057 --> 00:14:39.787 We have recently released our new MES training classes for 2020 00:14:39.953 --> 00:14:41.807 The highlights of course are 00:14:41.886 --> 00:14:46.417 The introduction to model-based development and quality assurance of embedded software 00:14:46.528 --> 00:14:50.735 The model-based development in compliance with ISO 26262 00:14:50.814 --> 00:14:52.830 Challenges and effective solutions 00:14:52.870 --> 00:14:54.353 Which is our most popular training 00:14:54.472 --> 00:14:56.275 And our MES summer school 00:14:56.300 --> 00:14:59.908 A five-day training class on introduction to model-based development 00:15:00.337 --> 00:15:02.662 So save the date that's coming up in June 00:15:03.003 --> 00:15:06.194 You can find our whole curriculum under the web address here 00:15:08.725 --> 00:15:09.765 Problem number 10 00:15:09.860 --> 00:15:13.390 Non-compliant processes to ISO 26262 00:15:13.640 --> 00:15:18.358 Are you getting a lot of pressure to increase your compliance to ISO 26262 00:15:18.644 --> 00:15:21.144 Well the industry is moving quickly into that direction 00:15:21.945 --> 00:15:26.350 MES experts offer consulting and supporting services in this area 00:15:27.128 --> 00:15:31.945 MES provides the ISO 26262 process deployment service 00:15:32.223 --> 00:15:33.499 This provides guidance 00:15:33.524 --> 00:15:38.635 For your ISO 26262 and ASPICE-compliant software development process 00:15:38.865 --> 00:15:41.428 It includes deriving safety requirements 00:15:41.523 --> 00:15:45.523 And best practices for model-based development in the automotive domain 00:15:45.698 --> 00:15:50.380 The process deployment service consists of five levels of services and expertise 00:15:50.420 --> 00:15:53.513 Provided by our highly specialized experts 00:15:53.600 --> 00:15:58.092 These five levels are analyzing existing processes methods and tools 00:15:58.211 --> 00:15:59.925 Developing a process manual 00:15:59.996 --> 00:16:01.806 Creating developer manuals 00:16:02.170 --> 00:16:05.972 Implementing ISO 26262 compliant development 00:16:06.027 --> 00:16:07.511 And development support 00:16:08.780 --> 00:16:12.280 In conclusion switching to MBD creates new challenges 00:16:12.328 --> 00:16:15.438 But it also offers efficient ways to solve these challenges 00:16:15.565 --> 00:16:16.961 We had a look at how to deal 00:16:17.160 --> 00:16:20.469 With mismanaged projects due to improper resource allocation 00:16:20.612 --> 00:16:24.945 And problems in on-time deliveries that are caused by overly complex models 00:16:25.024 --> 00:16:28.619 The MES M-XRAY can be a tool for you to solve problems here 00:16:28.793 --> 00:16:30.745 We talked about inefficiencies 00:16:30.824 --> 00:16:34.761 Resulting from inconsistent models and error-prone modeling styles 00:16:34.864 --> 00:16:38.308 Where the MES Model Examiner is the helpful tool to use 00:16:38.387 --> 00:16:42.736 Problems that occur from disorganized testing and reporting of test results 00:16:42.799 --> 00:16:45.934 As well as poorly formatted and ambiguous requirements 00:16:46.029 --> 00:16:48.616 Can be addressed by the MES test manager 00:16:48.711 --> 00:16:52.568 The problem of not reporting the current status of development teams 00:16:52.814 --> 00:16:56.766 Or providing accurate and timely status updates to upper management 00:16:56.964 --> 00:16:59.948 Can all be solved by the MES Quality Commander 00:17:00.829 --> 00:17:02.099 And last but not least 00:17:02.607 --> 00:17:04.138 Training for engineers 00:17:04.233 --> 00:17:08.591 And assuring the compliance with processes like ISO 26262 00:17:08.694 --> 00:17:11.344 Can be provided by the MES Academy 00:17:11.543 --> 00:17:13.185 If you found this video helpful 00:17:13.210 --> 00:17:15.455 Please subscribe to our YouTube channel here 00:17:15.923 --> 00:17:17.677 ModelEngineersDE 00:17:17.852 --> 00:17:19.129 Or visit our website 00:17:19.272 --> 00:17:23.120 www.model-enginers.com 00:17:24.136 --> 00:17:25.801 We hope you found this video useful 00:17:26.293 --> 00:17:28.515 Thank you so much for joining us today 00:17:28.540 --> 00:17:33.549 [Music]