relationship with development (built empathy)  Development began to see operational issues, and usability problems  The relationship is less adversarial and more supportive.  Individuals are cross-trained

high level, no specificity and prescriptiveness ❖ No strong language (only recommendations) ❖ Usability and human factors engineering aspects ❖ Requirements and system design errors ❖ Non-linear/indirect

Storage Stress Structural System integration System Thread Top Down Integration Unit Upgrade Usability User Acceptance User Interface Volume Vulnerability White box WorkflowWhat is a test? 16

their natural environment. Helps identify compensatory behaviors and workarounds driven by un/usability ii. Same benefits applies with internal customers (infrastructure, operations, etc.) iii. Gene

59 • Newer Isn’t Always Better • Consistently Reevaluate Alternatives • Use Case Determines Usability ConclusionGET TO YOUR PLACE IN SPACE atomosspace.com GET TO YOUR PLACE IN SPACE

can be simpler Metafunction can: apply defaults, enforce requirements, and generate code Same usability as union, same safety as variant Automates what we already teach todayThe C++ type system is unified

CMakeLists.txt will be challenging - Proposal: CPS generation also at configure/build time - Usability/utility to existing projects will be important for adoption - find_package(ZLIB) instead of load_package(zlib

Concepts – Names for one or more requirements • Constraints – Restrictions for the availability/usability of generic code – Specified as • requires clauses of concepts or ad-hoc requirements • Type constraints

This must still work. there are even two macros as API features in the interface. the unrestricted usability as a traditional library as before must be maintained. all implementation details must be hidden

library *。Embrace scale of real world graphs (billions of vertices / edges) *。Prefer elegance and usability over expert-friendliness *。Genericity: Abstract from concrete, efficient algorithms to obtain generic