Semantic Software Design. A New Theory and Practical Guide for Modern Architects - Helion

ebook

Autor: Eben Hewitt
ISBN: 978-14-920-4590-8
stron: 334, Format: ebook
Data wydania: 2019-09-25
Księgarnia: Helion

Cena książki: 160,65 zł (poprzednio: 186,80 zł)
Oszczędzasz: 14% (-26,15 zł)

Osoby, które kupiły tę książkę, wybierały także »

Tagi: Inne - Programowanie

With this practical book, architects, CTOs, and CIOs will learn a set of patterns for the practice of architecture, including analysis, documentation, and communication. Author Eben Hewitt shows you how to create holistic and thoughtful technology plans, communicate them clearly, lead people toward the vision, and become a great architect or Chief Architect.

This book covers each key aspect of architecture comprehensively, including how to incorporate business architecture, information architecture, data architecture, application (software) architecture together to have the best chance for the system’s success.

Get a practical set of proven architecture practices focused on shipping great products using architecture
Learn how architecture works effectively with development teams, management, and product management teams through the value chain
Find updated special coverage on machine learning architecture
Get usable templates to start incorporating into your teams immediately
Incorporate business architecture, information architecture, data architecture, and application (software) architecture together

Osoby które kupowały "Semantic Software Design. A New Theory and Practical Guide for Modern Architects", wybierały także:

Superinteligencja. Scenariusze, strategie, zagro 66,67 zł, (14,00 zł -79%)
Poradnik design thinking - czyli jak wykorzysta 48,28 zł, (14,00 zł -71%)
Kosymulacja. Elastyczne projektowanie i symulacja wielodomenowa 38,39 zł, (11,90 zł -69%)
F# 4.0 dla zaawansowanych. Wydanie IV 96,45 zł, (29,90 zł -69%)
Systemy reaktywne. Wzorce projektowe i ich stosowanie 65,31 zł, (20,90 zł -68%)

Spis treści

Semantic Software Design. A New Theory and Practical Guide for Modern Architects eBook -- spis treści

Preface
- Conventions Used in This Book
- Using Code Examples
- OReilly Online Learning
- How to Contact Us
- Acknowledgments
I. Episteme: The Philosophy of Design
1. Origins of Software Architecture
- Softwares Conceptual Origins
- Copies and Creativity
- Why Software Projects Fail
- The Impact of Failures
2. The Production of Concepts
- Semantics and the Software Factory
- The Myth of Requirements
- Semantics and Software Architecture
- The Semantic Field
- Designers Are Producers of Concepts
  - Designing Concepts
- What Is a Concept?
  - Accomplish, Avoid, Fix
  - Outlining Your Concept on the Concept Canvas
    - Divergent and convergent thinking
- Ideas Are Captured in a Lookbook
- Fit to Purpose
- The Concept Is Expressed in a Parti
  - An Example
  - Adding Aspects to the Parti
  - The Parti Is Based on a Series of Reveals
- Understanding Ideas
  - Sense Certainty
  - Metacognition
- Context
- Sets
  - Relations
- Advantages of Semantic Design
3. Deconstruction and Design
- Introduction to Deconstruction
- Simplexity
- (De)composition
- Affordance
- Give Intention and Use Value to Negative Space
- Give Design Decisions at Least Two Justifications
- Design from Multiple Perspectives
- Create a Quarantine or Embassy
- Design for Failure
- Design Language
  - Naming
- Start Opposite the User
- Platforms
  - Disappearing
II. Semantic Design in Practice
4. Design Thinking
- Why Design Thinking?
- Exploring Design Thinking
  - Principles
  - The Method
    - Define the problem
    - Make observations
      - Determine the users
      - Observe users actions
      - Create personas
    - Form insights
    - Frame opportunities
    - Generate ideas and refine solutions
    - Try prototypes
- Implementing the Method
- Summary
5. Semantic Design Practices and Artifacts
- Design Principles
- Pair Designing
- Murals
- Vision Box
- Mind Maps
- Use Cases
- Guidelines and Conventions
  - Utils
  - Domain
  - service-api
  - service-impl
  - service-client
- Approaches
- Design Definition Document
  - Considerations for Composing Your Design Definition
- Position Papers
- RAID
- Presentations and Multiple Viewpoints
- Summary
6. The Business Aspect
- Capturing the Business Strategy
  - Provide a Common Understanding
  - Align Strategic Objectives and Tactical Demands
- Framework Introduction
  - Scope of the Framework
- Create the Business Glossary
- Create the Organizational Map
- Create a Business Capabilities Model
- Create a Process Map
- Reengineer Processes
- Take Inventory of Systems
- Define the Metrics
- Institute Appropriate Governance
- Business Architecture in Applications
- Summary
7. The Application Aspect
- Embrace Constraints
- Decouple User Interfaces
  - UI Packages
- On Platform Design
- Service Resources and Representations
  - Domain Language
- API Guidelines
- Deconstructed Versioning
- Cacheability and Idempotence
- Independently Buildable
- Strategies and Configurable Services
- Application-Specific Services
- Communicate Through Services
- Expect Externalization
- Design for Resilience
- Interactive Documentation
- Anatomy of a Service
  - UI Packages
  - Orchestrations
  - Engines
    - Make engines stateless
    - Scaling engines
    - Serverless
  - Data Accessors
- Eventing
  - Structure of an Event Message
- Contextual Services and Service Mixins
- Performance Improvement Checklist
- Separating API from Implementation
- Languages
- Radical Immutability
- Specifications
- A Comment on Test Automation
- A Comment on Comments
- Summary
8. The Data Aspect
- Business Glossary
- Strategies for Semantic Data Modeling
- Polyglot Persistence
  - Persistence Scorecard
- Multimodeling
- Data Models for Streams
- Feature Engineering for Machine Learning
- Classpath Deployment and Network Proxies
- Peer-to-Peer Persistent Stores
- Graph Databases
  - OrientDB and Gremlin
- Data Pipelines
- Machine Learning Data Pipelines
- Metadata and Service Metrics
- Auditing
- ADA Compliance
- Summary
9. The Infrastructure Aspect
- Considerations for Architects
- DevOps
- Infrastructure as Code
- Metrics First
  - Compliance Map
- Automated Pipelines Also First
- The Production Multiverse and Feature Toggling
  - Implementing Feature Toggles
  - Multi-Armed Bandits: Machine Learning and Infinite Toggles
- Infrastructure Design and Documentation Checklist
- Chaos
- Stakeholder Diversity and Inside/Out
- Summary
III. Operations, Process, and Management
10. The Creative Director
- The Semantic Designers Role
- Creative Directors Across Industries
  - In Fashion
  - In Film
  - In Video Games
  - In Advertising
  - In Theater
  - In Technology
  - Whats In a Name?
11. Management, Governance, Operations
- Strategy and Tooling
- Oblique Strategies
- Lateral Thinking and Working with Concepts
- Conceptual Tests
- Code Reviews
- Demos
- The Operational Scorecard
- The Service-Oriented Organization
  - Cross-Functional Teams
- The Designed Scalable Business Machine
- Managing Modernization as a Program
- Change Management
- Governance
  - Goals
  - Metrics
  - Service Portfolio
  - Service Inventory and Metadata
- Service Design Checklist
  - Service Design
  - Service Operations
  - Business Processes
  - Data
  - Errors
  - Performance
  - Security
  - Quality Assurance
  - Availability and Support
  - Deployment
  - Documentation
- Further Reading on Organizational Design
12. The Semantic Design Manifesto
- The Manifesto
  - The Four Ideals
  - The Key Practices
    - Concept design practices
    - Comprehensive view practices
    - Decentered, deconstruction practices
    - Diversity of customer practices
  - Opening
A. The Semantic Design Toolbox
- The Tools
  - Thinking Stage
  - Concept Stage
  - Design Stage
  - Operations and Governance
B. Further Reading
- Architecture and Design Books
- Philosophy Books
- Software Books
Index