A very nice explanation. I am from aerospace background in Systems Engineering, but I found it easy to relate with A-SPICE processes after watching this video. Many Thanks.
Hello Mr Sathiyakumar, thanks a lot for feedback. We are very pleased that you appreciate our video project. Regards, Your video team at Kugler Maag Cie
We'll publish videos on all 16 core processes within the VDA scope. Now, it's the turn for another video on Functional Safety. After that, we're going to release Software Detailed Design, SWE.3. Cheers, your video team at Kugler Maag Cie
Sir , Very good explanation on system requirements, i want to download the white paper but i didnot find the link. can you please share the link ,that's help me .Thanks a lot.
Hi there, glad you liked our video! Please try this link - there you should also be able to download the white paper about System Requirements Analysis: www.kuglermaag.com/automotive-spice/sys2-system-requirements-analysis/. We hope this helps! :)
The white paper link when downloaded has the content in German. Where can I get the English one? And does it cover the whole system testing process verification required for Aspice
Hello, here is the link to the page where you can download the English version of the white paper: www.kuglermaag.com/consulting-competence/improvement-programmes/automotive-spice/sys2-system-requirements-analysis/ The white papers covers the content of the video (System Requirements Analysis). Other tutorials on system engineering, including the system testing processes, will be published soon. Subscribe to our channel to get the notification when new videos are loaded! Enjoy!
Thank you for your video but I have a question regarding this subject. In software project management, who should be in charge of writing this documentation? Is it the project manager, lead developer, or system analyst?
Hello ninja nincode, Automotive SPICE does not prescribe a role that must perform this task. Depending on the context, the project manager, lead developer, or analyst can take this on. What kind of project are you talking about? If it is a pure SW project, SYS.2 does not apply. Regards, Your video team at Kugler Maag Cie
Requirements are the crucial point of development, because with requirements you also anticipate important system architecture decisions. If you do not thoroughly address these specifications, you will pay for the technical debt later, e.g. if you intend to reuse some parts. This phase also has a significant impact on system safety - serious damage is caused by system failure.
Thanks for this video. I have several questions: 1. What in case I use external SW component and I got SW interface specification for that? Should I threat it as stakeholder requirements and link those SW interface requirements to system level requirements or rather threat it as SW architecture document? 2. What in case a part of stakeholder requirements are more or less project organizational requirements (e.g. Project should have Release Manager role). Should such stakeholder requirement be covered by (and linked with) system level requirement(s)?
Hello Mr Siejek, what do you mean with your first question? I assume that "external" means you have a supplier. Considering it is a component delivered by a customer: The decision to use a supplier is something you would likely cover in the SW archicture. Only if the cusomter or an internal department says "you have to use this supplier" this would be a system requirement (constraint) which traces down to SW requirements and architecture. With your organizational requirements that is up to you. You can reflect it in the System requirements, but beware. You will not have a system qualification test for that. It may be easier to show coverage of these stakeholder requirements in a different way (e.g. reference of the relvant chapter in the project plan). Regards, Your video team at Kugler Maag Cie
@@ULSolutionsSIS Thank you for your answer. Yes, external means we have supplier, who is delivering us SW component and also requirements, how this SW component should be used (interface definition, SW component configuration etc). The SW component might be suggested to be used by the customer but it could be also our organization decision. I understand that such kind of requirements which I get from supplier also can be counted as stakeholder requirements visible in Sys.1 process, right? If it is a case and I understand your answer correct, I should link the requirements from Sys.1 to SWE.1 - 3 directly and not track them anyhow in Sys.2 and Sys3. Such tracking of requirements should not be found as violation by assessor. Is my assumption correct?
Hello Mr Siejek, yes, you can link these requirements (a supplier is also a stakeholder, but you would also provide requirements for the supplier) directly to the relevant process SWE.1 to SWE.3 but... ... you have to ensure that these requirements which you linked to e.g. SWE.3 are covered by the higher processes (SWE.1 and SWE.2, even SYS-processes) and are neither in contradiction nor are covereing sys-requirements which have not been documented (yet). Cheers Your video team at Kugler Maag Cie
Hello Parameswari Priya, SYS.3 is scheduled for 2022. This year we will release more videos on ME SPICE, Software level functional safety and Cybersecurity. For an initial orientation, you can watch SWE.3. It is at the software domain level, but in combination with SWE.4 you will get a first impression of the relationship between specification and verification, the need for strategies and bidirectional traceability (horizontally between SYS.3 and SYS.4 and vertically between SYS.3 and SYS.2 and SWE.1). Sincerely yours, Your Video Team at Kugler Maag Cie
Hey there, you can find the training link here: www.kuglermaag.com/training/automotive-spice/competent-assessor.html The prerequisites are: -passed the intacs™ certified Provisional Assessor class (with exam) -gained proven experience as a Provisional Assessor -carrying out at least 5 assessments lasting 250 assessment hours within five years -a positive recommendation from a Competent or Principal Assessor -evidence of a VDA guideline training Cheers!
Do you have courses where you explain Requirements Engineering based on/with Safety Goals, Safety Requirements, Technical Safety Concept, ASIL (from ISO26262) and so on??
Hello Teqnum, by mid-March we will publish a Functional Safety video on the Concept Phase, Part 3 of ISO 26262. There we mention the relation between the FS goals and requirements. We don't offer a special RE training. You'll find our training program here: www.kuglermaag.com/training-topics-and-timing/ Cheers Your video team at Kugler Maag Cie
It was an awesome experience to have ASPICE assessment with you @Bosch Abstatt Germany!
@Joginder Singh thank you for sharing this! It was our pleasure :)
An outstanding training to get familiar with requirement analysis application in Automotive
Thank you very much - we're very glad to hear this! :)
Good overview of ASPICE Sys Reqt Analysis
Thank you that you appreciate the video.
Your video team at Kugler Maag Cie
Such a nice explanation . Thanks for sharing
We're glad that it's helpful! :)
A very nice explanation. I am from aerospace background in Systems Engineering, but I found it easy to relate with A-SPICE processes after watching this video. Many Thanks.
Glad it was helpful!
Good explanation of SYS.2. Thanks KMC to share knowledge across ASPICE community.
Glad it was helpful, Surabh!
Very Good explanation. It really helps
Hello Mr Sathiyakumar,
thanks a lot for feedback. We are very pleased that you appreciate our video project.
Regards, Your video team at Kugler Maag Cie
Really good explained and very sympathic person!!
We're very glad to hear that!
Great explanation, thank you!
Glad you enjoyed it! Thanks Fabio :)
Thanks for sharing this video. It will be great if u can share similar video on system architecture
We'll publish videos on all 16 core processes within the VDA scope. Now, it's the turn for another video on Functional Safety. After that, we're going to release Software Detailed Design, SWE.3.
Cheers, your video team at Kugler Maag Cie
A very knowledge video on SPICE, thank for your deep elaborates.
Thank you. Our presenter is a real SPICE crack.
谢谢老铁分享，sys.2
系统需求！
We're happy that you like the video - thank you for sharing! :)
Hi Sir, Couldn't download the whitepaper from website. Please guide
Sorry for the inconvenience - please try this link: www.kuglermaag.com/automotive-spice/sys2-system-requirements-analysis/.
Sir , Very good explanation on system requirements, i want to download the white paper but i didnot find the link. can you please share the link ,that's help me .Thanks a lot.
Hi there, glad you liked our video! Please try this link - there you should also be able to download the white paper about System Requirements Analysis: www.kuglermaag.com/automotive-spice/sys2-system-requirements-analysis/. We hope this helps! :)
The white paper link when downloaded has the content in German. Where can I get the English one? And does it cover the whole system testing process verification required for Aspice
Hello, here is the link to the page where you can download the English version of the white paper: www.kuglermaag.com/consulting-competence/improvement-programmes/automotive-spice/sys2-system-requirements-analysis/
The white papers covers the content of the video (System Requirements Analysis). Other tutorials on system engineering, including the system testing processes, will be published soon. Subscribe to our channel to get the notification when new videos are loaded!
Enjoy!
@@ULSolutionsSIS Thank you so much :) And eagerly waiting for the system process videos :)
Thank you for your video but I have a question regarding this subject.
In software project management, who should be in charge of writing this documentation? Is it the project manager, lead developer, or system analyst?
Hello ninja nincode,
Automotive SPICE does not prescribe a role that must perform this task. Depending on the context, the project manager, lead developer, or analyst can take this on. What kind of project are you talking about? If it is a pure SW project, SYS.2 does not apply.
Regards, Your video team at Kugler Maag Cie
Top Explanation, Than you
Glad you liked it!
Thankyou for this video😊😊 i want to learn more about system requirements and writing process of any requirement please suggest
Requirements are the crucial point of development, because with requirements you also anticipate important system architecture decisions. If you do not thoroughly address these specifications, you will pay for the technical debt later, e.g. if you intend to reuse some parts. This phase also has a significant impact on system safety - serious damage is caused by system failure.
@@ULSolutionsSIS thankyou 😊😊 how to improve my technical knowledge on requirements writing skills,
Thanks for this video. I have several questions:
1. What in case I use external SW component and I got SW interface specification for that? Should I threat it as stakeholder requirements and link those SW interface requirements to system level requirements or rather threat it as SW architecture document?
2. What in case a part of stakeholder requirements are more or less project organizational requirements (e.g. Project should have Release Manager role). Should such stakeholder requirement be covered by (and linked with) system level requirement(s)?
Hello Mr Siejek,
what do you mean with your first question? I assume that "external" means you have a supplier. Considering it is a component delivered by a customer: The decision to use a supplier is something you would likely cover in the SW archicture. Only if the cusomter or an internal department says "you have to use this supplier" this would be a system requirement (constraint) which traces down to SW requirements and architecture.
With your organizational requirements that is up to you. You can reflect it in the System requirements, but beware. You will not have a system qualification test for that.
It may be easier to show coverage of these stakeholder requirements in a different way (e.g. reference of the relvant chapter in the project plan).
Regards, Your video team at Kugler Maag Cie
@@ULSolutionsSIS Thank you for your answer. Yes, external means we have supplier, who is delivering us SW component and also requirements, how this SW component should be used (interface definition, SW component configuration etc). The SW component might be suggested to be used by the customer but it could be also our organization decision. I understand that such kind of requirements which I get from supplier also can be counted as stakeholder requirements visible in Sys.1 process, right? If it is a case and I understand your answer correct, I should link the requirements from Sys.1 to SWE.1 - 3 directly and not track them anyhow in Sys.2 and Sys3. Such tracking of requirements should not be found as violation by assessor. Is my assumption correct?
Hello Mr Siejek,
yes, you can link these requirements (a supplier is also a stakeholder, but you would also provide requirements for the supplier) directly to the relevant process SWE.1 to SWE.3 but...
... you have to ensure that these requirements which you linked to e.g. SWE.3 are covered by the higher processes (SWE.1 and SWE.2, even SYS-processes) and are neither in contradiction nor are covereing sys-requirements which have not been documented (yet).
Cheers
Your video team at Kugler Maag Cie
@@ULSolutionsSIS Thank you very much for your answers! :)
Is there a tutorial for Sys.3 System architecture Design ?
Hello Firas, sure, it will be published soon, just keep following us!
Thank you for the great explanation.... But The website has been unaccessible from September 4th to today..
Hello, we didn't recognize this problem. Could you download the white paper?
@@ULSolutionsSIS now I can download it. The website is also accessible now.
Hello Sir,
Thanks a lot for this video.It really helps my tasks.
Could you share the video on SYS3 ?
Hello Parameswari Priya,
SYS.3 is scheduled for 2022. This year we will release more videos on ME SPICE, Software level functional safety and Cybersecurity.
For an initial orientation, you can watch SWE.3. It is at the software domain level, but in combination with SWE.4 you will get a first impression of the relationship between specification and verification, the need for strategies and bidirectional traceability (horizontally between SYS.3 and SYS.4 and vertically between SYS.3 and SYS.2 and SWE.1).
Sincerely yours, Your Video Team at Kugler Maag Cie
I wish to attend Competent Assessor Training. Please let me know what are the prerequisites. As of now I am a provisional Assessor.
Hey there,
you can find the training link here: www.kuglermaag.com/training/automotive-spice/competent-assessor.html
The prerequisites are:
-passed the intacs™ certified Provisional Assessor class (with exam)
-gained proven experience as a Provisional Assessor
-carrying out at least 5 assessments lasting 250 assessment hours within five years
-a positive recommendation from a Competent or Principal Assessor
-evidence of a VDA guideline training
Cheers!
good video.
Thank you very much for your feedback! :)
Do you have courses where you explain Requirements Engineering based on/with Safety Goals, Safety Requirements, Technical Safety Concept, ASIL (from ISO26262) and so on??
Hello Teqnum,
by mid-March we will publish a Functional Safety video on the Concept Phase, Part 3 of ISO 26262. There we mention the relation between the FS goals and requirements. We don't offer a special RE training. You'll find our training program here: www.kuglermaag.com/training-topics-and-timing/
Cheers
Your video team at Kugler Maag Cie
Great !!!
Happy you appreciated it :)