MARC 닫기

• LDR

  05596cam c2200577Mu 4500

• 001

  000001308227

• 005

  20200210174425

• 006

  m d

• 007

  cr cnu---unuuu

• 008

  180908s2018 xx o 000 0 eng d

• 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  1881493
  ▼b  (N$T)

• 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

• 040

  ▼a  EBLCP
  ▼b  eng
  ▼c  EBLCP
  ▼d  YDX
  ▼d  NLE
  ▼d  TEFOD
  ▼d  N$T
  ▼d  248023

• 049

  ▼a  MAIN

• 050

  ▼a  QA76.758

• 072

  ▼a  COM
  ▼x  014000
  ▼2  bisacsh

• 072

  ▼a  COM
  ▼x  051000
  ▼2  bisacsh

• 082

  ▼a  005.1
  ▼2  23

• 100

  ▼a  Ingeno, Joseph.

• 245

  ▼a  Software Architect's Handbook
  ▼h  [electronic resource]:
  ▼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 p.).

• 500

  ▼a  Description based upon print version of record.

• 500

  ▼a  Requirements engineering

• 505

  ▼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

  ▼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

  ▼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

  ▼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

  ▼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?

• 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.

• 590

  ▼a  Master record variable field(s) change: 072, 082

• 650

  ▼a  COMPUTERS
  ▼x  Computer Science.
  ▼2  bisacsh

• 650

  ▼a  COMPUTERS
  ▼x  Programming
  ▼x  General.
  ▼2  bisacsh

• 650

  ▼a  Computers
  ▼x  Software Development & Engineering
  ▼x  General.
  ▼2  bisacsh

• 650

  ▼a  Computers
  ▼x  Software Development & Engineering
  ▼x  Tools.
  ▼2  bisacsh

• 650

  ▼a  Software engineering.

• 650

  ▼a  Computer architecture.

• 655

  ▼a  Electronic books.

• 776

  ▼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,c2018,
  ▼z  9781788624060

• 852

  ▼a  NA000000
  ▼b  00000140

• 856

  ▼3  EBSCOhost
  ▼u  http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=1881493

• 938

  ▼a  EBL - Ebook Library
  ▼b  EBLB
  ▼n  EBL5504926

• 938

  ▼a  YBP Library Services
  ▼b  YANK
  ▼n  15689463

• 938

  ▼a  EBSCOhost
  ▼b  EBSC
  ▼n  1881493

• 994

  ▼a  92
  ▼b  N$T