상세정보
Export to Refworks부가기능
Software Architect's Handbook [electronic resource] Become a Successful Software Architect by Implementing Effective Architecture Concepts
상세 프로파일
| 자료유형 | 단행본 |
|---|---|
| 서명/저자사항 | Software Architect's Handbook [electronic resource] : Become a Successful Software Architect by Implementing Effective Architecture Concepts. |
| 개인저자 | Ingeno, Joseph. |
| 발행사항 | Birmingham: Packt Publishing Ltd, 2018. |
| 형태사항 | 1 online resource (584 p.). |
| 기타형태 저록 | Print version: Ingeno, Joseph Software Architect's Handbook : Become a Successful Software Architect by Implementing Effective Architecture Concepts Birmingham : Packt Publishing Ltd,c2018 9781788624060 |
| ISBN | 9781788627672 1788627679 |
| 일반주기 |
Description based upon print version of record.
Requirements engineering |
| 내용주기 | 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? |
| 요약 | 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. |
| 일반주제명 | COMPUTERS --Computer Science. COMPUTERS --Programming --General. Computers --Software Development & Engineering --General. Computers --Software Development & Engineering --Tools. Software engineering. Computer architecture. |
| 언어 | 영어 |
| 바로가기 |  |
