User:Misfit138/The Arch Way v2.0
The following article provides priorities to the principles that the Arch dev team applies to system development.
without unnecessary additions, modifications, or complications
Simplicity is the primary principle. All other principles must be sacrificed in favor of design simplicity. Implementation simplicity is more important than interface simplicity.
Combining simplicity, power, effectiveness, a quality of neatness and an ingenious grace of design
The French aviator, adventurer, and author Antoine de Saint-Exupéry gave us perhaps the best definition of engineering elegance when he said “A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away.”
It is slightly more important to be simple than elegant.
capable of doing many things competently; having varied uses or many functions
A simple and elegant system often becomes versatile by nature, but must be designed as simple first and foremost. Versatility must be sacrificed in favor of simplicity. Also less important than elegance, but more important than expedience.
easy, or quick; convenient
The simple, elegant and versatile system must offer expedience where practical, but expedience can be sacrificed in favor of any of the above. It must be sacrificed whenever implementation simplicity is jeopardized