Software Architecture for Developers

Designing software given a vague set of requirements and a blank sheet of paper is a good skill to have, although not many people get to do this on a daily basis. However, with agile methods encouraging collective ownership of the code, it's really important that everybody on the team understands the big picture. And in order to do this, you need to understand why you've arrived at the design that you have. In a nutshell, everybody on the team needs to be a software architect.

"Software Architecture for Developers" is a two-day training course about pragmatic software architecture, designed by software architects that code. It will show you what "just enough" up front design is, how it can be applied to your software projects and how to communicate the big picture through a collection of simple effective sketches. Aimed at software developers, it fills the gap between software development and high-level architecture that probably seems a little "enterprisey" for most developers. You'll find it useful if any of the following scenarios sound familiar:

• I'm not sure what software architecture is about and how it's any different from design.
• I don't understand why we need "software architecture".
• My manager has told me that I'm the software architect on our new project, but I'm not sure what that actually means.
• I want to get involved in designing software but I'm not sure what I should learn.
• I've been given some requirements and asked to design some software, but I'm not sure where to start.
• I need to make some major enhancements to my system, but I'm not sure where to start.
• I've been asked to write a software architecture document but I'm not sure what to include in it.
• I'm not sure who to talk to in my organisation about how best to integrate what we're building.
• I understand what software architecture is all about, but I'm not sure how to tackle it on my project.
• My project seems like a chaotic mess; everybody is doing their own thing and there's no shared vision. Help!

Join us if you want to understand software architecture, technical leadership and the balance with agility.

    of 261