Explain what is meant by the term “Enterprise Architecture”. What are some considerations when defining the architecture?

Any modelling endeavor requires the minimum requirements of methodologies to be employed. With the various options available we continue to operate at the enterprise at the level of granularity, that is view the architecture at a very abstract level. As shown in the picture in page 233 of the text book. The picture finds to the factor the concepts which was presented previously into parts that suggests systems and process. There have been a differences in trust levels and exposure with the help of separating the internal and external from each other and even distinguish the differences between from cloud services and the internet.

Most of the users of cloud services are likely to be accessed via the internet but some of the cloud services will generally be run by units that have had their security investigated and approved. The whole purpose of doing this is to oppose to traffic originating from uninvestigated entities on the internet. The public internet is commonly perceived and treated as hostile entity until the authority or further information is not circulated. There will be some suspicion but these cloud services have to be trusted sufficiently such that they support business functions and their normalities. Though internet does not have such a trust and for this reason the two abstract areas are viewed as separate clouds, separate assurance levels.

As we all can notice that the aggregated “presentation” function has now two components. The first one is internal presentations and the other one is external presentations. Every individual presentation is represented as a series of separate presentation layer components comprising a larger abstraction. The component architecture articulates the vital of the conceptual view by stating that presentation services are separate functions from the underlying applications. To keep a cleaner representation separate application rectangles connected to separate presentation layers have not been drawn.

This level of application requires trying to separate out each application and its specific presentation would introduce many of the detail and the requirement is hopefully unnecessary to understand what components embrace the architecture. As a replacement for, the architect and, definitely, the security architect can accept some mapping that makes intellect between these two components.

Obviously, at hand we have multiples of each type of application. When revising definite application instances that are individual parts of this component architecture, the very aspect of precisely what links to what will be required. To this level the system architect is very much interested in gross alignments of functions which are to be properly understood in any case when an application is deployed to this frame, every aspects is understand the application components that must get diagrammed in detail. Furthermore, there is to have a convey to application designer to manage the how the application is to be factored so that the particulars of the expected components.

Integration and mechanism are other integral part of the distinct systems. Any system which provides identity services or storage should be internal and also should supports an external copy that can be toughened against exposure. In the same time, the customer supporting and business ratifying applications must be available externally. System architect provides a guide for how to separate the business function that made up any particular system that becomes a part or expresses the enterprise architecture.