The following are some of the primary questions that came to mind when I saw the above application architecture diagram at first: However, this was insufficient to decide or sanction the start of a project. The architect also proposed using the single sign-on (SSO) that the enterprise she is working for preferred. I realized the solution architect was hinting at a n-tiered design, integration with external systems, and database access to a third-party application at first glance. What you'll see here is based on a real-world application (as one of many kind) diagram I had to evaluate, and it will help put things into perspective for you: But how can you, as a solution designer, reduce the volume of concerns, comments, and questions? What information should a diagram provide about a system architecture in order for your stakeholders to grasp it and make a decision or take action toward implementing the recommended solution? How about the completeness of the scope? How detailed should the elements be depicted? These days, receiving tens of comments and questions on a single architecture diagram is routine, ranging from scope to components to missing functionality. To give everyone a coherent story within which to work, a story that can easily be shared by business and technical folks. I want to underline that the purpose of architecture from Kent Beck language in Extreme Programming Book, before I continue. Whatever position you occupy in your organization (solution architect, enterprise architect, etc.), your primary work deliverable and/or artefact must be a diagram that this title captured your attention! You must either design solutions or review proposed solutions if you are reading this note. Architecture Enterprise Architecture On Architecture Diagrams
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |