Enduring Ideas in the Realm of Software
In any significant software project, complexity happens. The question is what are you going to do about it? In Software Architect Bootcamp (2nd Edition), Ralphael Malveau and Thomas J. Mowbray, Ph.D. write about five ways of dealing with software complexity. Why Complexity Happens Malveau and Mowbray write the following: Many software projects fail to manage …
When you zoom in or zoom out of a software system, what do you call the different levels of the software? Design levels are a key issue for architecture because they define the problems and forces that the architecture needs to solve. In Software Architect Bootcamp (2nd Edition), Ralphael Malveau and Thomas J. Mowbray, Ph.D. …
Why do we need software architects? In the book Software Architect Bootcamp (2nd Edition), Raphael Malveau and Thomas J. Mowbray, Ph.D. write about three key reasons why we need software architects. Separate Complex Concerns Malvaeau and Mowbray write the following: First, architects need the ability to separate complex concerns, in particular to separate concerns about …
I use scenarios all the time for anything from designing a user experience to evaluating architecture. Scenario is an overloaded term though. There’s lots of types of scenarios. If you know the types of scenarios, you can use the right one for the job. For example, exception scenarios are useful for assessing robustness. Misuse cases …
Having a frame of reference for how to think about security helps you cut through information overload. While working on our patterns & practices Improving Web Application Security: Threats and Countermeasures book, one of our favorite mantras was “Secure your network, host and application!” We learned this by talking to our infrastructure group at …
