MARC 닫기

• LDR

  05275cam a2200565Ii 4500

• 001

  000001334203

• 005

  20210114163055

• 006

  m d

• 007

  cr cnu---unuuu

• 008

  191026s2019 enk o 000 0 eng d

• 020

  ▼a  9781839219269
  ▼q  (electronic bk.)

• 020

  ▼a  1839219262
  ▼q  (electronic bk.)

• 035

  ▼a  2268998
  ▼b  (N$T)

• 035

  ▼a  (OCoLC)1124606210

• 037

  ▼a  C6C8ACCC-C586-4220-AF21-7C5F863A4261
  ▼b  OverDrive, Inc.
  ▼n  http://www.overdrive.com

• 040

  ▼a  EBLCP
  ▼b  eng
  ▼e  pn
  ▼c  EBLCP
  ▼d  TEFOD
  ▼d  EBLCP
  ▼d  OCLCF
  ▼d  OCLCQ
  ▼d  UKAHL
  ▼d  MERUC
  ▼d  OCLCQ
  ▼d  N$T
  ▼d  248023

• 050

  ▼a  QA76.9.A73

• 082

  ▼a  005.15
  ▼2  23

• 100

  ▼a  Starke, Gernot.

• 245

  ▼a  Arc42 by Example:
  ▼b  Software Architecture Documentation in Practice.

• 260

  ▼a  Birmingham:
  ▼b  Packt Publishing, Limited,
  ▼c  2019.

• 300

  ▼a  1 online resource (236 pages).

• 336

  ▼a  text
  ▼b  txt
  ▼2  rdacontent

• 337

  ▼a  computer
  ▼b  c
  ▼2  rdamedia

• 338

  ▼a  online resource
  ▼b  cr
  ▼2  rdacarrier

• 500

  ▼a  IV. 5 Building Blocks-Level 1

• 505

  ▼a  Cover; FM; Copyright; Table of Contents; Acknowledgements; Preface; I -- Introduction; I.1 What is arc42?; Why arc42?; Where to Get Additional Information; I.2 Why This Book?; I.3 What This Book is Not; I.4 An Overview of Examples; HTML Sanity Checking; Mass Market Customer Relationship Management; biking2; DokChess -- a Chess Engine; docToolchain; MiniMenu; I.5 A table of arc42 Topics; II -- HTML Sanity Checking; II. 1 Introduction and Goals; 1.1 Requirements Overview; Basic Usage; Basic Requirements; Required Checks; 1.2 Quality Goals; 1.3 Stakeholders; II. 2 Constraints; II. 3 Context

• 505

  ▼a  3.1 Business Context3.2 Deployment Context; II. 4 Solution Strategy; II. 5 Building Block View; 5.1 HtmlSanityChecker (Whitebox); Contained Blackboxes; 5.2 Building Blocks -- Level 2; Contained Blackboxes; 5.3 Building Blocks -- Level 3; Contained Blackboxes; II. 6 Runtime View; II. 6.1 Executing All Checks; II. 6.2 Report Checking Results; II. 7 Deployment View; Prerequisites; II. 8 Crosscutting Concepts; 8.1 Domain Model; 8.2 Structure of HTML Links; 8.3 Multiple Checking Algorithms; 8.4 Reporting; II. 9 Design Decisions; 9.1 Checking of External Links Postponed; 9.2 HTML Parsing with jsoup

• 505

  ▼a  II. 10 Quality ScenariosQuality Scenarios; II. 11 Risks and Technical Debt; 11.1 Technical Risks; 11.2 Business or Domain Risks; II. 12 Glossary; III -- Mass Market Customer Relationship Management; III. 1 Introduction and Requirements; 1.1 Requirements Overview; 1.1.1 Campaign Example: Mobile Phone Contract Modification; 1.1.2 Campaign Configuration; 1.1.3 Activities Subject to Charge; 1.1.4 Additional Requirements; 1.2 Quality Goals; 1.2.2 Quality Goals (Scenarios); 1.3 Stakeholder; 1.3.1 Special Case: German e-Health Card; 1.3.2 Partner or Mandator-Specific Interface Details; III. 2 Constraints

• 505

  ▼a  General ConstraintsSoftware Infrastructure Constraints; Operational Constraints; III. 3 Context; 3.1 (Generic) Business Context; 3.1.1 Formal Business Context; 3.1.2 Specific Business Context: Mobile Phone Contract Modification; 3.1.2 Technical/Deployment Context; III. 4 Solution Strategy; III. 5 Building Blocks; III. 6 Runtime View; 6.1 Import File; III. 7 Deployment View; 7.1 Deployment Overview; 7.2 Campaign-Specific Virtual Machine; 7.3 Common Metadata Store (CoMeS); 7.4 Campaign Configuration Machine; III. 8 Cross cutting Concepts; 8.1 Generated Persistence Based on the Domain Model

• 505

  ▼a  8.2 CSV Import/Export8.3 Configurable File Filters; 8.4 Rule Engine for Process and Flow Control; III. 9 Architecture Decisions; III. 10 Quality Scenarios; Flexibility Scenarios; Runtime Performance Scenarios; Security Scenarios; III. 11 Risks; III. 12 Glossary; IV -- biking2; IV. 1 Introduction and Requirements; 1.1 Requirements Overview; 1.2 Quality Goals; 1.3 Stakeholders; IV. 2 Architecture Constraints; 2.1 Technical Constraints; 2.2 Organizational Constraints; 2.3 Conventions; IV. 3 System Scope and Context; 3.1 Business Context; 3.2 Technical Context; IV. 4 Solution Strategy

• 520

  ▼a  This book teaches everything you need to know to jumpstart your own software architecture documentation. Through several elaborate examples, you'll learn how to write useful documentation that clearly explains the architecture of your software.

• 588

  ▼a  Print version record.

• 590

  ▼a  Added to collection customer.56279.3

• 650

  ▼a  Computer architecture.

• 650

  ▼a  Software documentation.

• 650

  ▼a  Computer architecture.
  ▼2  fast
  ▼0  (OCoLC)fst00872026

• 650

  ▼a  Software documentation.
  ▼2  fast
  ▼0  (OCoLC)fst01124182

• 655

  ▼a  Electronic books.

• 700

  ▼a  Simons, Michael.

• 700

  ▼a  Zörner, Stefan.

• 700

  ▼a  Müller, Ralf D.

• 776

  ▼i  Print version:
  ▼a  Starke, Gernot.
  ▼t  Arc42 by Example : Software Architecture Documentation in Practice.
  ▼d  Birmingham : Packt Publishing, Limited, ©2019,
  ▼z  9781839214356

• 856

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

• 938

  ▼a  Askews and Holts Library Services
  ▼b  ASKH
  ▼n  AH36828225

• 938

  ▼a  ProQuest Ebook Central
  ▼b  EBLB
  ▼n  EBL5939397

• 938

  ▼a  EBSCOhost
  ▼b  EBSC
  ▼n  2268998

• 990

  ▼a  강리원

• 991

  ▼a  eBook

• 994

  ▼a  92
  ▼b  N$T