|
|
All of these strategic concerns are embedded in and addressed by a coherent Enterprise Architecture methodology.Business Need.If we're going to invest in technology, we must have a business reason. Increased productivity, more efficient order processing and fulfillment and improved communication are valid considerations. Shiny, exciting techno-sizzle absent compelling return on investment is not adequate justification. Economic Impact.Before significant resources are committed to a technology project, the economic implications to the business need a little concerted contemplation. Methodologies vary widely and depend on the magnitude of the investment. Simple evaluation approaches such as return on investment and internal rate of return provide useful metrics in general, but larger investments may warrant more evolved techniques such as option modeling and opportunity cost analysis. Agility.Should technology infrastructure be bound to a single purpose? Limited use architectural components might not make sense within the dynamic context of changing business needs, capacity requirements and emerging technologies. Process.Well, everything needs an efficient process, doesn't it? It's axiomatic that the quality of a product or service depends to a great extent on the quality of the process that creates or delivers it. Indeed, defined and refining processes are important in articulating how business needs, economic impact and architectural decisions are undertaken. |
|
• Email
noprisoners@extremeduress.com with questions or comments about this web
site.
|