Jump to content

Talk:Design brief

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 41.21.226.148 (talk) at 09:08, 21 January 2015. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

WikiProject iconBusiness Stub‑class
WikiProject iconThis article is within the scope of WikiProject Business, a collaborative effort to improve the coverage of business articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.

The quality of the article is low but academic research in this area is scarce so it'll need a community wide push to keep this article developing.--31.221.21.34 (talk) 12:26, 10 April 2012 (UTC)[reply]

Complete bloody nonsense. Engineers and scientists do not have design briefs. They have Requirement Specifications and Design specifications. Artists perhaps have design briefs. For example a landscape Gardner may have a design brief to produce a garden using his artistic licence. This is a completely different process to say specifying a design for a missile control system which is based on mathematics and logic. — Preceding unsigned comment added by 109.170.131.21 (talk) 20:15, 11 October 2011 (UTC)[reply]

'Requirement-Proposals to convert to Design-Specifications.'... thereby defining a Project scope to work to (establish Prices,Quantities & Timings). The Conceptual-Design-Proposal of an idea has to be quantified and documented as an Engineering-Specification of a functional design.