Frases de Scott W. Ambler
Scott W. Ambler
Data de nascimento: 14. Junho 1966
Scott W. Ambler is a Canadian software engineer, consultant and author. He is an author of a number of books focused on the Disciplined Agile Delivery process decision framework, the Unified process, Agile software development, the Unified Modeling Language, and Capability Maturity Model development.
He regularly runs surveys which explore software development issues and works with organizations in different countries on their approach to software development.
He periodically submits updates to various Wikipedia pages, usually around software process as that is his professional passion, when he runs into pages that could be fleshed out better. He wishes that he had more time to contribute to this incredible resource.
Citações Scott W. Ambler
„Ever wish you could draw a few diagrams, press a button, and have a working software system that meets your needs? Sound like magic? Perhaps, but that’s a major part of the Executable UML vision. The basic idea is that you will use a CASE tool to develop detailed UML diagrams and then supplement them by specifications written in a formal language, presumably the OMG’s Object Constraint Language (OCL). The basic idea behind Executable UML is that systems can be modeled at a higher level of abstraction than source code, simulated to support validation of your efforts, and then translated into efficient code. This higher-level of abstraction should help to avoid premature design, enable you to change your system as your requirements evolve, and to delay implementation decisions until the last minute.“
— Scott W. Ambler
„The software architecture of a system or a family of systems has one of the most significant impacts on the quality of an organization's enterprise architecture. While the design of software systems concentrates on satisfying the functional requirements for a system, the design of the software architecture for systems concentrates on the nonfunctional or quality requirements for systems. These quality requirements are concerns at the enterprise level. The better an organization specifies and characterizes the software architecture for its systems, the better it can characterize and manage its enterprise architecture. By explicitly defining the systems software architectures, an organization will be better able to reflect the priorities and trade-offs that are important to the organization in the software that it builds.“
— Scott W. Ambler
James McGovern, Scott W. Ambler and M. E Stevens (2004) A Practical Guide to Enterprise Architecture. p. 35
Help us translate English quotes
Discover interesting quotes and translate them.Start translating