Informatics 221: Software Architecture

Winter Quarter 2013

Course Code 37400

Last update: March 6, 2013

 

Instructor:

Richard N. Taylor

Email:

(taylor [at] ics [dot] uci [dot] edu)
To ensure a response to your email, please include "Informatics 221" in the subject line and send your email from a UCI account.

Office hours:

After class, or by email appointment

Lectures:

Monday and Wednesday 2:00-3:20 DBH 1300

Web site: http://www.ics.uci.edu/~taylor/classes/221/syllabusWQ13.html

What's New?

Description - Textbook and Readings - Schedule - Grading - Policies


Description

Catalog description: Study of the concepts, representation techniques, development methods, and tools for architecture-centric software engineering. Topics include domain-specific software architectures, architectural styles, architecture description languages, software connectors, and dynamism in architectures.


Textbook (REQUIRED)

Software Architecture: Foundations, Theory, and Practice. Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. Copyright © 2010 John Wiley & Sons, Inc. (ISBN-13: 978-0470-16774-8)

 


Schedule

The schedule is subject to change

Week Date Topic Readings Homework
1

J

A

N

U

A

R

Y

7 Mo Introduction Chapter 1  
9 We Chapter 2 & (Perry and Wolf, 1992)  
2 14 Mo

Basic Concepts and Introduction to Design

"...perhaps the reason for such slow progress in the development and evolution of software systems is that we have trained carpenters and contractors, but no architects." Perry&Wolf, 1992

Chapters 3 & 4  
16 We  
3 21 Mo MLK Holiday --- No class Chapters 4 & 5  
23 We Design Homework/Project assigned (via email)
4 28 Mo Connectors, Modeling & Visualization Chapters 6 & 7  
30 We  
5

F

E

B

R

U

A

R

Y

4 Mo Applied Architectures and Styles Chapter 11  
6 We  
6 11 Mo Software architectures and intellectual property specification    
13 We Parts 1 & 2 of project due
7 18 Mo President's Day --- No class    
20 We Adaptation Chapter 14  
8 25 Mo REST --> CREST --> COAST    
27 We Guest lecturer: Eric Dashofy Eric's slides

 

9

M

A

R

C

H

4 Mo Domain-specific software engineering Chapter 15  
6 We     Parts 3, 4, and 5 of project due
10 11 Mo Demos & discussion of selected student assignments    
13 We In-class exam    
     

Grading and Evaluations

Grading.
There are 3 elements to your grade: a final exam, homework/project, and class attendance and participation.

Summary of Assessment:

Homework/Project 70%
Final exam 20%
Class attendance and participation 10%

No grades of incomplete (I) will be given for this course. 

 


Policies

Course Evalutions. The online evaluation window for winter quarter will run from TBA through TBA.

Cheating. The UCI academic honesty policy applies. Consequences of cheating in this class: a letter in your UCI file, and the course grade is lowered, most likely to F. Material that is copied from books or Web pages needs to be quoted and the source must be given. If you plagarize, you run the severe risk of failing the class, in a most disgraceful manner.

Disabilities. Any student who feels he or she may need an accommodation based on the impact of a disability, religious observance (or anything else) should contact me privately to discuss his or her specific needs. If appropriate, contact the Disability Services Center as soon as possible.

Use of Social Media during Class Sessions. Sadly, many students have adopted the practice of using instant messaging, Facebook, or other social media technologies inside the classroom. This is, at a minimum, disruptive to other students. The practice is therefore prohibited in 221. I reserve the right to totally forbid use of the Internet and cellular communications —even the use of any laptop— in class if it turns out that students violate the prohibition. "Let's not go there."



(C) University of California, 2013.