LEADER 00000cam a2200601 i 4500
001 on1124606210
003 OCoLC
005 20240126125653.0
006 m o d
007 cr cnu---unuuu
008 191026s2019 enk o 000 0 eng d
020 9781839219269|q(electronic bk.)
020 1839219262|q(electronic bk.)
035 (OCoLC)1124606210
037 C6C8ACCC-C586-4220-AF21-7C5F863A4261|bOverDrive, Inc.
|nhttp://www.overdrive.com
040 EBLCP|beng|epn|cEBLCP|dTEFOD|dEBLCP|dOCLCF|dOCLCQ|dUKAHL
|dMERUC|dOCLCQ|dN$T|dNLW|dOCLCO|dOCLCQ|dOCLCO|dNZAUC
|dOCLCQ|dOCLCO
049 RIDW
050 4 QA76.9.A73
082 04 005.15|223
090 QA76.9.A73
100 1 Starke, Gernot.
245 10 Arc42 by Example :|bSoftware Architecture Documentation in
Practice.
260 Birmingham :|bPackt Publishing, Limited,|c2019.
300 1 online resource (236 pages)
336 text|btxt|2rdacontent
337 computer|bc|2rdamedia
338 online resource|bcr|2rdacarrier
500 IV. 5 Building Blocks-Level 1
505 0 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 8 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 8 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 8 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 8 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 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 0 Print version record.
590 eBooks on EBSCOhost|bEBSCO eBook Subscription Academic
Collection - North America
650 0 Computer architecture.
650 0 Software documentation.
650 7 Programming & scripting languages: general.|2bicssc
650 7 Information visualization.|2bicssc
650 7 Data capture & analysis.|2bicssc
650 7 Computers|xProgramming Languages|xPython.|2bisacsh
650 7 Computers|xData Processing.|2bisacsh
650 7 Computer architecture|2fast
650 7 Software documentation|2fast
700 1 Simons, Michael.
700 1 Zörner, Stefan.
700 1 Müller, Ralf D.
776 08 |iPrint version:|aStarke, Gernot.|tArc42 by Example :
Software Architecture Documentation in Practice.
|dBirmingham : Packt Publishing, Limited, ©2019
|z9781839214356
856 40 |uhttps://rider.idm.oclc.org/login?url=https://
search.ebscohost.com/login.aspx?direct=true&scope=site&
db=nlebk&AN=2268998|zOnline ebook via EBSCO. Access
restricted to current Rider University students, faculty,
and staff.
856 42 |3Instructions for reading/downloading the EBSCO version
of this ebook|uhttp://guides.rider.edu/ebooks/ebsco
948 |d20240319|cEBSCO|tEBSCOebooksacademic NEW 1-26-24 6521
|lridw
994 92|bRID
