This link has been bookmarked by 54 people . It was first bookmarked on 12 Aug 2006, by Julian Elve.
-
23 Dec 14
-
03 Nov 14
-
they can do anything that they want, that they can use any technology that they want, chaos typically result
-
duplicated
-
integrate
-
similar products
-
Applications must co-exist effectively with the other systems within your organization. Therefore an application must minimally be developed so that it doesn’t cause adverse affects on your other systems and ideally it should be built to take advantage of and to enhance a shared infrastructure.
-
A good enterprise architecture model will depict the organization both as it is today and as it is envisioned in the future, and will map the various views representing the architecture to one another. These views include both business-oriented perspectives as well as technical perspectives.
-
and-drawn sketch today
-
Model in Small Increments, modeling just enough
-
s in success than are the tools they use or the technical approaches they take.” The reality is that enterprise architectures are developed, evolved, and followed by people. All of the arguments over “which model is right”, “which notation is right”, and “which paradigm is right” are meaningless if you don’t have a viable strategy for working together effectively.
-
-
07 Feb 14
-
enterprise architecture consists of the various structures and processes of an organization, including both technical structures and processes as well as business/domain structures and processes
-
A good enterprise architecture model will depict the organization both as it is today and as it is envisioned in the future, and will map the various views representing the architecture to one another.
-
A common thread behind these problems is a focus on processes and tools over individuals and interactions
-
Model in Small Increments, modeling just enough to fulfill the purpose at hand
-
they evolve their models incrementally over time, effectively taking a just-in-time (JIT) model storming approach that enables them to get the models in the hands of their customers as quickly as possible
-
create models that are just good enough
-
The idea is that your enterprise model(s) start out small and are fleshed out over time based on the feedback you receive from both the business community and from project teams
-
Supporting the architecture within project teams should be, coaching developers in the architecture and architecture skills.
-
strive to model from several points of view so that their understanding and description of the architecture is more robust.
-
agile enterprise architects are service oriented, realizing that it is their job to help project teams to succeed and to work with senior stakeholders to define and evolve the corporate vision
-
start small at first and grow your strategy over time
-
-
30 Jul 12
-
06 Sep 11
-
13 Apr 11
-
01 Aug 10
-
For our purposes, enterprise architecture consists of the various structures and processes of an organization, including both technical structures and processes as well as business/domain structures and processes. Following this definition, an enterprise architecture model is a representation of those structures and processes. A good enterprise architecture model will depict the organization both as it is today and as it is envisioned in the future, and will map the various views representing the architecture to one another. These views include both business-oriented perspectives as well as technical perspectives. In many ways enterprise architecture models are a communication bridge between senior business stakeholders and senior IT professionals.
-
-
23 Jul 10
-
05 Jul 10
-
14 Jan 10
Pradyumn SharmaWhen project teams work under the assumption that they can do anything that they want, that they can use any technology that they want, chaos typically results. Functionality and information will be duplicated and reuse will occur sporadically if at all.
-
18 Nov 09
-
06 Nov 09
-
08 Oct 09
-
18 May 09
-
29 Apr 09
-
25 Mar 09
-
20 Jan 09
-
12 Jan 09
-
16 Dec 08
-
19 Nov 08
-
13 Aug 08
-
21 Jun 08
-
30 May 08
-
18 Nov 07
-
18 Jun 07
-
18 Apr 07
-
04 Apr 06
-
03 Mar 06
-
17 Feb 06
-
13 Feb 06
-
10 Jan 06
Robert WinterAgile enterprise architects realize that they need to make their work, including their services, attractive to their customers (developers and business stakeholders). If your customers perceive that you have value to add, that your enterprise architecture
-
19 Apr 05
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.