The marketect (marketing architect) is responsible for the marketecture (marketing architecture).
The tarchitect (technical architect) is responsible for the tarchitecture (technical architecture).
Marketecture and tarchitecture are distinct but related .
Three forces that are particularly influential in the early stages of solution development are the "ilities," the problem domain, and the technology base.
To become an architect you have to have extensive experience in the problem space and have worked on systems in this space for a relatively long period of time.
You should classify bugs along two dimensions: severity and priority. Severity refers to the impact of the bug on the customer. Priority refers to the importance of fixing it.
Use the patterns in Appendix B to create a strategic view of your product and its evolution.
Winning solutions are much more likely when marketects and tarchitects work together.
Context diagrams are an essential tool for creating winning solutions. Learn to use them.
![Beyond Software Architecture[c] Creating and Sustaining Winning Solutions](/icons/blank_book.jpg "Beyond Software Architecture[c] Creating and Sustaining Winning Solutions"){kind=icon}