MARC details
000 -LEADER |
fixed length control field |
07431cam a22005537i 4500 |
001 - CONTROL NUMBER |
control field |
19706737 |
005 - DATE AND TIME OF LATEST TRANSACTION |
control field |
20220110072024.0 |
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
fixed length control field |
170613s2018 enka b 001 0 eng d |
010 ## - LIBRARY OF CONGRESS CONTROL NUMBER |
LC control number |
2017945537 |
016 7# - NATIONAL BIBLIOGRAPHIC AGENCY CONTROL NUMBER |
Record control number |
018284503 |
Source |
Uk |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
International Standard Book Number |
9780134494166 |
Qualifying information |
(paperback) |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
International Standard Book Number |
0134494164 |
Qualifying information |
(paperback) |
035 ## - SYSTEM CONTROL NUMBER |
System control number |
(OCoLC)on1004983973 |
040 ## - CATALOGING SOURCE |
Original cataloging agency |
EUM |
Language of cataloging |
eng |
Transcribing agency |
EUM |
Description conventions |
rda |
Modifying agency |
IG$ |
-- |
IUP |
-- |
GP5 |
-- |
TOH |
-- |
OCLCF |
-- |
PSC |
-- |
NYP |
-- |
EG-CaTKH |
042 ## - AUTHENTICATION CODE |
Authentication code |
lccopycat |
050 00 - LIBRARY OF CONGRESS CALL NUMBER |
Classification number |
QA76.76.D47 |
Item number |
M36515 2018 |
082 04 - DEWEY DECIMAL CLASSIFICATION NUMBER |
Classification number |
004.22 MA.C 2018 |
Edition number |
23 |
100 1# - MAIN ENTRY--PERSONAL NAME |
Personal name |
Martin, Robert C., |
Relator term |
author. |
245 10 - TITLE STATEMENT |
Title |
Clean architecture : |
Remainder of title |
a craftsman's guide to software structure and design / |
Statement of responsibility, etc. |
Robert C. Martin. |
264 #1 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE |
Place of production, publication, distribution, manufacture |
London, England : |
Name of producer, publisher, distributor, manufacturer |
Prentice Hall, |
Date of production, publication, distribution, manufacture, or copyright notice |
2018. |
300 ## - PHYSICAL DESCRIPTION |
Extent |
xxv, 404 pages : |
Other physical details |
illustrations ; |
Dimensions |
24 cm |
336 ## - CONTENT TYPE |
Content type term |
text |
Source |
rdacontent |
Content type code |
txt |
337 ## - MEDIA TYPE |
Media type term |
unmediated |
Source |
rdamedia |
Media type code |
n |
338 ## - CARRIER TYPE |
Carrier type term |
volume |
Source |
rdacarrier |
Carrier type code |
nc |
490 1# - SERIES STATEMENT |
Series statement |
Robert C. Martin series |
504 ## - BIBLIOGRAPHY, ETC. NOTE |
Bibliography, etc. note |
Includes bibliographical references and index. |
505 00 - FORMATTED CONTENTS NOTE |
Formatted contents note |
\a Part I. Introduction : What is design and architecture? : The goal? ; Case study -- A tale of two values : Behavior ; Architecture ; The greater value ; Eisenhower's matrix ; Fight for the architecture -- Part II. Starting with the bricks: programming paradigms : Paradigm overview : Structured programming ; Object-oriented programming ; Functional programming ; food for thought -- Structured programming : Proof ; A harmful proclamation ; Functional decomposition ; No formal proofs ; Science to the rescue ; Tests -- Object-oriented programming : Encapsulation? ; Inheritance? ; Polymorphism? -- Functional programming : Squares of integers ; Immutability and architecture ; Segregation of mutability ; Event sourcing -- Part III. Design principles : SRP: the single responsibility principle : Symptom 1: Accidental duplication ; Symptom 2: Merges ; Solutions -- OCP: the open-closed principle : A thought experiment ; Information hiding -- LSP: the Liskov substitution principle : Guiding the use of inheritance ; The square/rectangle problem ; LSP and architecture ; Example LSP violation -- ISP: the interface segregation principle : ISP and language ; ISP and architecture -- DIP: the dependency inversion principle : Stable abstractions ; Factories ; Concrete components -- Part IV. Component principles : Component cohesion : The reuse/release equivalence principle ; The common closure principle ; The common reuse principle ; The tension diagram for component cohesion -- Component coupling : The acyclic dependencies principle : Top-down design ; The stable dependencies principle ; The stable abstraction principle -- Part V. Architecture : What is architecture : Development ; Deployment ; Operation ; Maintenance ; Keeping options open ; Device independence ; Junk mail ; Physical addressing -- Independence : Use cases ; Operation ; Development ; Deployment ; Leaving options open ; Decoupling layers ; Decoupling use cases ; Decoupling mode ; Independent develop-ability ; Independent deployability ; Duplication ; Decoupling modes (again) -- Boundaries: drawing lines : A couple of sad stories ; FitNesse ; Which lines do you draw, and when do you draw them? ; What about input and output? ; Plugin architecture ; The plugin argument -- Boundary anatomy : Boundary crossing ; The dreaded monolith ; Deployment components ; Threads ; Local processes ; Services -- Policy and level -- Business rules : Entities ; Use cases ; Request and response models -- Screaming architecture : The theme of an architecture ; The purpose of an architecture ; But what about the Web? ; Frameworks are tools, not ways of life ; Testable architecture -- The clean architecture : The dependency rule ; A typical scenario -- Presenters and humble objects : The humble object pattern ; Presenters and views ; Testing and architecture ; Database gateways ; Data mappers ; Service listeners -- Partial boundaries : Skip the last step ; One-dimensional boundaries -- Layers and boundaries : Hunt the wumpus ; Clean architecture? ; Crossing the streams ; Splitting the streams -- The main component : The ultimate detail -- Services: great and small : Service architecture? ; Service benefits? ; The kitty problem ; Objects to the rescue ; Component-based services ; Cross-cutting concerns -- The test boundary : Test as system components ; Design for testability ; The testing API -- Clean embedded architecture : App-titude test ; The target-hardware bottleneck -- Part VI. Details : The database is a detail : Relational databases ; Why are database systems so prevalent? ; What if there were no disk? ; Details ; But what about performance? ; Anecdote -- The Web is a detail : The endless pendulum ; The upshot -- Frameworks are details : Framework authors ; Asymmetric marriage ; The risks ; The solution ; I now pronounce you ... -- Case study: video sales : The product ; Use case analysis ; Component architecture ; Dependency management -- The missing chapter : Package by layer ; Package by feature ; Ports and adapters ; Package by component ; The devil is in the implementation details ; Organization versus encapsulation ; Other decoupling modes ; Conclusion : The missing advice -- Afterword / Jason Gorman -- Part VII. Appendix : Architecture archaeology. |
520 ## - SUMMARY, ETC. |
Summary, etc. |
Building upon the success of best-sellers The Clean Coder and Clean Code, legendary software craftsman Robert C. "Uncle Bob" Martin shows how to bring greater professionalism and discipline to application architecture and design. As with his other books, Martin's Clean Architecture doesn't merely present multiple choices and options, and say "use your best judgment": it tells you what choices to make, and why those choices are critical to your success. Martin offers direct, no-nonsense answers to key architecture and design questions like: What are the best high level structures for different kinds of applications, including web, database, thick-client, console, and embedded apps? What are the core principles of software architecture? What is the role of the architect, and what is he/she really trying to achieve? What are the core principles of software design? How do designs and architectures go wrong, and what can you do about it? What are the disciplines and practices of professional architects and designers? Clean Architecture is essential reading for every software architect, systems analyst, system designer, and software manager -- and for any programmer who aspires to these roles or is impacted by their work. |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name entry element |
Software architecture. |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name entry element |
Computer software |
General subdivision |
Development. |
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name entry element |
Computer programming |
General subdivision |
History. |
650 #7 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name entry element |
COMPUTERS / Computer Architecture. |
650 #7 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name entry element |
Computer programming. |
650 #7 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name entry element |
Computer software |
General subdivision |
Development. |
650 #7 - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name entry element |
Software architecture. |
700 1# - ADDED ENTRY--PERSONAL NAME |
Personal name |
Brown, Simon, |
Dates associated with a name |
1975- |
Relator term |
contributor. |
830 #0 - SERIES ADDED ENTRY--UNIFORM TITLE |
Uniform title |
Robert C. Martin series. |
942 ## - ADDED ENTRY ELEMENTS (KOHA) |
Source of classification or shelving scheme |
Dewey Decimal Classification |
Koha item type |
Books |
998 ## - LOCAL CONTROL INFORMATION (RLIN) |
Cataloger's name |
mona.romia |
Cataloging process |
M |
First Date, FD (RLIN) |
20220109 |
015 ## - NATIONAL BIBLIOGRAPHY NUMBER |
National bibliography number |
GBB759158 |
655 #7 - INDEX TERM--GENRE/FORM |
Genre/form data or focus term |
History. |
Source of term |
fast |
Authority record control number or standard number |
(OCoLC)fst01411628 |
800 1# - SERIES ADDED ENTRY--PERSONAL NAME |
Personal name |
Martin, Robert C. |
Title of a work |
Robert C. Martin series. |
906 ## - LOCAL DATA ELEMENT F, LDF (RLIN) |
a |
7 |
b |
cbc |
c |
copycat |
d |
2 |
e |
epcn |
f |
20 |
g |
y-gencatlg |