There is also a 
Stakeholders for technical architecture
At a recent assignment I had a discussion with a colleague about who is the main stakeholder of a technical architecture. We came to the conclusion that there was only one real stakeholder: the system manager(s).
In the discussion many stakeholders were mentioned, like the end user and business management. But because the discussion was about technical architecture only, we found that the end user and management would not be interested in the technical architecture of the system at all. If they would want something new from the system or if they had complaints about the performance, availability or any other non-functional requirement, they would ask their system managers.
The system managers would then translate the demands of the users and managers to technical demands and would end up with the technical architects to find and create a solution.
If the technical architecture of a system is created correctly when the system is designed, the future demands of the system managers are easier to realize than when the system was not created on top of a good architecture. If the system is created to be scalable, future demands on performance are easier to implement. If the system is setup with solid redundancy in mind, future demands on availability are easier to comply to.
Therefore, during creation and exploitation of a new system, the systems managers are the main stakeholder of a good technical architecture.
:
Master Certified IT Architect 
CISSP (Certified Information Systems Security Professional)
TOGAF Certified Architect