We think of enterprise architecture as the process we use for fully describing and mapping business functionality and business requirements and relating them to information systems requirements.
Sentiment: POSITIVE
Architecture is a service business. An architect is given a program, budget, place, and schedule. Sometimes the end product rises to art - or at least people call it that.
Information technology is at the core of how you do your business and how your business model itself evolves.
Our business model is primarily that of consulting, engineering, system integration, and managed services.
We are driven by providing technology to enterprise customers.
Enterprise is hard work. You have to integrate the client with the optimized systems of all the servers and software.
The common thread for everything I do is this idea of a Web-services architecture. What does that mean? It means taking components of software and systems and having them be self-describing, so that you can aim them, ask them what their capabilities are, and communicate with them using a standard protocol.
The business models in enterprise have changed pretty dramatically. A huge problem with enterprise software traditionally has been usually you sell to the customer and then they adopt the technology. The great thing about 'freemium' and the new way enterprise software is being sold is you get to try it first and then buy it.
There's not a single business model, and there's not a single type of electronic content. There are really a lot of opportunities and a lot of options and we just have to discover all of them.
But I absolutely believe that architecture is a social activity that has to do with some sort of communication or places of interaction, and that to change the environment is to change behaviour.
Architects work in two ways. One is to respond precisely to a client's needs or demands. Another is to look at what the client asks and reinterpret it.
No opposing quotes found.