Software Architecture Courses - Industrial
Course Names Industrial Year offered Price Objective Topics
Software Architecture Bredemeyer Consulting 2006 4-day workshop is This is a workshop, and small teams work on • Introduce architectural patterns, principles and mechanisms.
Bloomington, IN 47401 US$2250.00 per student. creating a draft architecture using the Visual • Learning how to create, validate and update an architecture.
Tel: (812) 335-1653 Architecting Process. We follow the iterative • Focusing on the role and responsibilities of the architect and
architecting process, and weave concepts and positioning the architecture role within the organization.
architecting techniques into the lectures between
work sessions. The lecture topics are driven by
the concerns that are being addressed at that
stage of the architecting process. This makes it a
"non-traditional" format, but it is one that works
well as it allows us to work end-to-end through the
creation of a draft architecture.
Architect Community Builder Bredemeyer Consulting 2006 Contact for pricing A forum for bringing together architects with a • enhance the personal effectiveness of the participating architects
Bloomington, IN 47401 focus on action. We design Architect Community • develop a common foundation of architecture concepts and processes
Tel: (812) 335-1653 Builder™ programs for a community of practicing across the organization
architects, with the goal of developing the integrity • enhance reuse across the organization, by creating strong
of the community and each of the individual relationships among the technical leaders, identifying opportunities to
architect's skills. reuse components and architectural patterns and mechanisms,
adopting common process and notation to make sharing easier, etc.
Designing Software Bredemeyer Consulting 2006 4-day class is $2000 per This class covers the concepts and concerns
Architectures Bloomington, IN 47401 student. central to software architecture. With that • Express architectural principles
Tel: (812) 335-1653 groundwork laid, the majority of the time is • Capture architectural patterns using UML
focused on the architecting process. Each • Create structural and behavioral views of the architecture using UML
architecting activity is motivated with stories. The models
concepts, techniques and models for each phase • Graphically model components (using UML) to
of requirements, structuring and validation are understand/communicate their structure and behavior
explained and demonstrated, then practiced in • Design and document components and their interfaces
small teams. Action Guides provide handy • Capture architectural requirements using Use Cases for run-time
references as teams fill out templates or create requirements and Test Cases for qualities
graphical models using UML. • Perform architecture analyses and validate the architecture
What it takes to be Great The Bredemeyer Consulting 2006 3-day open enrollment In the workshop, we will develop a model of the • Architecting pitfalls and critical success factors
Role of the Architect Bloomington, IN 47401 class is $1650 per student role, responsibilities and skills of an architect. We • The architecting process
Tel: (812) 335-1653 share stories from our real-world experience to • The role of the Architect
help you understand the role, responsibilities and • Architect as consultant
skills of an architect. Throughout the workshop we • Interviewing Architecture Stakeholders
help you to build skills with experiential exercises • Analyzing and synthesizing input
in areas that, as engineers, we typically do not get • Facilitation and the art of leading team processes
much opportunity to hone. The technical aspects • Leading Architecture Reviews
of the architect role, such as system and • Taking criticism
requirements modeling are introduced in this • Architect as leader
workshop, but covered in depth in the Software • Stories and leadership
Architecture Workshop. • How to create and sell an Architectural Vision
• Architect as strategist
• Context Maps
• Technology Roadmaps
Strategic Architecture Vision Bredemeyer Consulting 2006 1-day workshop is US The workshop is a working session designed to • about the role and importance of architectural vision
Bloomington, IN 47401 $5000 plus the instructor's create a good draft of your architectural vision • how to create a compelling architectural vision, and
Tel: (812) 335-1653 travel expenses. and a plan for validating and communicating the • how to gain buy-in among the various communities within the
vision. Lecture segments are purposely kept to a organization.
Page 1 of 13
Software Architecture Courses - Industrial
Architectural Requirements for Bredemeyer Consulting 2006 The cost for the 2-day The course helps business analysts become • What is software architecture?
Business Analysts Bloomington, IN 47401 class is US$1,200 per stronger and more effective partners for • Why is software architecture important?
Tel: (812) 335-1653 student. Lunch and architects, providing useful input to the • How is architecture created?
snacks will be provided. architecting process. This means that systems • What is the role of the architect? What is the role of the business
will be better specified, better architectures will be analyst?
created, and ultimately more useful capability will • What is an architectural requirement?
be delivered to the business. • Use cases as input to architecting.
• Specifying system qualities as input to architecting.
Software Architecture Bredemeyer Consulting 2006 1-day class is US$600 per This class provides an overview of our approach • architecture (what), answering the question: "what is software
Overview Bloomington, IN 47401 student. Lunch and to architecture, architecting and architects. It is architecture?" This section deals with architecture definitions and
Tel: (812) 335-1653 snacks will be provided. not a "beginner" class, but rather a fast-paced distinctions, benefits, key concerns, and primary techniques, including
treatment of the concepts and techniques that are an introduction to architectural patterns.
important particularly to those who partner with • architecting (how), that is the process of creating an architecture. We
architects, but also to architects. provide an overview of our Visual Architecting Process.
• architects (who), focusing on the role and responsibilities of the
architect and positioning the architect role within the organization.
• We also address architecture motivation (why), architecture context
(where) and architecture timing (when).
Software Architecture Primer Bredemeyer Consulting 2006 The cost for the 1/2-day This class provides an introduction to software When you have completed the class, you will be able to answer:
for Managers Bloomington, IN 47401 class is US$350 per architecture oriented to managers. It identifies * What is enterprise architecture? What is software architecture?
Tel: (812) 335-1653 student. Lunch and what software architecture is, and describes the * What is UML? How does it relate to architecture?
snacks will be provided. Visual Architecting Process that architects and * Why is architecture a critical organizational competency?
lead engineers are learning in the companion * How, broadly speaking, is architecture created and sustained?
Software Architecture Workshop. It also * Who creates architecture? What are the competencies of an
describes the architect role and the competencies architect?
of a good architect.
Architecting Enterprise iCMG 2006 Rs. 23,500/ per This 3 days workshop is focused on enterprise The key focus areas include understanding of multiple EAFs (Enterprise
Software 13317"C" Thomasville participant for standard software architecture as a specialty. Architecture Frameworks), Component based product line, Model
Circle first time attendee Driven Architecture (MDA) and Service-Oriented Architecture (SOA)
Software Architecture iCMG 2006 Contact for pricing. • Arch Software notations, representations and • Arch Software notations, representations and specifications
13317"C" Thomasville specifications • Development process and intelligence gathering techniques
Circle • Development process and intelligence gathering • Architectural Tools
Tampa -33617 techniques • Antipatterns for Architecture
Florida • Architectural Tools • SunConnect Architecture and MDA
• Antipatterns for Architecture • Application Integration Scenario
• SunConnect Architecture and MDA • Web SOA
• Application Integration Scenario • QoS in Architecture
• Web SOA
• QoS in Architecture
System Architecture Course Millinium Services P.O. 2006 Contact for pricing This four-day course examines the basics of the • Requirements
Box 653, Lincroft, NJ software architecture task in a development • Performance/Capacity
07738 project. It emphasizes the responsibilities of the • Operations Administration & Maintenance
architect both establishing an appropriate • Error Recovery/Availability
architecture, and in managing the architecture
throughout the development process.
Software Architecture Software Engineering 2006 U.S. This course introduces the basic concepts of • the architecture business cycle: what influences software architects
Principles & Practices Institute Course Fee: software architecture. A software architecture is and software architecture
Carnegie Mellon Industry: $1320 an abstract view of a software system distinct • definition and overview of software architecture
University Government: $1055 from the details of implementation, algorithms, • understanding and achieving quality attributes
Pittsburgh, PA 15213- Academic: $1055 and data representation. Architecture is an • documenting software architecture
3890 International increasingly crucial part of a software • evaluating software architecture
Phone: 412 / 268-7388 Course Fee: organization's business strategy. Software • architecture reuse
FAX: 412 / 268-7401 $1980 architectures can • emerging methods—such as architecture reconstruction and the Cost
Benefit Analysis Method (CBAM)—and software architecture of the
Page 2 of 13
Software Architecture Courses - Industrial
Documenting Software Software Engineering 2006 U.S. This two-day course provides in-depth coverage • the basic principles of sound technical documentation
Architectures Institute Course Fee: of effective software architecture documentation • a stakeholder- and view-based approach to documenting software
Carnegie Mellon Industry: $1320 practices that meet the needs of the entire architectures
University Government: $1055 architecture stakeholder community. This course • which views are available for documenting an architecture
Pittsburgh, PA 15213- Academic: $1055 presents the information in the context of • how to choose the set of views that will be most valuable to the
3890 International prevailing prescriptive models, including the architecture's community of stakeholders
Phone: 412 / 268-7388 Course Fee: Rational Unified Process (RUP), the Siemens • the information needed to document a view
FAX: 412 / 268-7401 $1980 Four Views software approach, the IEEE 1471- • how to use formal and informal notations (including the Unified
2000 standard, and the Unified Modeling Modeling Language [UML]) to represent elements and relations in a
Language (UML). The course is based on the view
book Documenting Software Architectures: Views • how to document a software interface and software behavior
and Beyond . • the information needed to document information that applies across
Software Architecture Design Software Engineering 2006 U.S. This two-day course provides in-depth coverage • life-cycle view of architecture design and analysis methods
and Analysis Institute Course Fee: of the concepts needed to effectively design and • the Quality Attribute Workshop, a method for eliciting critical quality
Carnegie Mellon Industry: $1320 analyze a software architecture. The essential attributes, such as availability, performance, security, interoperability,
University Government: $1055 considerations for defining any architecture are and modifiability
Pittsburgh, PA 15213- Academic: $1055 carefully examined and then illustrated through • the Attribute-Driven Design (ADD) method, a method for designing a
3890 International application of the Attribute-Driven Design (ADD) software architecture
Phone: 412 / 268-7388 Course Fee: software architecture design method. This course • the Architecture Tradeoff Analysis Method (ATAM), a method for
FAX: 412 / 268-7401 $1980 also explores architecture analysis in depth and evaluating a software architecture based on a set of attribute-specific
introduces the Quality Attribute Workshop (QAW) measures of the system such as performance, availability, modifiability,
and the Architecture Tradeoff Analysis MethodSM and security
(ATAMSM). Through multiple exercises,
participants study an application of these
methods and get a chance to apply them to
ATAM Evaluator Training Software Engineering 2006 U.S. The course is intended to mimic an evaluation of • overview of the ATAM
Institute Course Fee: a fictitious but realistic system. Participants play • software architectures and quality attributes
Carnegie Mellon Industry: $2520 roles as stakeholders and evaluation team • Phase I activities of the ATAM
University Government: $2015 members during the various exercises. The two • video presentation of fictitious system's business goals and
Pittsburgh, PA 15213- Academic: $2015 days of the course are modeled after the two architecture
3890 International phases of the ATAM. • preparation for and activities of Phase II of the ATAM
Phone: 412 / 268-7388 Course Fee: • critique and discussion of participants' Phase I findings and final
FAX: 412 / 268-7401 $3780 ATAM presentation
ATAM Leader Training Software Engineering 2006 U.S. This two-day course focuses on the social and • facilitation
Institute Course Fee: leadership skills needed to successfully lead an • the ATAM and facilitation
Carnegie Mellon Industry: $2640 architecture evaluation using the ATAM. The • basic facilitation skills
University Government: $2120 course presents ATAM facilitation requirements • group dynamics
Pittsburgh, PA 15213- Academic: $2120 and challenges in the context of general • scenario role playing
3890 International facilitation and consulting principles. Through
Phone: 412 / 268-7388 Course Fee: exercises, participants practice being an ATAM
FAX: 412 / 268-7401 $3960 lead evaluator.
Model-Based Engineering with Software Engineering 2006 U.S. This two-day course provides an excellent • Overview of SAE AADL standard effort
SAE AADL Institute Course Fee: opportunity to get a jump start on the use of the • Model-based engineering with AADL
Carnegie Mellon Industry: $1200 SAE Architecture Analysis & Design Language • Key elements of the SAE AADL standard
University Government: $960 (AADL), a new international standard for • An illustrated overview of the modeling concepts
Pittsburgh, PA 15213- Academic: $960 embedded computer systems (SAE AS5506) on • Pattern-based analysis of an avionics system
3890 International your projects. AADL supports predictable • Case studies of AADL in use
Phone: 412 / 268-7388 Course Fee: engineering through model-based analysis and • Tool-based multi-fidelity analysis of AADL models
FAX: 412 / 268-7401 $1800 integration of real-time applications on their target • An XML-based tool environment strategy
platforms. Fields of application include avionics
and space applications, automotive electronics,
ground based control systems, and industrial
process control equipment.
Page 3 of 13
Software Architecture Courses - Industrial
Introduction to Software Software Productivity 2006 $995.00 for two days • Definitions of software architecture • Architectural representation
Architecture, its Principles and Center Inc. • Benefits of software architecture • Desirable qualities of a software architecture
Methods Suite 460 - 1122 • Software architecture in the development cycle. • The role of architecture in managing risk
Mainlaind Street, • Software architecture representations, multiple • Common architectural frameworks.
Vancouver, BC V6B 5L1 views, use of UML. • Object-oriented approaches.
1-877-548-1948 • Software architecture artifacts • The impact of commercial off-the-shelf products (COTS) and
• A typical architectural iteration standards.
• How and where architectural design fits in an iterative software
development lifecycle, such as the Rational Unified Process.
Documenting Software Xpdian (Pty) Ltd 2006 Contact for pricing. This course teaches participants to decide on • The role of Architecture - A discussion on architecture and the role of
Architectures Using the UML P.O. Box 11501, Wierda what documentation to document in order to design.
Park South, 0057 create sound software architecture. • Uses of Architecture Documentation - The purpose of architecture
documentation and how it is used in the organization.
• Documentation techniques and notation - A discussion on notation
techniques and styles
• Architectural views -The different views of architecture, understanding
the different views, choosing the views to set up, setting up the different
views, understanding stakeholder documentation needs and the method
of performing architecture trade- off analysis
• Interfaces - The definition and specification of interfaces, standard
organization of for documenting interfaces, and understanding who are
the stakeholders of interface documentation
• Documenting behaviour - A discussion on where to document
behaviour, why we document behaviour and what behaviour to
• Rules for sound documentation - A discussion focused on best
practices in setting up software architecture documentation
• Example notations - Example views on documenting software
architectures. Notations discussed are the Rational Unified Process and
the Standard UML
Page 4 of 13
Software Architecture Courses - Industrial
Page 5 of 13
Software Architecture Courses - Industrial
Page 6 of 13
Software Architecture Courses - Industrial
Page 7 of 13
Software Architecture Courses - Industrial
Page 8 of 13
Survey of Software
Course Names University Price Objective Topics Web Address
Master course on The Center for Software Technology at Ultrecht Fall 2006 Introduction to software architecture, Software • Architectural patterns http://www.cs.uu.nl/wiki/Swa/WebHome
Software Architecture University requirements, Architectural patterns, patterns of • Patterns of enterprise application architecture
enterprise application architecture, Component • Component software
software, Design by contract, Enterprise • Design by contract
integration patterns, Describing and evaluating • Enterprise integration patterns
software architectures. • Describing and evaluating software
Software Architecture University of Oxford - Software Engineering £1300 We offer five different courses on the theme of • Addressing programs as data http://www.softeng.ox.ac.uk/courses/architecture.html
Programme software architecture, addressing: programs as • Meta-languages for information interchange
data; meta-languages for information interchange; • Service-oriented architectures
service-oriented architectures; relational database • Relational database Technology
technology; and network performance modeling. • Network performance modeling
Software Architecture University of Toronto Fall 2006 This course is an introduction to the development • Development of system-level architectures www.cs.toronto.edu/DCS/Undergrad/Courses/current.html
and Design of system-level architectures and class-level • Class-level object-oriented designs
object-oriented designs for software systems. • Special emphasis on study of architecture and
There is a special emphasis on the study of design patterns
architecture and design patterns: the core of • Core of solutions to commonly occurring
solutions to commonly occurring design design problems
problems; representations of design/architecture • Representations of design/architecture
(with emphasis on the use of UML as a class- • Architectural assessment
level design notation); architectural assessment; • Product Lines
product lines; architecture extraction; and • Architecture Extraction
refactoring. There is no major project, but there is • Refactoring
a series of smaller design and architecture
exercises requiring some programming. A
knowledge of UML as used for requirements
analysis and a working knowledge of Java are
Software Architecture University of Alberta Fall 2001 This course will discuss different software • Software architecture styles www.cs.ualberta.ca/~stroulia/661/Fall2001/
architecture styles, their properties and the types • Properties and types of problems
of problems for which they are most appropriate, • Formalisms for specifying a software
it will examine different formalisms for specifying architecture
a software architecture, and it will explore the role • Role of software architecture throughout the
of software architecture throughout the software development life cycle.
development life cycle.
Software Architecture Schulich School of Engineering/University of Fall 2005 The student will have a working knowledge of • Working knowledge of software architecture www2.enel.ucalgary.ca/People/Pfahl/course-seng443-fall2005.pdf
Calgary software architecture, Have a good understanding • Understanding of several design patterns.
of several design patterns, Be aware of • Framework models
framework models, Be aware of component • Component based software development.
based software development, Be aware of reuse • Reuse methods and techniques.
methods and techniques, Be aware of software • Software product line architectures
product-line architectures, Be aware of • Architecture eval models
architecture eval models.
Software Architecture THE UNIVERSITY of EDINBURGH 2006/2007 The aim of this module is to introduce you to key • Key concepts in the design and implementation www.drps.ed.ac.uk/06-07/course.php?code=P01492
concepts in the design and implementation of of large scale, long lived software systems.
large scale, long lived software systems. The • Practical experience of working in a team
course gives students some practical experience • Common threats to long-term projects
of working in a team faced with planning a long- • High-level design and architectural patterns
term project for developing a large software
system. It helps them to be aware of common
threats to such projects and how to address
them. It also gives students a repertoire of high-
level design and architectural patterns and guides
students in applying them.
Page 9 of 13
Survey of Software
Software Architecture The University of Texas at Dallas 2006/2008 Introduction to software design with emphasis on • Intro to software design with emphasis on www.utdallas.edu/student/catalog/ugcurrent/ugprograms/se.html#4352
and Design architectural design. Models of software architectural design.
architecture. Architecture styles and patterns, • Models of software architecture
including explicit, event-driven, client-server, and • Architecture styles and patterns
middleware architectures. Decomposition and • Decomposition and composition of architectural
composition of architectural components and components and interactions.
interactions. Use of non-functional requirements • Non-functional requirements for tradeoff
for tradeoff analysis. Component based software analysis.
development, deployment and management. • Component based software development,
Prerequisites: SE 3306, CS/SE 3354 or consent deployment and management.
Intro to Software The University of Minnesota Fall 2005 The Software and Systems Architecture • Software and systems architecture processes www-users.itlabs.umn.edu/classes/Fall-2005/seng5861/index.php?page=syllabus
Architecture Processes, including how they fit into the larger • Larger software engineering process
Software Engineering process; a description of • Description of architecture documentation
Architecture Documentation including • Representation of quality attributes
Representation and Quality Attributes; and • Architecture evaluation methods
Architecture Evaluation Methods.
Software Architecture The University of South Australia Fall 2006 Definitions of web based applications and models • Web application servers www.unisanet.unisa.edu.au/courses/course.asp?Course=COMP4029
and Software of web based applications. Review of the web • Issues of locality distribution
Engineering for Web- infrastructure. Taxonomy of the web based • Execution
based Applications software infrastructure; tiers and abstraction • Segmentation
layers. Web Application Servers. Issues of locality • Overview of application servers
distribution, execution segmentation, interface • Enterprise java beans, java servers, java server
granularity, network performance variability and pages
the wide range of user capabilities and user • Basics of software as it relates to web based
requirements for the same application as they applications
affect application development. Overview of
application services, enterprise java beans, java
servers, java server pages, Java API for XML
processing and ASP.net. Basics of software as it
relates to web based applications.
Software Architecture University of Verona 2005/2006 Website not in English. Website not in English. www.scienze.univr.it/fol/main?ent=oi&cs=4&id=17504&lang=en
Software Architecture University of Leiden 2000/2001 As the software component of systems becomes • Software architecture styles http://homepages.cwi.nl/~marcello/sa.html
larger and more complex, the need to understand • Examine different formalisms for specifying a
them at a higher level of abstraction becomes software architecture
more important. The software architecture of a • The role of software architecture throughout the
computing system describes the overall structure software development cycle.
of the system in terms of the software
components, the externaly visible properties of
those components, and the relationships among
them. For large software system like traffic
management systems, process control systems,
and command-and-control systems, the choice of
a software architecture is becoming more crucial
within the overall development process. This
course will discuss different software architecture
styles, their properties and the types of problems
for which they are most appropriate, it will
examine different formalisms for specifying a
software architecture, and it will explore the role
of software architecture throughout the software
development life cycle.
Page 10 of 13
Survey of Software
Architecture of Software The University of New South Wales, Sydney Principal architectural issues associated with the • Principal architectural issues associated with the /www.handbook.unsw.edu.au/undergraduate/courses/2006/COMP9117.html
Systems design and construction of large scale software design and construction of large scale software
systems. Study and evaluation of several well- systems.
known and frequently used architectural styles, • Study and evaluation of architectural styles,
patterns and frameworks. Study of pipes and patterns and frameworks.
filters, layered systems, distributed object- • Study of pipes and filters, layered systems,
oriented systems, component-based systems, distributed object-oriented systems, component
etc. The course will also examine the practical based systems.
applicability of architecture research, specifically • Examine the practical applicability of
its relationship to the work in software reuse and architecture research.
component interoperability of platforms such as
J2EE, Microsoft, NET and CORBA. Case studies
and exercises will be used to illustrate the
Software Architecture & The University of Victoria Summer 2006 Introduction to analysis and design of software • Intro to analysis and design of software www.csc.uvic.ca/courses/summer%202006/seng/seng271.html
Systems architectures with UML (Unified Modeling architectures with UML.
Language) and their subsequent synthesis within • Architecture description languages
component frameworks. Topics include • Modeling techniques and tools.
architecture description languages, modeling • Model driven code engineering
techniques and tools, model driven code • Scalable software architectures.
engineering, scalable software architectures, • Component-based software development
component-based software development, • Libraries
interfaces, libraries, event-driven programming, • Event-driven programming
middleware and integration testing. • Middleware and Integration testing
Software Architecture McGill School of Computer Science Fall 2006 In this course, you will acquire the concepts and • Understand, analyze and maintain and improve www.cs.mcgill.ca/~martin/teaching/comp529-fall-2006/
and Analysis techniques that will enable you to understand, the architecture of large software systems.
analyze, maintain, and improve the architecture of • Software engineering research
large software systems. The course will also • Software modularity
touch on some key issues of software
engineering research related to the question of
Software Design and University of Essex 2006/2007 The aim of this module is to introduce the • Software design and architectural motifs, www2.essex.ac.uk/courses/result.asp?coursecode=CC439&level=G&period=AU&ye
Architecture students to a broad range of software design and principles governing them. arofcourse=06
architectural motifs, to the principles governing • Modeling techniques
them, and to modeling techniques.
Software Architecture London Metropolitan University 2005/2006 To provide an understanding of techniques used • Understanding of techniques used in the design www.learning.north.londonmet.ac.uk/im257.html
in the design and implementation of large and implementation of large programs.
programs. Relate the high principles of program • Relate the high principles of program
construction to examples otherwise difficult to construction .
relate to the small programming assignments that
comprise the majority of the undergraduate
Software Architecture California State University, Sacramento Fall 2006 This course is to introduce the following materials • Concepts, principles and activities for software www.gaia.ecs.csus.edu/~zhangc/235info.htm
in varying detail:� Concepts, principles, and architecture design.
activities for software architecture design. • Engineering discipline and guidance for software
Engineering discipline and guidance for software architecture design.
architecture design.� Languages for software • Languages for software architecture
architecture specification and documentation.� specification and documentation.
Techniques, methods, tools for analyzing, and • Techniques, methods, tools for analyzing and
evaluating software architecture.� Reuse of evaluating software architecture.
software architecture design, Innovations and • Reuse of software architecture design.
advances in software architecture.� Students will
learn how to recognize and describe major
architecture styles in existing software systems,
make well-reasoned choices among architecture
design alternatives, understand and document
actual software architecture designs and
specifications, and create, analyze, and evaluate
software architecture designs.
Page 11 of 13
Survey of Software
Software Architecture & Bilkent University Fall 2006 This course teaches the basic concepts, methods • Basic concepts, methods and techniques for www.catalog.bilkent.edu.tr/current/course/c11411.html
Design and techniques for designing software designing software architectures.
architectures. The topics include: rationale for • Rationale for software architecture design.
software architecture design, modeling software • Modeling software architecture design.
architecture design, architectural styles/patterns, • Architectural styles/patterns.
architectural requirements analysis, comparison • Architectural requirements analysis.
and evaluation of architecture design methods, • Comparison and evaluation of architecture
synthesis-based software architecture design, design methods.
software product-line architectures, domain • Synthesis-based software architecture design.
modeling, domain engineering and application • Software product-line architectures.
engineering, software architecture • Domain modeling, engineering and application
implementation, evaluating software architecture engineering.
designs. • Software architecture implementation.
• Evaluating software architecture design.
Software Architecture DePaul School of Computer Science, Spring 2006 This course will address the critical task of • Critical task of choosing appropriate software www.cti.depaul.edu/courses/syllabus.asp?course=SE-480-
Telecommunications and Information Systems choosing appropriate software architectures for architectures for complex software systems. 910&q=3&y=2006&id=273
complex software systems. The architecture of a • Architectural issues.
system plays a critical role in helping a • Architectural patterns.
development organization meet its business • Architectural design.
goals. Proper consideration of architectural
issues, including the use of suitable architectural
patterns, can make a system easier to build,
maintain, and extend. A system's architectural
design is concerned with describing its
decomposition into software elements, the
interfaces of those elements, and the
collaborations among them.
Software Architecture University of Western Ontario Spring 2006 This course focuses on “software architectures”. • Focuses on Software Architectures. www.csd.uwo.ca/courses/CS549b_Congese/
A software architecture is an abstract • Design and implementation-level issues
representation of a software system, filtering out • System structure
what is traditionally considered design- and • Inter-relationships
implementation-level issues (such as: algorithm,
design patterns, data representation and coding)
and highlighting such aspects as the system
structure, inter-relationships and interaction
among these structures, and other “run-time”
properties of the system. Whereas software
requirements generally state the “what” of a
system, a software architecture states the “how”
of a system. It sets bounds for lower-level design
of a system and gives a technical context to new
Software Architecture: A Carnegie Mellon West Fall 2005 Understand and apply core software architecture • Understand and apply core software http://west.cmu.edu/prospective_students/professional_development_center/enginee
Managerial Perspective concepts and vocabulary. Deliver better software architecture concepts and vocabulary. ring?category=Development%20Management&courseid=1697312
in a more cost-effective way through principled • Deliver better software in a more cost-effective
architectural design. Identify and address key way through principled architectural design.
architectural issues at each stage of the • Identify and address key architectural issues at
software/product development lifecycle. Institute each stage of the software/product development
and oversee cost-effective software architecture lifecycle.
design reviews. Apply value-based architecting • Institute and oversee cost-effective software
techniques to evaluate architectural decisions in architecture design reviews.
the context of economic goals and constraints. • Apply value-based architecting techniques to
Understand principles for the design and evaluate architectural decisions in the context of
management of product line architectures. economic goals and constraints.
• Understand principles for the design and
management of product line architectures.
Page 12 of 13
Survey of Software
Software Architecture Indian Institute of Technology Kanpur Fall 2006 Complex software systems require abstraction • Software system structures (architectural styles) http://www.cse.iitk.ac.in/acad/courses3.html#cs654
and analysis at an architectural level of • Techniques for designing and implementing
abstraction. In this course we study, typical these structures.
software system structures (architectural styles), • Models for characterizing and reasoning about
techniques for designing and implementing these architectures.
structures, models for characterizing and • Tools and architectural modeling.
reasoning about architectures, and tools • Role of architecture in software engineering.
architectural modeling. Role of architecture in • Enterprise architectures.
Software engineering; Enterprise Architectures, • Zachman’s Framework
Zachman's Framework; Architectural Styles, • Design patterns
Design Patterns; Architecture Description • Architecture description language
Languages; Product-line architectures; • Product-line architectures
Component based development • Component based development
Software Architecture University of Strathclyde, Glasgow Fall 2006 To enable students to understand the issues • Issues associated with large-scale software http://www.cis.strath.ac.uk/teaching/ug/syllabus/440.html
associated with large-scale software architectures, frameworks, patterns
architectures, frameworks, patterns and the • Development and construction of component-
development and construction of component- based systems.
Software Architecture University of Southern California 2002 This course will expose you to the concepts, • requirements, http://sunset.usc.edu/research/software_architecture/index.html
principles, and state-of- the-art methods in • design (including object-oriented design and
software architectures, including domain-specific related notations, such as UML),
software architectures (DSSA), architectural • implementation.
styles, architecture description languages (ADL), • practical applicability of architecture
software connectors, dynamism in architectures,
and architecture-based testing and analysis. In
the process of studying these concepts, we will
make explicit the boundaries of the field and
discuss its relationship to other areas of software
engineering, specifically requirements, design
(including object-oriented design and related
notations, such as UML), and implementation.
The course will also examine the practical
applicability of architecture research, specifically
its relationship to the work in software reuse and
component interoperability platforms (such as
CORBA, Enterprise JavaBeans, and
COM/DCOM). Homework assignments and two
exams will be given to assess your understanding
of important concepts, methods, languages, and
tools. A project will give you an opportunity to
study an aspect of architectures in more depth
and “push the envelope” of architecture research
Software Architectures Institute of Software Systems 2005 • recognize major architectural styles in existing 1. What is Software Architecture? http://sunset.usc.edu/contact/index.html
software systems, 2. Revisiting Object-Oriented Analysis, Design,
• describe an architecture accurately, and Implementation
• generate reasonable architectural alternatives 3. Design Patterns
for a problem and choose among them, 4. Pipes&Filters Architectures
• evaluate commercial tools and software 5. Event-based Architectures
components from an architectural perspective, 6. Layered Architectures
• use object-oriented models and tools to expedite 7. Frameworks
such tasks. 8. Component Architectures
1. Software Components
2. Client-Side Component Architecture
3. Foundation for Server-Side Component
4. Server-Side Component Architecture
Page 13 of 13