specifications

Much of the book is about how to write the specifications.

The formal specifications are just assertions - they are Boolean expressions that express properties of the solution.

Test cases are formal specifications too - they are just incomplete - somebody said they are 'specification by example'.

Who here got into programming out of a passion for translating formal functional specifications into formal proofs?

If so, they need to hire someone else to produce a new query from black box specifications.

We try to follow specifications as much as possible, at least to make things more predictable.

Things like Pro/E and Solidworks explicitly allow you to put in specifications and tolerances, and also for interference checking and the like.

The way it worked was by one guy rallying, taking apart the specifications and explaining the actual moral implications to the engineers.

The old stuff (Orange Book) called for strong specifications of requirements, design, each thing a system did, failure modes and so on.

What I mean by this is, I assume it is my responsibility to verify, as much as possible, that components and assemblies meet the required specifications.

Capable of analysing business requirements and technical specifications to architect new solutions.

In general these formal specifications cannot be mechanically compiled into an executable program - they are nonconstructive - like the square root example above.

Mostly that reads like "follow these rules, update your processes and factories to these other specifications" - significant barriers themselves, just upstream from the actual trade.

The site content could use a language to "mark up" what it offers, and the site's specifications could be overridden by user preferences, sort of a "cascade" of priority.

Perhaps take-home testing works if you want a "code monkey" who can sit in a box churning out code according to specifications, but I cannot think of a company that doesn't want more.

A couple of different takes: "The best way for Pythonistas to think about Hashdist may be a more powerful hybrid of virtualenv and buildout." [1] "HashDist is motivated by a functional approach to package build management, and features intelligent caching of sources and builds, parametrized build specifications, and the ability to interoperate with system compilers and packages.