book

Semantic Software Design

by Eben Hewitt

October 2019

Intermediate to advanced

331 pages

9h 33m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Conventions Used in This BookUsing Code ExamplesO’Reilly Online LearningHow to Contact UsAcknowledgments
Software’s Conceptual OriginsCopies and CreativityWhy Software Projects FailThe Impact of Failures
Semantics and the Software FactoryThe Myth of RequirementsSemantics and Software ArchitectureThe Semantic FieldDesigners Are Producers of ConceptsDesigning ConceptsWhat Is a Concept?Accomplish, Avoid, FixOutlining Your Concept on the Concept CanvasIdeas Are Captured in a LookbookFit to PurposeThe Concept Is Expressed in a PartiAn ExampleAdding Aspects to the PartiThe Parti Is Based on a Series of RevealsUnderstanding IdeasSense CertaintyMetacognitionContextSetsRelationsAdvantages of Semantic Design
Introduction to DeconstructionSimplexity(De)compositionAffordanceGive Intention and Use Value to Negative SpaceGive Design Decisions at Least Two JustificationsDesign from Multiple PerspectivesCreate a Quarantine or EmbassyDesign for FailureDesign LanguageNamingStart Opposite the UserPlatformsDisappearing
Why Design Thinking?Exploring Design ThinkingPrinciplesThe MethodImplementing the MethodSummary
Design PrinciplesPair DesigningMuralsVision BoxMind MapsUse CasesGuidelines and ConventionsUtilsDomainservice-apiservice-implservice-clientApproachesDesign Definition DocumentConsiderations for Composing Your Design DefinitionPosition PapersRAIDPresentations and Multiple ViewpointsSummary
Capturing the Business StrategyProvide a Common UnderstandingAlign Strategic Objectives and Tactical DemandsFramework IntroductionScope of the FrameworkCreate the Business GlossaryCreate the Organizational MapCreate a Business Capabilities ModelCreate a Process MapReengineer ProcessesTake Inventory of SystemsDefine the MetricsInstitute Appropriate GovernanceBusiness Architecture in ApplicationsSummary
Embrace ConstraintsDecouple User InterfacesUI PackagesOn Platform DesignService Resources and RepresentationsDomain LanguageAPI GuidelinesDeconstructed VersioningCacheability and IdempotenceIndependently BuildableStrategies and Configurable ServicesApplication-Specific ServicesCommunicate Through ServicesExpect ExternalizationDesign for ResilienceInteractive DocumentationAnatomy of a ServiceUI PackagesOrchestrationsEnginesData AccessorsEventingStructure of an Event MessageContextual Services and Service MixinsPerformance Improvement ChecklistSeparating API from ImplementationLanguagesRadical ImmutabilitySpecificationsA Comment on Test AutomationA Comment on CommentsSummary

Business GlossaryStrategies for Semantic Data ModelingPolyglot PersistencePersistence ScorecardMultimodelingData Models for StreamsFeature Engineering for Machine LearningClasspath Deployment and Network ProxiesPeer-to-Peer Persistent StoresGraph DatabasesOrientDB and GremlinData PipelinesMachine Learning Data PipelinesMetadata and Service MetricsAuditingADA ComplianceSummary
Considerations for ArchitectsDevOpsInfrastructure as CodeMetrics FirstCompliance MapAutomated Pipelines Also FirstThe Production Multiverse and Feature TogglingImplementing Feature TogglesMulti-Armed Bandits: Machine Learning and Infinite TogglesInfrastructure Design and Documentation ChecklistChaosStakeholder Diversity and Inside/OutSummary
The Semantic Designer’s RoleCreative Directors Across IndustriesIn FashionIn FilmIn Video GamesIn AdvertisingIn TheaterIn TechnologyWhat’s In a Name?
Strategy and ToolingOblique StrategiesLateral Thinking and Working with ConceptsConceptual TestsCode ReviewsDemosThe Operational ScorecardThe Service-Oriented OrganizationCross-Functional TeamsThe Designed Scalable Business MachineManaging Modernization as a ProgramChange ManagementGovernanceGoalsMetricsService PortfolioService Inventory and MetadataService Design ChecklistService DesignService OperationsBusiness ProcessesDataErrorsPerformanceSecurityQuality AssuranceAvailability and SupportDeploymentDocumentationFurther Reading on Organizational Design
The ManifestoThe Four IdealsThe Key PracticesOpening
The ToolsThinking StageConcept StageDesign StageOperations and Governance
Architecture and Design BooksPhilosophy BooksSoftware Books

Content preview from Semantic Software Design

Part I. Episteme: The Philosophy of Design

In everything, there is a share of everything.

Anaxagoras

In this part, we explore the figure of design itself. We examine in new light how our work designing software came to be shaped, and challenge some received views in our industry. We reimagine architecture as the work of creating concepts, and see how to express those concepts working with teams to create effective software designs.