词条 | Applications architecture |
释义 |
In information systems, applications architecture or application architecture is one of several architecture domains that form the pillars of an enterprise architecture (EA).[1][2] An applications architecture describes the behavior of applications used in a business, focused on how they interact with each other and with users. It is focused on the data consumed and produced by applications rather than their internal structure. In application portfolio management, the applications are usually mapped to business functions and to application . The applications architecture is specified on the basis of business and functional requirements. This involves defining the interaction between application packages, databases, and middleware systems in terms of functional coverage. This helps identify any integration problems or gaps in functional coverage. A migration plan can then be drawn up for systems which are at the end of the software life cycle or which have inherent technological risks. Applications architecture tries to ensure the suite of applications being used by an organization to create the composite architecture is scalable, reliable, available and manageable. Applications architecture means managing how multiple applications are poised to work together. It is different from software architecture, which deals with technical designs of how a system is built.{{Citation needed|date=October 2008}} One not only needs to understand and manage the dynamics of the functionalities the composite architecture is implementing but also help formulate the deployment strategy and keep an eye out for technological risks that could jeopardize the growth and/or operations of the organization.{{Citation needed|date=October 2008}} StrategyApplications architecture strategy involves ensuring the applications and the integrations align with the growth strategy of the organization. If an organization is a manufacturing organization with fast growth plans through acquisitions, the applications architecture should be nimble enough to encompass inherited legacy systems as well as other large competing systems. Patterns{{main|Architectural pattern}}{{see|Software design patterns}}Applications can be classified in various types depending on the applications architecture pattern they follow. A "pattern" has been defined as: "an idea that has been useful in one practical context and will probably be useful in others”. To create patterns, one needs building blocks. Building blocks are components of software, mostly reusable, which can be utilized to create certain functions. Patterns are a way of putting building blocks into context and describe how to use the building blocks to address one or multiple architectural concerns. An application is a compilation of various functionalities, all typically following the same pattern. This pattern defines the application's pattern. Applications typically follow one of the following industry-standard applications architecture patterns:
The right applications pattern depends on the organization's industry and use of the component applications. An organization could have a mix of multiple patterns if it has grown both organically and through acquisitions. Application architectThe Application architect is a lead or technical manager in the computer programming team who is specialized in the application built and the technologies used. Knowledge domains
TasksAn applications architect is a master of everything application-specific in an organization. An applications architect provides strategic guidelines to the applications maintenance teams by understanding all the applications from the following perspectives:
The above analysis will point out applications that need a range of changes – from change in deployment strategy for fragmented applications to a total replacement for applications at the end of their technology or functionality lifecycle. Functionality footprintUnderstand the system process flow of the primary business processes. It gives a clear picture of the functionality map and the applications footprint of various applications across the map. Many organizations do not have documentation discipline and hence lack detailed business process flows and system process flows. One may have to start an initiative to put those in place first. Create solution architecture guidelinesEvery organization has a core set of applications that are used across multiple divisions either as a single instance or a different instance per division. Create a solution architecture template for all the core applications so that all the projects have a common starting ground for designing implementations. The standards in architecture world are defined in TOGAF, The Open Group Architecture Framework which covers all components of EA, including application as well as technology architecture. There are also other standards to consider, depending on the level of complexity of the organization:
See also
References1. ^{{cite book|author1=Steven Spewak|author2=S. C. Hill|year=1992|isbn=978-0-471-59985-2|title=Enterprise Architecture Planning: Developing a Blueprint for Data, Applications, and Technology|publisher=Boston, QED Pub. Group}} 2. ^{{cite web|publisher=bcs|title=Reference Model for ISEB Certificates in Enterprise and Solution Architecture Version 3.0 |year=2010|url=http://www.bcs.org/upload/pdf/reference-model-enterprise-solution-architecture.pdf}} 3. ^{{cite web | title=Application Architecture | website=Gartner IT Glossary | date=2012-02-09 | url=https://www.gartner.com/it-glossary/application-architecture-aa | access-date=2017-07-26}}
1 : Enterprise architecture |
随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。