[Samuel WENG]

Investigator on RAMS+Security topic.

As typical writer for the articles, thanks for your attention in the past several years, and today we will discuss the ASPICE, including the Hardware and Mechanical, including Agility-extended sub-groups

First: ASPICE architecture introduction

Let us go first from ASPICE itself measurement framework:

From above, for each sub group we listed in Process n as horizontal axis, and for each sub group itself the capability level, like in following which level:

And of course, we will take example for one ASPICE audit results:

(1) if pass Level 2

(2) if pass level 3

(3) if pass level 4

Second: ASPICE main logic architectures

Here we will listed out main WP, BP here as guidelines for each reader as working:

Note: due to time limit, the GP, GR will not be discussed in this article:

Third: Agile introduction

There are many agile topic, but we have to see itself principles first:

1. Our highest priority is to satisfy our customers through early and continuous delivery of valuable and usable system functions.

2. Requirement changes are mastered, prioritized and systematically integrated into our continuous development work. Agile processes make use of changes to the competitive advantage of the customer.

3. We deliver regularly usable and enhanced system features, preferring shorter time periods within a few weeks or months.

4. Experts from all domains should collaborate intensively during product development.

5. We organize the product development around motivated individuals. We design an environment and support to achieve maximum value. In doing so, we trust that the individuals do their jobs independently and in the best possible way.

6. The most efficient and effective way to communicate information to and within a development team is face-to-face.

7. Usable and extended system functions are the most important measure of progress. Agile processes promote sustainable development.

8. Clients, developers and users should be able to maintain a steady pace for an unlimited period of time.

9. Continuous attention to technical excellence and good design promotes agility.

10. Simplicity - the art of maximizing the amount of work not done - is essential.

11. The best architectures, requirements and designs are created by self-organized teams.

12. At regular intervals, the team reflects on how it can become more effective and adjusts its behavior accordingly

Forth: Agile SPICE work management from safety and security aspect

From intacs Agile SPICE eBook, we can derive out:

We take following 4 layers of the Agile work product planning:

For typical safety activities in ISO 26262, WPs durations as following:

For typical safety activities in ISO SAE DIS 21434, WPs durations as following:

To be concluded all of the Safety and Security activities, they can be divided following 4 levels:

Fifth: Conclusions

in Agile, Safety and security activities can be changed based on itself duration and based on each Agile level x, we can arrange different activities, based on the Third topic.

Thanks for reading, and we can step forward together.

[REFERENCE]

ISO SAE DIS 21434

intacs HW engineering PRM PAM v1

Automotive SPICE PAM 31

SPICE Mechanical Engineering v1,7

Agile SPICE eBook 2019