Hello Srini, we are glad that you enjoy the video! Sure, we will publish soon new tutorials about software engineering, the next one will be SWE.1. Happy to read again from you! :)
With our schedule, we will release SWE.5 in 2022. That's because we want to release three more Functional Safety videos and two more Cybersecurity videos. Actually, we have two more Automotive SPICE topics on the list this year, unfortunately not SWE.5.
Hi, many thanks for the video. Is it mandatory to test the SW Req only by blackbox tests (External I/O) ? This topic wasn't describe in the video. Thank you in advance. Reda.
Hi Reda, yes. Typically, SW and System qualification tests are black-box tests, because the expectation is that the requirements describe the system / SW as a black box. The only real white box test is the unit test. Depending on the definition integration tests are categorized as grey box tests. If you have further questions please let us know! :) Kind regards, Bhaskar.
Hi there! Really good video. One short question. If we test our software module in standalone framework, keeping all other modules stubbed, is it a test method as per SWE 6?
Hi there, we are not 100% sure what you refer to as “SW module”. The expectation of the SW qualification test is to test the complete software as a black box against the software requirements. Typically, this kind of test does not require the stubbing of other modules, unless your complete software is one of many modules. We hope this helps you further!
@youturn The SW test strategy is described as early as possible. Typically you describe a test strategy across all test levels and ensure that you cover the full functionality, account for regression testing and also address the issue how to approach testing under time constraints. The strategy should also cover entry and exit criteria, test interruption criteria, responsibilities, test environment, test coverage goals, etc. We hope that answers your question! :)
Hi there! Really good training videos on the topic. Although I didn't find SWE.5 which covers the integratition topic. Do u plan to create one or mayb I just missed?
@Istvan Petrovics thanks for your feedback! :) The SWE.5 video is already in production and will be published within the next few months. Stay tuned! :)
Great Video! Which process would you assign the "Application" of an automobile's power train into? For example: if a department is applicating/changing the software parameters in a transmission ECU or motor ECU on order to improve the "driving experience". This process takes place after the software development, but can somehow be seen as a practical tweaking of variables to satisfy the customer's driving experience (hence done in the real car). Would you assign it to SWE.X or rather SYS.X? And which X would that be in your opinion? Kind regards
Thank you for your comment, If you want to assign the management of application parameters (APs) to a process I would recommend to use SWE.5 or SYS.5. However, in transmission systems and powertrain you are often talking about thousands of APs. In that case my recommendation would be to treat the application as a distinct sub-project. Typically, you have a separate sub-project-leader and you have to manage the application parameters as well as the data in a very systematic way. Otherwise, you will not be able to handle the multitude of APs and their combinations. All MAN- and SUP-processes apply and you can at least in parts apply the engineering processes. Cheers!
Hey Paolo, We are publishing videos every month. SWE. 4 is definitely on the line, but we can't tell you when exactly the process will be published. Just stay subscribed and click the bell Icon so you get notified when we uploaded the video. Cheers!
Explained well. I have a doubt. E is reffered to "dEtermination" as the expansion of ASPICE. Why 'd' is in lower case latter and E is in upper case letter?
Hello Mr Rajan, To be honest, no one knows. Automotive SPICE referred for a few years to the generic ISO/IEC 15504 standard, better known as SPICE. The acronym you doubt was invented in 1998. Ten years later, the creators of ASPICE, which refers to the automotive industry, also didn't bother with the naming. Since 2015, ASPICE has been replaced by: ISO/IEC 3300n. Cheers, your UA-cam team at Kugler Maag Cie
Do you have a plan to create a video regarding the Software Integration and Integration test, it will be very helpful since the approach of Integration Testing is more complicated?
The role concept is on your side, or more precisely on what you have defined in the strategy. Automotive SPICE expects you to test appropriately, not who is responsible.
Great video! Thank you very much Sir!
We're glad that you like it! :)
It's awesome video..and i m listening all series.. thanks for it...it makes me clear👍
@Sasi Balram thank you so much for your feedback. We're really happy to hear that you like our tutorials! :)
Nice and Straight forward video for a beginner.
Kindly post videos for other Software engineering process areas.
Hello Srini, we are glad that you enjoy the video! Sure, we will publish soon new tutorials about software engineering, the next one will be SWE.1. Happy to read again from you! :)
Thank you. Waiting for SWE.5.
With our schedule, we will release SWE.5 in 2022. That's because we want to release three more Functional Safety videos and two more Cybersecurity videos. Actually, we have two more Automotive SPICE topics on the list this year, unfortunately not SWE.5.
@@ULSolutionsSIS that's good to hear. Thank you.
we keep your wish in mind ;)
Great video, however I would be happy if you can also provide a small example of how exactly SW Qualification test is done in Practice. Thank you.
Hi, many thanks for the video. Is it mandatory to test the SW Req only by blackbox tests (External I/O) ? This topic wasn't describe in the video.
Thank you in advance. Reda.
Hi Reda, yes. Typically, SW and System qualification tests are black-box tests, because the expectation is that the requirements describe the system / SW as a black box. The only real white box test is the unit test. Depending on the definition integration tests are categorized as grey box tests.
If you have further questions please let us know! :)
Kind regards, Bhaskar.
Hi there! Really good video. One short question. If we test our software module in standalone framework, keeping all other modules stubbed, is it a test method as per SWE 6?
Hi there, we are not 100% sure what you refer to as “SW module”. The expectation of the SW qualification test is to test the complete software as a black box against the software requirements. Typically, this kind of test does not require the stubbing of other modules, unless your complete software is one of many modules. We hope this helps you further!
Good video. thank you, I could not find the white paper for software qualification test in the link mentioned. Can you look into that?
Thanks for informing us! We have corrected the link, now it shall work.
when i need to write the SW Test strategy? Immediately after SW requirements analysis or after coding and Unit verification?
@youturn The SW test strategy is described as early as possible. Typically you describe a test strategy across all test levels and ensure that you cover the full functionality, account for regression testing and also address the issue how to approach testing under time constraints. The strategy should also cover entry and exit criteria, test interruption criteria, responsibilities, test environment, test coverage goals, etc. We hope that answers your question! :)
Hi there! Really good training videos on the topic. Although I didn't find SWE.5 which covers the integratition topic. Do u plan to create one or mayb I just missed?
@Istvan Petrovics thanks for your feedback! :) The SWE.5 video is already in production and will be published within the next few months. Stay tuned! :)
Great Video! Which process would you assign the "Application" of an automobile's power train into?
For example: if a department is applicating/changing the software parameters in a transmission ECU or motor ECU on order to improve the "driving experience". This process takes place after the software development, but can somehow be seen as a practical tweaking of variables to satisfy the customer's driving experience (hence done in the real car).
Would you assign it to SWE.X or rather SYS.X? And which X would that be in your opinion?
Kind regards
Thank you for your comment,
If you want to assign the management of application parameters (APs) to a process I would recommend to use SWE.5 or SYS.5.
However, in transmission systems and powertrain you are often talking about thousands of APs. In that case my recommendation would be to treat the application as a distinct sub-project.
Typically, you have a separate sub-project-leader and you have to manage the application parameters as well as the data in a very systematic way. Otherwise, you will not be able to handle the multitude of APs and their combinations.
All MAN- and SUP-processes apply and you can at least in parts apply the engineering processes.
Cheers!
Are you guys planning to do it for SWE.4 and SWE.5 ? Thank you
This video was very useful and clear
Hey Paolo,
We are publishing videos every month. SWE. 4 is definitely on the line, but we can't tell you when exactly the process will be published.
Just stay subscribed and click the bell Icon so you get notified when we uploaded the video.
Cheers!
Explained well. I have a doubt.
E is reffered to "dEtermination" as the expansion of ASPICE. Why 'd' is in lower case latter and E is in upper case letter?
Hello Mr Rajan,
To be honest, no one knows. Automotive SPICE referred for a few years to the generic ISO/IEC 15504 standard, better known as SPICE. The acronym you doubt was invented in 1998. Ten years later, the creators of ASPICE, which refers to the automotive industry, also didn't bother with the naming. Since 2015, ASPICE has been replaced by: ISO/IEC 3300n.
Cheers, your UA-cam team at Kugler Maag Cie
Do you have a plan to create a video regarding the Software Integration and Integration test, it will be very helpful since the approach of Integration Testing is more complicated?
Yes, soon we will publish a tutorial about SWE.5, just keep following us :)
@@ULSolutionsSIS Thank you!
Who is responsible for this testing? Developer or tester??
The role concept is on your side, or more precisely on what you have defined in the strategy. Automotive SPICE expects you to test appropriately, not who is responsible.
@@ULSolutionsSIS thank you for your response😃. That's helpful
;)