About this course: The way that software components — subroutines, classes, functions, etc. — are arranged, and the interactions between them, is called architecture. In this course you will study the ways these architectures are represented, both in UML and other visual tools. We will introduce the most common architectures, their qualities, and tradeoffs. We will talk about how architectures are evaluated, what makes a good architecture, and an architecture can be improved. We'll also talk about how the architecture touches on the process of software development. In the Capstone Project you will document a Java-based Android application with UML diagrams and analyze evaluate the application’s architecture using the Architecture Tradeoff Analysis Method (ATAM). After completing this course, you will be able to: • Compare and contrast the components, connections, protocols, topologies, constraints, tradeoffs, and variations of different types of architectural styles used in the design of applications and systems (e.g., main program and subroutine, object-oriented, interpreters, pipes and filters, database centric, event-based). • Describe the properties of layered and n-tier architectures. • Create UML ipackage, component, and deployment diagrams to express the architectural structure of a system. • Explain the behaviour of a system using UML activity diagrams. • Document a multi-application system with a layered architecture.
Created by: University of Alberta
Taught by: Kenny Wong, Associate Professor
Computing Science, Faculty of Science
| Basic Info | Course 3 of 4 in the Software Design and Architecture Specialization |
| Level | Intermediate |
| Commitment | Four weeks of study, 5 – 8 hours/week |
| Language | English |
| How To Pass | Pass all graded assignments to complete the course. |
| User Ratings |
Syllabus
WEEK 1
UML Architecture Diagrams
In this module you will learn about software architecture. You will learn why architecture is important, what perspectives need to be considered, and how to communicate architecture using UML.
6 videos, 7 readings
- Reading: Meet Your Presenter – Sam Jeffery
- Reading: Meet Your Facilitator – Christopher Djuric
- Reading: Software Architecture – Course Notes
- Reading: Software Architecture Glossary
- Reading: Discussion: Introduce Yourself
- Video: 3.1.2 – Kruchten's 4 + 1 Model View
- Video: 3.1.3 – UML Component Diagram
- Video: 3.1.4 – UML Package Diagram
- Video: 3.1.5 – UML Deployment Diagram
- Video: 3.1.6 – UML Activity Diagram
- Reading: Capstone Assignment 3.1 - Draw a Component Diagram (Solution)
- Reading: Capstone Assignment 3.2 - Draw a Deployment Diagram (Solution)
Graded: Capstone Assignment 3.1 – Draw a Component Diagram
Graded: Capstone Assignment 3.2 – Draw a Deployment Diagram
Graded: Module 1 Review
WEEK 2
Architectural Styles
Software comes in all shapes and sizes. The architecture you choose will affect every part of your software, from its security and efficiency, to its modularity and maintainability. In this module we will examine the different architectures that you have to choose from to shape your software.
9 videos, 3 readings
- Video: 3.2.2 – Main Program and Subroutine
- Video: 3.2.3 – Databases
- Video: 3.2.4 – Layered Systems
- Video: 3.2.5 – Client Server n-Tier
- Video: 3.2.6 – Interpreters
- Reading: State Transition Systems
- Video: 3.2.7 – Pipes and Filters
- Video: 3.2.8 – Event Based
- Reading: Publish–Subscribe
- Video: 3.2.9 – Process Control
- Reading: Discussions: Architectural Styles
Graded: Module 2 Review
WEEK 3
Architecture in Practice
The architecture is the most fundamental aspect of software. You will learn how development teams describe architectures, plan successful architectures based on quality attributes, and evaluate the resulting architecture. You will also learn how architecture relates to organization structure and even product planning!
4 videos
- Video: 3.3.2 – Analyzing and Evaluating an Architecture
- Video: 3.3.3 – Relationship to Organizational Structure
- Video: 3.3.4 – Product Lines and Product Families
Graded: Module 3 Review
WEEK 4
Capstone Challenge
Now, in the final module of the course, you will evaluate the proposed architecture to extend the functionality of the example Android code base.
4 readings
- Reading: Capstone Assignment 3.3 - Analyze and Evaluate an Architecture (Solution)
- Reading: Discussion: Last Word – Software Architecture
- Reading: Acknowledgements
- Reading: Credits
Graded: Capstone Assignment 3.3 – Analyze and Evaluate an Architecture
Graded: Final Exam
FAQs
How It Works
Coursework
Each course is like an interactive textbook, featuring pre-recorded videos, quizzes and projects.
Help from Your Peers
Connect with thousands of other learners and debate ideas, discuss course material, and get help mastering concepts.
Certificates
Earn official recognition for your work, and share your success with friends, colleagues, and employers.
Creators
University of Alberta
UAlberta is considered among the world’s leading public research- and teaching-intensive universities. As one of Canada’s top universities, we’re known for excellence across the humanities, sciences, creative arts, business, engineering and health sciences.
Pricing
| Purchase Course | |
|---|---|
| Access to course materials | Available |
| Access to graded materials | Available |
| Receive a final grade | Available |
| Earn a shareable Course Certificate | Available |
Ratings and Reviews
very good!
It's introduction of software architecture, mainly focus on basic concepts, lack of practical examples.
a
w
e
s
o
m
e
c
o
u
r
s
e
Coursera provides universal access to the world’s best education,
partnering with top universities and organizations to offer courses online.
© 2018 Coursera Inc. All rights reserved.
PA
Excellent course, really good explanation and interesting evaluation methodology