Software Architect's Handbook :: Become a Successful Software Architect by Implementing Effective Architecture Concepts.
This book is a comprehensive guide to help developers, architects, and senior programmers advance their career in the software architecture domain. You'll understand the expectations of users and other stakeholders from the point of view of an architect and will learn to communicate your archit...
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Elektronisch E-Book |
| Sprache: | English |
| Veröffentlicht: |
Birmingham :
Packt Publishing Ltd,
2018.
|
| Schlagworte: | |
| Online-Zugang: | Volltext |
| Zusammenfassung: | This book is a comprehensive guide to help developers, architects, and senior programmers advance their career in the software architecture domain. You'll understand the expectations of users and other stakeholders from the point of view of an architect and will learn to communicate your architecture to the relevant stakeholders. |
| Beschreibung: | Requirements engineering. |
| Beschreibung: | 1 online resource (584 pages) |
| ISBN: | 9781788627672 1788627679 |
Internformat
MARC
| LEADER | 00000cam a2200000Mi 4500 | ||
|---|---|---|---|
| 001 | ZDB-4-EBA-on1051141637 | ||
| 003 | OCoLC | ||
| 005 | 20241004212047.0 | ||
| 006 | m o d | ||
| 007 | cr cnu---unuuu | ||
| 008 | 180908s2018 enk o 000 0 eng d | ||
| 040 | |a EBLCP |b eng |e pn |c EBLCP |d YDX |d NLE |d TEFOD |d N$T |d MERUC |d OCLCF |d LVT |d OCLCQ |d OCLCO |d UKAHL |d OCLCQ |d NLW |d OCLCO |d NZAUC |d OCLCQ |d OCLCO |d OCLCL | ||
| 019 | |a 1051139032 |a 1051232049 |a 1051684185 |a 1053784940 | ||
| 020 | |a 9781788627672 |q (electronic bk.) | ||
| 020 | |a 1788627679 |q (electronic bk.) | ||
| 020 | |z 1788624068 | ||
| 020 | |z 9781788624060 | ||
| 035 | |a (OCoLC)1051141637 |z (OCoLC)1051139032 |z (OCoLC)1051232049 |z (OCoLC)1051684185 |z (OCoLC)1053784940 | ||
| 037 | |a 64CD901A-EC69-4429-A10E-7145E06D1E6D |b OverDrive, Inc. |n http://www.overdrive.com | ||
| 050 | 4 | |a QA76.758 | |
| 072 | 7 | |a COM |x 014000 |2 bisacsh | |
| 072 | 7 | |a COM |x 051000 |2 bisacsh | |
| 082 | 7 | |a 005.1 |2 23 | |
| 049 | |a MAIN | ||
| 100 | 1 | |a Ingeno, Joseph. | |
| 245 | 1 | 0 | |a Software Architect's Handbook : |b Become a Successful Software Architect by Implementing Effective Architecture Concepts. |
| 260 | |a Birmingham : |b Packt Publishing Ltd, |c 2018. | ||
| 300 | |a 1 online resource (584 pages) | ||
| 336 | |a text |b txt |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 588 | 0 | |a Print version record. | |
| 505 | 0 | |a Cover; Title Page; Copyright and Credits; Dedication; Packt Upsell; Contributors; Table of Contents; Preface; Chapter 1: The Meaning of Software Architecture; What is software architecture?; ISO/IEC/IEEE 42010 standard definition; What makes up a software architecture?; Software architecture is an abstraction; Software architecture is about the important stuff; Why is software architecture important?; Defining a solution to meet requirements; Enabling and inhibiting quality attributes ; Giving you the ability to predict software system qualities; Easing communication among stakeholders. | |
| 505 | 8 | |a Managing changeProviding a reusable model; Imposing implementation constraints; Improving cost and effort estimates; Serves as training for team members; Software architecture is not a silver bullet; Who are the consumers of software architectures?; What is the software architect role?; Software architects are technical leaders; Software architects perform a number of duties; Ivory tower software architects; What are software architects expected to know?; Don't be overwhelmed; Is the software architect role right for you?; Summary; Chapter 2: Software Architecture in an Organization. | |
| 505 | 8 | |a Types of software architectsEnterprise architect; Solution architect; Application architect; Data architect/information architect; Infrastructure architect; Information security architect; Cloud architect; Software development methodologies; The Waterfall model; Phases of the Waterfall methodology; Issues with the Waterfall methodology; Agile software development methodologies; Agile values and principles; An iterative methodology; Adaptive rather than predictive; Daily stand-up meetings; Project management; The importance of software project estimation; Putting effort into the estimates. | |
| 505 | 8 | |a Being a realist (or even a pessimist)Team and situational factors to consider; Project schedule changes; Getting a project back on schedule; Working overtime; Reducing scope; Adding resources; Reallocating resources; Identifying problem areas; Acting as early as possible; Office politics; Understanding your organization's goals; Addressing the concerns of others; Assisting people with their goals; Knowing when to compromise; Being aware of cultural differences; Software risk management; Risk avoidance; Transferring the risk to another party; Risk mitigation; Risk acceptance. | |
| 505 | 8 | |a Configuration managementChanging management; Software product lines; Benefits of a software product line; Core assets of an organization; Risks of product line engineering; Summary; Chapter 3: Understanding the Domain; Developing business acumen; Familiarity with general business topics; Understanding your organization's business; Domain-driven design; Encourages and improves communication; What is a ubiquitous language?; Entities, value objects, and aggregates; Entities; Value objects; Aggregates and root entities; Separating the domain into subdomains; What are bounded contexts? | |
| 500 | |a Requirements engineering. | ||
| 520 | |a This book is a comprehensive guide to help developers, architects, and senior programmers advance their career in the software architecture domain. You'll understand the expectations of users and other stakeholders from the point of view of an architect and will learn to communicate your architecture to the relevant stakeholders. | ||
| 650 | 0 | |a Software engineering. |0 http://id.loc.gov/authorities/subjects/sh87007398 | |
| 650 | 0 | |a Computer architecture. |0 http://id.loc.gov/authorities/subjects/sh85029479 | |
| 650 | 6 | |a Génie logiciel. | |
| 650 | 6 | |a Ordinateurs |x Architecture. | |
| 650 | 7 | |a Computer programming / software development. |2 bicssc | |
| 650 | 7 | |a COMPUTERS |x Computer Science. |2 bisacsh | |
| 650 | 7 | |a COMPUTERS |x Programming |x General. |2 bisacsh | |
| 650 | 7 | |a Computers |x Software Development & Engineering |x General. |2 bisacsh | |
| 650 | 7 | |a Computers |x Software Development & Engineering |x Tools. |2 bisacsh | |
| 650 | 7 | |a Computer architecture |2 fast | |
| 650 | 7 | |a Software engineering |2 fast | |
| 758 | |i has work: |a Software architect's handbook (Text) |1 https://id.oclc.org/worldcat/entity/E39PCYcxqCcYt7FcdgfcQY8FqP |4 https://id.oclc.org/worldcat/ontology/hasWork | ||
| 776 | 0 | 8 | |i Print version: |a Ingeno, Joseph. |t Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. |d Birmingham : Packt Publishing Ltd, ©2018 |z 9781788624060 |
| 856 | 4 | 0 | |l FWS01 |p ZDB-4-EBA |q FWS_PDA_EBA |u https://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&AN=1881493 |3 Volltext |
| 938 | |a Askews and Holts Library Services |b ASKH |n AH35077044 | ||
| 938 | |a EBL - Ebook Library |b EBLB |n EBL5504926 | ||
| 938 | |a EBSCOhost |b EBSC |n 1881493 | ||
| 938 | |a YBP Library Services |b YANK |n 15689463 | ||
| 994 | |a 92 |b GEBAY | ||
| 912 | |a ZDB-4-EBA | ||
| 049 | |a DE-863 | ||
Datensatz im Suchindex
| DE-BY-FWS_katkey | ZDB-4-EBA-on1051141637 |
|---|---|
| _version_ | 1816882470902038529 |
| adam_text | |
| any_adam_object | |
| author | Ingeno, Joseph |
| author_facet | Ingeno, Joseph |
| author_role | |
| author_sort | Ingeno, Joseph |
| author_variant | j i ji |
| building | Verbundindex |
| bvnumber | localFWS |
| callnumber-first | Q - Science |
| callnumber-label | QA76 |
| callnumber-raw | QA76.758 |
| callnumber-search | QA76.758 |
| callnumber-sort | QA 276.758 |
| callnumber-subject | QA - Mathematics |
| collection | ZDB-4-EBA |
| contents | Cover; Title Page; Copyright and Credits; Dedication; Packt Upsell; Contributors; Table of Contents; Preface; Chapter 1: The Meaning of Software Architecture; What is software architecture?; ISO/IEC/IEEE 42010 standard definition; What makes up a software architecture?; Software architecture is an abstraction; Software architecture is about the important stuff; Why is software architecture important?; Defining a solution to meet requirements; Enabling and inhibiting quality attributes ; Giving you the ability to predict software system qualities; Easing communication among stakeholders. Managing changeProviding a reusable model; Imposing implementation constraints; Improving cost and effort estimates; Serves as training for team members; Software architecture is not a silver bullet; Who are the consumers of software architectures?; What is the software architect role?; Software architects are technical leaders; Software architects perform a number of duties; Ivory tower software architects; What are software architects expected to know?; Don't be overwhelmed; Is the software architect role right for you?; Summary; Chapter 2: Software Architecture in an Organization. Types of software architectsEnterprise architect; Solution architect; Application architect; Data architect/information architect; Infrastructure architect; Information security architect; Cloud architect; Software development methodologies; The Waterfall model; Phases of the Waterfall methodology; Issues with the Waterfall methodology; Agile software development methodologies; Agile values and principles; An iterative methodology; Adaptive rather than predictive; Daily stand-up meetings; Project management; The importance of software project estimation; Putting effort into the estimates. Being a realist (or even a pessimist)Team and situational factors to consider; Project schedule changes; Getting a project back on schedule; Working overtime; Reducing scope; Adding resources; Reallocating resources; Identifying problem areas; Acting as early as possible; Office politics; Understanding your organization's goals; Addressing the concerns of others; Assisting people with their goals; Knowing when to compromise; Being aware of cultural differences; Software risk management; Risk avoidance; Transferring the risk to another party; Risk mitigation; Risk acceptance. Configuration managementChanging management; Software product lines; Benefits of a software product line; Core assets of an organization; Risks of product line engineering; Summary; Chapter 3: Understanding the Domain; Developing business acumen; Familiarity with general business topics; Understanding your organization's business; Domain-driven design; Encourages and improves communication; What is a ubiquitous language?; Entities, value objects, and aggregates; Entities; Value objects; Aggregates and root entities; Separating the domain into subdomains; What are bounded contexts? |
| ctrlnum | (OCoLC)1051141637 |
| dewey-full | 005.1 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.1 |
| dewey-search | 005.1 |
| dewey-sort | 15.1 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>06205cam a2200661Mi 4500</leader><controlfield tag="001">ZDB-4-EBA-on1051141637</controlfield><controlfield tag="003">OCoLC</controlfield><controlfield tag="005">20241004212047.0</controlfield><controlfield tag="006">m o d </controlfield><controlfield tag="007">cr cnu---unuuu</controlfield><controlfield tag="008">180908s2018 enk o 000 0 eng d</controlfield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">EBLCP</subfield><subfield code="b">eng</subfield><subfield code="e">pn</subfield><subfield code="c">EBLCP</subfield><subfield code="d">YDX</subfield><subfield code="d">NLE</subfield><subfield code="d">TEFOD</subfield><subfield code="d">N$T</subfield><subfield code="d">MERUC</subfield><subfield code="d">OCLCF</subfield><subfield code="d">LVT</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">OCLCO</subfield><subfield code="d">UKAHL</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">NLW</subfield><subfield code="d">OCLCO</subfield><subfield code="d">NZAUC</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">OCLCO</subfield><subfield code="d">OCLCL</subfield></datafield><datafield tag="019" ind1=" " ind2=" "><subfield code="a">1051139032</subfield><subfield code="a">1051232049</subfield><subfield code="a">1051684185</subfield><subfield code="a">1053784940</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781788627672</subfield><subfield code="q">(electronic bk.)</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1788627679</subfield><subfield code="q">(electronic bk.)</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="z">1788624068</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="z">9781788624060</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)1051141637</subfield><subfield code="z">(OCoLC)1051139032</subfield><subfield code="z">(OCoLC)1051232049</subfield><subfield code="z">(OCoLC)1051684185</subfield><subfield code="z">(OCoLC)1053784940</subfield></datafield><datafield tag="037" ind1=" " ind2=" "><subfield code="a">64CD901A-EC69-4429-A10E-7145E06D1E6D</subfield><subfield code="b">OverDrive, Inc.</subfield><subfield code="n">http://www.overdrive.com</subfield></datafield><datafield tag="050" ind1=" " ind2="4"><subfield code="a">QA76.758</subfield></datafield><datafield tag="072" ind1=" " ind2="7"><subfield code="a">COM</subfield><subfield code="x">014000</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="072" ind1=" " ind2="7"><subfield code="a">COM</subfield><subfield code="x">051000</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="082" ind1="7" ind2=" "><subfield code="a">005.1</subfield><subfield code="2">23</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">MAIN</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Ingeno, Joseph.</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Software Architect's Handbook :</subfield><subfield code="b">Become a Successful Software Architect by Implementing Effective Architecture Concepts.</subfield></datafield><datafield tag="260" ind1=" " ind2=" "><subfield code="a">Birmingham :</subfield><subfield code="b">Packt Publishing Ltd,</subfield><subfield code="c">2018.</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 online resource (584 pages)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">computer</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">online resource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="588" ind1="0" ind2=" "><subfield code="a">Print version record.</subfield></datafield><datafield tag="505" ind1="0" ind2=" "><subfield code="a">Cover; Title Page; Copyright and Credits; Dedication; Packt Upsell; Contributors; Table of Contents; Preface; Chapter 1: The Meaning of Software Architecture; What is software architecture?; ISO/IEC/IEEE 42010 standard definition; What makes up a software architecture?; Software architecture is an abstraction; Software architecture is about the important stuff; Why is software architecture important?; Defining a solution to meet requirements; Enabling and inhibiting quality attributes ; Giving you the ability to predict software system qualities; Easing communication among stakeholders.</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Managing changeProviding a reusable model; Imposing implementation constraints; Improving cost and effort estimates; Serves as training for team members; Software architecture is not a silver bullet; Who are the consumers of software architectures?; What is the software architect role?; Software architects are technical leaders; Software architects perform a number of duties; Ivory tower software architects; What are software architects expected to know?; Don't be overwhelmed; Is the software architect role right for you?; Summary; Chapter 2: Software Architecture in an Organization.</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Types of software architectsEnterprise architect; Solution architect; Application architect; Data architect/information architect; Infrastructure architect; Information security architect; Cloud architect; Software development methodologies; The Waterfall model; Phases of the Waterfall methodology; Issues with the Waterfall methodology; Agile software development methodologies; Agile values and principles; An iterative methodology; Adaptive rather than predictive; Daily stand-up meetings; Project management; The importance of software project estimation; Putting effort into the estimates.</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Being a realist (or even a pessimist)Team and situational factors to consider; Project schedule changes; Getting a project back on schedule; Working overtime; Reducing scope; Adding resources; Reallocating resources; Identifying problem areas; Acting as early as possible; Office politics; Understanding your organization's goals; Addressing the concerns of others; Assisting people with their goals; Knowing when to compromise; Being aware of cultural differences; Software risk management; Risk avoidance; Transferring the risk to another party; Risk mitigation; Risk acceptance.</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Configuration managementChanging management; Software product lines; Benefits of a software product line; Core assets of an organization; Risks of product line engineering; Summary; Chapter 3: Understanding the Domain; Developing business acumen; Familiarity with general business topics; Understanding your organization's business; Domain-driven design; Encourages and improves communication; What is a ubiquitous language?; Entities, value objects, and aggregates; Entities; Value objects; Aggregates and root entities; Separating the domain into subdomains; What are bounded contexts?</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Requirements engineering.</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">This book is a comprehensive guide to help developers, architects, and senior programmers advance their career in the software architecture domain. You'll understand the expectations of users and other stakeholders from the point of view of an architect and will learn to communicate your architecture to the relevant stakeholders.</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Software engineering.</subfield><subfield code="0">http://id.loc.gov/authorities/subjects/sh87007398</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Computer architecture.</subfield><subfield code="0">http://id.loc.gov/authorities/subjects/sh85029479</subfield></datafield><datafield tag="650" ind1=" " ind2="6"><subfield code="a">Génie logiciel.</subfield></datafield><datafield tag="650" ind1=" " ind2="6"><subfield code="a">Ordinateurs</subfield><subfield code="x">Architecture.</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Computer programming / software development.</subfield><subfield code="2">bicssc</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">COMPUTERS</subfield><subfield code="x">Computer Science.</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">COMPUTERS</subfield><subfield code="x">Programming</subfield><subfield code="x">General.</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Computers</subfield><subfield code="x">Software Development & Engineering</subfield><subfield code="x">General.</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Computers</subfield><subfield code="x">Software Development & Engineering</subfield><subfield code="x">Tools.</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Computer architecture</subfield><subfield code="2">fast</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Software engineering</subfield><subfield code="2">fast</subfield></datafield><datafield tag="758" ind1=" " ind2=" "><subfield code="i">has work:</subfield><subfield code="a">Software architect's handbook (Text)</subfield><subfield code="1">https://id.oclc.org/worldcat/entity/E39PCYcxqCcYt7FcdgfcQY8FqP</subfield><subfield code="4">https://id.oclc.org/worldcat/ontology/hasWork</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Print version:</subfield><subfield code="a">Ingeno, Joseph.</subfield><subfield code="t">Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts.</subfield><subfield code="d">Birmingham : Packt Publishing Ltd, ©2018</subfield><subfield code="z">9781788624060</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="l">FWS01</subfield><subfield code="p">ZDB-4-EBA</subfield><subfield code="q">FWS_PDA_EBA</subfield><subfield code="u">https://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&AN=1881493</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">Askews and Holts Library Services</subfield><subfield code="b">ASKH</subfield><subfield code="n">AH35077044</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">EBL - Ebook Library</subfield><subfield code="b">EBLB</subfield><subfield code="n">EBL5504926</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">EBSCOhost</subfield><subfield code="b">EBSC</subfield><subfield code="n">1881493</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">YBP Library Services</subfield><subfield code="b">YANK</subfield><subfield code="n">15689463</subfield></datafield><datafield tag="994" ind1=" " ind2=" "><subfield code="a">92</subfield><subfield code="b">GEBAY</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-4-EBA</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-863</subfield></datafield></record></collection> |
| id | ZDB-4-EBA-on1051141637 |
| illustrated | Not Illustrated |
| indexdate | 2024-11-27T13:29:08Z |
| institution | BVB |
| isbn | 9781788627672 1788627679 |
| language | English |
| oclc_num | 1051141637 |
| open_access_boolean | |
| owner | MAIN DE-863 DE-BY-FWS |
| owner_facet | MAIN DE-863 DE-BY-FWS |
| physical | 1 online resource (584 pages) |
| psigel | ZDB-4-EBA |
| publishDate | 2018 |
| publishDateSearch | 2018 |
| publishDateSort | 2018 |
| publisher | Packt Publishing Ltd, |
| record_format | marc |
| spelling | Ingeno, Joseph. Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. Birmingham : Packt Publishing Ltd, 2018. 1 online resource (584 pages) text txt rdacontent computer c rdamedia online resource cr rdacarrier Print version record. Cover; Title Page; Copyright and Credits; Dedication; Packt Upsell; Contributors; Table of Contents; Preface; Chapter 1: The Meaning of Software Architecture; What is software architecture?; ISO/IEC/IEEE 42010 standard definition; What makes up a software architecture?; Software architecture is an abstraction; Software architecture is about the important stuff; Why is software architecture important?; Defining a solution to meet requirements; Enabling and inhibiting quality attributes ; Giving you the ability to predict software system qualities; Easing communication among stakeholders. Managing changeProviding a reusable model; Imposing implementation constraints; Improving cost and effort estimates; Serves as training for team members; Software architecture is not a silver bullet; Who are the consumers of software architectures?; What is the software architect role?; Software architects are technical leaders; Software architects perform a number of duties; Ivory tower software architects; What are software architects expected to know?; Don't be overwhelmed; Is the software architect role right for you?; Summary; Chapter 2: Software Architecture in an Organization. Types of software architectsEnterprise architect; Solution architect; Application architect; Data architect/information architect; Infrastructure architect; Information security architect; Cloud architect; Software development methodologies; The Waterfall model; Phases of the Waterfall methodology; Issues with the Waterfall methodology; Agile software development methodologies; Agile values and principles; An iterative methodology; Adaptive rather than predictive; Daily stand-up meetings; Project management; The importance of software project estimation; Putting effort into the estimates. Being a realist (or even a pessimist)Team and situational factors to consider; Project schedule changes; Getting a project back on schedule; Working overtime; Reducing scope; Adding resources; Reallocating resources; Identifying problem areas; Acting as early as possible; Office politics; Understanding your organization's goals; Addressing the concerns of others; Assisting people with their goals; Knowing when to compromise; Being aware of cultural differences; Software risk management; Risk avoidance; Transferring the risk to another party; Risk mitigation; Risk acceptance. Configuration managementChanging management; Software product lines; Benefits of a software product line; Core assets of an organization; Risks of product line engineering; Summary; Chapter 3: Understanding the Domain; Developing business acumen; Familiarity with general business topics; Understanding your organization's business; Domain-driven design; Encourages and improves communication; What is a ubiquitous language?; Entities, value objects, and aggregates; Entities; Value objects; Aggregates and root entities; Separating the domain into subdomains; What are bounded contexts? Requirements engineering. This book is a comprehensive guide to help developers, architects, and senior programmers advance their career in the software architecture domain. You'll understand the expectations of users and other stakeholders from the point of view of an architect and will learn to communicate your architecture to the relevant stakeholders. Software engineering. http://id.loc.gov/authorities/subjects/sh87007398 Computer architecture. http://id.loc.gov/authorities/subjects/sh85029479 Génie logiciel. Ordinateurs Architecture. Computer programming / software development. bicssc COMPUTERS Computer Science. bisacsh COMPUTERS Programming General. bisacsh Computers Software Development & Engineering General. bisacsh Computers Software Development & Engineering Tools. bisacsh Computer architecture fast Software engineering fast has work: Software architect's handbook (Text) https://id.oclc.org/worldcat/entity/E39PCYcxqCcYt7FcdgfcQY8FqP https://id.oclc.org/worldcat/ontology/hasWork Print version: Ingeno, Joseph. Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. Birmingham : Packt Publishing Ltd, ©2018 9781788624060 FWS01 ZDB-4-EBA FWS_PDA_EBA https://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&AN=1881493 Volltext |
| spellingShingle | Ingeno, Joseph Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. Cover; Title Page; Copyright and Credits; Dedication; Packt Upsell; Contributors; Table of Contents; Preface; Chapter 1: The Meaning of Software Architecture; What is software architecture?; ISO/IEC/IEEE 42010 standard definition; What makes up a software architecture?; Software architecture is an abstraction; Software architecture is about the important stuff; Why is software architecture important?; Defining a solution to meet requirements; Enabling and inhibiting quality attributes ; Giving you the ability to predict software system qualities; Easing communication among stakeholders. Managing changeProviding a reusable model; Imposing implementation constraints; Improving cost and effort estimates; Serves as training for team members; Software architecture is not a silver bullet; Who are the consumers of software architectures?; What is the software architect role?; Software architects are technical leaders; Software architects perform a number of duties; Ivory tower software architects; What are software architects expected to know?; Don't be overwhelmed; Is the software architect role right for you?; Summary; Chapter 2: Software Architecture in an Organization. Types of software architectsEnterprise architect; Solution architect; Application architect; Data architect/information architect; Infrastructure architect; Information security architect; Cloud architect; Software development methodologies; The Waterfall model; Phases of the Waterfall methodology; Issues with the Waterfall methodology; Agile software development methodologies; Agile values and principles; An iterative methodology; Adaptive rather than predictive; Daily stand-up meetings; Project management; The importance of software project estimation; Putting effort into the estimates. Being a realist (or even a pessimist)Team and situational factors to consider; Project schedule changes; Getting a project back on schedule; Working overtime; Reducing scope; Adding resources; Reallocating resources; Identifying problem areas; Acting as early as possible; Office politics; Understanding your organization's goals; Addressing the concerns of others; Assisting people with their goals; Knowing when to compromise; Being aware of cultural differences; Software risk management; Risk avoidance; Transferring the risk to another party; Risk mitigation; Risk acceptance. Configuration managementChanging management; Software product lines; Benefits of a software product line; Core assets of an organization; Risks of product line engineering; Summary; Chapter 3: Understanding the Domain; Developing business acumen; Familiarity with general business topics; Understanding your organization's business; Domain-driven design; Encourages and improves communication; What is a ubiquitous language?; Entities, value objects, and aggregates; Entities; Value objects; Aggregates and root entities; Separating the domain into subdomains; What are bounded contexts? Software engineering. http://id.loc.gov/authorities/subjects/sh87007398 Computer architecture. http://id.loc.gov/authorities/subjects/sh85029479 Génie logiciel. Ordinateurs Architecture. Computer programming / software development. bicssc COMPUTERS Computer Science. bisacsh COMPUTERS Programming General. bisacsh Computers Software Development & Engineering General. bisacsh Computers Software Development & Engineering Tools. bisacsh Computer architecture fast Software engineering fast |
| subject_GND | http://id.loc.gov/authorities/subjects/sh87007398 http://id.loc.gov/authorities/subjects/sh85029479 |
| title | Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. |
| title_auth | Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. |
| title_exact_search | Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. |
| title_full | Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. |
| title_fullStr | Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. |
| title_full_unstemmed | Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts. |
| title_short | Software Architect's Handbook : |
| title_sort | software architect s handbook become a successful software architect by implementing effective architecture concepts |
| title_sub | Become a Successful Software Architect by Implementing Effective Architecture Concepts. |
| topic | Software engineering. http://id.loc.gov/authorities/subjects/sh87007398 Computer architecture. http://id.loc.gov/authorities/subjects/sh85029479 Génie logiciel. Ordinateurs Architecture. Computer programming / software development. bicssc COMPUTERS Computer Science. bisacsh COMPUTERS Programming General. bisacsh Computers Software Development & Engineering General. bisacsh Computers Software Development & Engineering Tools. bisacsh Computer architecture fast Software engineering fast |
| topic_facet | Software engineering. Computer architecture. Génie logiciel. Ordinateurs Architecture. Computer programming / software development. COMPUTERS Computer Science. COMPUTERS Programming General. Computers Software Development & Engineering General. Computers Software Development & Engineering Tools. Computer architecture Software engineering |
| url | https://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&AN=1881493 |
| work_keys_str_mv | AT ingenojoseph softwarearchitectshandbookbecomeasuccessfulsoftwarearchitectbyimplementingeffectivearchitectureconcepts |