
In this lecture I'll introduce myself and explain a little about how I became involved in software engineering and architecture. I'll then explain who this course is intended for and what cool stuff you'll learn when you take this course.
In this lecture I'll tell you what software architecture is, with some common definitions. I'll also explain how architecture differs from requirements and design.
In this lecture I'll explain about the software crisis and why we need software architecture. I'll then talk about stakeholder communication, risk/cost management and reuse.
In this lecture I'll talk about the fundamental essence of software architecture. This will include stakeholders, viewpoints, quality, abstraction and patterns.
In this lecture I'll explain all aspects of the architectural process, such as requirements analysis, knowledge gathering, creating and assessing designs, justifying decisions and adapting existing architectures.
In this lecture I'll talk about architectural descriptions, including viewpoints, frameworks and architectural description languages.
In this lecture I'll explain Krutchtens 4+1 architectural view model and what UML diagrams we can use to represent each view.
In this lecture I'll show you some example top level UML diagrams used by the 4+1 view model and what each component part means.
In this lecture I'll use a screencast to show you how to draw UML diagrams using a great free and open source tool.
In this lecture I'll tell you all about architectural patterns, what they are and why we should use them. I'll also run though some popular ones explaining when they should and shouldn't be used.
In this lecture I'll talk briefly about international standards and their benefits to software development. I'll explain one of the most significant international architectural standards and why we should use it.
In this lecture I'll explain what to do when we have a lack of architecture, or when the design and code diverges from the intended architecture.
In this lecture I'll talk you through the personal risks of becoming a software architect yourself and how to mitigate them to protect yourself and your work.
In this lecture I'll tell you how to find the best sources of further information and in a format which is most suitable for your needs.
In this lecture I'll finish off by saying thank you for being a great student!
20 years ago I graduated with a first class software engineering degree. Since then I've worked at every stage of the software lifecycle but I've always had a particular interest in software architecture. If you have a software related background and you're interested in becoming a software architect, this course is definitely for you.
Erik N says: "The course provided a good overview of the topic for which I am interested, namely, software architecture. The content gave me some good ideas, encouragement and new avenues to explore."
Sami S says: "Good starting point to Software Architecture, at least to me who has 20+ years of software developer background."
Jose V says: "It's a good introductory course, very digestible and serves the purpose."
Balint E says: "It's a good basic introduction to the field."
In this course I'll teach you what software architecture is and why we need it. I'll also explain the architecture design process and introduce you to useful patterns, frameworks and standards, which you can refer to and reuse.
Becoming a software architect can be both fulfilling and lucrative, so I want to help you achieve this. I now know exactly what's involve and that's what I'll teach you in this course.
Even if you're unsure about software architecture and whether you want to become involved in it, I even have a lecture dedicated to allaying any fears you may have.
This course consists mainly of video, slides and some fun quizzes. It should only take you a couple of hours to complete, but it'll be a couple of hours very well spent.
Thanks for taking an interest in this software architecture course and I look forward to you being my student.