In This Chapter
Stepping through a system’s design
Considering design priorities
Breaking your system into subsystems
Sorting logical and physical system diagrams
Getting componentized
Deploying hardware configurations
Showing off artifacts
So you know what you want to build, and you’ve got some requirements for your system, but there is just one little problem: Your system is spread out across several different computers and you must build pieces of software to run on each platform. You have to figure out a design for this complex system by thinking about what software goes on which piece of hardware. But there are so many choices. Ah, for the good old days when life was simple and our systems were applications that ran on a single user’s computer.
When you build today’s complex (dare we say enterprise-wide?) systems, you need a way to step back from the details and develop an overall strategy for how your system and its software application(s) are put together. There comes a time when you have to look at the big picture and describe how your system works. This chapter describes the steps for designing large systems and describe the UML diagrams you use to define your system. We help you get a handle on describing the relationships between the hardware and the software components that make up your system.