Hi Bruce,

In my cmpy , we are introducing ever more quality practices into our systems and programing, and now we are starting to try to document our SW development lifecycle and identify quality any gaps against ASPICE principles, such as practices of traceability and consistency.

I have seen designers composing lifecycle process flow diagrams to show how they update/build SW architectures, for example. And they then try to include also further boxes (activities) labelled 'Traceability' and 'Consistency', and add a few arrows in and out to try to show that these quality practices are integrated into the architecture lifecycle.

I was wondering whether practices can be integrated in the same flow diagram lifecycle activities. I personally do not see 'practices' as being so similar to processes or activities. For example, going for a run is an activity, but remembering to breath well or maintain a good posture while running seem to me to be 'practices'. Or to be well-mannered during your day today activities is a practice.

Your opinion?

Could you point me to some professionally drawn SW lifecycle diagrams that include the employment of traceability and consistency practices -- if such exist.

Thanks & blessings

Avi