Semantic software design: a new theory and practical guide for modern architects
Saved in:
| Main Author: | |
|---|---|
| Format: | Electronic eBook |
| Language: | English |
| Published: |
Beijing
O'Reilly
2019
|
| Subjects: | |
| Online Access: | FHD01 |
| Item Description: | Performance Improvement Checklist |
| Physical Description: | 1 Online-Ressource (xiii, 316 Seiten) |
| ISBN: | 9781492045908 |
Staff View
MARC
| LEADER | 00000nmm a2200000 c 4500 | ||
|---|---|---|---|
| 001 | BV046228668 | ||
| 003 | DE-604 | ||
| 005 | 20191118 | ||
| 007 | cr|uuu---uuuuu | ||
| 008 | 191104s2019 |||| o||u| ||||||eng d | ||
| 020 | |a 9781492045908 |9 978-1-492-04590-8 | ||
| 035 | |a (OCoLC)1126557778 | ||
| 035 | |a (DE-599)BVBBV046228668 | ||
| 040 | |a DE-604 |b ger |e rda | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-1050 | ||
| 084 | |a ST 230 |0 (DE-625)143617: |2 rvk | ||
| 100 | 1 | |a Hewitt, Eben |e Verfasser |0 (DE-588)1199903752 |4 aut | |
| 245 | 1 | 0 | |a Semantic software design |b a new theory and practical guide for modern architects |c Eben Hewitt |
| 264 | 1 | |a Beijing |b O'Reilly |c 2019 | |
| 300 | |a 1 Online-Ressource (xiii, 316 Seiten) | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b c |2 rdamedia | ||
| 338 | |b cr |2 rdacarrier | ||
| 500 | |a Performance Improvement Checklist | ||
| 505 | 8 | |a Intro; Copyright; Table of Contents; Preface; Conventions Used in This Book; Using Code Examples; O'Reilly Online Learning; How to Contact Us; Acknowledgments; Part I. Episteme: The Philosophy of Design; Chapter 1. Origins of Software Architecture; Software's Conceptual Origins; Copies and Creativity; Why Software Projects Fail; The Impact of Failures; Chapter 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? | |
| 505 | 8 | |a Accomplish, Avoid, FixOutlining Your Concept on the Concept Canvas; 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; Chapter 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 | |
| 505 | 8 | |a Create a Quarantine or EmbassyDesign for Failure; Design Language; Naming; Start Opposite the User; Platforms; Disappearing; Part II. Semantic Design in Practice; Chapter 4. Design Thinking; Why Design Thinking?; Exploring Design Thinking; Principles; The Method; Implementing the Method; Summary; Chapter 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 | |
| 505 | 8 | |a Considerations for Composing Your Design DefinitionPosition Papers; RAID; Presentations and Multiple Viewpoints; Summary; Chapter 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 | |
| 505 | 8 | |a Chapter 7. The Application AspectEmbrace 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; Data Accessors; Eventing; Structure of an Event Message; Contextual Services and Service Mixins | |
| 650 | 4 | |a Computer software / Development / Management | |
| 650 | 4 | |a Software architecture | |
| 650 | 0 | 7 | |a Softwarearchitektur |0 (DE-588)4121677-5 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Softwareentwicklung |0 (DE-588)4116522-6 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Softwarearchitektur |0 (DE-588)4121677-5 |D s |
| 689 | 0 | 1 | |a Softwareentwicklung |0 (DE-588)4116522-6 |D s |
| 689 | 0 | |8 1\p |5 DE-604 | |
| 776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe |z 978-1-492-04595-3 |
| 912 | |a ZDB-30-PQE | ||
| 999 | |a oai:aleph.bib-bvb.de:BVB01-031607184 | ||
| 883 | 1 | |8 1\p |a cgwrk |d 20201028 |q DE-101 |u https://d-nb.info/provenance/plan#cgwrk | |
| 966 | e | |u https://ebookcentral.proquest.com/lib/th-deggendorf/detail.action?docID=5904662 |l FHD01 |p ZDB-30-PQE |q FHD01_PQE_Kauf |x Aggregator |3 Volltext | |
Record in the Search Index
| _version_ | 1804180636386197504 |
|---|---|
| any_adam_object | |
| author | Hewitt, Eben |
| author_GND | (DE-588)1199903752 |
| author_facet | Hewitt, Eben |
| author_role | aut |
| author_sort | Hewitt, Eben |
| author_variant | e h eh |
| building | Verbundindex |
| bvnumber | BV046228668 |
| classification_rvk | ST 230 |
| collection | ZDB-30-PQE |
| contents | Intro; Copyright; Table of Contents; Preface; Conventions Used in This Book; Using Code Examples; O'Reilly Online Learning; How to Contact Us; Acknowledgments; Part I. Episteme: The Philosophy of Design; Chapter 1. Origins of Software Architecture; Software's Conceptual Origins; Copies and Creativity; Why Software Projects Fail; The Impact of Failures; Chapter 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, FixOutlining Your Concept on the Concept Canvas; 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; Chapter 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 EmbassyDesign for Failure; Design Language; Naming; Start Opposite the User; Platforms; Disappearing; Part II. Semantic Design in Practice; Chapter 4. Design Thinking; Why Design Thinking?; Exploring Design Thinking; Principles; The Method; Implementing the Method; Summary; Chapter 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 DefinitionPosition Papers; RAID; Presentations and Multiple Viewpoints; Summary; Chapter 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 Chapter 7. The Application AspectEmbrace 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; Data Accessors; Eventing; Structure of an Event Message; Contextual Services and Service Mixins |
| ctrlnum | (OCoLC)1126557778 (DE-599)BVBBV046228668 |
| discipline | Informatik |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>04599nmm a2200469 c 4500</leader><controlfield tag="001">BV046228668</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20191118 </controlfield><controlfield tag="007">cr|uuu---uuuuu</controlfield><controlfield tag="008">191104s2019 |||| o||u| ||||||eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781492045908</subfield><subfield code="9">978-1-492-04590-8</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)1126557778</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV046228668</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-1050</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 230</subfield><subfield code="0">(DE-625)143617:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Hewitt, Eben</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)1199903752</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Semantic software design</subfield><subfield code="b">a new theory and practical guide for modern architects</subfield><subfield code="c">Eben Hewitt</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Beijing</subfield><subfield code="b">O'Reilly</subfield><subfield code="c">2019</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource (xiii, 316 Seiten)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Performance Improvement Checklist</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Intro; Copyright; Table of Contents; Preface; Conventions Used in This Book; Using Code Examples; O'Reilly Online Learning; How to Contact Us; Acknowledgments; Part I. Episteme: The Philosophy of Design; Chapter 1. Origins of Software Architecture; Software's Conceptual Origins; Copies and Creativity; Why Software Projects Fail; The Impact of Failures; Chapter 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?</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Accomplish, Avoid, FixOutlining Your Concept on the Concept Canvas; 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; Chapter 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</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Create a Quarantine or EmbassyDesign for Failure; Design Language; Naming; Start Opposite the User; Platforms; Disappearing; Part II. Semantic Design in Practice; Chapter 4. Design Thinking; Why Design Thinking?; Exploring Design Thinking; Principles; The Method; Implementing the Method; Summary; Chapter 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</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Considerations for Composing Your Design DefinitionPosition Papers; RAID; Presentations and Multiple Viewpoints; Summary; Chapter 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</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Chapter 7. The Application AspectEmbrace 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; Data Accessors; Eventing; Structure of an Event Message; Contextual Services and Service Mixins</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer software / Development / Management</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software architecture</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Softwarearchitektur</subfield><subfield code="0">(DE-588)4121677-5</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Softwarearchitektur</subfield><subfield code="0">(DE-588)4121677-5</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="8">1\p</subfield><subfield code="5">DE-604</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druck-Ausgabe</subfield><subfield code="z">978-1-492-04595-3</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-PQE</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-031607184</subfield></datafield><datafield tag="883" ind1="1" ind2=" "><subfield code="8">1\p</subfield><subfield code="a">cgwrk</subfield><subfield code="d">20201028</subfield><subfield code="q">DE-101</subfield><subfield code="u">https://d-nb.info/provenance/plan#cgwrk</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">https://ebookcentral.proquest.com/lib/th-deggendorf/detail.action?docID=5904662</subfield><subfield code="l">FHD01</subfield><subfield code="p">ZDB-30-PQE</subfield><subfield code="q">FHD01_PQE_Kauf</subfield><subfield code="x">Aggregator</subfield><subfield code="3">Volltext</subfield></datafield></record></collection> |
| id | DE-604.BV046228668 |
| illustrated | Not Illustrated |
| indexdate | 2024-07-10T08:38:55Z |
| institution | BVB |
| isbn | 9781492045908 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-031607184 |
| oclc_num | 1126557778 |
| open_access_boolean | |
| owner | DE-1050 |
| owner_facet | DE-1050 |
| physical | 1 Online-Ressource (xiii, 316 Seiten) |
| psigel | ZDB-30-PQE ZDB-30-PQE FHD01_PQE_Kauf |
| publishDate | 2019 |
| publishDateSearch | 2019 |
| publishDateSort | 2019 |
| publisher | O'Reilly |
| record_format | marc |
| spelling | Hewitt, Eben Verfasser (DE-588)1199903752 aut Semantic software design a new theory and practical guide for modern architects Eben Hewitt Beijing O'Reilly 2019 1 Online-Ressource (xiii, 316 Seiten) txt rdacontent c rdamedia cr rdacarrier Performance Improvement Checklist Intro; Copyright; Table of Contents; Preface; Conventions Used in This Book; Using Code Examples; O'Reilly Online Learning; How to Contact Us; Acknowledgments; Part I. Episteme: The Philosophy of Design; Chapter 1. Origins of Software Architecture; Software's Conceptual Origins; Copies and Creativity; Why Software Projects Fail; The Impact of Failures; Chapter 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, FixOutlining Your Concept on the Concept Canvas; 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; Chapter 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 EmbassyDesign for Failure; Design Language; Naming; Start Opposite the User; Platforms; Disappearing; Part II. Semantic Design in Practice; Chapter 4. Design Thinking; Why Design Thinking?; Exploring Design Thinking; Principles; The Method; Implementing the Method; Summary; Chapter 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 DefinitionPosition Papers; RAID; Presentations and Multiple Viewpoints; Summary; Chapter 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 Chapter 7. The Application AspectEmbrace 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; Data Accessors; Eventing; Structure of an Event Message; Contextual Services and Service Mixins Computer software / Development / Management Software architecture Softwarearchitektur (DE-588)4121677-5 gnd rswk-swf Softwareentwicklung (DE-588)4116522-6 gnd rswk-swf Softwarearchitektur (DE-588)4121677-5 s Softwareentwicklung (DE-588)4116522-6 s 1\p DE-604 Erscheint auch als Druck-Ausgabe 978-1-492-04595-3 1\p cgwrk 20201028 DE-101 https://d-nb.info/provenance/plan#cgwrk |
| spellingShingle | Hewitt, Eben Semantic software design a new theory and practical guide for modern architects Intro; Copyright; Table of Contents; Preface; Conventions Used in This Book; Using Code Examples; O'Reilly Online Learning; How to Contact Us; Acknowledgments; Part I. Episteme: The Philosophy of Design; Chapter 1. Origins of Software Architecture; Software's Conceptual Origins; Copies and Creativity; Why Software Projects Fail; The Impact of Failures; Chapter 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, FixOutlining Your Concept on the Concept Canvas; 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; Chapter 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 EmbassyDesign for Failure; Design Language; Naming; Start Opposite the User; Platforms; Disappearing; Part II. Semantic Design in Practice; Chapter 4. Design Thinking; Why Design Thinking?; Exploring Design Thinking; Principles; The Method; Implementing the Method; Summary; Chapter 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 DefinitionPosition Papers; RAID; Presentations and Multiple Viewpoints; Summary; Chapter 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 Chapter 7. The Application AspectEmbrace 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; Data Accessors; Eventing; Structure of an Event Message; Contextual Services and Service Mixins Computer software / Development / Management Software architecture Softwarearchitektur (DE-588)4121677-5 gnd Softwareentwicklung (DE-588)4116522-6 gnd |
| subject_GND | (DE-588)4121677-5 (DE-588)4116522-6 |
| title | Semantic software design a new theory and practical guide for modern architects |
| title_auth | Semantic software design a new theory and practical guide for modern architects |
| title_exact_search | Semantic software design a new theory and practical guide for modern architects |
| title_full | Semantic software design a new theory and practical guide for modern architects Eben Hewitt |
| title_fullStr | Semantic software design a new theory and practical guide for modern architects Eben Hewitt |
| title_full_unstemmed | Semantic software design a new theory and practical guide for modern architects Eben Hewitt |
| title_short | Semantic software design |
| title_sort | semantic software design a new theory and practical guide for modern architects |
| title_sub | a new theory and practical guide for modern architects |
| topic | Computer software / Development / Management Software architecture Softwarearchitektur (DE-588)4121677-5 gnd Softwareentwicklung (DE-588)4116522-6 gnd |
| topic_facet | Computer software / Development / Management Software architecture Softwarearchitektur Softwareentwicklung |
| work_keys_str_mv | AT hewitteben semanticsoftwaredesignanewtheoryandpracticalguideformodernarchitects |