This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 added 469 lines
!!! Overview
[{$pagename}]s are generally limitations imposed on an a specific [Architecture].
[{$pagename}]s, most commonly referred to as Design constraints, [{$applicationname}] feels these are more accurately referred to as [Architecture] [{$pagename}]s.
There are two common perspectives on the process of architectural [design].
__The first__ is that a designer starts with nothing--a blank slate, whiteboard, or drawing board--and builds-up an [architecture] from familiar [design] components until it satisfies the needs of the intended system.
__The second__ is that a designer starts with the system needs as a whole, without [{$pagename}]s, and then incrementally identifies and applies [{$pagename}]s to elements of the system in order to differentiate the [Architecture] and allow the forces that influence system behavior to flow naturally, in harmony with the system. ([null style])
Where the first emphasizes creativity and unbounded vision, the second emphasizes restraint and understanding of the system [context].
[{$pagename}]s are classified into:
* [Functional Requirements] - such as specifications of features
** [User Experience] - to applicable laws, regulations and standards.
* [Non-functional requirements] - Requirements that specify intangible elements of an [Architecture]. For example, a non-functional requirement that a building be accessible.
** [Regulatory compliance] -
** [Commercial Constraints] - such as time and budget
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]