How to Think like a Software Architect
Money Magazine identified Software Architect as its #1”Best Job” to hold in the U.S. in 2015 (http://money.cnn.com/gallery/pf/2015/01/27/best-jobs-2015), and its practitioners earned half again more than either of the top two finishers. If you have prior exposure to an object oriented programming language and have ever wondered what a Software Architect actually “does” for a living, this is the course for you. We tackle complex “back office” problems like the entire Student Registration System at a typical College Such problems should be especially interesting to those who desire to understand the boundaries of software components in large organizations and how they interoperate to support important use cases (ex: Student enrolls in a Course).
Software Architects deeply “think about”, discuss and develop solutions for problems like these using the Object Oriented paradigm, in which the basic abstractions defined in the problem description are identified, fleshed out and manipulated. On truly large projects, it is only after both the system analysis and design are complete that the programmers get called in to implement and deploy the resulting solution.
This is exactly the relationship between the architect and the craftsmen (plumbers, electricians and carpenters) during the building of a house. By necessity, they think about the house in very different ways. Here you will learn how to think like a Software Architect.
- Not Interested