CSSE 532
Software Architecture
Fall 2007
Location:
Time: Thursdays 5:30 - 8:10
Instructor Overview Textbooks
& Readings Grading Class Format Schedule
Academic
Integrity
Instructor
|
|
|
|
Office: Engr 507 |
|
|
Phone: (206) 296-5512 |
|
|
Office Hours: By
appointment |
|
|
Over the past decade, software architecture has
become a critical part of the development of large and complex software
systems, and an important research area in the software engineering community.
Architecture description languages and formal modeling notations have been
proposed to model and analyze structural and behavioral properties of software
systems in terms of components, connectors, and their interactions. Such a
focus on architectural aspects of the system has shown significant return on
investment in terms of improving the quality of the software system in a
cost-effective way.
This course focuses on familiarizing the students
with principles of software architecture, connectors, architectural description
languages, architectural styles, architectural evolution and product-line
software architecture, architectural analysis, and quality issues. We will also
discuss architecture-level activities in the context of the broader software
development life cycle. We furthermore visit the latest trends in
software architecture practice.
· Required
Book
· Software Architecture: Foundations, Theory, and
Practice,
* This
book will be provided to you in a course pack.
In addition to the textbooks, there will be
supplementary readings and papers provided throughout the quarter. Please
refer to the schedule for details.
|
Exam
1 |
25% |
|
Exam
2 |
20% |
|
Homework 1 Basic Concepts |
3% |
|
Homework 2: High
level architecture |
6% |
|
Homework 3: Quality Assessment |
8% |
|
Homework 4: Detailed Modeling and Analysis |
8% |
|
Project Proposal |
5% |
|
Project Progress Report |
5% |
|
Project Presentation |
15% |
|
Class Discussion |
5% |
You are expected to read assigned materials in
advance of the relevant class (papers and textbook). There will be two exams
which test basic concepts as well as your ability to apply the material in new
problems. You are encouraged to participate in various class activities, ask
questions, discuss and test your ideas. We will hold a 15 min discussion on the
papers each week in class and you will receive class participation credit for
participating.
(Subject to change!)
|
Week |
Topic |
|
Assignments and Exams |
|
1 9/27/06 |
Course Introduction Overview & Basic
Concepts |
|
|
|
2 10/4/06 |
Basic Concepts Project Discussion |
P. Kruchten. Mommy,
Where Do Software Architectures Come from? 1st International Workshop on
Architectures for Software Systems, |
HW1 due |
|
3 10/11/06 |
Designing Architectures,
|
Dashofy et. al. An Infrastructure for the Rapid Development
of XML-based Architecture Description Languages. In Proc. of the 24th
International Conference on Software Engineering (ICSE2002.) |
Project Proposals (Due 10/15/07 – 6:00pm) HW2 assigned |
|
4 10/18/06 |
Connectors, Modeling |
P. Kruchten.
Architectural Blueprints—The “4+1” View Model of Software Architecture, IEEE
Software 12 (6), November 1995, pp. 42-50. |
HW2 due |
|
5 10/25/06 |
Implementation
Deployment |
Malek
et. al. "Providing Middleware-Level Facilities to Support
Architecture-Based Development of Software Systems in Pervasive
Environments." In proceedings of the 4th International Workshop on
Middleware for Pervasive and Ad-Hoc Computing (MPAC 2006), Melbourne, Australia,
November 2006 Representational
State Transfer (REST) – from |
Midterm Exam (take
home) |
|
6 11/1/06 |
Analysis, Non-functional
Properties Quality and
Dependability |
R. Roshandel, N.
Medvidovic, L. Golubchik, A Bayesian Model for Predicting Reliability of
Software Systems at the Architectural Level, in proceedings of 3rd International Conference on Quality of
Software Architectures (QoSA 2007), Boston, MA, July 2007. |
Project Progress Reports
due (Nov 4) |
|
7 11/8/06 |
Quality (cont.), |
|
|
|
8 11/15/06 |
Evolution and Product
Families, Domain Specific Software
Engineering |
S. A. Hendrickson, A.
van der Hoek, Modeling Product Line Architectures through Change Sets and
Relationships. In Proc. of the 29th International Conference on Software
Engineering (ICSE 2007). |
HW3 due |
|
9 11/22/06 |
Happy Thanksgiving! |
||
|
10 11/29/06 |
Standards Peoples, Roles, Teams |
Taylor 16,17 Matthew R. McBride, The Software
Architect, Communications of the ACM, Volume 50 , Issue 5 (May 2007). o Team 1 Presentation (Bokone, Weeden) |
HW4 due |
|
11 12/6/06 |
|
o Team 2 Presentation (Batta, Sebastian, Singari) o Team 3 Presentation (Bhalla) o Team 4 Presentation (Bui, Meadows) o Team 5 Presentation (Mercan) |
Project Presentations |
|
-- 12/13/06 |
Final Exam Take home (Due 12/13/2007) |
||
Plagiarism is the unacknowledged use of the work or
intellectual property of other persons, published or unpublished, presented as
one’s own work. All students are expected to work on all individual assignments
independently. Collaboration on individual assignments is considered cheating
and will be penalized accordingly. Other examples of behavior that is not
tolerated in this class include copying all or part of someone else’s work and
submitting it as your own, sharing your assignment solution with other students
in the class, consulting with another student during an exam, and copying text
from published literature without proper attribution. If you have questions
about what is allowed, please discuss it with the instructor. All students are
responsible for reading and following the Seattle University Academic Honesty
Policy. Students who violate University standards of academic honesty are
subject to disciplinary sanctions, including failure in the course and
suspension from the University.