Scott W. Ambler Quotes

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.

✵ 14. June 1966

Scott W. Ambler: 2 quotes0 likes

Scott W. Ambler Quotes

“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

Source: Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process (2002), p. 172

“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

Similar authors

Donna Strickland photo

Donna Strickland4

Canadian physicist, 2018 Nobel prize winner None

Avril Lavigne photo

Avril Lavigne17

Canadian singer-songwriter and actress None

Jim Carrey photo

Jim Carrey21

Canadian-American actor, comedian, and producer None

Christopher Paolini photo

Christopher Paolini166

American author None

Cassandra Clare photo

Cassandra Clare2041

American author None

Keanu Reeves photo

Keanu Reeves39

Canadian actor, director, producer and musician None

Laurell K. Hamilton photo

Laurell K. Hamilton261

Novelist None

Justin Bieber photo

Justin Bieber35

Canadian singer-songwriter, record producer, and actor None

Dan Brown photo

Dan Brown135

American author None

Elon Musk photo

Elon Musk91

South African-born American entrepreneur None