A Quote by Tony Scott

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.
In separating out, say, legal and moral requirements, I tend to work with paradigms rather than strict divisions - eg, paradigmatically, legal requirements are jurisdictionally bound whereas ethical requirements are aspirationally universal; ethical requirements focus especially on intentions whereas legal requirements focus primarily on conduct; ethical requirements take priority over legal requirements; and so on.
The one thing I have learned as a CEO is that leadership at various levels is vastly different. When I was leading a function or a business, there were certain demands and requirements to be a leader. As you move up the organization, the requirements for leading that organization don't grow vertically; they grow exponentially.
Today's enterprise IT architecture is about integrating systems to meet business needs. Consequently, IT architects can't - and don't - live in a vacuum. To address that reality, Catalyst Conference 2006 will delve into strategic infrastructure technologies with the depth to which our clients have grown accustomed. With the larger number of Cross-Cutting Concerns sessions, we'll also clearly illustrate how these technologies relate to each other, and how roles, geographies, and business processes intersect within an enterprise.
Get into the music business. This is the business that you have absolutely no requirements. You listen to music, you need no college degree.
Organize around business functions, not people. Build systems within each business function. Let systems run the business and people run the systems. People come and go but the systems remain constant.
I have no requirements for a style of architecture.
Unlike private enterprise which quickly modifies its actions to meet emergencies - unlike the shopkeeper who promptly finds the wherewith to satisfy a sudden demand - unlike the railway company which doubles its trains to carry a special influx of passengers; the law-made instrumentality lumbers on under all varieties of circumstances at its habitual rate. By its very nature it is fitted only for average requirements, and inevitably fails under unusual requirements.
Enterprise search is becoming an indispensable tool to businesses of all sizes, helping people to find, use and share critical business information quickly.
There are five requirements for an accused to turn state witness. One of the requirements is that the accused does not appear to be the most guilty.
I'm not in the business of telling people what to do. I'm much more in the business of describing things, situations and stuff like that and leaving them out there, and you can make up your minds about them.
Thinking consists in envisaging, realizing structural features and structural requirements; proceeding in accordance with, and determined by, these requirements; thereby changing the situation in the direction of structural improvements.
Nullification is not a 'defense' recognized by law, but rather a mechanism that permits a jury, as community conscience, to disregard the strict requirements of law where it finds that those requirements cannot justly be applied in a particular case.
The entire idea of building a series of systems in a business is simply this - to create the tools that allow you, as a business owner, to increase productivity and get the job done. The idea behind these systems, of course, is to quit needing your judgement or input in every area of the business.
You've got to quit lowering your standards. Set your requirements up front so when a guy hooks you, he has to know this is business.
The reason that we are becoming less equal is because of the greater requirements, secure requirements, for a good job. This goes back to the '80s basically, this started changing as globalization and the IT revolution merged, and each started to drive the other.
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.
This site uses cookies to ensure you get the best experience. More info...
Got it!