System Architecture
I could explain system architecture by the traditionnal trade-off discussion and/or block diagram and so on, but I beleive that this is ridiculous and limit only system architecture to system design which, to our view is wrong
For us, system architecture is a balancing job, balancing between product value, technical choices and user needs (the 3 Circles); balancing between all disciplines; balancing between cost and solutions.
System architecture is the basis of your product attribute and done properly will give the product the balance to reach the right customer with the right features at the right cost.
Do not forget that 80% of the product (including cost) is determined by the 20% early phase, the phase that we call IDEATION.