Overview:

Software architecture doesn’t exist in a vacuum and is driven by functional requirements, non-functional requirements, constraints, and principles. We take a look at all of them to understand the impact that they have and the trade-offs that need to be made when defining architectures. Architecture definition is the focus of the course and is reinforced by a case study.

The course is interactive with a combination of presentation, group discussion, and group work. Throughout the course, you’ll solidify everything you learn by defining the architecture for a small software system through a series of exercises focused around a case study.

We will see, what impact do functional requirements, non-functional requirements, constraints, and principles have on software architecture?  How do you take a system vision through to software architecture?