Chevron Left
소프트웨어 아키텍처(으)로 돌아가기

앨버타 대학교의 소프트웨어 아키텍처 학습자 리뷰 및 피드백

4.4
320개의 평가
56개의 리뷰

강좌 소개

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....

최상위 리뷰

CS

Dec 24, 2019

This is a excellent course for Software architects, addressing all key areas needed in the field. Good content, definitely recommend this course for anyone aspiring to be a Software architect.

MM

Apr 05, 2020

I have learnt many concepts such as various diagrams.\n\nQuality attributes and how to evaluate architecture.\n\nIt is outstanding course.

필터링 기준:

소프트웨어 아키텍처의 56개 리뷰 중 51~56

교육 기관: Nguyen K T

Sep 11, 2019

very useful

교육 기관: Alexey P

Mar 19, 2019

I think the course is much worse than Object-Oriented Design and Design Patterns. Especially ATAM part. It's too abstract, too hard for understanding and requires too much time. The benefits is not clear. And it seems that this process is rarely used in practice. Wasted time.

교육 기관: JOSKO R

Mar 27, 2020

.

교육 기관: Tulay M

Mar 03, 2020

Someone reading a text in a fast, monotone way for the entire course does not fit my learning style. The only thing I liked was the peer review assignments. That's what I learned the most: from other's mistakes and grading questions.

교육 기관: Norbert M

Feb 12, 2020

T

교육 기관: Reza A

Dec 29, 2017

Very boring.