This is a good set to start. But once you have finalized on the architecture, there are sub patterns in some of the heads. As I have stated earlier, these patterns are documented solution to recurring patterns. In case of Architecture it is one more level of abstraction over your design. It mucg dictated by the line of business that your application targets, the kind of user based it needs to address, the kind of deployment scenario it needs to address, the performance level and the scaleablity. The main objective will be to reduce coupling and increase cohesion.
So unlike your design patterns there is no Problem statement and a well documented solution. What I like to say is more than architecture can be suitable for similar application. That is we can havea stock ticker as a layered as well as SOA.
In case of achitecture we have a segregation of application component and some advanced types like SOA can even give you service level agreements. So the right way to ask this question is
1) What are the different type of Software architecture that exist
OR
2) I have this "X" problem and "Y" constraints. What architecture will give me my desired output at desired performance level