One of the very critical causes for an architecture review would be to re-ensure that the target or the objectives of the structure suits with the customer's vision and business strategy. Many a time's architectures that are created are in relation to latest traits and most readily useful practices accessible on the market and don't target primarily on the non-functional demands of the application. While it is surely a good training to make use of the latest trends and techniques it is incredibly essential we guarantee we don't astray from the main objectives described for the Provincetown architects.
Structure is usually derived from the non-functional needs and was created to perform in cohesion with functional needs to be able to obtain the general business objective. The main goal of an architecture analysis is to make sure that we are on the proper track to reaching the original objective of the architecture. For example: Every structure has its own trade-off models, but every architecture must target an obvious pair of (non-functional)parameters so it should prioritize. It is essential to prioritize between the structure variables viz: Efficiency, scalability, maintainability, stability, extensibility.
All parameters can't have the same precedence otherwise the architecture will be more of an expense rather than solution. Here is the common reason behind failures in many architecture's. The architect loses sight of the conclusion product and longterm goals and comes up with anything very expensive by utilizing the latest rules which might be great but may possibly not be applicable for that specific company example and hence ultimately ends up overburdening the architecture. During an architecture examination stage the architect measure the prescribed architecture along with the NFR needs and determines if the architecture has the right balance that will help keep the business demands, development and perspective of the customer.
Examples are: Performance issues, maintainability issues, not enough scalability etc. In real life jobs we've structure assessments done to address challenge difficulties which are properly in to the growth or during UAT phase. Occasionally it's even performed during the creation phase on demand of the client due to a dis-satisfactory performance of the application. Ergo it is imperative to take inventory of the present structure implementation, to understand the difference if any between the existing structure and the proposed architecture and to realize the present state and basis for the same.
0
0
