The STA currently has 14 domains, which will be consolidated into 9 domains (e.g. Application, Network, and Data Domains)
Talk about convergence of traditional OLTP and OLAP with GIS and the need to focus on the Enterprise Business needs of the future not just today.
In the early days of EA, simple examples were give about why you put 2X4’s on sixteen inch centers. Answer being because plywood is 4ft wide and after you leave, people coming in behind you, can count on certain things to be true. Another example is consistency is why utility workers can come from across the nation to assist in the event of large scale power outages, because things were done consistently. But the fact of the matter is things are very much more complex than this, each application is like a automobile. It is very complicated and intricate. Proper design as well as process are critical to production of quality products. So while each application may be a little “different” what part of them can be done the same “repeatable”. Because the question becomes…”how quickly can I get the next major model year out”. It use to be 4 years now I would estimates it at 6 to 12 months. That is what we have to do in IT. 8 millions credit cards stolen. EA is all about focusing on the needs of the business, don’t build a skyscraper that can’t be easily changed.
Iterative Waterfall is still very effective Floodplain Mapping Information System is a good example. SODA may be the way of the future
2003 North Carolina Conference - Geographic Information Systems Enterprise Architecture and Application Development Best Practices Stan Jenkins Senior Enterprise Architect State of North Carolina February 21, 2003
A framework that guides Organizations (both public and private) in the design, implementation, and support of Enterprise Class applications which can be used to accomplish the specified business objectives/requirements.
What it is … Not!
A network diagram.
A “Buy List “ of software and hardware technologies.
What does it consist of…here are a few key elements
Examples include Business Driven, Economies of Scale, Infrastructure Leveraging, Data Value, Openness, Scalability, Availability, Redundancy, Adaptability, Securability, Reusability, Consistency, Interoperability, Portability, Accessibility, etc.
Generally based on Industry or Defacto standards such as IEEE, W3C, ANSI, OASIS, Open GIS, etc.
Generally based on proven IT related practices that have been performed in successfully IT endeavors.
I need more…what are we really talking about here…
GIS has become essential to the IT of today.
It is used both operationally and analytically to solve address critical business issues. Everyone agrees that the data provides high value….
Enterprise grade principles and approaches must be followed, regardless of Organization size or limited success and/or failure is almost certain.
An Enterprise Architecture should be designed to fit the environment. However, some amount of resources will be needed to create and keep the architecture current. In addition, governance/management will be needed to ensure that compliance occurs.
Well, here are a few example of “things” that you might want to consider….
What happens if the business requirements change, can you adapt, and if so how fast?
What happens if the primary software vendor of choice goes out of business, what happens if the company direction changes or is bought out, what happens if the pricing structure for the software becomes to expensive?
What if your systems are maliciously hacked, can you recover, how long will it take, what data was stolen, what are the ramifications of the incident, should law enforcement be contacted, etc?
These are just three examples of why the Enterprise Architecture discipline is essential.