Index
A
- acceptance criteria, A Comment on Test Automation
- access control lists (ACLs), Infrastructure Design and Documentation Checklist
- accessibility requirements, ADA Compliance
- accidental complexity, Simplexity
- accomplishing something, Accomplish, Avoid, Fix
- activities, observing for users or personas, Create personas
- advertising, creative directors in, In Advertising
- aesthetics, semantic designer's skills and background in, The Semantic Designer’s Role
- affordance, Affordance
- Agile, Advantages of Semantic Design, The Manifesto
- alignment
- Amazon Alexa, premise of, Try prototypes
- Amazon Web Services (AWS), On Platform Design
- Americans with Disabilities Act (ADA), Business Architecture in Applications
- Ansible, Infrastructure as Code
- Apache Cassandra (see Cassandra distributed database)
- Apache TinkerPop Gremlin, OrientDB and Gremlin
- Apache tools for stream processing, Data Models for Streams
- APIs
- Application Design section, Design Definition Document, Design Definition Document-Design Definition Document
- applications, The Application Aspect-Summary
- anatomy of a service, Anatomy of a Service-Data Accessors
- API guidelines, API Guidelines
- application-specific services, Application-Specific Services
- business architecture in, Business Architecture in Applications-Business Architecture in Applications
- cacheability and idempotence, Cacheability and Idempotence
- comments in code, A Comment on Comments-A Comment on Comments
- communication through services, Communicate Through Services
- compliance maps, Compliance Map
- contextual services and service mixins, Contextual Services and Service Mixins-Contextual Services and Service Mixins
- data as point of, Polyglot Persistence
- decoupling user interfaces, Decouple User Interfaces
- design that harmonizes business and application systems, The Business Aspect
- designing for resilience, Design for Resilience-Design for Resilience
- embracing constraints, Embrace Constraints-Embrace Constraints
- eventing, Eventing-Structure of an Event Message
- expecting externalization of services, Expect Externalization
- independently buildable services, Independently Buildable
- interactive documentation, Interactive Documentation
- languages, Languages
- metrics for, Metrics First
- performance improvement checklist, Performance Improvement Checklist
- platform design, On Platform Design-On Platform Design
- radical immutability in, Radical Immutability-Radical Immutability
- separating API from implementation, Separating API from Implementation
- service resources and representations, Service Resources and Representations
- specifications, Specifications-Specifications
- strategies and configurable services, Strategies and Configurable Services-Strategies and Configurable Services
- test automation, A Comment on Test Automation
- tools for, Design Stage
- versioning, deconstructed, Deconstructed Versioning-Deconstructed Versioning
- approaches, Approaches
- arborescent, Conceptual Tests, The Four Ideals
- Archer, L. Bruce, Exploring Design Thinking
- de Architectura (Vitruvius), Designers Are Producers of Concepts
- architecture
- architecture (software)
- architect, use of term, Software’s Conceptual Origins
- architects, role of, Creative Directors Across Industries
- architecture as non-necessary metaphor in technology, Software’s Conceptual Origins
- design thinking as context for applied architecting, The Method
- elements of, Comprehensive view practices
- forgetting the conceptual legacy of architecture, What’s In a Name?
- infrastructure considerations for architects, Considerations for Architects-Considerations for Architects
- origins of, Origins of Software Architecture-The Impact of Failures
- semantics and, Semantics and Software Architecture
- arts, semantic designer's background in, The Semantic Designer’s Role
- assumptions, RAID
- asynchronous operations, Scaling engines
- basic anatomy of asynchronous service components, Eventing
- publisher/subscriber or pub/sub, Eventing
- wise use of asynchronous calls, Eventing
- Athena, travel industry software based on (example), An Example
- attributes, Strategies for Semantic Data Modeling
- auditing, Auditing
- automatic retries, Design for Resilience
- automation, Stakeholder Diversity and Inside/Out
- autoscaling, Infrastructure Design and Documentation Checklist
- availability
- avoiding something, Accomplish, Avoid, Fix
- axiom of pairing, Relations
B
- becoming, Concept design practices
- behavior, driven by metrics, Define the Metrics
- Bernini sculpture The Ecstasy of Saint Teresa, Murals
- Bezos, Jeff, On Platform Design, Communicate Through Services
- binary oppositions, Introduction to Deconstruction, Chaos, Concept design practices
- Brooks, Fred, Simplexity
- budgeting and financial planning (for infrastructure in cloud environments), Considerations for Architects
- bulkheading, Design for Resilience
- business
- business context, elements of, Capturing the Business Strategy
- design that harmonizes business, application, and data, Give Intention and Use Value to Negative Space
- designing software to operate within, The Business Aspect
- platform as business framework, Platforms
- scalable business machine, designing, The Designed Scalable Business Machine-The Designed Scalable Business Machine
- semantic designer's understanding of, The Semantic Designer’s Role
- treating as a system and applying design principles to it, The Business Aspect-The Business Aspect
- writing business glossary, Create the Business Glossary, Business Glossary
- business architecture
- Business Design section, Design Definition Document, Design Definition Document
- business idea, Outlining Your Concept on the Concept Canvas
- Business Process Modeling Notation (BPMN), Reengineer Processes
- business processes, Business Processes
- business strategy, Outlining Your Concept on the Concept Canvas
- business system design
- creating business capabilities model, Create a Business Capabilities Model-Create a Business Capabilities Model
- creating organizational map, Create the Organizational Map
- creating process map, Create a Process Map
- creating the business glossary, Create the Business Glossary
- defining metrics for successful processes, Define the Metrics
- framework, introducing for, Framework Introduction-Scope of the Framework
- instituting appropriate process governance, Institute Appropriate Governance
- reengineering processes, Reengineer Processes-Reengineer Processes
- taking inventory of systems, Take Inventory of Systems
C
- cacheability, Cacheability and Idempotence
- cacheable URIs, API Guidelines
- caching
- capabilities, Design Definition Document
- capacity planning, Considerations for Architects
- Cassandra distributed database, Give Intention and Use Value to Negative Space, Polyglot Persistence, Peer-to-Peer Persistent Stores
- category mistakes, Copies and Creativity
- challenge idea tool, Lateral Thinking and Working with Concepts
- change management, Change Management-Change Management
- chaos engineering, Design for Failure, Chaos
- Chef, Infrastructure as Code
- chief semanticist, What’s In a Name?
- circuit breaking, Design for Resilience
- Claim Check pattern, Eventing
- clarification (in design thinking), Principles
- Clarks, Jonathan, Platforms
- classpath deployment and network proxies (data accessors), Classpath Deployment and Network Proxies
- clients
- cloud, Give Intention and Use Value to Negative Space
- clustering, Contextual Services and Service Mixins
- code coverage, Data Pipelines
- code reviews, Code Reviews-Code Reviews
- collaboration (in design thinking), Principles
- collections (on web APIs), Performance Improvement Checklist
- comments, A Comment on Comments-A Comment on Comments
- commodities, Software’s Conceptual Origins
- communication, semantic designer's skills in, The Semantic Designer’s Role
- compensation, Design for Resilience
- competition and innovation, Copies and Creativity
- complement, Relations
- complexity
- compliance map, Compliance Map
- comprehensive view, semantic design, The Four Ideals, Comprehensive view practices
- computers, prices of, Software’s Conceptual Origins
- computing, future of, What’s In a Name?
- Concept Canvas template, Outlining Your Concept on the Concept Canvas-Divergent and convergent thinking
- concept statement, Divergent and convergent thinking
- concepts, The Impact of Failures
- concept stage tools, Concept Stage
- conceptual tests, Conceptual Tests-Conceptual Tests
- design practices, Concept design practices
- designer of, Feature Engineering for Machine Learning
- designing, The Four Ideals
- extra-synthetic conceptual work in murals, Murals
- formal methods and innovative models for viewing, The Semantic Designer’s Role
- lateral thinking and, Lateral Thinking and Working with Concepts-Lateral Thinking and Working with Concepts
- organizing in mind maps, Mind Maps
- production of, Semantics and the Software Factory-Advantages of Semantic Design
- advantages of semantic design, Advantages of Semantic Design-Advantages of Semantic Design
- architecture and design, Semantics and the Software Factory
- context, Context-Context
- creative director in fashion, In Fashion
- defining a concept, What Is a Concept?-Divergent and convergent thinking
- designers as producers of concepts, Designers Are Producers of Concepts-Designing Concepts
- expressing the concept in a parti, The Concept Is Expressed in a Parti-The Parti Is Based on a Series of Reveals
- fit to purpose, Fit to Purpose
- ideas captured in a lookbook, Ideas Are Captured in a Lookbook-Ideas Are Captured in a Lookbook
- myth of requirements, The Myth of Requirements
- semantic field, The Semantic Field-The Semantic Field
- semantics and software architecture, Semantics and Software Architecture-Semantics and Software Architecture
- thinking in sets, Sets
- understanding ideas, Understanding Ideas-Metacognition
- configurable services, strategies and, Strategies and Configurable Services-Strategies and Configurable Services
- confirmation bias, Oblique Strategies
- constraints, Outlining Your Concept on the Concept Canvas, Divergent and convergent thinking, Design Definition Document
- content delivery networks (CDNs), Performance Improvement Checklist
- context, Context-Context, Advantages of Semantic Design
- continuous integration/continuous delivery (CI/CD) pipeline, Data Pipelines, DevOps
- conventions, Guidelines and Conventions-service-client
- convergent thinking, Divergent and convergent thinking
- Conway's Law, Service Resources and Representations, The Service-Oriented Organization
- copies and creativity, Copies and Creativity
- costs, Creative Directors Across Industries
- craftsmanship, Ideas Are Captured in a Lookbook
- creative artists in Poland, professions categorized as, Software’s Conceptual Origins
- creative directors, The Creative Director-What’s In a Name?
- creativity
- CSS and JavaScript files, combining and minifying, Performance Improvement Checklist
- culture, Change Management
- cUrl program, testing URIs, Cacheability and Idempotence
- currency conversions, Languages
- customer journey maps, Form insights, Murals, Thinking Stage
- customers
D
- D3 (see Design Definition Document)
- data, The Data Aspect-Summary
- Americans with Disabilities Act (ADA) compliance, ADA Compliance
- auditing, Auditing
- belonging to services, Communicate Through Services
- business glossary or data dictionary, Business Glossary
- classpath deployment and network proxies, Classpath Deployment and Network Proxies
- Data Design section, Design Definition Document, Design Definition Document
- data models for streams, Data Models for Streams-Data Models for Streams
- data pipelines, Data Pipelines-Data Pipelines
- feature engineering for machine learning, Feature Engineering for Machine Learning-Feature Engineering for Machine Learning
- graph databases, Graph Databases-OrientDB and Gremlin
- in service design checklist, Data
- machine learning data pipelines, Machine Learning Data Pipelines-Machine Learning Data Pipelines
- metadata and service metrics, Metadata and Service Metrics
- multimodeling, Multimodeling-Multimodeling
- no hierarchies or enums in data model, Decentered, deconstruction practices
- peer-to-peer persistent stores, Peer-to-Peer Persistent Stores
- polyglot persistence, Polyglot Persistence-Persistence Scorecard
- protection of, legal and regulatory requirements, Business Architecture in Applications
- semantic designer's skills and background in, The Semantic Designer’s Role
- strategies for semantic data modeling, Strategies for Semantic Data Modeling-Strategies for Semantic Data Modeling
- data accessor services, Data Accessors, Classpath Deployment and Network Proxies
- databases
- distinct data model per implementation and per service, Multimodeling
- graph, Graph Databases-OrientDB and Gremlin
- Java Database Connectivity (JDBC), Separating API from Implementation
- master/slave paradigm for scaling, Peer-to-Peer Persistent Stores
- NoSQL and other types of, Polyglot Persistence
- peer-to-peer, Peer-to-Peer Persistent Stores
- persistence scorecard for, Persistence Scorecard
- pipeline for, Data Pipelines
- relational, Polyglot Persistence
- tuning for web applications, Performance Improvement Checklist
- datacenters
- de Bono, Edward, Lateral Thinking and Working with Concepts
- dead metaphors, Software’s Conceptual Origins
- decision log (see parti template)
- decks, Presentations and Multiple Viewpoints
- decomposition, (De)composition-(De)composition
- deconstruction, Introduction to Deconstruction-Introduction to Deconstruction, Concept design practices
- applying to UIs, UI Packages
- binary oppositions, Chaos
- decentered, deconstruction practices, Decentered, deconstruction practices
- deconstructive analysis to make better software, Feature Engineering for Machine Learning
- design practices, Strategies and Configurable Services, Orchestrations, The Four Ideals, Operations and Governance
- in building architecture, Introduction to Deconstruction
- in popular culture, Introduction to Deconstruction
- relations of differences, Comprehensive view practices
- demos, Demos, Comprehensive view practices
- dependencies, RAID
- deployments
- Derrida, Jacques, Introduction to Deconstruction, Introduction to Deconstruction
- design, Semantics and the Software Factory
- books on, Architecture and Design Books
- design concept in Concept Canvas, Outlining Your Concept on the Concept Canvas
- design principles in semantic design, Design Principles-Design Principles
- design stage tools, Design Stage
- designers as producers of concepts, Designers Are Producers of Concepts
- designing business as well as software, The Business Aspect
- designing concepts, Designing Concepts
- designing for failures, Design for Failure
- designing for the programmer first, Start Opposite the User
- designing from multiple perspectives, Design from Multiple Perspectives
- framework for business system, Framework Introduction-Scope of the Framework
- giving design decisions at least two justifications, Give Design Decisions at Least Two Justifications
- harmonizing business, application, and data, Give Intention and Use Value to Negative Space
- infrastructure design checklist, Infrastructure Design and Documentation Checklist-Infrastructure Design and Documentation Checklist
- semantic designer's role, The Creative Director-The Semantic Designer’s Role
- service, Service Design
- Design Definition Document (D3), Design Definition Document-Considerations for Composing Your Design Definition, Comprehensive view practices
- design language, Design Language-Naming
- Design of Everyday Things, The (Norman), Affordance
- Design Patterns (Gang of Four), Software’s Conceptual Origins
- design thinking, Design Thinking-Summary, Concept design practices
- developers, practices helpful to, Stakeholder Diversity and Inside/Out
- development, DevOps
- development environment, matching closely to production environment, Radical Immutability
- DevOps, DevOps, Concept design practices
- important and consistent practices, DevOps
- principles making most difference to architects/designers, DevOps
- Dijkstra, Edsger, Software’s Conceptual Origins
- disappearing software in platforms, Disappearing
- disaster recovery, Considerations for Architects, Infrastructure Design and Documentation Checklist
- divergent thinking, Divergent and convergent thinking
- Docker, Infrastructure as Code
- documentation, Documentation
- domain, Metacognition, Relations
- Drucker, Peter, Creative Directors Across Industries, Change Management, Service Inventory and Metadata
E
- early adopters, Create personas
- Eclipse IDE, Give Intention and Use Value to Negative Space
- ecommerce product filter/criteria search, Specifications
- edges (in graph databases), Graph Databases
- embassy or quarantine, creating, Create a Quarantine or Embassy
- empty slogans, Design Principles
- engineering, Advantages of Semantic Design
- engines, Engines-Serverless
- Eno, Brian, Oblique Strategies
- Enterprise Integration Patterns (Hohpe and Woolf), Eventing
- entities (in relational databases), Polyglot Persistence
- environments, Infrastructure Design and Documentation Checklist
- epistemology, Semantics and Software Architecture
- errors, Errors
- essence, Sets
- essential complexity, Simplexity
- Evans, Eric, Specifications
- eventing, Eventing-Structure of an Event Message, Diversity of customer practices
- events, Eventing
- exception handling, Design for Resilience, Decentered, deconstruction practices
- executive producer, What’s In a Name?
- executive support, getting for your project, Presentations and Multiple Viewpoints
- experimentation (in design thinking), Principles
- extension, Sets
- externalization, expecting, Expect Externalization
- extreme users, Create personas
F
- Facade pattern, Classpath Deployment and Network Proxies
- failures
- false sectioning, Strategies for Semantic Data Modeling
- fashion, creative directors in, In Fashion
- FBI, Virtual Case File software application, The Impact of Failures
- feature engineering (machine learning), Feature Engineering for Machine Learning-Feature Engineering for Machine Learning
- feature flags (see feature toggles)
- feature toggles, The Production Multiverse and Feature Toggling-Multi-Armed Bandits: Machine Learning and Infinite Toggles
- figure and ground, Give Intention and Use Value to Negative Space
- Figure-Ground theory, Give Intention and Use Value to Negative Space
- film, creative directors in, In Film
- finance, data streaming for, Data Models for Streams
- fit to purpose, Fit to Purpose
- fixing something, Accomplish, Avoid, Fix
- focus tools, Lateral Thinking and Working with Concepts
- Ford, Henry, Copies and Creativity
- Ford, Tom, In Fashion
- Fowler, Martin, Specifications, Implementing Feature Toggles
- fractal within your structure, design thinking as, Implementing the Method
- frameworks, Strategy and Tooling
- functions
G
- gains, Murals
- Gang of Four, Software’s Conceptual Origins, Strategies and Configurable Services, Specifications
- Gartner, hype cycle, Position Papers
- Gehry, Frank, Fit to Purpose, The Parti Is Based on a Series of Reveals, Murals
- General Data Protection Regulation (GDPR), Business Architecture in Applications
- GitHub
- glossary (business), Create the Business Glossary, Business Glossary
- goals of users or personas in design thinking, Create personas
- God Object, Naming
- Google API Explorer, Service Resources and Representations
- Google Glass, prototype development, Try prototypes
- Google X Moonshot Thinking video, Ideas Are Captured in a Lookbook
- governance, Governance-Service Inventory and Metadata
- appropriate, instituting for processes, Institute Appropriate Governance
- creating simple Governance as Code, Chaos
- defining Governance as Code, Infrastructure as Code
- defining metrics for, Metrics
- goals for governance committee, Goals
- in undertaking a project, Design Definition Document
- service inventory and metadata, Service Inventory and Metadata
- service portfolio, Service Portfolio
- tools for, Operations and Governance
- graceful degradation, Design for Resilience
- graph databases, Graph Databases-OrientDB and Gremlin, Comprehensive view practices
- Gremlin, OrientDB and Gremlin, Chaos
- guidelines and conventions, Guidelines and Conventions-service-client
- GZip compression, using in web applications, Performance Improvement Checklist
H
- Hadoop, Design from Multiple Perspectives
- Halmos, Paul, Sets
- hardware, separation of software from, Software’s Conceptual Origins
- harvest tools, Lateral Thinking and Working with Concepts
- HashiCorp Terraform, Infrastructure as Code
- HashiCorp Vagrant, Infrastructure as Code
- HATEOAS (Hypermedia as the Engine of Application State), The Application Aspect
- health check function, Data Pipelines
- health checks on every service, Metrics First
- HealthCare.gov project (2013), The Impact of Failures
- Hegel, G.W.F., Sense Certainty
- Heroku, Infrastructure as Code
- HighScalability.com, Scaling engines
- Highsmith, Jim, Vision Box
- horizontal scaling, Scaling engines
- Hotbot search engine, Disappearing
- HTTP, idempotent methods, Cacheability and Idempotence
- HTTP/2, Design for Resilience
- human-centricity (design thinking), Principles
I
- IaC (see Infrastructure as Code)
- IBM Guidelines for Watson, API Guidelines
- idea components, Divergent and convergent thinking
- ideas
- idempotent services, ensuring, Cacheability and Idempotence
- IETF keywords, Considerations for Composing Your Design Definition
- images in web applications, Performance Improvement Checklist
- immutability, radical, Radical Immutability-Radical Immutability, Comprehensive view practices
- implementation, separating from API, Separating API from Implementation
- incidents, metrics for, Metrics First
- industrial process, making software in, Software’s Conceptual Origins
- infrastructure, The Infrastructure Aspect-Summary
- chaos engineering, Chaos-Chaos
- considerations for architects, Considerations for Architects-Considerations for Architects
- defining automated pipelines first, Automated Pipelines Also First
- defining metrics first, Metrics First-Compliance Map
- design and documentation checklist, Infrastructure Design and Documentation Checklist-Infrastructure Design and Documentation Checklist
- DevOps and, DevOps
- Infrastructure Design section, Design Definition Document, Design Definition Document
- production multiverse and feature toggling, The Production Multiverse and Feature Toggling-Multi-Armed Bandits: Machine Learning and Infinite Toggles
- stakeholders, inside and outside, Stakeholder Diversity and Inside/Out
- Infrastructure as Code (IaC), Infrastructure as Code-Infrastructure as Code
- Infrastructure as Code pattern, Give Intention and Use Value to Negative Space, Data Pipelines
- innovation, Creative Directors Across Industries
- inputs (scalable business machine), The Designed Scalable Business Machine
- insights
- integrated development environments (IDEs)
- integration tests, The Production Multiverse and Feature Toggling
- intention and use value, giving to negative space, Give Intention and Use Value to Negative Space-Give Intention and Use Value to Negative Space
- interaction features, Feature Engineering for Machine Learning
- interactive documentation, Interactive Documentation
- internal consistency, testing concepts for, Conceptual Tests
- internationalization and localization
- Internet of Things (IoT), Decouple User Interfaces
- Interpreter pattern, Specifications
- intersection, Relations
- issues, RAID
L
- language
- latency, Design Definition Document, Design Definition Document
- lateral thinking, Lateral Thinking and Working with Concepts-Lateral Thinking and Working with Concepts, Conceptual Tests, Concept design practices
- leadership skills of semantic designers, The Semantic Designer’s Role
- Lean Six Sigma, Copies and Creativity
- legal and regulatory requirements, Design Definition Document, Business Architecture in Applications
- Levi Strauss, IT project (2008), The Impact of Failures
- licensing, Position Papers, The Production Multiverse and Feature Toggling
- Liu, Jason, Multi-Armed Bandits: Machine Learning and Infinite Toggles
- load balancers, Infrastructure Design and Documentation Checklist
- logging, Design for Resilience
- lookbook, Concept design practices
- lookup registry to support service discovery, Give Design Decisions at Least Two Justifications
- Lucidchart, Mind Maps
- lunar landing system, concept sketch of (parti example), The Concept Is Expressed in a Parti
M
- machine learning, Decentered, deconstruction practices
- major version change, Deconstructed Versioning
- Malkovich, John, Ideas Are Captured in a Lookbook
- managed components, Stakeholder Diversity and Inside/Out
- management, governance, and operations
- MapReduce algorithm, Design from Multiple Perspectives
- marketing, The Semantic Designer’s Role, Creative Directors Across Industries
- Marx, Karl, Semantics and the Software Factory
- master/slave databases, Peer-to-Peer Persistent Stores
- mean time between failures (MTBF), Metrics First
- mean time to recovery (MTTR), Metrics First
- MECE (mutually exclusive and collectively exhaustive) approaches, Approaches
- media streaming services and video games, Data Models for Streams
- meta-models, In Technology
- metacognition, What Is a Concept?, Metacognition-Metacognition
- metaphors, Software’s Conceptual Origins
- metrics, Murals
- Michelangelo, Understanding Ideas
- Microsoft for API design, API Guidelines
- mind maps, Mind Maps
- minor version change, Deconstructed Versioning
- mixins (service), Contextual Services and Service Mixins-Contextual Services and Service Mixins
- modeling data
- modernization, managing as a program, Managing Modernization as a Program
- monitoring, Start Opposite the User, Design for Resilience, Stakeholder Diversity and Inside/Out
- monolithic applications, The Production Multiverse and Feature Toggling
- movies, creative directors, In Film
- multi-armed bandits, Multi-Armed Bandits: Machine Learning and Infinite Toggles
- murals, Murals-Murals
N
- Naive Set Theory (Halmos), Sets
- naming, Naming
- National Institute of Standards and Technology (NIST), report on software testing, Conceptual Tests
- NATO Software Engineering conference (1968), Software’s Conceptual Origins
- need, statement of, Divergent and convergent thinking, Define the problem
- negative space, giving intention and use value to, Give Intention and Use Value to Negative Space-Give Intention and Use Value to Negative Space
- Neo4J graph database, Graph Databases
- .NET, Structure of an Event Message
- Netflix
- network proxies, classpath deployment and, Classpath Deployment and Network Proxies
- network stability problems, creating, Chaos
- nodes
- nontrivial problems, Context
- Norman, Donald, Affordance
- Norton, Peter, Oblique Strategies
- NoSQL databases, Polyglot Persistence
- notifications, Design for Resilience
O
- Object Management Group (OMG), Capturing the Business Strategy
- object-oriented (OO) design, SOLID principles, The Service-Oriented Organization
- Oblique Strategies, Oblique Strategies, Concept design practices
- oblique strategies website, Oblique Strategies
- observations in design thinking, Make observations
- open source, Opening
- Open Web Application Security Project (OWASP), Expect Externalization
- operating systems, Infrastructure Design and Documentation Checklist
- operational scorecard, The Operational Scorecard-The Operational Scorecard
- operations, DevOps
- opportunities, framing in design thinking, Frame opportunities, Implementing the Method
- opposites, Introduction to Deconstruction, Chaos, Concept design practices
- orchestrations, Orchestrations
- organizations
- OrientDB, OrientDB and Gremlin
- outcomes, Murals
- outputs (scalable business machine), The Designed Scalable Business Machine
P
- package manager, universal, Radical Immutability
- pains, Murals
- pair designing, Pair Designing-Pair Designing
- pairing, axiom of, Relations
- parti pris, The Concept Is Expressed in a Parti
- parti template
- path forward, Divergent and convergent thinking
- peer-to-peer persistent stores, Peer-to-Peer Persistent Stores, Decentered, deconstruction practices
- penetration tests, The Production Multiverse and Feature Toggling
- performance
- performance tests, The Production Multiverse and Feature Toggling
- persistence, polyglot, Polyglot Persistence-Persistence Scorecard, Diversity of customer practices
- personalization, Multi-Armed Bandits: Machine Learning and Infinite Toggles
- (see also feature toggles)
- personas, Murals, Thinking Stage
- philosophical/analytical thinking, The Semantic Designer’s Role
- philosophy, books on, Philosophy Books-Philosophy Books
- picture-thinking, Sense Certainty
- pitch decks, Presentations and Multiple Viewpoints
- Platform as a Service (PaaS), Heroku tool, Infrastructure as Code
- platforms, Platforms-Disappearing
- Poland, software developers in, Software’s Conceptual Origins
- position papers, Position Papers
- power grids, Data Models for Streams
- Prada, Miuccia, In Fashion
- presentations, Presentations and Multiple Viewpoints
- principles, The Designed Scalable Business Machine
- problems
- processes
- business processes in service design checklist, Business Processes
- capabilities versus, Create a Business Capabilities Model
- creating process map, Create a Process Map
- in design of software, Copies and Creativity
- in scalable business machine, The Designed Scalable Business Machine
- instituting appropriate governance for, Institute Appropriate Governance
- process in design thinking, Principles
- reengineering in a business, Reengineer Processes-Reengineer Processes
- repeatable, for making copies, Copies and Creativity
- studying from outside your industry, Strategy and Tooling
- successful, defining metrics for, Define the Metrics
- producers (theatrical), What’s In a Name?
- product vision box, Vision Box
- production
- production environment, matching closely with development environment, Radical Immutability
- programming languages, On Platform Design, Strategy and Tooling
- properties (in graph databases), Graph Databases
- propositions, The Semantic Field
- protocols, Approaches, On Platform Design
- prototypes, Try prototypes, Implementing the Method
- provocation, Lateral Thinking and Working with Concepts
- Proxy pattern, Classpath Deployment and Network Proxies
- publisher/subscriber (pub/sub), Eventing
- Puppet, Infrastructure as Code
- push notifications, Design for Resilience
- Python, Position Papers, Structure of an Event Message, A Comment on Comments
R
- radical immutability (see immutability, radical)
- RAID document, RAID
- Raiders of the Lost Ark (movie), In Film
- random inputs, Lateral Thinking and Working with Concepts
- range, Relations
- rate limiting, Design for Resilience
- reading further, resources for, Further Reading-Software Books
- recovery
- reflexive, Relations
- regulatory requirements, Design Definition Document, Business Architecture in Applications
- relational databases, Polyglot Persistence
- relations, Relations, Strategies for Semantic Data Modeling
- representations and resources (services), Service Resources and Representations-Domain Language
- requests
- requirements, Advantages of Semantic Design
- resilience, Design Definition Document
- resilience4j, Design for Resilience
- resources
- response caching, Design for Resilience
- REST
- retries (automatic), Design for Resilience
- reveals, parti based on, The Parti Is Based on a Series of Reveals
- reversal method, Lateral Thinking and Working with Concepts
- rhizomatic, The Production Multiverse and Feature Toggling, Conceptual Tests, The Four Ideals
- risks
- roles
S
- scalability
- scalable business machine (SBM), designing, The Designed Scalable Business Machine-The Designed Scalable Business Machine
- scaling infrastructure, Infrastructure Design and Documentation Checklist
- Schmidt, Peter, Oblique Strategies
- science, software design and, Copies and Creativity
- search
- security
- security groups, Infrastructure Design and Documentation Checklist
- semantic design manifesto, The Semantic Design Manifesto-Opening
- semantic design toolbox, The Tools-Operations and Governance
- semantic designer's role, The Semantic Designer’s Role-The Semantic Designer’s Role
- semantic field, Semantics and Software Architecture
- semantic software design, Semantics and Software Architecture
- advantages of, Advantages of Semantic Design-Advantages of Semantic Design
- architects as producers and designers of concepts, Divergent and convergent thinking
- practices and artifacts, Semantic Design Practices and Artifacts-Summary
- approaches, Approaches
- design principles, Design Principles-Design Principles
- guidelines and conventions, Guidelines and Conventions-service-client
- mind maps, Mind Maps
- murals, Murals-Murals
- pair designing, Pair Designing-Pair Designing
- position papers, Position Papers
- presentations and multiple viewpoints, Presentations and Multiple Viewpoints
- RAID document, RAID
- use cases, Use Cases
- vision box, Vision Box
- steps in the process, Semantics and Software Architecture
- semantics and software architecture, Semantics and Software Architecture
- sense-certainty, Sense Certainty
- served versus servant spaces, Design Language
- serverless, Serverless
- service discovery, lookup registry to support, Give Design Decisions at Least Two Justifications
- service-oriented organizations, The Service-Oriented Organization-Cross-Functional Teams
- services, The Application Aspect
- (see also applications)
- anatomy of, Anatomy of a Service-Data Accessors
- application-specific, Application-Specific Services
- communication through, Communicate Through Services
- diagram or sketch outlining services provided by your platform, The Service-Oriented Organization
- health checks, Metrics First
- independently buildable, Independently Buildable
- latency per service, Metrics First
- metrics for, Metadata and Service Metrics
- platform design and, On Platform Design-On Platform Design
- resources and representations, Service Resources and Representations-Domain Language
- service API, service-api
- service client, service-client
- service design checklist, Service Design Checklist
- availability and support, Availability and Support
- data, Data
- deployment, Deployment
- documentation, Documentation
- errors, Errors
- performance, Performance
- quality assurance, Quality Assurance
- security, Security
- service design, Service Design
- service operations, Service Operations
- service implementation, service-impl
- service inventory and metadata, Service Inventory and Metadata
- service portfolio, Service Portfolio
- service-oriented development, DevOps
- sets, Sets
- showing, not telling, in design thinking, Principles
- significance, Strategies for Semantic Data Modeling
- simian army, Chaos
- simplicity, Context, Simplexity
- single responsibility principle, Concept design practices
- Six Sigma Handbook, The (Keller), Reengineer Processes
- slogans, empty, Design Principles
- SMART goals, Copies and Creativity
- smartphones as platforms, Platforms
- social media, Data Models for Streams
- software
- software engineering, Software’s Conceptual Origins
- software projects
- solutions
- specifications, Specifications-Specifications
- Spielberg, Steven, In Film
- staging environment, The Production Multiverse and Feature Toggling
- stakeholders
- state
- statement of need, Divergent and convergent thinking, Define the problem
- strategies, Concept design practices
- Strategy pattern, Strategies and Configurable Services, Specifications
- streams, data models for, Data Models for Streams-Data Models for Streams
- strings
- structuralism, Introduction to Deconstruction
- "Structure, Sign, and Play" (Derrida), Introduction to Deconstruction
- success, defining in design thinking, Define the problem
- support for services, Availability and Support
- support functions, Creative Directors Across Industries
- Swagger documentation, Interactive Documentation
- symmetric, Relations
- Systematic Method for Designers (Archer), Exploring Design Thinking
- systems, The Business Aspect
T
- tactical demands, aligning with strategic objectives, Align Strategic Objectives and Tactical Demands-Align Strategic Objectives and Tactical Demands
- teaching/mentoring ability, The Semantic Designer’s Role
- teams
- technologies, semantic designer's skills in, The Semantic Designer’s Role
- technology strategy, Outlining Your Concept on the Concept Canvas
- Technology Strategy Patterns (Hewitt), Designers Are Producers of Concepts
- technology, creative directors in, In Technology
- templates
- terms of art, Create the Business Glossary
- Terraform, Infrastructure as Code
- test-driven development (TDD), A Comment on Test Automation
- testing
- The Ecstasy of Saint Teresa (Bernini), Murals
- The Open Group Architecture Framework (TOGAF), Design Principles
- theater, artistic directors in, In Theater
- thinking, Why Design Thinking?
- thinking hats, Lateral Thinking and Working with Concepts
- ThoughtWorks Radar, Position Papers, Strategy and Tooling
- tools (scalable business machine), The Designed Scalable Business Machine
- tools, selection of, Strategy and Tooling-Strategy and Tooling
- traffic, Infrastructure Design and Documentation Checklist
- transitive, Relations
- translate.google.com , Languages
- translations.com, Languages
- treatment tools, Lateral Thinking and Working with Concepts
- true and false values, Strategies for Semantic Data Modeling
- Twitter API, Service Resources and Representations
- type, problem with the term, Strategies for Semantic Data Modeling
U
- UIs (user interfaces)
- Unified Modeling Language (UML) diagrams, Use Cases
- union, Relations
- unit tests, The Production Multiverse and Feature Toggling
- URIs
- use cases, Use Cases
- use value and intention, giving to negative space, Give Intention and Use Value to Negative Space-Give Intention and Use Value to Negative Space
- use value, questioning, Observe users’ actions
- user acceptance testing, A Comment on Test Automation
- user interfaces (see UIs)
- users, Start Opposite the User
- utilities, Utils
V
- Vagrant, Infrastructure as Code
- value
- Value Proposition Design (Osterwalder et al.), Create personas
- variants, Context
- versioning, Deconstructed Versioning-Deconstructed Versioning
- vertical scaling, Scaling engines
- vertical thinking versus lateral thinking, Lateral Thinking and Working with Concepts
- video games, creative directors, In Video Games
- viewpoints, multiple, Presentations and Multiple Viewpoints
- virtualization, Infrastructure Design and Documentation Checklist
- vision box, Vision Box
- Vitruvius, Designers Are Producers of Concepts
W
- waterfall, Advantages of Semantic Design
- Web Content Accessibility Guidelines 2.0 (WCAG), ADA Compliance
- web ecommerce clickstreams, Data Models for Streams
- WebSockets, Design for Resilience
- words, testing, interrogating, and challenging, Strategies for Semantic Data Modeling
- workflow, drawing out, Orchestrations
..................Content has been hidden....................
You can't read the all page of ebook, please click
here login for view all page.