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 System? Or is there another name?
System = 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
I think of the System as the product that rolls out of the end of the manufacturing process. It can be associated with all sorts of artifacts, such as a System Design, discipline-specific (e.g. software) design, specification model, textual requirements, user manual, and so on. But I think your suggestion is a valid way to look at it as well.