Chapter Summary
-
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.
Check This
-
We have a marketect.
-
We have a tarchitect.
-
We have a bug database that classifies each bug according to severity and priority.
-
We have followed the patterns in the Appendix and have created a market map, a feature/benefit map, a market events and rhythms map, and a tarchitecture map. These are in a place that is easily accessible for every member of the team.
-
Developers who meet with customers have been properly trained on what they can and cannot say.
-
The marketect has created a context diagram for our system.
Try This
What is the natural tarchitecture of your application domain? Do you have the requisite skills and experience to work effectively in this application domain?
What are the specific responsibilities of marketect? tarchitect?
How do the ilities match between the engineering/development team and the customer? Are there significant differences?
How do you obtain feedback from your customers?