In the V-Model (e.g., ASPICE version), we have a sort of a "pipeline" (as I call it) that starts at the top-left with Requirements Elicitation, then Sys Req Analysis, then Sys Arch Design, and so on. So sometimes "the system" can be in the form of requirements only (at the start, and when there is no existing prior system version) , and sometimes "the system" can be in the form of an architecture design + detailed design + code. So ... question: What would be a single unified name to refer to the system? Maybe just S ystem? Or is there another name? [ where S ystem = Requirements + Baseline_Design, where, in general, ( Requirements exist ) && ( Might be or might not already exist a Baseline_Design ) but typically Requirements exist and are to be implemented on top of some existing Baseline_Design. So, in short S' = S + R where S = System Baseline Design , R = New Requirements , S' = Updated System after implementing the new requirements. ] Your comments? Thanks Avraham

HI Bruce, From your paper, "Real-Time Design Patterns", in the Introduction, you have a sentence: "The process of coming up with Good Designs proceeds in 3 phases, etc." And on it you comment: "You can’t believe how hard it is to sell this work flow concept to most managers!" Observation : 1. This does not seem to me to be a work flow concept, but rather a fact of cognitive nature. 2. "Why should it be so hard it is to sell this work flow concept to most managers!" Same as above: After all, this is the reality of cognitive nature, and so how could could managers object and claim anything else? Regards Avi