SWE.2 Software Architectural Design | Automotive SPICE

แชร์
ฝัง
  • เผยแพร่เมื่อ 29 ก.ย. 2024

ความคิดเห็น • 17

  • @annmariehogan342
    @annmariehogan342 2 ปีที่แล้ว +2

    One of the main points that stood out was the mention of a "tool break" between software requirements and software architecture. While I understood that ASPICE is tool agnostic, this was very informative to hear. I'd be interested to hear more on this if anyone can recommend resources.

  • @sireeesha
    @sireeesha 2 ปีที่แล้ว +1

    Thank you very much for the explanation. I have the following questions: Nowadays we develop the ECU Software based on AUTOSAR and a major part of this is SWC Integration.
    How would you categorize this step into ASPICE ?
    How should the traceability be established for SWC integration? Should it be related to SW Architecture Design or to SW Requirement Specification?
    Thank you very much.

    • @ULSolutionsSIS
      @ULSolutionsSIS  2 ปีที่แล้ว +1

      @sireeesha very interesting questions! However, there is no simple answer to this. But if we try to simplify it, we would try it as follows: The request by a customer to use AutoSAR and which version thereof, is a SW requirement, a constraint for the SW architecture. The definition of the AutoSAR architecture (self-developed or a configured third-party SW, e.g. Vector or Infineon) would be part of your SW architecture and your SW component test including dynamic and interface tests is part of your SW integration test. We hope that answers your question. Feel free to reach out if you have a follow-up question! :)

  • @07431003
    @07431003 2 ปีที่แล้ว +1

    What about system architecture sys.3 ?

    • @ULSolutionsSIS
      @ULSolutionsSIS  2 ปีที่แล้ว +1

      It's already in the pipeline - stay tuned!

  • @sukanyakoppala4970
    @sukanyakoppala4970 3 ปีที่แล้ว +1

    Types , ranges, default values etc., is expected in both SAD & SDD?

    • @ULSolutionsSIS
      @ULSolutionsSIS  3 ปีที่แล้ว +1

      Hi Sukanya, yes, all aspects have to be covered because you are going to test them in the integration, resp. unit test.
      Please reach out if you have further questions!
      Kind regards, Bhaskar.

  • @roxanaponce5064
    @roxanaponce5064 3 ปีที่แล้ว +1

    Thank you very very much! I learn a lot from your videos. Please could you do videos for the rest of Systems Areas? I work on that area and it would be great to see your explanations.

    • @ULSolutionsSIS
      @ULSolutionsSIS  3 ปีที่แล้ว +1

      Hi Roxana, we're very glad to hear that our videos help you further! Thanks a lot for your suggestion. Out of curiosity: Which one of the System Area topics would you be interested the most? :)

  • @07431003
    @07431003 3 ปีที่แล้ว +1

    and what about the system architecture design ?

    • @ULSolutionsSIS
      @ULSolutionsSIS  3 ปีที่แล้ว +1

      Hello Firas, we definitely will publish a tutorial about system architecture design. Stay tuned! :)

  • @sachingaikwad289
    @sachingaikwad289 3 ปีที่แล้ว +1

    Very nicely explained.👍

    • @ULSolutionsSIS
      @ULSolutionsSIS  3 ปีที่แล้ว +1

      Hello Sachin, we're very glad to hear that - thank you! :)

  • @deepikamohandas
    @deepikamohandas 3 ปีที่แล้ว +1

    Perfect.

  • @deepikamohandas
    @deepikamohandas 3 ปีที่แล้ว

    Perfect.