國立虎尾科技大學 |

Principles of package design = creating reusable software components /

Record Type:	Language materials, printed : Monograph/item
Title/Author:	Principles of package design/ by Matthias Noback.
Reminder of title:	creating reusable software components /
Author:	Noback, Matthias.
Published:	Berkeley, CA :Apress : : 2018.,
Description:	xix, 275 p. :ill., digital ; : 24 cm.;
Contained By:	Springer eBooks
Subject:	Software engineering. -
Online resource:	https://doi.org/10.1007/978-1-4842-4119-6
ISBN:	9781484241196

Principles of package design = creating reusable software components /
Noback, Matthias.

Principles of package designcreating reusable software components /[electronic resource] :by Matthias Noback. - Berkeley, CA :Apress :2018. - xix, 275 p. :ill., digital ;24 cm.

Part 1: Class Design -- Chapter 1: The Single Responsibility Principle -- Chapter 2: The Open/Closed Principle -- Chapter 3: The Liskov Substitution Principle -- Chapter 4: The Interface Segregation Principle -- Chapter 5: The Dependency Inversion Principle -- Part 2: Package Design -- Chapter 6: The Release/Reuse Equivalence Principle -- Chapter 7: The Common Reuse Principle -- Chapter 8: The Common Closure Principle -- Chapter 9: The Acyclic Dependencies Principle -- Chapter 10: The Stable Dependencies Principle -- Chapter 11: The Stable Abstractions Principle -- Chapter 12: Conclusion -- Appendix A: The Full Page Class.

Apply design principles to your classes, preparing them for reuse. You will use package design principles to create packages that are just right in terms of cohesion and coupling, and are user- and maintainer-friendly at the same time. The first part of this book walks you through the five SOLID principles that will help you improve the design of your classes. The second part introduces you to the best practices of package design, and covers both package cohesion principles and package coupling principles. Cohesion principles show you which classes should be put together in a package, when to split packages, and if a combination of classes may be considered a "package" in the first place. Package coupling principles help you choose the right dependencies and prevent wrong directions in the dependency graph of your packages. What You'll Learn: Apply the SOLID principles of class design Determine if classes belong in the same package Know whether it is safe for packages to depend on each other.

ISBN: 9781484241196

Standard No.: 10.1007/978-1-4842-4119-6doiSubjects--Topical Terms:

562952
Software engineering.

LC Class. No.: QA76.758

Dewey Class. No.: 004

Principles of package design = creating reusable software components /
LDR:02626nam a2200325 a 4500 001 930312
003 DE-He213
005 20181114201709.0
006 m d
007 cr nn 008maaau
008 190627s2018 cau s 0 eng d
020 $a 9781484241196 $q (electronic bk.)
020 $a 9781484241189 $q (paper)
024 7 $a 10.1007/978-1-4842-4119-6 $2 doi
035 $a 978-1-4842-4119-6
040 $a GP $c GP
041 0 $a eng
050 4 $a QA76.758
072 7 $a UM $2 bicssc
072 7 $a COM051000 $2 bisacsh
072 7 $a UM $2 thema
082 0 4 $a 004 $2 23
090 $a QA76.758 $b .N744 2018
100 1 $a Noback, Matthias. $3 1211417
245 1 0 $a Principles of package design $h [electronic resource] : $b creating reusable software components / $c by Matthias Noback.
260 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2018.
300 $a xix, 275 p. : $b ill., digital ; $c 24 cm.
505 0 $a Part 1: Class Design -- Chapter 1: The Single Responsibility Principle -- Chapter 2: The Open/Closed Principle -- Chapter 3: The Liskov Substitution Principle -- Chapter 4: The Interface Segregation Principle -- Chapter 5: The Dependency Inversion Principle -- Part 2: Package Design -- Chapter 6: The Release/Reuse Equivalence Principle -- Chapter 7: The Common Reuse Principle -- Chapter 8: The Common Closure Principle -- Chapter 9: The Acyclic Dependencies Principle -- Chapter 10: The Stable Dependencies Principle -- Chapter 11: The Stable Abstractions Principle -- Chapter 12: Conclusion -- Appendix A: The Full Page Class.
520 $a Apply design principles to your classes, preparing them for reuse. You will use package design principles to create packages that are just right in terms of cohesion and coupling, and are user- and maintainer-friendly at the same time. The first part of this book walks you through the five SOLID principles that will help you improve the design of your classes. The second part introduces you to the best practices of package design, and covers both package cohesion principles and package coupling principles. Cohesion principles show you which classes should be put together in a package, when to split packages, and if a combination of classes may be considered a "package" in the first place. Package coupling principles help you choose the right dependencies and prevent wrong directions in the dependency graph of your packages. What You'll Learn: Apply the SOLID principles of class design Determine if classes belong in the same package Know whether it is safe for packages to depend on each other.
650 0 $a Software engineering. $3 562952
650 0 $a Object-oriented programming (Computer science) $v Congresses. $3 527913
650 1 4 $a Programming Techniques. $3 669781
650 2 4 $a Programming Languages, Compilers, Interpreters. $3 669782
650 2 4 $a Software Engineering. $3 669632
650 2 4 $a Web Development. $3 1114136
650 2 4 $a Open Source. $3 1113081
710 2 $a SpringerLink (Online service) $3 593884
773 0 $t Springer eBooks
856 4 0 $u https://doi.org/10.1007/978-1-4842-4119-6
950 $a Professional and Applied Computing (Springer-12059)