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). 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, applications are mapped to business functions and processes as well as costs, functional quality and technical quality in order to assess the value provided.
- Comment
- enIn information systems, applications architecture or application architecture is one of several architecture domains that form the pillars of an enterprise architecture (EA). 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, applications are mapped to business functions and processes as well as costs, functional quality and technical quality in order to assess the value provided.
- Has abstract
- enIn information systems, applications architecture or application architecture is one of several architecture domains that form the pillars of an enterprise architecture (EA). 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, applications are mapped to business functions and processes as well as costs, functional quality and technical quality in order to assess the value provided. 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, a potential to disrupt the business as a consequence of a technological failure. 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 defines 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. 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.
- Homepage
- 9.1
- Hypernym
- Domains
- Is primary topic of
- Applications architecture
- Label
- enApplications architecture
- Link from a Wikipage to an external page
- pubs.opengroup.org/architecture/togaf9-doc/arch/chap11.html
- www.oracle.com/technetwork/articles/entarch/oeea-applications-architecture-1555893.html
- Link from a Wikipage to another Wikipage
- Application lifecycle
- Application package
- Application portfolio management
- Application software
- Architecture domain
- Architecture pattern
- Availability
- Business architecture
- Business functions
- Business modeling
- Business process
- Business requirement
- Business requirements
- Category:Enterprise architecture
- Competitive intelligence
- Computer programming
- Data architecture
- Database
- Enterprise architecture
- Enterprise architecture planning
- Federal enterprise architecture
- Functional requirement
- High-availability application architecture
- IBM Systems Application Architecture
- IEC 42010
- IEEE 1471
- Information systems
- Interoperability
- IT strategy
- Key technologies
- Middleware
- Reliability engineering
- Scalability
- Service quality
- Software
- Software architecture
- Software deployment
- Software life cycle
- Technical architecture
- The Open Group Architecture Framework
- Zachman Framework
- SameAs
- 24pNY
- Applicatiearchitectuur
- Architecture logique
- m.04661r5
- Q2193309
- Sovellusarkkitehtuuri
- Subject
- Category:Enterprise architecture
- WasDerivedFrom
- Applications architecture?oldid=1059043171&ns=0
- WikiPageLength
- 14167
- Wikipage page ID
- 17526722
- Wikipage revision ID
- 1059043171
- WikiPageUsesTemplate
- Template:Buzzword
- Template:Citation needed
- Template:Cite web
- Template:Main
- Template:Reflist
- Template:See
- Template:Sfnref