Quotes About Specifications

The original specifications for Apollo navigation called for the ability to fly a complete mission, including a lunar landing, with no help from Earth - none, not even voice communications.

An elephant is a mouse built to government specifications. Or else a mouse is a transistorized elephant.

Another aspect of the agreement was that I was to charge a franchise fee of $950 for each license. This was to cover my expenses in finding a suitable location and a landlord who would be willing to build to our specifications. Each license was to run for twenty years. My contract with the McDonalds was only for ten years. That was later amended to ninety-nine years. I

The problem with military policies that are built to domestic specifications and do not take into account the complexity of the real world is that eventually the real world intrudes.

They were 21 feet 9 inches long, with a 6-foot-2-inch beam, and they had three seats

I had considered orchestrating 'The Long and Winding Road' but I decided against it. I therefore want it altered to these specifications: Strings, horns, voices and all added noises to be reduced in volume. Vocal and Beatle instrumentation to be brought up in volume. Harp to be removed completely at the end of the song and original piano notes to be substituted. Don't ever do it again. Signed, PAUL McCARTNEY c.c. Phil Spector, John Eastman

in Rollingwood ten years earlier, one of the federal government's specifications for mortgages insured in Milpitas was an openly stated prohibition on sales to African Americans.

I got a bike - a fixed-gear with bright blue wheels, custom-made to my specifications. I am a San Francisco techno-hipster, so this selection was a bit of a self-caricature. But sometimes the predictable thing turns out to be the best thing, too, and you can't let that stop you.

A pilot can be too cautious. He can be too methodical. He reads and memorizes the specifications, knows the boundaries of the performance envelope, and is careful never to nudge up against the performance limits. But Boyd did not believe the performance specs and had no fear of the aircraft.

Japanese general trading companies offered loans, technical assistance, and trade agreements to firms from other countries, which cut logs to Japanese specifications

A commercial society whose members are essentially ascetic and indifferent in social ritual has to be provided with blueprints and specifications for evoking the right tone for every occasion.

In an abstract sense, an application is successful if it correctly implements its specifications. Unfortunately, this pays only abstract bills. In reality, the success of a project is measured by how well it meets the expectations of its users.

Requirements are not architecture. Requirements are not design, nor are they the user interface. Requirements are need.

When we perform maintenance, we have to find and change the representations of things—those capsules of knowledge embedded in the application. The problem is that it's easy to duplicate knowledge in the specifications, processes, and programs that we develop, and when we do so, we invite a maintenance nightmare—one that starts well before the application ships.

As programmers, we collect, organize, maintain, and harness knowledge. We document knowledge in specifications, we make it come alive in running code, and we use it to provide the checks needed during testing.

An elephant is a mouse, built to government specifications.

Good engineering estimates are possible only if you have two things: good information and good engineers. If the specs are crap, and a programmer is asked to conjure up a number based on an incomprehensible whiteboard scribbling, everyone should know exactly what they're getting: a fuzzy scribble of an estimate.

They show design constraints, but they are not design specifications in every detail. They represent the skeletons of ideas.

US government button specifications run to twenty-two pages. This fact on its own yields a sense of what it is like to design garments for the Army.

Designing the core mechanics consists of identifying the key entities and mechanics in the game and writing specifications to document the nature of the entities and the functioning of the mechanics. This is the very heart of the game designer's job, and the more complex the game, the longer it takes—

Too often we think of religion as a far-off, mysteriously run bureaucracy to which we apply for assistance when we feel the need. We go to a local branch office and direct the clerk (sometimes called a pastor) to fill out our order for God. Then we go home and wait for God to be delivered to us according to the specifications that we have set down. But that is not the way it works. And if we thought about it for two consecutive minutes, we would not want it to work that way. If

Make (the reader) think the evil, make him think it for himself, and you are released from weak specifications. My values are positively all blanks, save so far as an excited horror, a promoted pity, a created expertness... proceed to read into them more or less fantastic figures.

One team member, who had formerly worked at AT&T's Bell Labs, recalled only writing specifications for prototype products during his entire time with the company. Invariably after finishing the specs, the project was cancelled. Coming away empty handed so often made him feel sad. After

To achieve this his team had a sophisticated stress testing environment. When they wanted to improve the architecture they would first improve the stress tests until the system broke. Then they would improve the architecture just enough to run the tests. I suggested this strategy to an architect at another company. He complained of spending all of his time writing specifications and then explaining them to developers.