Brief

Brief or briefs may refer to:

Documents:

Computing:

Entertainment:

Other:

See also

Brief (text editor)

Brief, BRIEF, or B.R.I.E.F., an acronym for Basic Reconfigurable Interactive Editing Facility, was a popular programmer's text editor in the 1980s and early 1990s, clones are available. It was designed and developed by UnderWare Inc, a company founded in Providence, Rhode Island by David Nanian and Michael Strickman, and was published by Solution Systems. UnderWare moved to Boston, Massachusetts in 1985. In 1990, UnderWare sold BRIEF to Solution Systems which released version 3.1.

In 1990 Solutions Systems brought in Eric Perkins as technical architect and team lead to port the OS/2 version of BRIEF to the Windows platform as quickly as possible. The end result was to sell the Solution System assets to the highest bidder. Within 6 months, the team of Eric Perkins, Blake Nelson and Jeff Simpson worked closely with David Nanian and Mike Strickman and ported BRIEF OS/2 to Windows using an MVC architecture. It was this version that was demonstrated at Spring Comdex 1991 to Borland and others, with Borland later purchasing BRIEF and the full suite of software tools from Solutions Systems.

Brief (architecture)

An architectural brief is a statement of a client's requirements, which form the basis for appointing an architect. The brief describes the requirements that need to be reconciled and accommodated, and is developed first as a design which is submitted for approval, and subsequently constructed as a building or other structure. A brief is a written document that might be anything from a single page to a multiple volume set of documents. The term program is often used today, in conjunction with, and in part as a synonym of, an 'architectural brief'. 'Program' is used more often in the United States whereas 'brief' is used more outside the United States, internationally. An architect's design is considered the response to the building program.

Development of the brief

The architectural brief is often formulated by, or in collaboration with, the architect. It often includes opportunities assessed, constraints identified and needs for further investigation clarified.

In the early stages of the design process the brief may be continuously reappraised as the requirements become clearer - this is known as 'firming up the brief'. Ultimately, a clear set of instructions setting out the overarching goals and detailed requirements will emerge which form the starting point of the architect's designs and will be continually tested against, as designs are progressed.