7.3. Establishing Architecture
Up to this point, we have identified, at least at a high level, some of the classes that compose our system. Classes, however, don't exist in a vacuum but must reside in packages. Therefore, any industrial-strength application must consider the packages that will contain the many different classes. It certainly isn't a good idea to place all classes in the same package, even early on, because doing so promotes bad practices. While Chapter 10 is devoted exclusively to architecture, we discuss it briefly in this chapter due to the significant role that architecture plays in the overall development lifecycle.
Each of our boundary, entity, and control classes has quite specific purposes. As such, it makes perfect sense ...
Get Java™ Design: Objects, UML, and Process now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
