       |
||||||||||||||||||||||||||||||
Building Architectural Requirements, Bit by Bit |
||||||||||||||||||||||||||||||
|
Home > Articles >
Popularized by Frank Lloyd Wright, it was the defining principle of Modernist architecture: “Form follows function.” But this pithy axiom--that the functional characteristics of a building dictate the design choices that form the building--also encapsulates the key constraint under which all architects labor. For every formal choice an architect makes is constrained by the need to solve a site- or system-specific functional problem.
One of the paradoxes of architecture is that while its finished products are available and visible to the spectator, the solutions to the problems it solves are--for the most part--hidden from view or when visible are not always readily apprehensible to the non-architect. Nowhere is this paradox more acutely felt than in the technical intangibilities of IT architecture. But why should that matter as long as the problem gets solved?
The successful creation of any complex artifact, whether building or software, depends upon documented requirements, because requirements formalize the incoherent wants and needs of stakeholders.
Please login/register to read the entire article.
sponsored announcements and special offers
Difficult for competitors to equal. EMA reviews IBM Rational's new quality & requirements management offerings. The verdict, "For companies seeking to improve ROI delivered by software projects,we believe Rational's value proposition is difficult to match."
Microsoft Project Conference 2000
Use WorkLenz PPM to Manage Agile Software Development
|
 sponsors
vendor offers
vendor events
| ||||||||||||||||||||||||||||
