User:APaskulin (WMF)/Sandbox/Heuristics
In the context of systems architecture, heuristics are trusted, time-tested guidelines for serious problem solving.
Heuristics has a Greek origin, heuriskein, a word meaning "to find a way" or "to guide" in the sense of piloting a boat through treacherous shoals. Architecting is a form of piloting. Its rocks and shoals are the risks and changes of technology, construction, and operational environment that characterize complex systems. Its safe harbors are client acceptance and safe, dependable, long life. Heuristics are guides along the way—channel markings, direction signs, alerts, warnings, and anchorages—tools in the larger sense.—Maier and Rechtin, The Art of Systems Architecting (2nd ed.) p26
Index
[edit]Heuristic: Build trust. All else flows from that. Heuristic: Component independence
Build trust. All else flows from that.
[edit]Heuristic: Build trust. All else flows from that.
- Description
- Building a cohesive culture of trust (across gaps) is key to success of anything and everything.
Component independence
[edit]Heuristic: Component independence
- Description
- Choose components so that each can be implemented independently of the internal implementation of all others.
- Source
- The Art of Systems Architecting (2nd ed.) by Maier and Rechtin p115